Command server codes (X'D5')
If a command server reason code occurs that is not listed here, an internal error has occurred. Collect the following diagnostic items and contact the IBM support center.
Diagnostics
- A description of the actions that led to the error or, if applicable, either a listing of the application program or the input string to a utility program that was being run at the time of the error.
- The console output for the period leading up to the error.
- The queue manager job log.
- The system dump resulting from the error.
- Appropriate WebSphere MQ, z/OS, Db2, CICS, and IMS service levels.
- Any trace information collected.
- If message CSQN104I or CSQN202I was issued was issued, return and reason codes from the message.
- 00D50101
-
During initialization, the command server was unable to obtain storage. This is probably because there is insufficient storage in your region.
- System action
-
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.
Note: If there is a storage problem, startup might not be successful. - System programmer response
-
Check that we are running in a region that is large enough, and if not, reset the system and
restart the queue manager. If this is not the cause of the problem, collect the following items and
contact the IBM support center:
- Return and reason codes from CSQN104I message
- Trace of startup (if available)
- 00D50102
-
The command preprocessor ended abnormally while processing a command in the initialization input data set.
- System action
-
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.
- System programmer response
-
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 Diagnostics and contact the IBM support center.
- 00D50103
-
During initialization, an internal error occurred.
- System action
-
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.
- System programmer response
-
Review the job log for messages about other errors that might be related. If we are unable to solve the problem, collect the items listed in Diagnostics, and contact the IBM support center.
- 00D50104
-
An internal error occurred during initialization.
- System action
-
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.
- System programmer response
-
Stop and restart the queue manager.
Collect the items listed in Diagnostics and contact the IBM support center.
- 00D50105
-
An internal error has occurred.
- System action
-
The command server terminates, and a dump is produced.
- System programmer response
-
Stop and restart the queue manager.
Collect the items listed in Diagnostics and contact the IBM support center.
- 00D50201
-
The command server was unable to obtain storage while starting. This return code typically occurs because there is insufficient storage in your region.
- System action
-
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.
- System programmer response
-
Check that we are running in a region that is large enough, and if not, reset the system and restart the queue manager. If this is not the cause of the problem, collect the items listed in Diagnostics and contact the IBM support center.
- 00D50202
-
An internal error has occurred.
- System action
-
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.
- System programmer response
-
Review the job log for messages about other errors that might be related. If we are unable to solve the problem, collect the items listed in Diagnostics and contact the IBM support center.
- 00D50203
-
An internal error has occurred.
- System action
-
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.
- System programmer response
-
Issue the START CMDSERV command to restart the command server.
Collect the items listed in Diagnostics and contact the IBM support center.
- 00D50208
-
The command server was unable to obtain storage during startup.
- System action
-
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.
- System programmer response
-
Check that we are running in a region that is large enough, and if not, reset the system and restart the queue manager. If this is not the cause of the problem, collect the items listed in Diagnostics and contact the IBM support center.
- 00D50209
-
The command preprocessor ended abnormally while processing a command from the command server.
- System action
-
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.
- System programmer response
-
Check that the command is correctly formed, that it applies to a valid object.
If the command is correct, collect the items listed in Diagnostics and contact the IBM support center.
- 00D5020C
-
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:
- The arrival of a message
- The STOP CMDSERV command
- System action
-
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.
- System programmer response
-
Issue the START CMDSERV command to restart the command server.
Collect the items listed in Diagnostics and contact the IBM support center.
- 00D5020E
-
The command processor attempted to get a command from the system-command-input queue, but the attempt was unsuccessful because of an internal error.
- System action
-
The command server continues processing. Message CSQN203I is written to the console containing the return and reason codes from the API call.
- System programmer response
-
Collect the items listed in Diagnostics and contact the IBM support center.
- 00D5020F
-
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.
- System action
-
The command processor processes the next command message.
- 00D50210
-
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.
- System action
-
The command processor processes the next command message.
- 00D50211
-
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.
- System action
-
The command processor processes the next command message.
- 00D50212
-
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.
- System action
-
The command processor processes the next command message.
- 00D54000
-
An internal error has occurred.
- System action
-
The command server is terminated and a dump is produced.
- System programmer response
-
Issue the START CMDSERV command to restart the command server.
Collect the items listed in Diagnostics and contact the IBM support center.
- 00D54nnn
-
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.
- System action
-
The command processor processes the next command message.
- System programmer response
-
Refer to API completion and reason codes for information about the reason code nnn.
Parent topic: IBM MQ for z/OS codes