Previous Topic: Special OptionsNext Topic: Remove Special Option


Set Special Options

Set special options to alter the CA InterTest for CICS standard monitoring procedures. Remove the special options to reinstate the default monitoring rules.

To set or remove special options, follow these steps.

  1. Specify function 22, S or R.
  2. Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press Enter.

The Special Options screen opens. For detailed instructions, see The Function Selection Menu.

Specify the following options on this screen. The equivalent option used in single‑line commands is specified in parentheses.

Source Listing Breakpoint (SLB)

Specifies that the Source Listing Breakpoint screen be displayed rather than the full breakpoint display screen. For more information, see the chapter "Source Listing Facility."

No file updating (NUP)

Specifies that a monitored program not update any files. This option only affects VSAM and BDAM files; databases are unaffected.

Reentrancy check (RNT)

Prevents a program from modifying its own code.

Follow monitoring (FOL)

Instructs CA InterTest for CICS to continue monitoring a program even if it branches directly to another program (wild branch). All monitoring options remain in effect. Specify the following:

Number of times to be monitored (MUS)

Limits the number of times a program should be monitored.

Limit total size of CICS storage (MXS)

Limits the amount of storage, including program storage, a program acquires.

Limit total number of CICS requests (MXR)

Limits the number of requests a transaction issues. This option is useful when a program is in a loop that includes a CICS request.

Setting for Structure Display Format (SDF)

Use this option to override, by program, the global default setting. Specify the following:

Set local automatic breakpoint (ABP)

Activates the automatic breakpoint facility for a particular program, transaction, or terminal.

Specify the terminal to receive automatic breakpoint displays.

Note: This option is useful when you do not want the breakpoint display routed to the terminal where the program is running, or when the display cannot be routed to that terminal (for example, a non‑terminal task or a task running on a non‑3270 terminal). In those cases, specify the terminal to which breakpoint displays should be routed. The local automatic breakpoint option is also useful in a production environment when the global Automatic Breakpoint facility is disabled and you want to monitor a specific program, transaction, or terminal.

Limit monitoring (TON)

Specifies that the program be monitored and that the special options, if specified, take effect only when the program executes at the current terminal (*), a specific terminal (termid), or without a terminal (.NO).