Source Listing Facility › Maintain Synchronized Processing › COBOL and PL/I Symbolic Version Processing

COBOL and PL/I Symbolic Version Processing

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

• If an exact match is found and there are no later versions, CA InterTest for CICS automatically selects that version of the listing and displays it.
• If a match is not found, CA InterTest for CICS displays the Symbolic Version List from which you can either:
  • Select the appropriate symbolic file and program version
  • Ignore symbolic processing for the program

    The Symbolic Version List screen might also explain the cause of the mismatch. The following are possible causes for the mismatch:

  • There was no matching program listing for the load module.
  • A matching listing was found for the load module, but it is not the most recently compiled version. You can select the matching listing at this point or new copy the load module so that it matches the most recently compiled version and then retry the LIST or CNTL command.

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

• If an exact match is found, CA InterTest for CICS automatically selects and displays it.
• If a match is not found, CA InterTest for CICS displays the Symbolic Version List from which you can choose a non-matching program listing version or ignore symbolic processing for the program.

Once a symbolic file is selected for a program, CA InterTest for CICS continues to use the selected file and program version. If a new version of the program is compiled and linked and you have one or more breakpoints set by Statement # or Offset, then you should deactivate monitoring for the program, new copy the program , and then reset any Statement # or Offset breakpoints. This will insure that your breakpoints are in sync with the new program version. Alternatively, if you do not have any breakpoints set or only breakpoints set by paragraph-name, you can execute a CNTL=NEW,PROG= command or ITST Option 2.1 NEWCOPY, which will reset monitoring for the new program version.

For PL/I Programs

Successful date and time matching for PL/I modules requires that PL/I programs be compiled using the default TSTAMP=YES option.