Many of the following reason codes are returned in register 15 at the time of an abnormal termination with completion code X'0Cx', and not as the reason code for a completion code of X'5C6'. This is indicated in the descriptions that follow.
If a subsystem support reason code occurs that is not listed here, an internal error has occurred. Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The request is not processed.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The requester's task is ended abnormally with completion code X'5C6'. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
The recovery coordinator for the caller has already terminated, so the connection from the caller to MQ has been terminated.
The request is not processed. The connection from the caller to MQ is terminated.
The caller may reconnect to MQ when the recovery coordinator has been restarted.
Identify and restart the recovery coordinator.
This abnormal termination is most commonly associated with a termination of RRS. There may be additional CSQ3009E messages on the console log associated with the termination of RRS.
An internal error has occurred.
The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The connection request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
Functional recovery for the connection processing could not be established. The executing module could not establish its ESTAE. This can occur if the current address space has insufficient storage. This might lead to an abnormal termination of the queue manager.
The connection request is not processed. The caller is ended abnormally with completion code X'5C6' and this reason code.
Restart the queue manager if necessary. A dump should be taken for problem analysis.
Examine the usage and free areas in the LSQA portion of the current address space private area. If necessary, have the size of the private areas expanded.
The caller should produce a SYS1.LOGREC entry and an SVC dump, so that you can examine the LSQA area. You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The connection request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The application program is ended abnormally with completion code X'5C6' and this reason code. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
The application program issued an RRSAF IDENTIFY function request, but RRS is not available.
The IDENTIFY request is not processed.
Retry the IDENTIFY request after RRS has been started.
The application program issued an RRSAF TERMINATE THREAD or TERMINATE IDENTIFY function request, but the application has issued an MQ API request since the last invocation of SRRCMIT or SRRBACK and therefore is not at a point of consistency.
The function request is not processed.
You can continue processing with a corrected request.
An internal error was detected in either MQ or RRS.
The application is ended abnormally. The error is recorded in the SYS1.LOGREC data set and an SVC dump is requested.
This error might, in many cases, eventually cause the queue manager to terminate abnormally.
This is probably either an error in MQ or in RRS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error was detected in either MQ or RRS Context Services.
The application is ended abnormally. The error is recorded in the SYS1.LOGREC data set and an SVC dump is requested.
This error might, in many cases, eventually cause the queue manager to terminate abnormally.
This is probably either an error in MQ or in RRS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error. See message CSQ3101E for details.
See message CSQ3101E.
See message CSQ3101E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error. The MQ command prefix (CPF) must not be blank. For details, see message CSQ3102E.
See message CSQ3102E.
See message CSQ3102E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error or the named module is not resident in a library available during IPL. See message CSQ3103E for details.
See message CSQ3103E.
See message CSQ3103E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
Module CSQ3UR00 was unable to obtain the affinity table index for the named subsystem. z/OS did not recognize the named subsystem. See message CSQ3109E for details.
See message CSQ3109E.
See message CSQ3109E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
Module CSQ3UR00 was unable to load Early module CSQ3EPX. Either there was an I/O error, or the named module is not resident in a library available during IPL. See message CSQ3105E for details.
See message CSQ3105E.
See message CSQ3105E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error. The scope of the MQ command prefix (CPF) is not valid. For details, see message CSQ3112E.
See message CSQ3112E.
See message CSQ3112E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An error occurred during command prefix registration.
The MQ subsystem ends abnormally.
See the accompanying CSQ3xxx messages for information about the cause of the problem.
An internal error has occurred.
The caller is ended abnormally. An SVC dump and associated SYS1.LOGREC entries are produced.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An attempt to create a queue manager address space failed. This is probably because the user who issued the START QMGR command has insufficient authority.
The current START command processing is terminated. An SVC dump and associated SYS1.LOGREC entries are produced.
Check the authority of users and consoles to issue commands. Retry the command.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
The console ID for the z/OS console that entered the current command is not found in the z/OS unit control module (UCM) structure. An internal z/OS command might have been incorrectly issued by an application program that provided invalid input parameters.
The caller is ended abnormally.
Retry the START QMGR command. If the command was unsuccessful, collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The current task is ended abnormally. The calling task might have requested an SVC dump or created associated SYS1.LOGREC entries.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The calling task is ended abnormally. The calling task might have requested an SVC dump or created associated SYS1.LOGREC entries.
Cancel the queue manager. (End-of-task processing might still work, and it does a more complete clean-up than end-of-memory processing does.) If this does not work, issue the z/OS command FORCE for the queue manager. If the problem is still unresolved, re-IPL z/OS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The calling task is ended abnormally. An SVC dump and associated SYS1.LOGREC entries are produced.
Stop the queue manager and reissue the START QMGR command.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established. This can occur if the z/OS system address space that is broadcasting the command has insufficient storage.
The caller is ended abnormally (without a dump). The current START command processing is terminated.
Retry the command. If the error persists, re-IPL z/OS.
Examine the LOGREC entries, and the console log for indications of a z/OS error, and try increasing the storage.
If you are unable to resolve the problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during either the initialization or termination of the queue manager.
This can occur during initialization if the z/OS system address space that is broadcasting the first command (assumed to be the START command) has insufficient storage. e
This can occur during termination if the current address space (usually the queue manager, or in the case of EOM broadcast, a z/OS system address space) has insufficient storage.
The caller is ended abnormally (without a dump). The initialization stops, but termination proceeds.
Retry the command after the queue manager has terminated. If the problem persists, a re-IPL of z/OS might be necessary.
Examine the LOGREC entries, and the console log for indications of a z/OS error, and try increasing the storage.
If you are unable to resolve the problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established while in the process of routing control to the actual ESTAE routine. The caller (RTM) is ended abnormally. This causes the original error to percolate to a higher-level recovery routine and causes this reason code to be shown in an RTM recovery environment.
This can occur if the current address space (usually an allied address space) has insufficient storage.
The caller is ended abnormally and a dump is produced.
Examine the usage and free areas in the LSQA portion of the current address space private area. If necessary, have the size of the private area expanded.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The caller is not ended abnormally. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The connection between the allied address space and the queue manager terminated. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The invoker is ended abnormally. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during the processing of a resolve-indoubt request. This can occur if the current address space has insufficient storage. This will probably cause an abnormal termination of the queue manager.
The caller is ended abnormally.
Restart the queue manager if necessary.
Examine the usage and free areas in the local system queue area (LSQA) portion of the current address space private area. If necessary, have the size of the private area expanded.
The caller should produce a SYS1.LOGREC entry and an SVC dump, so that you can examine the LSQA area.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An ESTAE could not be established during the processing of a resolve-indoubt-UR request. This can occur if the current address space has insufficient storage.
The caller is ended abnormally.
Examine the usage and free areas in the local system queue area (LSQA) portion of the current address space private area. If necessary, have the size of the private area expanded.
The caller should produce a SYS1.LOGREC entry and an SVC dump.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
A control block could not be allocated. This could occur when the storage pool has no more free space available.
The request is not processed. The application program is ended abnormally with completion code X'5C6' and this reason code.
A dump should be taken for problem analysis.
Check that you are running with the recommended region size, and if not, reset your system and retry. If you are unable to resolve the problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The program which made the request might produce diagnostics to report the error.
Collect the diagnostics produced by the application program reporting the error, if any, and contact your IBM support center.
The queue manager has gone to EOM (end-of-memory). This is probably because the z/OS command FORCE has been issued.
The queue manager is terminated, and a dump is taken.
The queue manager can be restarted after termination completes.
Determine why the z/OS command FORCE was issued.
An internal error has occurred.
The queue manager is terminated with an SVC dump.
The queue manager can be started again after it terminates.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
See message CSQ3001E.
See message CSQ3001E.
See message CSQ3001E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The queue manager is terminated with an SVC dump.
The queue manager can be started again after it terminates.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated.
The queue manager should be restarted.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated.
The queue manager can be started again after it terminates.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated.
The queue manager can be started again after it terminates.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated.
The queue manager can be started again after it terminates. If the problem persists, request a stand-alone dump, and re-IPL z/OS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during the processing of an EOM SSI broadcast. This is probably a z/OS problem, because these modules are executing in the z/OS master scheduler address space.
The queue manager is terminated.
The queue manager can be started again after it terminates. If the problem persists, re-IPL z/OS.
This can occur if the z/OS master scheduler address space has insufficient free storage. If such is the case, MQ is unable to write a SYS1.LOGREC record or request a dump. The z/OS master scheduler should have produced these diagnostic aids. Examine the dump to determine whether the problem is in z/OS or MQ. Other unrelated errors in the z/OS Master Scheduler address space would indicate a z/OS problem.
If the problem appears to be an MQ problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during the processing of an EOM for an allied address space.
The queue manager is terminated.
The queue manager can be started again after it terminates. If the problem persists, re-IPL z/OS.
This can occur if the z/OS master scheduler address space has insufficient free storage. If such is the case, MQ is unable to write a SYS1.LOGREC record or request a dump. The z/OS master scheduler should have produced these diagnostic aids. Examine the dump to determine whether the problem is in z/OS or MQ. Other unrelated errors in the z/OS Master Scheduler address space would indicate a z/OS problem.
If the problem appears to be an MQ problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated.
The queue manager can be started again after it terminates.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated with an SVC dump.
The queue manager can be started again after it terminates.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established by the deferred end-of-task (EOT) processor. This error could occur only during queue manager startup. Probably, an ESTAE could not be established because of a shortage of LSQA space.
The queue manager is terminated.
Restart the queue manager.
If the problem persists, increase the size of the queue manager address space private area.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The queue manager is terminated. A SYS1.LOGREC entry and associated SVC dump were requested.
Restart the queue manager.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated with an SVC dump.
Restart the queue manager.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during the processing of an identify SSI call. This can occur if the current address space has insufficient storage.
The allied address space is ended abnormally (without a dump). A dump should be produced by the allied task.
The user can retry the identify request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An ESTAE could not be established during the processing of an identify SSI call. This can occur if the current address space has insufficient storage.
The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.
The user can retry the identify request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An ESTAE could not be established during the processing of an identify SSI call. This can occur if the current address space has insufficient storage.
The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.
The user can retry the identify request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
ESTAEs could not be established during the processing of a n SSI call other than FEOT, EOM, HELP, COMMAND, and IDENTIFY. This can occur if the current address space has insufficient storage.
The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.
The user can retry the request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The allied task is ended abnormally.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during the processing of an identify termination request. This can occur if the current address space has insufficient storage.
The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.
The user can retry the request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The calling task is ended abnormally.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The caller is ended abnormally. The error might, in many cases, eventually terminate the queue manager.
Restart the queue manager if necessary.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager is terminated with a reason code of X'00F30420'.
Restart the queue manager.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
The queue manager was unable to successfully restart with RRS because of an internal error in either MQ or RRS.
The queue manager is not connected to RRS and all services dependent on that connection are unavailable. This means that applications might not connect to the queue manager using RRSAF and that WLM-established address spaces might not be used for MQ stored procedures until the queue manager successfully restarts with RRS.
Stop and then start RRS. Stop and then start the queue manager. If the problem persists, perform an RRS cold start.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The requester is ended abnormally, and the request is not processed.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
CSQ6SYSP is missing from the system parameter load module.
Queue manager start-up is terminated.
Recreate your system parameter load module (if a customized version is being used) and restart the queue manager. For information about the coding procedure for system parameter modules, see the WebSphere MQ for z/OS System Setup Guide.
An internal error has occurred.
The requester is ended abnormally, and the request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The requester is ended abnormally.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The queue manager ends abnormally. The startup/shutdown ESTAE creates a SYS1.LOGREC entry and takes an SVC dump.
Restart the queue manager.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The allied task is ended abnormally, and the request is not processed.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The connection name associated with the error is probably unable to continue communication with MQ until the queue manager is terminated and restarted.
If necessary, stop and restart the queue manager.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
Asynchronous events occurred which caused the premature termination of the thread. The thread could not be recovered.
There might be other errors or messages concerning this allied user indicating what the asynchronous events were.
The allied user is ended abnormally with completion code X'5C6' and this reason code.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An ESTAE could not be established during the processing of an 'end stop-work force' notification. This can occur if there is insufficient storage. This might lead to abnormal termination of the queue manager.
The caller is ended abnormally. An SVC dump and related SYS1.LOGREC entry are requested.
If necessary, restart the queue manager.
If necessary, increase the private area size of the address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The queue manager is terminated. An SVC dump is requested.
Restart the queue manager.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An internal error has occurred.
The task is not ended abnormally.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
An ESTAE could not be established during the processing of an application program support call. This can occur if the current address space has insufficient storage.
The allied task is ended abnormally. The allied task might have requested an SVC dump.
The user can retry the request. If necessary, increase the private area size of the application address space.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An internal error has occurred.
The request might have been processed or rejected.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
MQ has lost its cross-memory authority to an allied address space because the ally has released its authorization index.
The allied address space is terminated.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
MQ has detected a recursive error condition while processing End-of-Task for a task in an allied address space.
The allied address space is terminated.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
An error has occurred while processing End-of-Task for the queue manager address space.
The address space is forced to 'end-of-memory' with this reason code.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
End-of-Task occurred for the queue manager address space, and MQ could not establish an ESTAE to protect its processing. Insufficient storage might be the reason the ESTAE could not be established.
The address space is forced to 'end-of-memory' with this reason code.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
Attempt to determine if one or more MQ address spaces is storage-constrained. Examination of the console output for the time period preceding this condition might reveal other messages or indications that the terminating address space was storage-constrained.
End-of-Task occurred for the job step task in an allied address space. MQ would normally attempt to terminate the address space's connection to the queue manager but was unable to protect its processing by establishing an ESTAE. Insufficient storage might be the reason the ESTAE could not be established.
The address space is forced to 'end-of-memory' with this reason code.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
Attempt to determine if one or more allied address spaces is storage-constrained. Examination of the console output for the time period preceding this condition might reveal other messages or indications that the terminating allied address space was storage-constrained.
The MQ thread is read-only.
A prepare issued by the application program was processed through Phase-1. MQ discovered there were no resources modified and no need for COMMIT or BACKOUT to be subsequently issued.
This might create a path length saving by not issuing the subsequent commit or backout which normally follows prepare. No further action is required to complete the unit of recovery; the unit of recovery is complete.
Collect the following diagnostic items:
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0444 |