What steps are required to allow me to define multiple symbolic files (PROTSYM files) to CA InterTest for CICS?

Document ID : KB000013221
Last Modified Date : 14/02/2018
Show Technical Document Details

One of the major advantages of using CA InterTest for CICS to debug programs is the ability to step through the code of an application program while the program is executing.  Many sites may have a need to store program source for different applications in a PROTSYM file unique to that specific application.  CA InterTest for CICS does offer the capability of defining multiple symbolic files (PROTSYM files) that are exclusive to each application that execute in a single CICS region.  These are the steps  necessary to accomplish this task.    


What are the steps necessary in order to define multiple CA InterTest for CICS symbolic files to a single CICS region in order to separate the programs that make up different applications? 

CA InterTest for CICS executing in a CICS region.

Assume that there is an application being developed for all phases of creating and selling a product by a specific company.  The application is divided up into six categories and each category requires an individual set of programs, each contained in a specific symbolic file.  A file is needed for Parts, Manufacturing, Inventory, Marketing, Sales, and Distribution.  These six files are in addition to the standard PROTSYM and NDVRSYM definitions.          

There are 4 requirements to define multiple symbolic files to CA InterTest for CICS:

  1. Define each file using VSAM and intialize them using IN25UTIL which is found in your cai.CAVHLOAD.  Reference the CAVHPROT member found in your cai.CAVHJCL to define and initialize a symbolic file for use with InterTest.
  2. Define an FCT entry for each file using the definition for the PROTSYM file distributed with InterTest as a model.  For example PARTSYM, MNUFSYM, INTYSYM, MKTGSYM, SALESYM, DISTSYM.  
  3. Add a DD statement for each file to your CICS region JCL using the FCT entries as the DDNAMEs to point to the files defined in step 1.
  4. Finally define the files to InterTest using the SYMFIL keyword of IN25OPTS.  Reassemble and link your IN25OPTS.

Assuming you are making no further changes to your IN25OPTS file, the input to the assembly would look something like this: 

//SYSIN          DD *

The SYMFIL keyord serves a dual purpose.  It will define each file to InterTest and also specifies the search order used by InterTest to find a specific program; PARTSYM first, MNUFSYM next, etc..  Be sure to start the SYMFIL keyword in column 16 and if more than one line is needed, end the first line with a comma and a non blank character in column 72 as shown above.  




Additional Information:

Additional information on defining multiple files as well as the IN25OPTS keywords in general can be found in the