Code Indirect Commands

PL/I Advanced Monitoring Features › Set the Code Counting/Coverage Option › INTC--Indirect Commands › Code Indirect Commands

Code Indirect Commands

CA InterTest for CICS provides an Indirect Commands facility for coding the statements. You can access it from the Source Listing or from the ITST menus.

To access the Indirect Commands facility from the Source Listing facility, type ICMDS in the command line or 11 in the Option # field and press Enter.

Note: Tab to the More: + field and press Enter to view labels of Options 6 to 15. Notice Option 11 is Indirect commands, and Option 12 is Breakpoint options.

CA InterTest for CICS Release 9.1.00 - PROTSYM FILE ABEND DETECTED BREAKPOINT COMMAND ===> ICMDS Program= PLIDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ TASKNUM | ?00000. ---------+--------------------------------------------------------------------- _ 636.1 CONTINUE_TASK: _ 637.1 MAPNUM = '00'; A ==>.1 1 TASKNUM = TASKNUM + 1; . . .

To access the Indirect Commands facility from the menus, access the Program Monitoring menu (fastpath is ITST 2.1), and select the Commands option. Detailed steps follow.

Select option 2 Monitoring on the Primary Option Menu. The Monitoring Menu appears.
Select option 1 Programs. The Program Monitoring screen appears.
In the Program field, type the name of the program for which you want to create Indirect Commands.

Type an s to the left of the Command option (Indirect commands). Press Enter.

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ CA InterTest Release 9.1.00 PROGRAM MONITORING ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ COMMAND ===> Type information and S to set or R to remove option(s) below. Program . . PLIdemo_ Program name (or .ALL, .OPTIONS or generic) User ID . . ____ User (or .ANY) for whom the program is monitored Option Description More: + _ Status Display and/or remove monitoring options (S only) _ Monitor Monitoring (R removes monitoring and all options previously set) _ UBP Unconditional breakpoints (specific program only) _ CBP Conditional breakpoints (specific program only) _ RBP Breakpoints for CICS, DB2, DL/I or external CALL requests _ Stmt Trace Statement tracing and data monitoring (COBOL only) _ New copy Fetch new copy of program and reset monitoring options (S only) s Commands Indirect commands defined for a specific COBOL or PL/I program _ Replace CICS resource name replacement options _ Protect Storage protection monitoring options _ Special Other options (storage allocation, file updating, etc.) _ Composite Monitor multi‑CSECT program's separately compiled components PF1 Help 2 3 End 4 Return 5 6 PF7 Backward 8 Forward 9 10 11 12

When you choose Commands from the Program Monitoring menu, another screen lets you set the terminal ID (terminal ID, .ANY or .NO) where the indirect commands take effect, and the user ID who executes the program (.ANY or a specific ID).

Normally you can accept the defaults. However, these entries need to match any existing monitoring entry for the program, which can be viewed on the Monitoring Status display.

CA InterTest MONITORING COMMAND BUILDER ‑ INDIRECT COMMANDS 24

SET option to EDIT indirect commands defined for execution in: PROG=PLIDEMO Term ID (or .ANY or .NO) where commands will take effect: ____ User ID (or .ANY) who will execute the program: ________ PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12

Press Enter to display the Indirect Commands facility.