Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

User Abend Codes

Abend codes

Description

ABEND 3000

Module: XPHOGNPF, XPHOGNIF, XPHOGNBF, XPHOGNTF, XPRDLIST, XPBTSLNK, XPEDCTL, ADSRA207, and ADSRA300

Explanation: This ABEND always means there is insufficient storage for a Code Debug TSO compile.

User Response: Increase the REGION for the JOB or STEP, and resubmit the compile job.

ABEND 3001

AN INVALID SERVICE REQUEST HAS BEEN SENT TO ADSRA000

Module: ADSRA000

Explanation: Module ADSRA000 is the dynamic CALL TRANSFER version of Code Debug. One of its functions is to manage Code Debug modules, both loading and deleting. The module also maintains an internal control stack. An invalid service call was issued.

User Response: Contact your internal technical support.

ABEND 3002

UNABLE TO TEST USER PROGRAM

Module: ADSRA410, CSSMVS, XPTSO, XPDRP, XPMMAIN and XPINIT

Explanation: Code Debug is unable to test the user program.

User Response: See the session log for additional details. The ABEND reason code is set as follows:

20

The user program named on the TEST and/or INTERCEPT control card could not be found.

22

The XPIN control cards are invalid.

24

The required PARM field was omitted for an IMS or BTS test.

26

The XPOUT DD card was missing or could not be opened.

28

The TASKLIB and/or XTASKLIB DD card was missing or could not be opened.

2A

The TEST ID was not specified for a Code Coverage test.

2C

The SYSTEM NAME was not specified for a Code Coverage test.

2E

The XCOVER DD card was missing or could not be opened.

30

The XPIN DD card was missing or could not be opened.

32

An error exists in the assembly of ADSRA093 (the user may have updated ADSCPDEF).

34

A Db2 stored procedure test encountered an unrecoverable error.

36

Multi-Batch Communication Task failure – see WTO message.

38

Multi-Batch Staging File record not found.

ABEND 3003

CODE DEBUG BLDL FAILURE

Module: ADSIM002

Explanation: An attempt to call a Code Debug module failed because the module could not be found in the STEP or JOBLIB libraries.

User Response: Verify that the correct libraries are present; if the problem persists, contact your internal technical support.

ABEND 3007

A CODE DEBUG RECURSIVE ABEND HAS OCCURRED

Module: ADSRA105

Explanation: Successive ABENDS occurred while an application module was being tested.

User Response: Contact your internal technical support.

ABEND 3008

A CODE DEBUG TIME-OUT HAS OCCURRED DURING TERMINAL RECOVERY.

Module: ADSRA105

Explanation: Code Debug exhausted the time threshold while attempting to recover from a terminal ABEND.

User Response: Contact your internal technical support.

ABEND 3009

A DIAGNOSE ABEND HAS BEEN REQUESTED

Module: ADSRA148

Explanation: The Code Debug DIAGNOSE command was used to generate an ABEND of the Code Debug region, or the EXIT ABEND command was entered without specifying a System or User abend code (U3009 is the default).

User Response: If you did not enter the Code Debug EXIT ABEND command, contact your internal technical support and provide them with the SYSUDUMP and other materials.

ABEND 3010

AN ERROR WAS ENCOUNTERED DURING THE MULTI-BATCH INITIALIZATION RELEASE VERIFICATION PROCESS

Module: XPMINIT

Explanation: During Multi-Batch initialization an unrecoverable error occurred.

User Response: See the XPMINIT JES joblog for error messages. The ABEND reason code is set as follows:

10

Miscellaneous errors that could occur during Multi-Batch initialization.

20

Unable to find the release level in one of the modules.

30

There is a release level mismatch.

ABEND 3011

CODE DEBUG TSO PRODUCT CONFIGURATION OPTIONS COULD NOT BE LOADED

Module: LXTCMSC1

Explanation: Configuration options could not be loaded because the in-storage instance of the Code Debug PARMLIB member is missing, possibly due to an invalid member.

User Response: Contact your internal technical support.

ABEND 3020

CODE DEBUG TSO/IMS SVC HAS ENCOUNTERED AN INVALID PARAMETER LIST

Module: CWXTSVC

Explanation: The Code Debug SVC has encountered an invalid parameter. Ensure proper installation.

User Response: Contact BMC Support and provide them with SYSUDUMP/SVC dump and other materials.

ABEND 3051

MAXIMUM OF 15 BASE REGISTERS EXCEEDED

Module: ADSRA217

Explanation: The maximum number of base locator cells that Code Debug can maintain is 15. This maximum was exceeded.

User Response: Contact your internal technical support.

ABEND 3052

ALLOCATION OF GPR BUFFER FAILED

Module: ADSRA217

Explanation: An attempt to allocate memory failed for the GPR buffer.

User Response: Contact your internal technical support.

ABEND 3092

OPEN FAILED FOR XTASKLIB

Module: XPHOGNFF

Explanation: An attempt to open the XTASKLIB DD failed.

User Response: Add the XTASKLIB DD to your JCL or CLIST and try again.

ABEND 3093

IDENTIFY FAILED FOR SUBTASK

Module: XPHOGNFF and ADSIM004

Explanation: A critical error occurred during setup of the BTS environment.

User Response: Contact your internal technical support.

ABEND 3094

ATTACH OF SUBTASK FAILED

Module: XPHOGNFF and ADSIM004

Explanation: A critical error occurred during setup of the BTS environment.

User Response: Contact your internal technical support.

ABEND 3095

ATTACH OF BTS FAILED

Module: XPBTBTSF, XPHOGNFF, and ADSIM004

Explanation: A critical error occurred during setup of the BTS environment.

User Response: Verify that the appropriate BTS libraries were included in the STEPLIB and run again.

ABEND 3097

BTS CONTROL BLOCK NOT FOUND

Module: ADSIM004

Explanation: A previously constructed BTS control block cannot be located. Probable memory overlay.

User Response: Contact your internal technical support.

ABEND 3099

LOAD OF CODE DEBUG FAILED

Module: ADSIM004

Explanation: The load module for Code Debug could not be found.

User Response: Include the Code Debug load module library in the STEPLIB concatenation and try again.

ABEND 3100

LOAD OF APPLICATION MODULE FAILED

Module: ADSRA000

Explanation: The application load module could not be found.

User Response: Include the library containing the load module in the XUSERLIB concatenation and try again.

ABEND 3104

INVALID BREAKPOINT INSTRUCTION EXECUTED

Module: ADSRA104 and ADSRA478

Explanation: A breakpoint instruction has been encountered which was not placed by Code Debug. The Code Debug SVC or TEST instruction has occurred within the user’s code or a supporting product. These instructions are not supported in a debugging session unless placed by Code Debug.

User Response: The PSW address indicates the location of the offending instruction. If the instruction was not compiled as part of the user’s application and there is no active product utilizing the instruction, contact BMC Support.

ABEND 3333

Module: ADSRA417, XPHOGNBF, XPHOGNEQ, XPHOGNFF, XPHOGNIF, XPHOGNKQ, XPHOGNPF, XPHOGNSQ, or XPHOGNTF

Explanation: An abend occurred in Code Debug TSO. The abend is preceded by an error message.

User Response: Contact your internal technical support and provide them with the session log and other materials.

ABEND 3398

CODE DEBUG TSO ABEND IN ADSRANNNEP N(8) IA N(8) DISP N(6)

Module: ADSRA000 and ADSRA106

Explanation: An ABEND occurred in Code Debug TSO. A Code Debug TSO internal control stack will follow this message.

User Response: Contact BMC Support for a circumvention and to open a PTN (Problem Tracking Number) to resolve the problem.

ABEND 3399

Explanation: This ABEND occurs if there is not enough memory available for Code Debug for Db2 Extension.

User Response: Log off and then log back on with more memory.

ABEND 3669

Explanation: When PARMLIN option CTLEXABN = YES, an attempt to issue EXIT or QUIT without parameters is changed to EXIT ABEND U3669.

User Response: Expected behaviour.

ABEND U4000

(1) NON-ZERO RETURN CODE FROM ISPEXEC

(2) NON-ZERO RETURN CODE FROM PANEL QUERY

(3) INSUFFICIENT MEMORY FOR SVT BUFFER

(4) NON-ZERO RETURN CODE FROM CONTROL DISPLAY LINE


Module: ADSRA429, ADSSU082, and ADSRA470

Explanation: Module ADSRA429 issues two messages: message 1 indicates an error in an ISPEXEC call for ISPF services; 2 indicates an error in an ISPF panel request. Module ADSSU082 issues message 3, which indicates that the JOB being run needs more memory and should be run in a larger region. Module ADSRA470 issues message 4, which indicates an error in the use of the ISPF DISPLAY function.

User Response: Contact the BMC Support.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*