PL/I Basic Demo Session › Maintain Synchronized Processing

Maintain Synchronized Processing

Before you begin testing, you should be aware that when CA InterTest for CICS searches the symbolic files for the PL/I programs you specify for testing, it tries to match the date and time in the symbolic file to that of the load module. If a match cannot be found, one of the following is displayed:

• A Symbolic Version List
• A warning message

This feature lets you maintain synchronized processing at all times by enabling you to select the correct symbolic version of the program that you want to test.

Note: For a complete description of this feature, see the User Guide.

Symbolic Version Processing

When you request a 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.

• If an exact match is found, CA InterTest for CICS automatically selects and displays the program. However, if an exact match is found and a more recently compiled version of the program is in a PROTSYM file, CA InterTest displays the symbolic version list from which you can do the following:
  • Select the matching listing and debug the program.
  • Do not select the matching listing and cancel monitoring. Then new copy the latest version of the program into your CICS region and select the latest program version for monitoring.
• If a match is not found, CA InterTest for CICS displays the Symbolic Version List from which you can:
  • Select the appropriate symbolic file.
  • Ignore symbolic processing for the program.

  The Symbolic Version List screen also explains the cause of the mismatch.

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.

• If an exact match is found, CA InterTest for CICS automatically selects and displays the program.
• If a match is not found, CA InterTest for CICS automatically selects the first symbolic file that contains the program and displays it with a warning message on the first Source Listing Breakpoint screen indicating the mismatch. This is shown on the following screen.

  CA InterTest for CICS Release 9.1.00 ‑ SYMBOLIC VERSION LIST                            
                                                                                  
     Program = PLIDEMO     Load Module Date/Time =  11/12/2000 09:02:03           
                                                                                  
     File ID     Date       Time    Language     Comments                         
   _ PROTSYM  11/12/2000  09.52.23  PLI        LATEST VERSION                     
   _ PROTDMO  08/31/2000  14.12.15  PLI 
  .
  .
  . 
           S ‑ Select which Symbolic file to use                                   
   ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
   PFKEYS:  1 Help      2           3 No file   4           5           6         
            7           8           9          10          11          12         
   CAIN8000 The latest Symbolic version does not match the current load module
  

Note: 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 for the program, or until a NEWCOPY command is executed. This can be done from ITST Option 2.1 by selecting the Option for New copy, or by typing the following command from CICS:

CNTL=NEW,PROG=progname