Previous Topic: Inspect the FREEMAIN StatementNext Topic: Review What Happened


Resume Program Execution

Continue program execution at the first instruction after the statement that triggered the breakpoint. In the PL/I demo, this is GOTO SENDMP00.

  1. Tab to the GOTO SENDMP00 statement following the breakpoint.
  2. Type g (go).
  3. Press Enter to continue program execution.

    CA InterTest for CICS Release 9.1.00 - PROTSYM FILE ABEND DETECTED BREAKPOINT COMMAND ===> Program= PLIDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ CKPTNAME | PROTCPF _____ NUP_AREA | THIS IS NOT A NAME PRIME THE _____ REC_LEN | +00681. _____ INPUT_REC_2 | ......................... _____ OUTPUT_REC_2 | ......................... ---------+--------------------------------------------------------------------- _ 1431.1 1 1 END; _ 1432.1 1 OUTPUT_REC_2 = INPUT_REC_2; A ==>.1 1 INPUT_REC_2 = OUTPUT_REC_2; ==> ==> an attempt to change an area that does not belong to this task. ==> Possible system damage has been prevented. ==> ==> Press PF1 for a detailed description. ==> g 1434.1 1 GOTO SENDMP00; U 1435.1 1 LOOPRTN: _ 1436.1 DO I = 1 TO 50; _ 1437.1 /* EXEC CICS ASKTIME */

    CA InterTest for CICS resumes program execution. PLIDEMO successfully completes execution and the Options Menu appears.

    By going around the storage violation, you have allowed PLIDEMO to continue executing despite the problem CA InterTest for CICS detected.