Chapter Contents
Previous
Next
Running and Debugging SAS/C Programs in the CICS Environment

Running SAS/C Programs under CICS

Before you can run SAS/C applications under CICS, you must perform the following steps. Step 1 involves the SAS/C Command Language Translator and Compiler; the remaining steps are required by CICS, regardless of the application language.

  1. Before you can run your program under CICS, you must have successfully translated, compiled, and linked your program using the SAS/C Translator and Compiler. Preprocessing, Compiling, and Linking explains this process in detail.

  2. The load module resulting from Step 1 must be stored in a load library that is contained in the CICS load module library concatenation (DDname DFHRPL). Ask your CICS system administrator for information on how to store the load library at your site.

  3. To identify the program to CICS, you must define the program name (load module name) in the processing program table (PPT). Remember that SAS/C load modules (programs) should be specified as assembler language programs, not as C programs. You must also define in the PPT (with the appropriate language specified) any other programs that will be dynamically loaded by the SAS/C application program. You must also define any basic mapping support (BMS) maps.

  4. Define the initiating CICS transaction code in the program control table (PCT). You must specify on the PCT entry the name of the module to be loaded and executed when the transaction is initiated.

  5. If your program reads or writes to any files, you must define those files in the file control table (FCT).

  6. Just as you defined FCT entries in the previous step, you must define any extrapartition or intrapartition destinations in the destination control table (DCT).

  7. You must define the BMS maps (if any) used by your application. For CICS, this usually involves the following steps:

    1. Code the maps with macros.

    2. Assemble the maps to create a physical map.

    3. Create a logical map.

Note:    In addition to these steps, for C programs on pre-ESA versions of CICS, you must process the symbolic assembly output using the DSECT2C utility. Terminal Control and Basic Mapping Support describes how to use this utility.  [cautionend]

After you have defined everything, you can initiate the program as you would any other CICS application. The usual method is to enter the transaction identifier in the upper left corner of the screen, and then to press ENTER.


Chapter Contents
Previous
Next
Top of Page

Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.