What documentation is needed by CA Technical Support to resolve a CA InterTest for CICS Automatic Breakpoint (ABP) code 2D?

Document ID : KB000017744
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

During an active monitoring session CA InterTest for CICS may occasionally encounter an abend within CA InterTest for CICS itself and either stop program execution and display an Automatic Breakpoint (ABP) code 2D or abend the task with an INTE abend and generate a transaction dump.

Solution:

An automatic breakpoint, code 2D is an internal CA InterTest for CICS abend which is most likely occurring within the central monitoring module, IN25PGM2. Unfortunately, the program storage for IN25PGM2 is not included in any transaction dumps and, unless a system dump is generated, it may be necessary to recreate the problem and obtain a CICS system dump in order to find where the abend is occurring. To ensure that a system dump is generated for review by CA Technical Support, please take the following steps before attempting to recreate the problem:

If CICS itself is suppressing the system dump, change the "DUMP=NO" setting in the SIT to "DUMP=YES" and recycle the region.

Set CICS to generate a system dump for a specific abend code using the CICS CEMT transaction. Using the CA Intertest for CICS INTE abend code as an example, enter the command CEMT SET SYD(INTE) ADD. Combined with the change to the SIT in step 1, upon problem recreation, CICS will generate the necessary system dump for the INTE abend code.

However, please be aware that even if CICS is set up to take the system dump, the following steps may also be necessary to ensure that CA InterTest for CICS and/or CA Symdump do not suppress the dump.

By default, CA InterTest for CICS will also suppress dumps for an actively monitored program. Executing the CA for CICS transaction IGLU will display the CICS Global User Exits. Notice that the CA for CICS program IN25HOOK is defined at the CICS Global User EXIT XDUREQ. When IN25HOOK receives control at this exit point, it is designed to suppress dumps during an active monitoring session. In order to override this default and allow any dumps to be taken, enter the command CNTL=DUMP,ON. If entering the command results in a password prompt, the default is $FUN.

If Symdump for CICS is also active in the region, it is designed to suppress system dumps as well. To allow the dump to be taken, either terminate CA Symdump for CICS by executing the SYME transaction, recreating the problem to generate the system dump, and restarting CA Symdump for CICS by executing the SYMS transaction. The other alternative is to execute the CA Symdump for CICS transaction, SYMI, change the default setting for "SUPPRESS AP001 DUMPS" from "Y" to "N", recycle CA Symdump for CICS using SYME/SYMS as above, and recreating the problem to generate the system dump.

If the task was initially abended with an INTE transaction dump, a system dump will now be generated.

If the task was initially stopped at an Automatic Breakpoint, CA InterTest for CICS must be abended at the breakpoint to generate the system dump. In order to accomplish this, it is necessary to use the Detailed Breakpoint Screen. The command at the Detailed Breakpoint Screen will look similar to this


CNTL=GO,TASK=02916,A 

If the breakpoint is generated at the Source Listing Display, press PF3 to display the Detailed Breakpoint Display. Once displayed, the CNTL=GO command can be altered. Tab to the end of the command, and again using the INTE abend code as an example, change the command to:


CNTL=GO,TASK=02916,AINTE 

Pressing enter at this point will abend the task and generate the CICS System Dump with the INTE abend code.

In addition to the system dump, other extremely helpful documentation includes:

A complete set of screen prints from all options of the CA InterTest for CICS VRPT transaction.

The CICS system log of the region which includes the messages related to the problem and the generated INTE system dump

A screen print of a CNTL=INQ display to show the monitoring options that were in effect at the time the problem was encountered.

The documentation listed above should give CA Technical Support enough information to diagnose the problem and resolve it in a timely and efficient manner.