If a message manager reason code occurs that is not listed here, an internal error has occurred. Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a DEFINE or ALTER command for a queue.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a DEFINE or ALTER command for a process.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a DEFINE or ALTER command for a queue.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while attempting to establish a processing environment for the command processors.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while attempting to establish a processing environment.
The current execution unit terminates with completion code X'5C6'
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An attempt to write a trigger message to the initiation queue or the dead-letter queue was unsuccessful because of an internal error (for example, a storage overwrite).
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a DEFINE CHANNEL or ALTER command for a channel.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An attempt to write a message to a queue was unsuccessful because of an internal error (for example, a storage overwrite).
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a channel command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
The report option requested in a message was not recognized.
The current execution unit terminates with completion code X'5C6'. A dump is produced.
Correct the value of the report option field (the value specified is given in register 2).
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a STGCLASS command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination. Also collect details of the queue-sharing group (QSG) and of the queue managers active, as well as the queue managers defined to the QSG at the time of the error. This information can be obtained by entering the following z/OS commands:
D XCF,GRP
to display a list of all QSGs in the Coupling Facility.
D XCF,GRP,qsg-name,ALL
to display status about the queue managers defined to QSG qsg-name. Contact your IBM support center.
An internal error has occurred while processing a DEFINE CFSTRUCT or ALTER CFSTRUCT or DELETE CFSTRUCT command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing an AUTHINFO command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred while processing a DEFINE MAXSMSGS or ALTER QMGR command.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal processing error has occurred. The repository cannot locate an object that it has been asked to release.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal processing error has occurred while attempting to create the queue manager object during end restart processing.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'. The IGQ agent then attempts to recover.
If the IGQ agent fails to recover properly, an attempt could be made to disable the SYSTEM.QSG.TRANSMIT.QUEUE to force the IGQ agent to enter retry, or if this fails, the IGQ agent task can be restarted by issuing an ALTER QMGR IGQ(ENABLED) command or by restarting the queue manager.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination together with a dump of the coupling facility list structure that the shared queue is defined to use, and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination. Also collect details of the queue-sharing group (QSG) and of the queue managers active, as well as the queue managers defined to the QSG at the time of the error. This information can be obtained by entering the following z/OS commands:
D XCF,GRP
to display a list of all QSGs in the Coupling Facility.
D XCF,GRP,qsg-name,ALL
to display status about the queue managers defined to QSG qsg-name. Contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred during shared channel recovery.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
The recovery process is terminated; some channels may have been recovered, while others have not. Any channels that were not recovered will be recovered when the recovery process next runs; alternatively, they can be restarted manually. See the WebSphere MQ Intercommunication manual for more information about shared channel recovery.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'. In some cases, the queue manager may terminate with completion code X'6C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
Restart the queue manager if necessary.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination. Also collect details of the queue-sharing group (QSG) and of the queue managers active, as well as the queue managers defined to the QSG at the time of the error. This information can be obtained by entering the following z/OS commands:
D XCF,GRP
to display a list of all QSGs in the Coupling Facility.
D XCF,GRP,qsg-name,ALL
to display status about the queue managers defined to QSG qsg-name. Contact your IBM support center.
An internal error has occurred invloving the cluster cache.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and the channel initiator job log, and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
Restart the queue manager if necessary.
An internal error has occurred invloving the cluster cache.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and the channel initiator job log, and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
Restart the queue manager if necessary.
An internal error has occurred invloving the cluster cache.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and the channel initiator job log, and contact your IBM support center.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
Restart the queue manager if necessary.
Whilst processing a get message request, the specified search type (message identifier or correll identifier) was found to be in error. This indicates a data corruption error.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that an object of the specified name exists, but is of a different subtype; it might not necessarily have the same disposition in the queue-sharing group. This can only occur with subtypes of queues or channels. Message CSQM099I is also issued, indicating the object in error.
8
The command is ignored.
Reissue the command, ensuring that all object subtypes are correct.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that the object specified on the request could not be located. Message CSQM094I or message CSQM125I is also issued, indicating the object in error.
It is also issued in message CSQM086E, indicating that the queue manager object could not be located.
8
For CSQM090E, the command is ignored. For CSQM086E, the queue manager fails to restart.
If you are using a queue-sharing group, check that DB2 is available and not suspended. Define the object in question. For the queue manager, reissue the START QMGR command to restart the queue manager.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that the object specified on the request already exists. This will only arise when trying to define a new object. Message CSQM095I is also issued.
8
The command is ignored.
Use the object in question.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that one or more of the keywords on the command failed the parameter validation rules that apply to them. One or more other more specific messages are also issued, indicating the reason for the validation failure.
8
The command is ignored.
Refer to the more specific associated message to determine what the error is.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that either:
8
The command is ignored.
Refer to the description of message CSQM101I, CSQM110I, or CSQM115I as appropriate.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that a request has been issued to delete a local queue. The PURGE option has not been specified, but there are messages on the queue. Message CSQM103I is also issued.
8
The command is ignored.
If the local queue must be deleted, even though there are messages on it, reissue the command with the PURGE option.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that a request has been issued for a local queue that is dynamic, but this queue has been flagged for deletion. Message CSQM104I is also issued.
8
The command is ignored.
None, the local queue will be deleted as soon as possible.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that the object specified on the request needs updating because the MQ version has changed, but that this cannot be done because the object is currently open. Message CSQM101I is also issued.
8
The command is ignored.
Wait until the object is closed and reissue the command.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM112E or message CSQM117E indicating the object in error. It is also issued in message CSQM086E during queue manager restart.
This code indicates that a request has been issued for an object, but the object information could not be accessed because of an error on page set zero.
8
The command is ignored or the queue manager fails to restart.
Check for error messages on the console log that might relate to the problem. Verify that page set zero is set up correctly; refer to the WebSphere MQ for z/OS System Administration Guide for information about this.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM113E indicating the object in error. It is also issued in message CSQM086E during queue manager restart. This code indicates that a request has been issued for an object, but page set zero is full.
8
The command is ignored or the queue manager fails to restart.
Increase the size of page set zero. Refer to the WebSphere MQ for z/OS System Administration Guide for information about how to do this.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM114E. This code indicates that a request has been issued for a local queue, but no more local queues could be defined. There is an implementation limit of 524 287 for the total number of local queues that can exist. For shared queues, there is a limit of 512 queues in a single coupling facility structure, and 512 structures altogether.
4
The command is ignored.
Delete any existing queues that are no longer required.
This reason code is issued in message CSQM090E when a command has failed. It indicates that the command is not allowed for a particular subtype of an object, as shown in the accompanying more specific message.
4
The command is ignored.
Reissue the command with the object name specified correctly.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM127I. This code indicates that a request was issued specifying a namelist as a list of cluster names, but there are no names in the namelist.
8
The command is ignored.
Specify a namelist that is not empty.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM112E or message CSQM117E indicating the object in error. It is also issued in message CSQM086E during queue manager restart. This code indicates that a request has been issued for an object, but that a page set that it requires is not defined.
8
The command is ignored or the queue manaager fails to restart.
Ensure that the necessary page set is defined in the initialization input data set CSQINP1, and has a DD statement in the queue manager started task JCL procedure. Restart the queue manager.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM112E or message CSQM117E indicating the object in error. It is also issued in message CSQM086E during queue manager restart. This code indicates that a request has been issued for an object, but that a page set that it requires is not open.
8
The command is ignored or the queue manager fails to restart.
Ensure that the necessary page set is defined in the initialization input data set CSQINP1, and has a DD statement in the queue manager started task JCL procedure. Restart the queue manager.
This reason code is issued in message CSQM090E when a command has failed. This code indicates that a request was issued to change the default transmission queue for the queue manager, but the queue is already in use.
8
The command is ignored.
Wait until the queue is no longer in use, or choose another queue.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM128E. This code indicates that a request was issued that required a message to be sent to a command queue, but the message could not be put.
8
The command is ignored.
Resolve the problem with the command queue.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM160I indicating the object in error.
8
The command is ignored.
See message CSQM160I for more information.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM161I.
8
The command is ignored.
See message CSQM161I for more information.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM164I indicating the object in error.
8
The command is ignored.
See message CSQM164I for more information.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM163I indicating the object in error.
8
The command stops processing.
See message CSQM163I for more information.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM112E or message CSQM117E indicating the object in error. It is also issued in message CSQM086E during queue manager restart.
This code indicates that a request has been issued for an object, but the object information could not be accessed because coupling facility structure has failed.
8
The command is ignored or the queue manager fails to restart.
Check for error messages on the console log that might relate to the problem. Use the RECOVER CFSTRUCT command to recover the coupling facility structure.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM112E or message CSQM117E indicating the object in error. It is also issued in message CSQM086E during queue manager restart.
This code indicates that a request has been issued for an object, but the object information could not be accessed because there is an error or inconsistency in the coupling facility information.
8
The command is ignored or the queue manager fails to restart.
Check for error messages on the console log that might relate to the problem. Check that DB2 is available and not suspended. If the problem persists, it may be necessary to restart the queue manager.
This reason code is issued in message CSQM090E when a command has failed, and is accompanied by message CSQM112E or message CSQM117E indicating the object in error. It is also issued in message CSQM086E during queue manager restart.
This code indicates that a request has been issued for an object, but the object information could not be accessed because DB2 is not available or is suspended.
8
The command is ignored or the queue manager fails to restart.
Check for error messages on the console log that might relate to the problem. Check that DB2 is available and not suspended.
An internal error has occurred.
The current execution unit terminates with completion code X'5C6'.
Collect the items listed in Message manager problem determination and contact your IBM support center.
Collect the following diagnostic items:
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq0515 |