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:
- 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.
- 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.
- 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.
- 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 *
SYMFIL=(PARTSYM, MNUFSYM, INTYSYM, MKTGSYM, SALESYM, DISTSYM, X (col 72)
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.