Previous Topic: Maintain Synchronized ProcessingNext Topic: Assembler Symbolic Version Processing


COBOL and PL/I Symbolic Version Processing

When you use LIST=program or CNTL=ON, PROG=program to request a COBOL or PL/I program that has no previously declared breakpoints or monitoring options set, CA InterTest for CICS matches the most recently compiled symbolic file date and time to the load module date and time.

During Automatic Breakpoint processing, if a program has no previously selected symbolic file, CA InterTest for CICS matches the load module's date and time to a symbolic file.

Once a symbolic file is selected for a program, CA InterTest for CICS continues to use the selected file and bypasses subsequent date and time matching until all declared breakpoints and monitoring options are removed from the program, or until a CNTL=NEW,PROG=program command is executed. The New Copy option is also available from the Program Monitoring menu, ITST Option 2.1.

For PL/I Programs

Successful date and time matching for PL/I modules requires PL/I programs be post‑compiled using the following:

Note: If PL/I programs were compiled with IN25SYMP from CA InterTest for CICS 5.3 or 5.4 and the program contains arrays, the program needs to be recompiled with the IN25SYMP from the 6.0 release to display PL1 array variables during a program breakpoint.