A request to start the command server with the START CMDSERV command has been accepted.
0
The command server is triggered to start. This message should be followed by message CSQN200I which indicates that the command server is starting up.
A START CMDSERV command has been entered, but the command server is already running.
0
The command is ignored.
In response to a START CMDSERV command in an initialization file, the command server has been put in to an enabled state.
0
The command server will be started automatically when initialization finishes.
A START CMDSERV command has been entered, but the command server was already enabled.
0
The command is ignored.
A request to stop the command server with a STOP CMDSERV command has been accepted.
0
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.
A STOP CMDSERV command was entered, but the command server was not running.
0
The command is ignored.
In response to a STOP CMDSERV command in an initialization file, the command server has been put in to a disabled state.
0
The command server will not start automatically when initialization finishes.
A STOP CMDSERV command has been entered, but the command server was already disabled.
0
The command is ignored.
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.
4
The command is ignored.
The command server is in an enabled state; that is, the command server will be started automatically when initialization finishes.
0
The command server is in a disabled state; that is, the command server will not be started automatically when initialization finishes.
0
The command server is in a running state; that is, the command server is currently processing a command.
0
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.
0
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.
0
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.
0
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.
0
This message could be caused by the following:
8
The task is not started.
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.
This message could be caused by the following:
8
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.
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.
csect-name was unable to start the command server task identifier.
8
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.
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).
The command server task identifier was unable to complete its processing during startup.
8
Queue manager startup continues.
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.
The command string was too long.
4
The command is ignored, and processing of CSQINP1 or CSQINP2 continues.
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.
The last command in the CSQINP1 or CSQINP2 data set ended with a continuation mark.
4
The command is ignored.
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.
An internal error has occurred.
4
This command is ignored, and the next command is processed.
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.
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:
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:
4
The next command is processed, if possible.
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.
An error occurred while processing one of the initialization data sets.
8
The system action depends on the reason code (reason). Refer to Command server codes (X'D5') for information the code you have received.
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.
This message forms the header for the output data sets CSQOUT1 and CSQOUT2.
0
The following messages are responses from queue manager qmgr-name to the indicated command - either entered or generated by another command - that specified CMDSCOPE.
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.
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.
Examine the preceding responses from the command. Reissue the command correctly if necessary for the queue managers where it failed.
While processing a command that specified CMDSCOPE, the command server experienced an error while trying to send data to the coupling facility.
8
The command is not processed.
The response you should make depends on the reason code (reason). Refer to Coupling Facility codes (X'C5') for information about the code.
While processing a command that specified CMDSCOPE, the command server was unable to obtain storage needed.
The command is not processed.
If the problem persists, you may need to restart the queue manager after making more storage available.
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.
8
The command is not processed.
The most likely cause is insufficient storage. If the problem persists, you may need to restart the queue manager after making more storage available.
A command that specified CMDSCOPE(qmgr-name) was too long.
The command is not processed.
Reissue the command correctly.
A command that specified CMDSCOPE(qmgr-name) was issued in the initialization input data set CSQINP1. This is not allowed.
The command is not processed.
Reissue the command later.
A command that specified CMDSCOPE(qmgr-name) with QSGDISP(disposition) or CHLDISP(disposition) was issued. This combination of values is not allowed.
The command is not processed.
Reissue the command correctly.
A command that specified CMDSCOPE(qmgr-name) was entered or generated by another command, but the command server is not running and not enabled.
The command is not processed.
Use the START CMDSERV command to start the command server, and reissue the command.
A command specifying CMDSCOPE(qmgr-name) was entered or generated by another command, but that queue manager is not currently active in the group.
The command is not processed.
Start the queue manager and reissue the command if required.
A command that requires a queue-sharing group was entered, but the queue manager is not in a group.
The command is not processed.
Reissue the command correctly.
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.
Processing continues.
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.
Processing continues.
This message confirms that the command server is shutting down after an error.
0
The command server shuts down and will not process any more commands.
Correct the errors reported in the preceding messages, and use the START CMDSERV command to restart the command server.
An error occurred in the command server, as indicated by the preceding messages.
8
The system action depends on the reason code (reason). Refer to Command server codes (X'D5') or Coupling Facility codes (X'C5') for information about the code.
The response you should make depends on the reason code (reason).
The return code rc is dependant on reason, and is of use to IBM service personnel.
An API call, as indicated in the preceding message, did not complete successfully. mqcc is the completion code, and mqrc is the reason code.
8
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
If you are unable to resolve the problem, note the numbers of any messages and codes associated with the error, and contact your IBM support center.
This message reports the results from the command processor (refer to the WebSphere MQ for z/OS System Administration Guide 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:
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:
0
The next command is processed, if possible.
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.
This message reports the ECB values associated with an error in the command server.
8
The command server terminates.
This message is usually preceded by a CSQN202I message. Refer to the preceding messages for more information about the cause of the problem.
The command server was unable to open the reply-to queue while processing a command.
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQOPEN request. The command responses are discarded.
Refer to Appendix A. API completion and reason codes for information about the 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 your IBM support center.
The command server was unable to open the system-command input queue while starting up.
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.
Refer to Appendix A. API completion and reason codes for information about the 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 your IBM support center.
While the command server was shutting down, an error occurred when closing the system-command input queue.
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQCLOSE request. The shutdown procedure continues.
Refer to Appendix A. API completion and reason codes for information about the completion and reason codes. If this does not help you to solve the problem, collect the following items, and contact your IBM support center:
The command server was unable to close the reply-to queue while processing a command.
Message CSQN203I is sent to the z/OS console reporting the completion and reason codes from the MQCLOSE request.
The command server continues.
Refer to Appendix A. API completion and reason codes for information about the completion and reason codes.
The command server experienced an error while trying to get a message from the system-command input queue.
Message CSQN203I is sent to the z/OS console, reporting the completion and reason codes from the MQGET request.
The command server terminates.
Refer to Appendix A. API completion and reason codes for information about the 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 your IBM support center:
The command server was unable to put a response message onto a reply-to queue while processing a command.
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.
Refer to Appendix A. API completion and reason codes for information about the completion and reason codes. If this does not help you to solve the problem, collect the following items, and contact your IBM support center:
While waiting for a command the system-command input queue has been disabled.
Message CSQN203I is sent to the console containing the return and reason codes from the request function. The command server terminates.
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 your IBM support center:
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.
8
The command may not be processed; any command responses are discarded. The command server continues.
If the problem persists, contact your IBM support center with details of this message, any previous messages pertaining to this error, and the dump (if applicable).
The command server experienced an error while monitoring command data in the coupling facility.
Message CSQN202I is sent to the z/OS console, reporting the return and reason codes from the request.
The command server terminates.
Refer to 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 your IBM support center:
The command server experienced an error while trying to get command data from the coupling facility.
Message CSQN202I is sent to the z/OS console, reporting the return and reason codes from the request.
The command server terminates.
Refer to 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 your IBM support center:
The command server experienced an error while trying to send command data to the coupling facility.
Message CSQN202I is sent to the z/OS console, reporting the return and reason codes from the request.
The command server terminates.
Refer to 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 your IBM support center:
The command server was unable to obtain storage needed for command data in the coupling facility.
The command server terminates.
Use the START CMDSERV command to restart the command server. If the problem persists, you may need to restart the queue manager after making more storage available.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0412 |