search cancel

Why would multiple users running the same program receive an Automatic Breakpoint (ABP) from CA Intertest for CICS if only one user is monitoring the program?


Article ID: 18197


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE InterTest - CICS InterTest - Batch InterTest VSE - CICS SymDump for CICS SymDump Batch



During a development cycle, it is not uncommon for multiple users to test the same program. When monitoring is declared for a program, terminal, or transaction and the program receives an Automatic Breakpoint (ABP), everyone using the same program may receive the same ABP even though they are not specifically monitoring the program themselves.


When CA InterTest monitoring is declared for an application program, transaction, or terminal, an entry is created for the monitored entity in an internal control block known as the Monitoring Table. Normally, this will not affect other users. However, CA InterTest for CICS is designed to minimize, or prevent damage to a CICS region. Therefore, once an Automatic Breakpoint (ABP) is issued, by default, CA InterTest for CICS will build a system wide or, Global Monitoring Entry, for the program being executed. Once the Global Monitoring entry is created, everyone executing the same program can possibly receive the ABP until monitoring is either removed or the cause for the ABP identified and corrected.

There are different methods that can be used to prevent an ABP from interfering with the work of other users.

The most efficient way is to limit monitoring to a specific terminal when declaring monitoring through the use of the Terminal Only Option (TON=). If you are using the CNTL Monitoring Command Builder menus, set this option using the Replacement Options, Protection Options, or Special Options displays. Otherwise, you can specify the TON option using a CNTL command when you declare monitoring.

There are two forms of this command:

  Set the terminal id to the terminal where the command is entered
   Limit monitoring  to the TCT entry named on the command.  

The second method is to limit monitoring to a specific Userid through the use of the USR= option. However, this option can only be used when the DFLTUSR keyword in IN25OPTS is set to DFLTUSER=SPECIFIC in a secured CICS region. Like the TON option, this can be accomplished using the CNTL Monitoring Command Builder menus or through the use of a command:


For details on the use of these options, please refer to the current copy of the CA InterTest for CICS User Guide.


Release: OSINBV00200-8.5-InterTest-Batch