If a command server reason code occurs that is not listed here, an internal error has occurred. Collect the items listed in Command server problem determination and contact your IBM support center.
During initialization, the command server was unable to obtain storage. This is probably because there is insufficient storage in your region.
Message CSQN104I is sent to the console containing this reason code and the return code from the internal storage macro. None of the commands in the initialization data set currently being processed are performed. Queue manager startup continues.
Check that you are running in a region that is large enough, and if not, reset your system and restart the queue manager. If this is not the cause of the problem, collect the following items and contact your IBM support center:
The command preprocessor ended abnormally while processing a command in the initialization input data set.
Message CSQ9029E is produced, followed by message CSQN103I with this code as the return code, and a reason code of -1 indicating that the command was not processed, and a dump is produced. The next command is processed.
Look in the output data set to determine the command in error. Check that the command is correctly formed, that it applies to a valid object.
If the command is correct, collect the items listed in Command server problem determination and contact your IBM support center.
During initialization, an internal error occurred.
Message CSQN104I is sent to the z/OS console, indicating the return and reason codes from the internal macro. The command server stops, without processing any commands.
Review the job log for messages about other errors that might be related. If you are unable to solve the problem, collect the items listed in Command server problem determination, and contact your IBM support center.
An internal error occurred during initialization.
Message CSQN104I is sent to the z/OS console, indicating the return and reason codes from the internal macro. The command server stops, without processing any commands.
Stop and restart the queue manager.
Collect the items listed in Command server problem determination and contact your IBM support center.
An internal error has occurred.
The command server terminates, and a dump is produced.
Stop and restart the queue manager.
Collect the items listed in Command server problem determination and contact your IBM support center.
The command server was unable to obtain storage while starting up. This is probably because there is insufficient storage in your region.
Message CSQN202I is sent to the z/OS console, indicating the return code from the internal storage macro. The command server stops, without processing any commands.
Check that you are running in a region that is large enough, and if not, reset your system and restart the queue manager. If this is not the cause of the problem, collect the items listed in Command server problem determination and contact your IBM support center.
An internal error has occurred.
Message CSQN202I is sent to the z/OS console, indicating the return code from the internal macro. The command server stops, without processing any commands.
Review the job log for messages about other errors that might be related. If you are unable to solve the problem, collect the items listed in Command server problem determination and contact your IBM support center.
An internal error has occurred.
Message CSQN202I is sent to the z/OS console, indicating the return code from the internal macro. The command server stops, without processing any commands.
Issue the START CMDSERV command to restart the command server.
Collect the items listed in Command server problem determination and contact your IBM support center.
The command server was unable to obtain storage during startup.
Message CSQN202I is sent to the z/OS console, indicating the return code from the internal macro. The command server stops, without processing any commands.
Check that you are running in a region that is large enough, and if not, reset your system and restart the queue manager. If this is not the cause of the problem, collect the items listed in Command server problem determination and contact your IBM support center.
The command preprocessor ended abnormally while processing a command from the command server.
Message CSQN205I is put onto the reply-to queue with COUNT=1, RETURN=00D50209, and REASON=-1 indicating that the command has not been processed. The command server processes the next command.
Check that the command is correctly formed, that it applies to a valid object.
If the command is correct, collect the items listed in Command server problem determination and contact your IBM support center.
While waiting for a command, the command server did not recognize the reason for the end of the wait. This is because it was not one of the following:
Messages CSQN203I and CSQN206I are sent to the console, containing the return and reason codes from the request function, and the ECB list.
The command server is terminated and a dump is produced.
Issue the START CMDSERV command to restart the command server.
Collect the items listed in Command server problem determination and contact your IBM support center.
The command processor attempted to get a command from the system-command-input queue, but the attempt was unsuccessful because of an internal error.
The command server continues processing. Message CSQN203I is written to the console containing the return and reason codes from the API call.
Collect the items listed in Command server problem determination and contact your IBM support center.
The command processor got a command from the system-command-input queue, but was unable to process it because the message was not of type MQMT_REQUEST.
The command processor processes the next command message.
The command processor got a command from the system-command-input queue, but was unable to process it because the command message was of length zero.
The command processor processes the next command message.
The command processor got a command from the system-command-input queue, but was unable to process it because the command message consisted of blank characters only.
The command processor processes the next command message.
The command processor got a command from the system-command-input queue, but was unable to process it because the command message was greater than 32 762 characters long.
The command processor processes the next command message.
An internal error has occurred.
The command server is terminated and a dump is produced.
Issue the START CMDSERV command to restart the command server.
Collect the items listed in Command server problem determination and contact your IBM support center.
The command processor got a command from the system-command-input queue, but was unable to process it because the command message indicated that data conversion was required and an error occurred during conversion. nnn is the reason code (in hexadecimal) returned by the MQGET call.
The command processor processes the next command message.
Refer to Appendix A. API completion and reason codes for information about the reason code nnn.
Collect the following diagnostic items:
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq0516 |