Agent services codes (X'E5')

If an agent services reason code occurs that is not listed here, an internal error has occurred. Collect the following diagnostic items and contact your IBM® support center.

Diagnostics

A description of the actions that led to the error or, if applicable, either a listing of the application program or the input string to a utility program that was being run at the time of the error.
The console output for the period leading up to the error.
The queue manager job log.
The system dump resulting from the error.
A printout of SYS1.LOGREC.
If you are using CICS®, the CICS transaction dump output.
Appropriate WebSphere® MQ, z/OS®, Db2®, CICS, and IMS service levels.

00E50001, 00E50002: An internal error has occurred.
System action: The requesting execution unit is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50004, 00E50005, 00E50006, 00E50007, 00E50008, 00E50009, 00E50012: An internal error has occurred.
System action: The requesting execution unit is ended abnormally. A record is written to SYS1.LOGREC and an SVC dump is requested.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50013

An MQ execution unit has been ended abnormally.

System action

The agent CANCEL processing continues.

System programmer response

This reason code might be issued as a result of any abnormal termination of a connected task, or a STOP QMGR MODE(FORCE) command. No further action is required in such cases.

If the error results in the termination of the queue manager, and you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50014: An internal error has occurred.
System action: An entry is written to SYS1.LOGREC, and an SVC dump is requested.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50015

An internal error has occurred.

System action

The operation is retried once. If this is not successful, the queue manager is terminated with reason code X'00E50054'.

A SYS1.LOGREC entry and an SVC dump are taken.

System programmer response

Restart the queue manager if necessary.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50029: The agent services function which establishes the MQ tasking structure ends abnormally with this reason code following the detection of a load module which was loaded without the 31-bit addressing capability. This is preceded by message CSQV029E.
System action: Queue manager start-up is terminated.
System programmer response: See message CSQV029E.

00E50030, 00E50031, 00E50032, 00E50035, 00E50036: An internal error has occurred.
System action: The requesting execution unit is ended abnormally. The error is recorded on SYS1.LOGREC, and an SVC dump is requested.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50040

Queue manager termination was invoked following an unrecoverable error while processing a terminate allied agent request at the thread, or identify level.

System action

The queue manager is terminated.

System programmer response

Restart the queue manager.

Scan the system log and the contents of SYS1.LOGREC for MQ errors occurring immediately before the system termination message CSQV086E. Follow the problem determination procedures for the specific errors. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50041

Queue manager termination was invoked following an unrecoverable error while processing a terminate agent request.

System action

The queue manager is terminated.

System programmer response

Restart the queue manager.

00E50042, 00E50044: An internal error has occurred.
System action: The current execution unit is ended abnormally. A record is written to SYS1.LOGREC and an SVC dump is requested.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50045

Queue manager termination was invoked following an unrecoverable error while processing a create allied agent service request at the thread, or identify level.

System action

The queue manager is terminated.

System programmer response

Restart the queue manager.

Scan the system log and the contents of SYS1.LOGREC for MQ errors occurring immediately before the termination message CSQV086E. Follow the problem determination procedures for the specific errors. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50046

Queue manager termination was invoked following an unrecoverable error while processing a create agent structure request.

System action

The queue manager is terminated.

System programmer response

Restart the queue manager.

00E50047

An internal error has occurred.

System action

The queue manager is terminated.

System programmer response

Restart the queue manager.

00E50050

An internal error has occurred.

System action

The requesting execution unit is ended abnormally.

An X'00E50054' recovery reason code is placed in the SDWACOMU field of the SDWA, indicating that synchronization services was responsible for queue manager termination.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50051

An internal error has occurred.

System action

The queue manager is ended abnormally with a X'5C6' completion code and this reason code.

An X'00E50054' recovery reason code is placed in the SDWACOMU field of the SDWA indicating that synchronization services was responsible for queue manager termination.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50052

The z/OS cross-memory lock (CML) could not be released.

System action

The queue manager is ended abnormally with a X'5C6' completion code and this reason code.

An X'00E50054' recovery reason code is placed in the SDWACOMU field of the SDWA indicating that synchronization services was responsible for queue manager termination.

A record is written to SYS1.LOGREC and an SVC dump is produced.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50054

The queue manager is ended abnormally by the synchronization services recovery routine when an unrecoverable error is encountered during recovery processing for the SUSPEND, CANCEL, RESUME, or SRB REDISPATCH functions. This is a queue manager termination reason code.

One of the following conditions was encountered during recovery processing for the requested function:

Unable to complete resume processing for an SRB mode execution unit that was suspended at time of error
Errors were encountered during primary recovery processing causing entry to the secondary recovery routine
Recovery initiated retry to mainline suspend/resume code caused retry recursion entry into the functional recovery routine
Unable to obtain or release the cross-memory lock (CML) of the queue manager address space either during mainline processing or during functional recovery processing (for example, reason code X'00E50052')

System action

The queue manager is terminated. This reason code is associated with a X'6C6' completion code indicating that synchronization services was responsible for termination.

System programmer response

Restart the queue manager.

00E50055

The synchronization services functional recovery routine was unable to successfully complete resume processing for a suspended TCB mode execution unit. The resume processing was requested by the CANCEL or RESUME functions.

System action

Because the suspended TCB mode execution unit must not be permitted to remain in a suspended state, the recovery routine invokes the z/OS CALLRTM (TYPE=ABTERM) service to end the execution unit abnormally with a X'6C6' completion code. Depending upon which execution unit was terminated, the queue manager might be ended abnormally.

System programmer response

Restart the queue manager if necessary.

Scan the system log and the contents of SYS1.LOGREC for MQ errors occurring immediately before the end of the execution unit. Follow the problem determination procedures for the specific errors. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50059

An internal error has occurred.

System action

If the module detecting the error is CSQVSDC0, it will be retried once. If validation is unsuccessful, the queue manager is terminated abnormally with a X'00E50054' reason code.

A SYS1.LOGREC entry and an SVC dump are requested.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50062: An internal error has occurred.
System action: The allied task is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50063: An internal error has occurred.
System action: The task is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50065: An internal error has occurred.
System action: The execution unit is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50069

This reason code is issued during recovery processing for the suspend function when executing in SRB mode under the recovery routine established by the z/OS SRBSTAT(SAVE) service. Because the recovery routine established by this service is the only routine in the FRR stack at the time of error, normal RTM percolation to the invoking resource manager recovery routine is not possible.

After recovery processing for the initial error has successfully completed, the RTM environment is exited through retry to a routine that restores the original FRR stack. This routine terminates abnormally with completion code X'5C6' and this reason code. This causes entry into the original recovery routine established during suspend initialization.

System action

After this is intercepted by the original suspend recovery routine, a SYS1.LOGREC entry and SVC dump are requested to document the original error. The original recovery reason code is placed in the SDWACOMU field of the SDWA indicating the actions performed during recovery processing of the initial error. Control is then returned to the invoking resource manager's recovery routine through RTM percolation.

System programmer response

Because this is used only to permit the transfer of the initial recovery reason code to the invoking resource manager's recovery routine, no further recovery actions are required for this reason code. Diagnostic information for the initial error encountered can be obtained through the SYS1.LOGREC and SVC dump materials provided.

00E50070

To enable an internal task to terminate itself, the task has ended abnormally. This is not necessarily an error.

System action

The task is ended abnormally.

If the service task is ended abnormally with a completion code of X'6C6', no SVC dump is taken.

System programmer response

The error should be ignored if it happens in isolation, however, if it occurs in conjunction with other problems, these problems should be resolved.

If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50071: An internal error has occurred.
System action: The internal task is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50072

An internal error has occurred.

System action

The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50073: An internal error has occurred.
System action: The current execution unit is ended abnormally. A record is written to SYS1.LOGREC, and an SVC dump is requested.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50074

This reason code is issued in response to a nonzero return code from ATTACH during an attempt to create an internal task.

System action

The ATTACH is retried. A record is written to SYS1.LOGREC, and an SVC dump is requested. If a problem occurs again, the queue manager is terminated.

System programmer response

Restart the queue manager if necessary.

Register 2, in the SDWA, contains the return code from the ATTACH request. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50075, 00E50076, 00E50077, 00E50078

An internal error has occurred.

System action

The requesting execution unit is terminated. The queue manager might also be terminated. A record is written to SYS1.LOGREC, and an SVC dump is requested.

System programmer response

Restart the queue manager if necessary.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50079: An internal error has occurred. This can occur if the allied address space is undergoing termination.
System action: The requesting execution unit is ended abnormally. A record is written to SYS1.LOGREC, and an SVC dump is requested.
System programmer response: If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50080, 00E50081: An internal error has occurred.
System action: An SVC dump is requested specifying a completion code of X'5C6' and this reason code. No record is written to SYS1.LOGREC. Execution continues.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50094, 00E50095, 00E50096, 00E50097, 00E50100: An internal error has occurred.
System action: The requesting recovery routine is ended abnormally. A record is written to SYS1.LOGREC, and an SVC dump is requested.
System programmer response: Collect the items listed in Diagnostics and contact your IBM support center.

00E50101

MQ was unable to establish an ESTAE.

System action

The error is passed on to a subsystem support subcomponent (SSS) ESTAE. Probably, the queue manager is ended abnormally. A record is written to SYS1.LOGREC, and an SVC dump is requested.

System programmer response

The inability to establish an ESTAE is normally due to insufficient free space in the local system queue area (LSQA) for an ESTAE control block (SCB). If necessary, increase the size of the queue manager address space.

Restart the queue manager.

Review the associated SVC dump for usage and free areas in the LSQA subpools belonging to the system services address space. If you are unable to solve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50102

An unrecoverable error occurred while canceling all active agents during processing of the STOP QMGR MODE(FORCE) command. This is a queue manager termination reason code.

System action

The queue manager is ended abnormally. A record is written to SYS1.LOGREC.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem. Review the SYS1.LOGREC entries for errors immediately preceding queue manager termination.

00E50500

A z/OS LOCAL or CML lock could not be obtained during queue manager abnormal termination processing.

System action

The execution unit is ended abnormally. The error is recorded on SYS1.LOGREC, and abnormal queue manager termination is completed under a different execution unit if possible.

System programmer response

Restart the queue manager if necessary.

You might find the items listed in Diagnostics useful in resolving the problem.

00E50501

A z/OS LOCAL or CML lock could not be released during queue manager abnormal termination processing.

System action

The execution unit is ended abnormally. The error is recorded on SYS1.LOGREC. Queue manager termination is completed under a different execution unit if possible.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem.

00E50502

A z/OS LOCAL lock could not be obtained during queue manager abnormal termination processing.

System action

The execution unit is ended abnormally. The error is recorded on SYS1.LOGREC, and abnormal queue manager termination is completed under a different execution unit if possible.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem.

00E50503

A z/OS LOCAL lock could not be released during queue manager abnormal termination processing.

System action

The execution unit is ended abnormally. The error is recorded on SYS1.LOGREC, and abnormal queue manager termination is completed under a different execution unit if possible.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem.

00E50504: This reason code is used to define the format of the information recorded in the SDWA variable recording area (VRA) by the queue manager termination processor. The code identifies additional information provided in the VRA for errors encountered in module CSQVATRM.
System action: Recording of the error encountered during queue manager termination continues.
System programmer response: None.

00E50505: This reason code is used to define the format of the information recorded in the SDWA variable recording area (VRA). The code identifies additional information provided in the VRA for errors encountered in module CSQVATR4.
System action: Recording of the error encountered during queue manager termination continues.
System programmer response: None.

00E50701

A problem occurred during Commit Phase-1. This is used to effect backout, deallocation, and end-UR processing.

System action

The queue manager is ended abnormally. A record is written to SYS1.LOGREC, and an SVC dump is requested.

System programmer response

Restart the queue manager.

If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50702

An error occurred while processing in SRB mode which could not be recovered.

SRB mode processing is often used internally by the queue manager to ensure data integrity and consistency of internal state. Where recovery is not possible, the queue manager is terminated with this reason code.

Most occurrences are due to internal errors which should be reported to IBM service for further investigation.

The error is also known to occur where log data sets have been reformatted, without reformatting the pagesets (so they still contain active data). This situation can be resolved by user action.

System action

The queue manager is ended abnormally with this reason code. An SVC dump of the original error was requested by the recovery routine for CSQVEUS2 and a record written to SYS1.LOGREC.

System programmer response

Restart the queue manager.

Scan the SYS1.LOGREC entries looking for one or more MQ errors immediately prior to the queue manager termination. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50703

This queue manager termination reason code is used following an error while attempting to resume a suspended execution unit. The successful completion of resume processing was 'indoubt'.

System action

The queue manager is ended abnormally. A record is written to SYS1.LOGREC, and an SVC dump is requested.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem.

00E50704

An internal error has occurred.

System action

The queue manager is terminated with this reason code. Additionally, if no SDWA was provided to the recovery routine, a dump is requested.

System programmer response

Restart the queue manager.

00E50705

An internal error has occurred.

System action

The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact your IBM support center.

00E50706

An internal error has occurred.

System action

The queue manager is terminated with this reason code. Additionally, if no SDWA was provided to the recovery routine, a dump is requested. A record is written to SYS1.LOGREC.

System programmer response

Restart the queue manager.

00E50707

An ESTAE could not be established.

System action

The queue manager is ended abnormally. A record is written to SYS1.LOGREC.

System programmer response

Review the usage and the free areas in the LSQA subpool of the queue manager address space. If necessary, increase the private area size of the address space.

Restart the queue manager.

If queue manager termination was requested by module CSQVRCT, a standard SVC dump was requested. If insufficient private storage is the cause of the problem, other MQ resource managers might have ended abnormally.

If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50708

An error occurred while connecting an allied agent to the queue manager address space. The connection must complete so that the allied agent can be terminated.

System action

The queue manager is terminated with this reason code. An SVC dump of the original error was requested and a record entered into SYS1.LOGREC.

System programmer response

Restart the queue manager.

Scan the SYS1.LOGREC entries looking for one or more MQ errors immediately prior to the queue manager termination.

00E50709

An internal error has occurred.

System action

The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

Scan the SYS1.LOGREC entries for one or more MQ errors occurring immediately prior to the queue manager termination. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50710

An internal error has occurred.

System action

The queue manager is terminated with this reason code. An SVC dump of the original error was requested and a record entered into SYS1.LOGREC.

System programmer response

Restart the queue manager.

00E50711

An internal error has occurred.

System action

The queue manager is terminated with this reason code. An SVC dump of the original error was requested and a record entered into SYS1.LOGREC.

System programmer response

Restart the queue manager.

00E50712

An error occurred in a latch manager function attempting to terminate the holder of an MQ latch. The holder's task has been set nondispatchable by z/OS and a CALLRTM to terminate this task was unsuccessful.

System action

The queue manager is terminated with this reason code. An SVC dump of the error is requested and a record entered into SYS1.LOGREC. Register 3 at time of error contains the latch-holder's TCB address in the home address space and register 4 contains the return code from CALLRTM.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem. Scan the SYS1.LOGREC entries for one or more MQ errors immediately prior to the queue manager termination.

00E50713

An internal error has occurred.

System action

The queue manager is ended abnormally. An SVC dump is requested by the queue manager termination processor and a record is written to SYS1.LOGREC.

System programmer response

Restart the queue manager.

Scan the SYS1.LOGREC entries for one or more MQ errors occurring immediately prior to the queue manager termination. It might be necessary to analyze the SVC dump requested. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50715

Queue manager termination was requested following an unrecoverable error in an SRB mode execution unit.

System action

The SRB-related task was ended abnormally as a result of SRB to TCB percolation. The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem. Scan the SYS1.LOGREC entries for one or more MQ errors occurring immediately prior to the queue manager termination.

00E50717

An internal error has occurred.

System action

The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

Scan the SYS1.LOGREC entries for one or more MQ errors occurring immediately prior to the queue manager termination. If an error preceded the queue manager termination request, diagnostic information can be obtained through SYS1.LOGREC and SVC dump materials. If you are unable to resolve the problem, collect the items listed in Diagnostics and contact your IBM support center.

00E50719

An internal error has occurred.

System action

The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

00E50725

Queue manager termination was requested because of an unrecovered error in a scheduled SRB-mode execution unit.

System action

The SRB-related task was ended abnormally, due to SRB to TCB percolation. The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem. Scan the SYS1.LOGREC entries for one or more MQ errors occurring immediately prior to the queue manager termination. If necessary, analyze the SVC dump requested by queue manager termination.

00E50727

A secondary error occurred during agent services functional recovery processing. This is a queue manager termination reason code.

System action

The queue manager is ended abnormally.

System programmer response

Restart the queue manager.

You might find the items listed in Diagnostics useful in resolving the problem. Scan the SYS1.LOGREC entries for one or more MQ errors occurring immediately prior to the queue manager termination.