Previous Topic: Halt the Demo Program at a Request BreakpointNext Topic: Use FILE to Inspect the Record


The No File Updating Option

As we did when we set and removed the MXR and MXS options, bring up the Program Monitoring screen. For convenience, use the CA InterTest for CICS fast path feature to navigate to this screen.

  1. Type SO on the command line and press Enter.

    The Special Options menu appears.

  2. Tab to the NUP field.
  3. Type an x, and press Enter.

    CA InterTest for CICS MONITORING COMMAND BUILDER ‑ SPECIAL OPTIONS 22 SET one or more options to override the default monitoring rules in: PROG=PLIDEMO Enter X next to each option desired: Source Listing Breakpoint (SLB) _ No file updating (NUP) x Reentrancy check (RNT) _ Follow monitoring (ON, name, NOPPT) (FOL) ________ Number of times to be monitored (MUS) _____ Limit total size of CICS storage (MXS) _______ Limit total number of CICS requests (MXR) _______ Set local automatic breakpoint ('*', TERMID, .ANY, OFF) ____ Limit monitoring to your TERMINAL ‑ '*' or TERMID: ____ User ID (or .ANY) who will execute the program: ________ PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12

    CA InterTest for CICS sets this option for the demo program.

  4. Type =x in the Command field and press Enter to return to the Source Listing Breakpoint screen.

    Before resuming program execution, look at the statement just before the EXEC CICS REWRITE command:

    NUP_NAME = 'THIS IS NOT A NAME'
    

    PLIDEMO is supposed to move the data string THIS IS NOT A NAME to the data field NUP_NAME. If PLIDEMO actually updates the file, this data string displays at the beginning of the first record in that file.

  5. Press PF5 to continue program execution.

    The demo program resumes execution.