Command server messages (CSQN...)
CSQN001ICOMMAND SERVER STARTEDExplanation:A request to start the command server with the START CMDSERV command has been accepted.
Severity:0
System Action:The command server is triggered to start. This message should be followed by message CSQN200I which indicates that the command server is starting up.
CSQN002ICOMMAND SERVER ALREADY STARTEDExplanation:A START CMDSERV command has been entered, but the command server is already running.
Severity:0
System Action:The command is ignored.
CSQN003ICOMMAND SERVER ENABLEDExplanation:In response to a START CMDSERV command in an initialization file, the command server has been put in to an enabled state.
Severity:0
System Action:The command server will be started automatically when initialization finishes.
CSQN004ICOMMAND SERVER ALREADY ENABLEDExplanation:A START CMDSERV command has been entered, but the command server was already enabled.
Severity:0
System Action:The command is ignored.
CSQN005ICOMMAND SERVER STOPPEDExplanation:A request to stop the command server with a STOP CMDSERV command has been accepted.
Severity:0
System Action:The command server shuts down when it finishes processing the current command (or immediately if it is not processing a command). This message is followed by message CSQN201I to confirm that the stop has started.
CSQN006ICOMMAND SERVER ALREADY STOPPEDExplanation:A STOP CMDSERV command was entered, but the command server was not running.
Severity:0
System Action:The command is ignored.
CSQN007ICOMMAND SERVER DISABLEDExplanation:In response to a STOP CMDSERV command in an initialization file, the command server has been put in to a disabled state.
Severity:0
System Action:The command server will not start automatically when initialization finishes.
CSQN008ICOMMAND SERVER ALREADY DISABLEDExplanation:A STOP CMDSERV command has been entered, but the command server was already disabled.
Severity:0
System Action:The command is ignored.
CSQN009Icsect-name verb-name pkw-name COMMAND DISABLEDExplanation:The command was not processed because it was not allowed during this stage of initialization or termination. verb-name might include the command prefix (CPF). This depends on how the command was entered.
Severity:4
System Action:The command is ignored.
CSQN011ICOMMAND SERVER STATUS IS ENABLEDExplanation:The command server is in an enabled state; that is, the command server will be started automatically when initialization finishes.
Severity:0
CSQN012ICOMMAND SERVER STATUS IS DISABLEDExplanation:The command server is in a disabled state; that is, the command server will not be started automatically when initialization finishes.
Severity:0
CSQN013ICOMMAND SERVER STATUS IS RUNNINGExplanation:The command server is in a running state; that is, the command server is currently processing a command.
Severity:0
CSQN014ICOMMAND SERVER STATUS IS WAITINGExplanation:The command server is in a waiting state; that is, the command server is waiting for a message to be put onto the system-command input queue.
Severity:0
CSQN015ICOMMAND SERVER STATUS IS STOPPEDExplanation:The command server is in a stopped state; that is, the command server will not process any commands until a START CMDSERV command is entered.
Severity:0
CSQN016ICOMMAND SERVER STATUS IS STARTINGExplanation:The command server is in a starting state; that is, a START CMDSERV command has been entered, but the command server has not yet started up.
Severity:0
CSQN017ICOMMAND SERVER STATUS IS STOPPINGExplanation:The command server is in a stopping state; that is, a STOP CMDSERV command has been entered, but the command server has not yet stopped.
Severity:0
CSQN018Ecsect-name INTERNAL ERROR FOR identifier, RETURN CODE=rcExplanation:This message could be caused by the following:
- Identifier
- Description
- INSSRV01
- During the early part of initialization, the queue manager was unable to start the task that processes commands in CSQINP1.
- INSSRV02
- During the later part of initialization, the queue manager was unable to start the task that processes commands in CSQINP2.
- RTSSRV01
- After initialization has completed with the command server enabled, or in response to a START CMDSERV command, the queue manager was unable to start the command server task that processes commands in the system-command input queue.
- GRSSRV01
- After initialization has completed with the command server enabled, or in response to a START CMDSERV command, the queue manager was unable to start the command server task that processes commands using CMDSCOPE.
Severity:8
System Action:The task is not started.
System Programmer Response:Stop and restart the queue manager. Check the console for other messages regarding this error, and note the message number, identifier, and rc. Also collect the system dump (if one was produced). Contact your IBM support center to report the problem.
CSQN019Ecsect-name INTERNAL ERROR FOR identifier, RETURN CODE=rcExplanation:This message could be caused by the following:
- Identifier
- Description
- INSSRV01
- During the early part of initialization an error occurred when trying to delete the task that processes commands in CSQINP1.
- INSSRV02
- During the later part of initialization an error occurred when trying to delete the task that processes commands in CSQINP2.
- RTSSRV01
- During termination with the command server running, or in response to a START CMDSERV command, an error occurred when trying to delete the command server task that processes commands in the system-command input queue.
- GRSSRV01
- During termination with the command server running, or in response to a START CMDSERV command, an error occurred when trying to delete the command server task that processes commands using CMDSCOPE.
Severity:8
System Action:If the value of identifier was INSSRV01 or INSSRV02, the error is ignored, and startup continues.
If the value of identifier was RTSSRV01 or GRSSRV01 and csect-name was CSQNESTP, the command server could have terminated while processing a command.
System Programmer Response:Check the console for other messages regarding this error. If you are unable to resolve the problem, note the message number, identifier, and rc, collect the system dump (if one was produced), and contact your IBM support center.
CSQN020Ecsect-name UNABLE TO START COMMAND SERVER identifierExplanation:csect-name was unable to start the command server task identifier.
Severity:8
System Action:If identifier is INSSRV01 or INSSRV02, initialization is not completed and a dump might be produced. In other cases, the command server is not started.
System Programmer Response:Stop and restart the queue manager. Contact your IBM support center with details of this message, any previous messages pertaining to this error, and the dump (if applicable).
CSQN021Ecsect-name COMMAND SERVER identifier ABNORMAL COMPLETIONExplanation:The command server task identifier was unable to complete its processing during startup.
Severity:8
System Action:Queue manager startup continues.
System Programmer Response:Check the z/OS console for related messages (probably concerning the CSQINPx data sets). The CSQOUTx data sets should also be checked to determine how much command processing was done before the error occurred. If required, reissue any unprocessed commands, or resolve the problem and restart the queue manager.
CSQN100ICOMMAND EXCEEDS MAXIMUM SIZE, COMMAND IGNOREDExplanation:The command string was too long.
Severity:4
System Action:The command is ignored, and processing of CSQINP1 or CSQINP2 continues.
System Programmer Response:The command in question precedes this message in the CSQOUT1 or CSQOUT2 data set. For details about forming a command string, see the WebSphere MQ for z/OS System Setup Guide.
CSQN101ICOMMAND ENDS WITH A CONTINUATION MARK, COMMAND IGNOREDExplanation:The last command in the CSQINP1 or CSQINP2 data set ended with a continuation mark.
Severity:4
System Action:The command is ignored.
System Programmer Response:The command in question precedes this message in the CSQOUT1 or CSQOUT2 data set. For details about forming a command string, see the WebSphere MQ for z/OS System Setup Guide.
CSQN102ICOMMAND BUFFER INVALID, ERROR UNKNOWN, COMMAND IGNOREDExplanation:An internal error has occurred.
Severity:4
System Action:This command is ignored, and the next command is processed.
System Programmer Response:The command in question precedes this message in the CSQOUT1 or CSQOUT2 data set. If you are unable to solve the problem, contact your IBM support center.
CSQN103ICOMMAND PROCESSOR RETURN CODE=rc, REASON CODE=reasonExplanation:An error occurred while processing the command preceding this message in the CSQOUT1 or CSQOUT2 data set. The possible values of rc are as follows:
- Return code
- Description
- 00000004
- Internal error
- 00000008
- Syntax or command preprocessor error, see the following lines in the CSQOUTx data set
- 0000000C
- Command processor error, see the following lines in the CSQOUTx data set
- 00000010
- Command processor abnormal termination
- 00000014
- Command completed, but there is insufficient storage for the messages
- 00000018
- Command preprocessor has insufficient storage (there could be further messages about this error)
- 0000001C
- The command processor has insufficient storage (the command could be partially completed)
- 00000020
- Security check
- 00D50102
- Refer to Command server codes (X'D5')
Note:If the return code is '00000010', the reason code has no meaning.If reason is 00000004 and return code is 00000000, the command has been accepted and will be completed later. Further messages will be produced when the command has been completed.
Otherwise the reason code indicates the command result as follows:
- Reason
- Description
- 00000000
- Command completed
- 00000004
- Partial completion
- 00000008
- Command not actioned
- 0000000C
- Command processor abend
- FFFFFFFF
- Command not actioned
Severity:4
System Action:The next command is processed, if possible.
System Programmer Response:If reason indicates that the command did not complete, examine the command and all associated messages. See the WebSphere MQ Script (MQSC) Command Reference manual for further information about the commands.
If you are unable to solve the problem, collect the input and output data sets and contact your IBM support center.
CSQN104IINITIALIZATION RETURN CODE=rc, REASON CODE=reasonExplanation:An error occurred while processing one of the initialization data sets.
Severity:8
System Action:The system action depends on the reason code (reason). Refer to Command server codes (X'D5') for information the code you have received.
System Programmer Response:The response you should make depends on the reason code (reason). Refer to Command server codes (X'D5') for information about the code you have received.
CSQN105ICommands from ddname for queue manager qmgr-name - date timeExplanation:This message forms the header for the output data sets CSQOUT1 and CSQOUT2.
Severity:0
CSQN121I'verb-name pkw-name' command responses from qmgr-nameExplanation:The following messages are responses from queue manager qmgr-name to the indicated command - either entered or generated by another command - that specified CMDSCOPE.
CSQN122I'verb-name pkw-name' command for CMDSCOPE(qmgr-name) normal completionExplanation:Processing for the indicated command that specified CMDSCOPE(qmgr-name) - either entered or generated by another command - has completed successfully on all requested queue managers.
CSQN123E'verb-name pkw-name' command for CMDSCOPE(qmgr-name) abnormal completionExplanation:Processing for the indicated command that specified CMDSCOPE(qmgr-name) - either entered or generated by another command - has completed, but not successfully. If the command was sent to more than one queue manager, it may have completed successfully on some and not on others.
System Programmer Response:Examine the preceding responses from the command. Reissue the command correctly if necessary for the queue managers where it failed.
CSQN127EQueue-sharing group error, reason=reasonExplanation:While processing a command that specified CMDSCOPE, the command server experienced an error while trying to send data to the coupling facility.
Severity:8
System Action:The command is not processed.
System Programmer Response:The response you should make depends on the reason code (reason). Refer to Coupling Facility codes (X'C5') for information about the code.
CSQN128EInsufficient storage for CMDSCOPE(qmgr-name)Explanation:While processing a command that specified CMDSCOPE, the command server was unable to obtain storage needed.
System Action:The command is not processed.
System Programmer Response:If the problem persists, you may need to restart the queue manager after making more storage available.
CSQN129EError saving command reply informationExplanation:While processing a command that specified CMDSCOPE or a command for the channel initiator, the command server experienced an error while trying to save information about the command.
Severity:8
System Action:The command is not processed.
System Programmer Response:The most likely cause is insufficient storage. If the problem persists, you may need to restart the queue manager after making more storage available.
CSQN130ECommand exceeds maximum size for CMDSCOPE(qmgr-name)Explanation:A command that specified CMDSCOPE(qmgr-name) was too long.
System Action:The command is not processed.
System Programmer Response:Reissue the command correctly.
CSQN131ECMDSCOPE(qmgr-name) not allowed during restartExplanation:A command that specified CMDSCOPE(qmgr-name) was issued in the initialization input data set CSQINP1. This is not allowed.
System Action:The command is not processed.
System Programmer Response:Reissue the command later.
CSQN132ECMDSCOPE(qmgr-name) not allowed with disposition dispositionExplanation:A command that specified CMDSCOPE(qmgr-name) with QSGDISP(disposition) or CHLDISP(disposition) was issued. This combination of values is not allowed.
System Action:The command is not processed.
System Programmer Response:Reissue the command correctly.
CSQN133ECMDSCOPE(qmgr-name) not allowed, command server unavailableExplanation:A command that specified CMDSCOPE(qmgr-name) was entered or generated by another command, but the command server is not running and not enabled.
System Action:The command is not processed.
System Programmer Response:Use the START CMDSERV command to start the command server, and reissue the command.
CSQN135EQueue manager qmgr-name not active in queue-sharing groupExplanation:A command specifying CMDSCOPE(qmgr-name) was entered or generated by another command, but that queue manager is not currently active in the group.
System Action:The command is not processed.
System Programmer Response:Start the queue manager and reissue the command if required.
CSQN136ENot in queue-sharing groupExplanation:A command that requires a queue-sharing group was entered, but the queue manager is not in a group.
System Action:The command is not processed.
System Programmer Response:Reissue the command correctly.
CSQN137I'verb-name pkw-name' accepted for CMDSCOPE(qmgr-name), sent to nExplanation:A command that specified CMDSCOPE was entered. It has been passed to the requested queue manager(s) for processing; n is the number of queue managers.
System Action:Processing continues.
CSQN138I'verb-name pkw-name' generated for CMDSCOPE(qmgr-name), sent to nExplanation:A command that specified CMDSCOPE was generated in response to the command originally entered. It has been passed to the indicated queue manager(s) for processing; n is the number of queue managers.
System Action: