Abend Codes-Xchange

Module: XGMINIT at Xchange start up

Problem Determination: 400, 401, and 402 (x'190', x'191', and x'192')

Explanation: Xchange did not find a required load module in the STEPLIB or JOBLIB data sets.

Operator Response: Make sure the following conditions have been satisfied:

• The JCL or PROC used to start Xchange contains the correct load libraries in the STEPLIB or JOBLIB concatenation.
• The module name is correct in the PARM operand of the EXEC statement used to execute Xchange.
• The RACROUTE module, XGVRACRT, exists in the correct load libraries.

Problem Determination: 403 (x'193')

Explanation: There was insufficient main storage for the operator request element (ORE) queue.

Operator Response: Ensure that the NUMORE parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 404 (x'194')

Explanation: There is insufficient main storage for the journal request element (JRE) queue.

Operator Response: Ensure that the NUMJRE parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 405 (x'195')

Explanation: There is insufficient main storage for the user request element (URE) queue.

Operator Response: Ensure that the NUMURE parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 406 (x'196')

Explanation: An Xchange address space using the same subsystem ID is already executing on this MVS system.

Operator Response: Only one Xchange address space can use a subsystem ID at a time. Make sure that the correct Xchange is being executed. Execute Xchange with a different configuration member name or terminate Xchange using the current subsystem ID.

Problem Determination: 407 (x'197')

Explanation: There is insufficient main storage for the Xchange request element (XRE) queue.

Operator Response: Ensure that the NUMXRE parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 408 (x'198')

Explanation: There is insufficient main storage for the Active Memory Block (AMB) pool.

Operator Response: Ensure that the NUMAMB parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 409 (x'199')

Explanation: There is insufficient main storage for the Active Task Block (ATB) pool.

Operator Response: Ensure that the NUMATB parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use) does not contain an unreasonably large value. If not, increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 410 and 411 (x'19A' and x'19B')

Explanation: Xchange cannot initialize the User Interface Task.

Operator Response: Contact BMC Support.

Problem Determination: 412 (x'19C')

Explanation: The system is unable to establish the main task ESTAE environment — a non-zero return code resulted from an ESTAE macro.

Operator Response: Contact BMC Support.

Problem Determination: 413 (x'19D')

Explanation: Xchange was unable to exchange itself with the IBM-supplied supervisor calls (SVCs), program call (PC) routines, or the branch-entered TIME processes.

Operator Response: Contact BMC Support.

Problem Determination: 414 and 415 (x'19E' and x'19F')

Explanation: Xchange cannot initialize the subsystem. When the main task abends, the associated subtasks may abend also.

Operator Response: Check whether subsystem is mistakenly running in SYS1.PARMLIB or reusing an old subsystem name following an upgrade. Contact BMC Support.

Problem Determination: 5000 and 5001

Explanation: Xchange cannot schedule its startup SRB in the master scheduler address space to establish the PC routine.

Operator Response: Contact BMC Support.

Explanation: There may be a problem somewhere within BMC PARMLIB.

Operator Response: Make sure the following conditions have been satisfied:

• Verify that the CMSC has been installed and is functioning properly. See to the Enterprise Common Components Installation and Configuration Guide for detailed instructions.
• Verify that the Xchange CMSC BMC PARMLIB member is present, is prefixed with XCHG, and is suffixed with either the default 00 or the suffix present on the PARM of the EXEC JCL statement in the Xchange startup JCL. Also verify that a CMSC REFRESH command was successfully performed. See the section entitled CSMC Commands in the ECC Advanced Configuration Guide for detailed instructions on issuing this command. If the CMSC refresh was successful, message LXG00001 can be located in the JESLOG of the CMSC address space.
• If using the default CMSC environment, verify that the default CMSC address space is up and functioning properly.
• If using a secondary CMSC environment, the CMSC identifier is specified on the PARM= EXEC JCL statement in the secondary CMSC address space. Verify that DD //CWSC?? is present in the Xchange startup JCL (where is the CMSC identifier), that ?? represents a valid CMSC environment, and that the secondary CMSC address space is up and functioning properly.

Module: XGIMSPGM

Explanation: End-of-File detected on XGIMSREQ file.

Operator Response: Restart IMS dependent region and then contact BMC Support.

Module: XGIMSPGM

Explanation: The Xchange internal request header could not be found for this IMS dependent region.

Operator Response: Restart IMS dependent region and then contact BMC Support.

Module: XGIMSPGM

Explanation: The Xchange address has been recycled in the middle of processing an IMS transaction being exchanged.

Operator Response: Restart IMS dependent region and then contact BMC Support.

Module: XGMINIT at Xchange start up

Problem Determination: 100

Explanation: There is insufficient main storage to obtain a global communications area (GCA).

Operator Response: Increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 101

Explanation: The PARM parameter on the EXEC statement is not valid. The value may be longer than eight characters or missing altogether. It is also possible that there was insufficient main storage for the above the 16m line work area queues.

Operator Response: Increase the value for the REGION parameter of the EXEC statement used to execute Xchange. Also, make sure the PARM parameter is correctly specified.

Problem Determination: 102

Explanation: There is insufficient virtual storage to obtain the "below the 16m line work' area queues.

Operator Response: Increase the value for the REGION parameter of the EXEC statement used to execute Xchange.

Problem Determination: 103

Explanation: The XGMINIT initialization module could not be loaded.

Operator Response: Ensure that the STEPLIB or JOBLIB concatenation specified the correct data sets.

Module: XGTMAIN

Explanation: BMC security failed during initialization.

Operator Response: Contact BMC Support.

Module: XGMMAIN

Explanation: The Xchange SVC11 recovery routine has detected more than three abends within a 15 minute interval. These abends are happening for jobs targeted for Xchange. The Xchange address space will be terminated.

Operator Response: Restart and then contact BMC Support

Module: XGJMAIN

Explanation: The operator communication task cannot be initialized.

Operator Response: Contact BMC Support.

Module: XGMHEDW

Explanation: A call to LICENSE MANAGEMENT CHECKOUT presented a nonzero return code. The Xchange address space will be terminated.

Operator Response: Contact BMC Support. There is a license issue that needs to be resolved.

Module: XGMHEDW

Explanation: A storage obtain error or nonzero return code from LMRETMSG processing. The Xchange address space will be terminated.

Operator Response: Contact BMC Support.

Module: XGJMAIN

Explanation: A FREEMAIN of a journal data set buffer has not been successful. Because journal buffers are relatively large, the journal task abends in this condition so MVS does not allocate unnecessary virtual storage.

Operator Response: Contact BMC Support.

Module: XGJMAIN

Explanation: An invalid journal data set buffer has been encountered. Because journal buffers are relatively large, the journal task abends in this condition so MVS does not allocate unnecessary virtual storage.

Operator Response: Contact BMC Support.

Module: XGJMAIN at Xchange start up

Explanation: Xchange was not able to attach the operator task or an insufficient number of operator request elements (OREs) were available.

Operator Response: Increase the value of the NUMORE parameter in the Xchange CMSC PARMLIB member (see Consider how NUM options affect Xchange use). Re-execute Xchange.

Module: XGJMAIN at Xchange start up

Explanation: The operator task was unable to complete initialization.

Operator Response: Contact BMC Support.

Module: XGJMAIN at Xchange start up

Explanation: The operator subtask has abended and restarted three times. It has abended again. Xchange terminates with this abend code.

Operator Response: Contact BMC Support.

Module: XGSTKINS

Problem Determination:

Explanation: XGSTKINS encountered an error. There will be an XG0xxx message in the joblog prior to the abend.

Operator Response: See appropriate XG0xxx message associated with each reason code for course of action.