Indirect Command Examples

Breakpoint Activities › Indirect Commands › Indirect Command Examples

Indirect Command Examples

The following examples explain how to use indirect commands to correct the errors in the CA InterTest for CICS demo program COBDEMO.

To prevent the ASRA problem caused by the invalid decimal arithmetic data value assigned to the COBOL data‑item TASKNUM:

Using Source Listing Option # 12 with a U line command, set an unconditional breakpoint at statement number 500.
Specify 10 as the indirect command statement number that you want to execute at the breakpoint.

Using the Source Listing Option # 11, access the indirect commands facility. Then, enter the indirect commands on the Indirect Commands screen, as shown next.

CA InterTest MONITOR COMMAND BUILDER COBDEMO INDIRECT COMMANDS 24 Term ID (or .ANY or .NO): X001 Delete ALL: NO LINE COMMAND ------------------------------------------------------------------------------ 00010 /* INITIALIZE TASKNUM */ 00020 MOVE 1 TO TASKNUM 00030 EXIT 1 Help 2 3 End 4 5 6 7 Backward 8 Forward 9 Top 10 Bottom 11 12 CAIN1261 Indirect commands added.

Note: Setting TASKNUM to 1 alters the demo results. The clear key must be used to complete the termination of the demo when the "You have completed the sample CA InterTest for CICS test session" screen appears.

To avoid the storage violation that occurs in COBDEMO:

Using Source Listing option 12 with a U line command, set an unconditional breakpoint at statement number 978
Specify 50 as the indirect command statement number that you want to execute at the breakpoint

Using the Source Listing Option # 11, access the indirect commands facility, and then add the following commands.

CA InterTest MONITOR COMMAND BUILDER COBDEMO INDIRECT COMMANDS 24 Term ID (or .ANY or .NO): X001 Delete ALL: NO ----------------------------------------------------------------------- 00010 /* INITIALIZE TASKNUM */ 00020 MOVE 1 TO TASKNUM 00030 EXIT 00040 * 00050 /* CIRCUMVENT STORAGE VIOLATION */ 00060 GOTO 'SENDMAP00' 1 Help 2 3 End 4 5 6 7 Backward 8 Forward 9 Top 10 Bottom 11 12 CAIN1261 Indirect commands added.

To perform the code that was bypassed at statement 1369 at another location where it will not cause a storage violation:

Using the Source Listing Option # 12 with a U line command, set an unconditional breakpoint at statement number 974
Specify 80 as the indirect command statement number that you want to execute at the breakpoint

Using the Source Listing Option # 11, access the indirect commands facility, then add the following commands.

CA InterTest MONITOR COMMAND BUILDER COBDEMO INDIRECT COMMANDS 24 Term ID (or .ANY or .NO): X001 Delete ALL: NO ---------------------------------------------------------------------------- LINE COMMAND 00010 /* INITIALIZE TASKNUM */ 00020 MOVE 0 TO TASKNUM 00030 EXIT 00040 * 00050 /* CIRCUMVENT STORAGE VIOLATION */ 00060 GOTO 'SENDMAP00' 00070 * 00080 /* INSERT MOVE AT A SAFE LOCATION */ 00090 IF NEWDATA > ZEROES THEN MOVE NEWDATA TO STGAREA1 00100 EXIT 1 Help 2 3 End 4 5 6 7 Backward 8 Forward 9 Top 10 Bottom 11 12 CAIN1261 Indirect commands added.

To debug a program that is invoked by multiple transaction IDs and take breakpoints only when a particular transaction ID is specified:
- Using the Source Listing Option # 10 with a U line command, set an unconditional breakpoint at the beginning of the procedure division.
- Specify the indirect command statement number that you want to execute at the breakpoint.
- Specify the FROM Terminal, where the breakpoint should take effect, as .ANY.
  Now, all other program breakpoints that are set may be taken only when the conditions specified by the indirect command 10 are true.

CA InterTest MONITOR COMMAND BUILDER COBDEMO INDIRECT COMMANDS 24 Term ID (or .ANY or .NO): X001 Delete ALL: NO ---------------------------------------------------------------------------- LINE COMMAND 00010 IF EIBTRNID = ‘DEC2’ THEN BREAK 00020 RUN 00030 EXIT 1 Help 2 3 End 4 5 6 7 Backward 8 Forward 9 Top 10 Bottom 11 12 CAIN1261 Indirect commands added.