Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Non-CPSM Dynamic Transaction Routing Considerations


Code Debug CICS cannot influence dynamic routing if the CICSPlex SM (CPSM) dynamic routing program is not used. In such situations, a Code Debug session must be initiated in each region where the program to be tested may be routed.

The following steps simplify the task of initiating Code Debug sessions in multiple AORs. The examples assume that the TOR has transactions named XPE1, XPE2, XPE3, etc. These transactions correspond to transaction XPED in each AOR. The actual transaction names may vary. The examples use the Code Debug demonstration program CWDEMCB2 and transaction XCB2 as well as demonstration program CWDEMASM and transaction XASM.

Example 1. Manually Start Code Debug in Multiple AORs

  1. Sign on to the TOR, then enter XPE1 to start Code Debug CICS in region AOR1. The Primary Menu is displayed. The system automatically establishes an abend trap for all abends that occur on the terminal (in region AOR1).
  2. Enter the CAPTURE ON command to create a script for future use. For additional information, see command description CAPTURE (CAP).
  3. Type =2.L in the COMMAND field and CWDEMCB2 in the MODULE field.
  4. Set breakpoints, a program trace, or protection rules for the program in region AOR1.
  5. Enter the CAPTURE OFF MYSCRIPT command.
  6. Press Clear, or type =X and press Enter, to transfer to the Exit Session screen (X).
  7. Press Enter on the Exit Session screen (X) to leave the Code Debug CICS session active and return to a blank CICS screen in the TOR.
  8. Enter XPE2 SCRIPT=MYSCRIPT to start Code Debug CICS in region AOR2 and include the script that was captured in AOR1. Repeat Step 6 and Step 7.

    Important

    SCRIPT= may be abbreviated S=.

  9. Repeat Step 8 as required for additional AORs.
  10. Enter XCB2 to run the test transaction.
  11.  If the program in either region encounters abends or breakpoints, Code Debug CICS automatically takes control and displays either the View Break/Abend screen (2.1) or the Source Listing screen (2.L). At this point, the system allows single-stepping, resuming, and other available functions.
  1. When finished debugging, end all of the Code Debug CICS sessions.

Example 2. Manually Start Code Debug in Multiple AORs

Important

This example requires a script such as MYSCRIPT that was created in Example 1. MYSCRIPT should contain a LOAD for program CWDEMCB2 and any other commands issued in Step 4 of Example 1.

  1. Sign on to the TOR, then enter XSTA S=MYSCRIPT.

    To review the results of script processing, enter XPE1 (or equivalent) then enter the HELP SCRIPT command.

  2. Enter XCB2 to run the test transaction.
  1. If the program in either region encounters abends or breakpoints, Code Debug CICS automatically takes control and displays either the View Break/Abend screen (2.1) or the Source Listing screen (2.L). At this point, the system allows single-stepping, resuming, and other available functions.
  2. When finished debugging, end all of the Code Debug CICS sessions.

Example 3. Manually Start Code Debug in Multiple AORs

Important

This example requires a script named BEFORE0. This script should contain a BEFORE 0 command to set a breakpoint at the first executable statement.

  1. Sign on to the TOR, then enter XSTA CWDEMASM S=BEFORE0.
  1. Enter XASM to run the test transaction.
  1. Continue with Step 2 through Step 4 as in Example 2.

    Important

    A script such as BEFORE0 may be defined by the Code Debug global parameter SCRIPT_FACILITY_SYSTEM_SCRIPT_AUTOPLAY to automatically run for every new Code Debug session.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*