![[z/OS]](ngzos.gif)
Command server messages (CSQN...)
- CSQN001I
-
COMMAND SERVER STARTED
- Severity
- 0
- Explanation
-
A request to start the command server with the START CMDSERV command has been accepted.
- System action
-
The command server is triggered to start.
- CSQN002I
-
COMMAND SERVER ALREADY STARTED
- Severity
- 0
- Explanation
-
A START CMDSERV command has been entered, but the command server is already running.
- System action
-
The command is ignored.
- CSQN003I
-
COMMAND SERVER ENABLED
- Severity
- 0
- Explanation
-
In response to a START CMDSERV command in an initialization file, the command server has been put in to an enabled state.
- System action
-
The command server will be started automatically when initialization finishes.
- CSQN004I
-
COMMAND SERVER ALREADY ENABLED
- Severity
- 0
- Explanation
-
A START CMDSERV command has been entered, but the command server was already enabled.
- System action
-
The command is ignored.
- CSQN005I
-
COMMAND SERVER STOPPED
- Severity
- 0
- Explanation
-
A request to stop the command server with a STOP CMDSERV command has been accepted.
- 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.
- CSQN006I
-
COMMAND SERVER ALREADY STOPPED
- Severity
- 0
- Explanation
-
A STOP CMDSERV command was entered, but the command server was not running.
- System action
-
The command is ignored.
- CSQN007I
-
COMMAND SERVER DISABLED
- Severity
- 0
- Explanation
-
In response to a STOP CMDSERV command in an initialization file, the command server has been put in to a disabled state.
- System action
-
The command server will not start automatically when initialization finishes.
- CSQN008I
-
COMMAND SERVER ALREADY DISABLED
- Severity
- 0
- Explanation
-
A STOP CMDSERV command has been entered, but the command server was already disabled.
- System action
-
The command is ignored.
- CSQN009I
-
csect-nameverb-namepkw-name COMMAND DISABLED
- Severity
- 4
- Explanation
-
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.
- System action
-
The command is ignored.
- CSQN011I
-
COMMAND SERVER STATUS IS ENABLED
- Severity
- 0
- Explanation
-
The command server is in an enabled state; that is, the command server will be started automatically when initialization finishes.
- CSQN012I
-
COMMAND SERVER STATUS IS DISABLED
- Severity
- 0
- Explanation
-
The command server is in a disabled state; that is, the command server will not be started automatically when initialization finishes.
- CSQN013I
-
COMMAND SERVER STATUS IS RUNNING
- Severity
- 0
- Explanation
-
The command server is in a running state; that is, the command server is currently processing a command.
- CSQN014I
-
COMMAND SERVER STATUS IS WAITING
- Severity
- 0
- Explanation
-
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.
- CSQN015I
-
COMMAND SERVER STATUS IS STOPPED
- Severity
- 0
- Explanation
-
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.
- CSQN016I
-
COMMAND SERVER STATUS IS STARTING
- Severity
- 0
- Explanation
-
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.
- CSQN017I
-
COMMAND SERVER STATUS IS STOPPING
- Severity
- 0
- Explanation
-
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.
- CSQN018E
-
csect-name INTERNAL ERROR FOR identifier, RETURN CODE=rc
- Severity
- 8
- Explanation
-
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.
- 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 IBM® Support to report the problem.
- CSQN019E
-
csect-name INTERNAL ERROR FOR identifier, RETURN CODE=rc
- Severity
- 8
- Explanation
-
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.
- 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 IBM Support.
- CSQN020E
-
csect-name UNABLE TO START COMMAND SERVER identifier
- Severity
- 8
- Explanation
-
csect-name was unable to start the command server task identifier.
- 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 IBM Support with details of this message, any previous messages pertaining to this error, and the dump (if applicable).
- CSQN021E
-
csect-name COMMAND SERVER identifier ABNORMAL COMPLETION
- Severity
- 8
- Explanation
-
The command server task identifier was unable to complete its processing during startup.
- 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.
- CSQN100I
-
COMMAND EXCEEDS MAXIMUM SIZE, COMMAND IGNORED
- Severity
- 4
- Explanation
-
The command string was too long.
- 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 Initialization commands.
- CSQN101I
-
COMMAND ENDS WITH A CONTINUATION MARK, COMMAND IGNORED
- Severity
- 4
- Explanation
-
The last command in the CSQINP1 or CSQINP2 data set ended with a continuation mark.
- 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 Initialization commands.
- CSQN102I
-
COMMAND BUFFER INVALID, ERROR UNKNOWN, COMMAND IGNORED
- Severity
- 4
- Explanation
-
An internal error has occurred.
- 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 IBM Support.
- CSQN103I
-
COMMAND PROCESSOR RETURN CODE=rc, REASON CODE=reason
- Severity
- 4
- Explanation
-
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
- See 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
- 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 IBM MQ for z/OS messages, completion, and reason codes for further information about the commands.
If you are unable to solve the problem, collect the input and output data sets and contact IBM Support.
- CSQN104I
-
INITIALIZATION RETURN CODE=rc, REASON CODE=reason
- Severity
- 8
- Explanation
-
An error occurred while processing one of the initialization data sets.
- System action
-
The system action depends on the reason code (reason). See 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). See Command server codes (X'D5') for information about the code you have received.
- CSQN105I
-
Commands from ddname for queue manager qmgr-name - date time
- Severity
- 0
- Explanation
-
This message forms the header for the output data sets CSQOUT1 and CSQOUT2.
- CSQN121I
- 'verb-namepkw-name' command responses from qmgr-name
- Explanation
-
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-namepkw-name' command for CMDSCOPE(qmgr-name) normal completion
- Explanation
-
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 completion
- Explanation
-
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 might 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.
- CSQN127E
-
Queue sharing group error, reason=reason
- Severity
- 8
- Explanation
-
While processing a command that specified CMDSCOPE, the command server experienced an error while trying to send data to the coupling facility.
- System action
-
The command is not processed.
- System programmer response
-
The response you should make depends on the reason code (reason). See Coupling Facility codes (X'C5') for information about the code.
- CSQN128E
- Insufficient 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 might need to restart the queue manager after making more storage available.
- CSQN129E
-
Error saving command reply information
- Severity
- 8
- Explanation
-
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.
- 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.
- CSQN130E
- Command 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.
- CSQN131E
- CMDSCOPE(qmgr-name) not allowed during restart
- Explanation
-
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.
- CSQN132E
- CMDSCOPE(qmgr-name) not allowed with disposition disposition
- Explanation
-
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.
- CSQN133E
- CMDSCOPE(qmgr-name) not allowed, command server unavailable
- Explanation
-
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.
- CSQN135E
- Queue manager qmgr-name not active in queue sharing group
- Explanation
-
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.
- CSQN136E
- Not in queue sharing group
- Explanation
-
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 n
- Explanation
-
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 n
- Explanation
-
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
-
Processing continues.
- CSQN201I
-
COMMAND SERVER IS SHUTTING DOWN
- Severity
- 0
- Explanation
-
This message confirms that the command server is shutting down after an error.
- System action
-
The command server shuts down and will not process any more commands.
- System programmer response
-
Correct the errors reported in the preceding messages, and use the START CMDSERV command to restart the command server.
- CSQN202I
-
COMMAND SERVER RETURN CODE=rc, REASON=reason
- Severity
- 8
- Explanation
-
An error occurred in the command server, as indicated by the preceding messages.
- System action
-
The system action depends on the reason code (reason). See Command server codes (X'D5') or Coupling Facility codes (X'C5') for information about the code.
- System programmer response
-
The response you should make depends on the reason code (reason).
The return code rc is dependent on reason, and is of use to IBM service personnel.
- CSQN203I
-
QUEUE queuename, MQCC=mqcc MQRC=mqrc (mqrc-text)
- Severity
- 8
- Explanation
-
An API call, as indicated in the preceding message, did not complete successfully. The completion code is mqcc, and the reason code is mqrc (mqrc-text provides the MQRC in textual form).
- System programmer response
-
For more information, see API completion and reason codes.
If you are unable to resolve the problem, note the numbers of any messages and codes associated with the error, and contact IBM Support.
Reason codes above 8000 are internal queue manager error codes. If such a code persists, report it to IBM Support.
- CSQN205I
-
COUNT=count, RETURN=rc, REASON=reason
- Severity
- 0
- Explanation
-
This message reports the results from the command processor (refer to the section Writing programs to administer IBM MQ for further information). count is the number of messages (including this one) to be written to the reply-to queue in response to the command. Possible values of rc are as follows:
- Return code
- Description
- 00000000
- Normal completion
- 00000004
- Internal error
- 00000008
- Syntax or command preprocessor error, see the following messages
- 0000000C
- Command processor error, see the following messages
- 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, check userid authority
- 00000024
- Command too long, see the following messages
- 00000028
- Queue sharing group error, see the following messages
- 00D5xxxx
- See 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 set of reply messages is incomplete. Further sets of messages, each including another CSQN205I message, will be produced later. The results of the command will be shown by the codes in the CSQN205I message included with the final set of messages.
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
- 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 IBM MQ for z/OS messages, completion, and reason codes for further information about the commands.
If you are unable to solve the problem, collect the input and output data sets and contact IBM Support.
- CSQN206I
-
COMMAND SERVER ECBLIST, STOP=ecb1, WAIT=ecb2
- Severity
- 8
- Explanation
-
This message reports the ECB values associated with an error in the command server.
- System action
-
The command server terminates.
- System programmer response
-
This message is usually preceded by a CSQN202I message. Refer to the preceding messages for more information about the cause of the problem.
- CSQN207I
- COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE
- Explanation
-
The command server was unable to open the reply-to queue while processing a command.
- System action
-
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQOPEN request.
If possible, the command server sends the response message to the dead-letter queue, otherwise the response is discarded.
- System programmer response
-
For more information, see API completion and reason codes. Use this information to solve the problem, and restart the command server. If this does not help you to solve the problem, collect the following items, and contact IBM Support.
- Return and reason codes from the message produced
- Any trace information collected
- CSQN208E
- COMMAND SERVER UNABLE TO OPEN COMMAND INPUT QUEUE
- Explanation
-
The command server was unable to open the system-command input queue while starting.
- System action
-
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQOPEN request. The command server stops, without processing any commands.
- System programmer response
-
For more information, see API completion and reason codes. Use this information to solve the problem, and restart the command server. If this does not help you to solve the problem, collect the following items, and contact IBM Support.
- Return and reason codes from the message produced
- Any trace information collected
- CSQN209E
- COMMAND SERVER ERROR CLOSING COMMAND INPUT QUEUE
- Explanation
-
While the command server was shutting down, an error occurred when closing the system-command input queue.
- System action
-
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQCLOSE request. The shutdown procedure continues.
- System programmer response
-
For more information, see API completion and reason codes. If this does not help you to solve the problem, collect the following items, and contact IBM Support:
- Return and reason codes from the message produced
- Any trace information collected
- CSQN210E
- COMMAND SERVER ERROR CLOSING REPLY TO QUEUE
- Explanation
-
The command server was unable to close the reply-to queue while processing a command.
- System action
-
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQCLOSE request.
The command server continues.
- System programmer response
-
For more information, see API completion and reason codes.
- CSQN211E
- COMMAND SERVER ERROR GETTING FROM COMMAND INPUT QUEUE
- Explanation
-
The command server experienced an error while trying to get a message from the system-command input queue.
- System action
-
Message CSQN203I is sent to the z/OS console, reporting the completion and reason codes from the MQGET request.
The command server terminates.
- System programmer response
-
For more information, see API completion and reason codes. Use this information to solve the problem, and restart the command server. If this does not help you to solve the problem, collect the following items, and contact IBM Support:
- Return and reason codes from the console message
- Any trace information collected
- CSQN212E
- COMMAND SERVER ERROR PUTTING TO REPLY TO QUEUE
- Explanation
-
The command server was unable to put a response message onto a reply-to queue while processing a command.
- System action
-
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQPUT request. If possible, the command server sends the response message to the dead-letter queue, otherwise the response is discarded.
The command server continues.
- System programmer response
-
For more information, see API completion and reason codes. If this does not help you to solve the problem, collect the following items, and contact IBM Support:
- Return and reason codes from the message produced
- Any trace information collected
- CSQN213E
- COMMAND SERVER ERROR, COMMAND INPUT QUEUE DISABLED
- Explanation
-
While waiting for a command the system-command input queue has been disabled.
- System action
-
Message CSQN203I is sent to the console containing the return and reason codes from the request function. The command server terminates.
- System programmer response
-
Change the system-command input queue to be enabled, and issue the START CMDSERV command.
If the problem persists, collect the following items, and contact IBM Support:- Return and reason codes
- Any trace data collected
- Printout of SYS1.LOGREC
- CSQN219E
-
Unable to find command reply information
- Severity
- 8
- Explanation
-
While processing responses from a command that specified CMDSCOPE or a command for the channel initiator, the command server could not find the information to determine where to send the responses.
- System action
-
The command might not be processed; any command responses are discarded. The command server continues.
- System programmer response
-
If the problem persists, contact IBM Support with details of this message, any previous messages pertaining to this error, and the dump (if applicable).
- CSQN220E
- Error monitoring CMDSCOPE command data
- Explanation
-
The command server experienced an error while monitoring command data in the coupling facility.
- System action
-
Message CSQN202I is sent to the z/OS console, reporting the return and reason codes from the request.
The command server terminates.
- System programmer response
-
See Coupling Facility codes (X'C5') for information about the reason code. Use this information to solve the problem, and restart the command server. If this does not help you to solve the problem, collect the following items, and contact IBM Support:
- Return and reason codes from the console message
- Any trace information collected
- CSQN221E
- Error receiving CMDSCOPE command data
- Explanation
-
The command server experienced an error while trying to get command data from the coupling facility.
- System action
-
Message CSQN202I is sent to the z/OS console, reporting the return and reason codes from the request.
The command server terminates.
- System programmer response
-
See Coupling Facility codes (X'C5') for information about the reason code. Use this information to solve the problem, and restart the command server. If this does not help you to solve the problem, collect the following items, and contact IBM Support:
- Return and reason codes from the console message
- Any trace information collected
- CSQN222E
- Error sending CMDSCOPE command data
- Explanation
-
The command server experienced an error while trying to send command data to the coupling facility.
- System action
-
Message CSQN202I is sent to the z/OS console, reporting the return and reason codes from the request.
The command server terminates.
- System programmer response
-
See Coupling Facility codes (X'C5') for information about the reason code. Use this information to solve the problem, and restart the command server. If this does not help you to solve the problem, collect the following items, and contact IBM Support:
- Return and reason codes from the console message
- Any trace information collected
- CSQN223E
- Insufficient storage for CMDSCOPE command data
- Explanation
-
The command server was unable to obtain storage needed for command data in the coupling facility.
- System action
-
The command server terminates.
- System programmer response
-
Use the START CMDSERV command to restart the command server. If the problem persists, you might need to restart the queue manager after making more storage available.
- CSQN224E
-
GROUP COMMAND SERVER ENDED ABNORMALLY. RESTARTING
- Severity
- 8
- Explanation
-
The Group Command Server has ended abnormally because a severe error occurred.
- System action
-
The Group Command Server is automatically restarted.
- System programmer response
-
Investigate the reason for abnormal termination. If the problem persists contact IBM Support.