This section of the demo session shows how to limit CICS main storage and CICS requests. Two different CA InterTest for CICS options are detailed in this part of the demo:
Before you begin this section, complete the steps outlined in Start-up (unless you did so earlier in this session). The Options Menu should be displayed.
ASMDEMO displays a screen that describes what will occur in this part of the demo.
********************************************************************** **** **** **** CA InterTest Demo Session **** **** MXR Option ‑ Limit Number of CICS Requests **** **** MXS Option ‑ Limit Amount of CICS Storage **** **** **** ********************************************************************** The program has a loop containing a CICS request and another loop containing a GETMAIN request. Here is what will happen: 1. The program is halted at an unconditional breakpoint before the loops. 2. You set the MXS and MXR options to limit storage and CICS requests. 3. The program continues to execute. 4. CA InterTest halts the program at automatic breakpoints when the limits are exceeded. 5. You remove the options and the program completes execution. When this section of the demo completes, you will return to the Options Menu. Press ENTER to continue or CLEAR to terminate
CA InterTest for CICS halts the program at the first instruction following the label LOOPRTN because you set an unconditional breakpoint there during Start‑Up.
ASMDEMO is halted at the first instruction after LOOPRTN. Because LOOPRTN does not have executable code, the unconditional breakpoint actually occurs before the first instruction; in this case, the highlighted ZAP instruction.
Now you can access the Special Options menu to set options you need for testing.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|