Utilities messages (CSQU...)
CSQU000Icsect-name IBM WebSphere MQ for z/OS versionExplanation:This is part of the header to the report issued by the utility program.
CSQU001Icsect-name Queue Manager Utility - date timeExplanation:This is part of the header to the report issued by the utility program.
System Action:The message is followed by a copy of the function statements from the SYSIN data set.
CSQU002EUnable to get storage of size n bytes, return code=ret-codeExplanation:An attempt to obtain some storage failed.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE or GETMAIN request.
CSQU003EUnable to free storage at address, return code=ret-codeExplanation:An attempt to release storage at address address back to the system failed.
System Action:The program usually ignores the error and continues with its function.
System Programmer Response:See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE or FREEMAIN request.
CSQU005ICOMMIT successfully completedExplanation:An MQCMIT call returned a completion code of MQCC_OK.
CSQU006IBACKOUT successfully completedExplanation:An MQBACK call returned a completion code of MQCC_OK.
System Action:The function is terminated.
System Programmer Response:Investigate the error that caused the backout to be done.
CSQU007EMQCMIT failed. MQCC=mqcc MQRC=mqrcExplanation:The utility program was unable to commit the last set of changes.
System Action:The updates are backed out, and the function is terminated.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU008EMQBACK failed. MQCC=mqcc MQRC=mqrcExplanation:The utility program was unable to back out the last set of changes.
System Action:None, the function is already being terminated because of the error that led to attempting the backout.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU009EMQCONN failed for conn-id. MQCC=mqcc MQRC=mqrcExplanation:An attempt to connect to a queue manager or queue-sharing group named conn-id was unsuccessful.
System Action:The requested function is not performed.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU010EMQDISC failed for conn-id. MQCC=mqcc MQRC=mqrcExplanation:An attempt to disconnect from a queue manager or queue-sharing group named conn-id was unsuccessful.
System Action:The utility program terminates. (This is not an error, because the disconnection request is the last function that the utility program processes.)
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
CSQU011ICommands from CSQINPX - date timeExplanation:This follows message CSQU000I as part of the header to the messages that indicate the progress of the utility program.
It is produced when the utility is invoked by distributed queuing to handle the CSQINPX data set.
CSQU012IInitialization command handling completedExplanation:The initialization command handler, which processes the CSQINPX command data set, completed successfully.
CSQU013EInitialization command handling failed, RC=return-codeExplanation:The initialization command handler, which processes the CSQINPX command data set, did not complete successfully. return-code shows the type of error:
- 00000008
- Some or all of the commands were not processed.
- 0000000C
- Severe error; this is most likely because the CSQINPX or CSQOUTX data sets are defined erroneously.
System Action:The initialization command handler ends, but the channel initiator continues.
System Programmer Response:Refer to the CSQOUTX data set and to the preceding messages for more information about the error.
See the WebSphere MQ for z/OS System Setup Guide for information about the initialization command handler and the CSQINPX or CSQOUTX data sets, and the WebSphere MQ for z/OS System Administration Guide for information about the COMMAND statement.
CSQU020EUnable to OPEN ddname data setExplanation:The program was unable to open data set ddname.
System Action:If the SYSPRINT or SYSIN data sets cannot be opened, the utility program terminates. For other data sets, the function requesting them is not performed.
System Programmer Response:Examine the error message that was sent to the job log to determine the reason for the error. Check that the data set was correctly specified.
CSQU023EUnable to CLOSE ddname data setExplanation:The input data set ddname is still open after a request was made to close it.
System Action:The program continues with its termination procedures.
System Programmer Response:Examine the error message that was sent to the job log to determine the reason for the error. Check that the data set was correctly specified.
CSQU030EPage nn in data set ddname is invalidExplanation:The utility program encountered a page that is invalid in the page set data set ddname. If the page number is 0, it might be that the data set is not the page set that is implied by ddname.
System Action:The function is terminated.
System Programmer Response:Check that the page set has not been corrupted, and that the page set number corresponds to the DDname.
CSQU031EQueue q-name with disposition QMGR or COPY does not existExplanation:The specified queue does not exist with disposition QMGR or COPY. (There may be such a queue with disposition SHARED, but the SCOPY function does not operate on shared queues.)
System Action:The function is terminated.
System Programmer Response:Check the queue name that was specified.
CSQU032EPage set psid is invalidExplanation:The utility program encountered a page set that is invalid. The page set is in an inconsistent state and so the standalone utility functions cannot process it.
System Action:The function is terminated.
System Programmer Response:This may be the result of performing a fuzzy backup (as described in the WebSphere MQ for z/OS System Administration Guide) or because the queue manager terminated abnormally. Restart the queue manager and then terminate it normally.
CSQU036EUtility not available - restricted functionalityExplanation:The utility cannot operate because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
System Action:The utility is terminated.
CSQU040EUnable to GET from ddname data setExplanation:The program was unable to read a record from the ddname data set.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:Examine the error message that was sent to the job log to determine the reason for the error. Check that the data set was correctly specified.
CSQU043EUnable to PUT to ddname data setExplanation:The program was unable to write the next record to the ddname data set. Either the data set was not opened, or there was a QSAM error.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:Examine the error message that was sent to the job log to determine the reason for the error. Check that the data set was correctly specified.
CSQU044ICommands made for qmgr-name only, not for other queue managersExplanation:Some of the DISPLAY object commands for the COMMAND function with MAKEDEF, MAKEREP, MAKEALT, or MAKEDEL used the CMDSCOPE option, and so information about objects for queue managers other than the target queue manager qmgr-name was received. Commands are not generated for such objects.
System Programmer Response:Avoid using CMDSCOPE in conjunction with the MAKEDEF, MAKEREP, MAKEALT, or MAKEDEL options. Use a separate COMMAND function for each target queue manager, with separate data sets for each set of generated commands.
CSQU045In data records readExplanation:This indicates how many data records were read from the input data set specified by the DATA keyword for the current function.
CSQU046Imaking client channel definitions in ddname data set using CCSID ccsidExplanation:This indicates that the COMMAND function will build client channel definitions in data set ddname, and that the data will have a coded character set identifier of ccsid.
CSQU047EUnable to convert data for client channel definitions. MQCC=mqcc MQRC=mqrcExplanation:When building a client channel definition file, data for a channel or authentication information object could not be converted from the character set used by the queue manager to that requested by the CCSID keyword.
System Action:The channel or authentication information definition is not built.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU048In authentication objects included, m excludedExplanation:This indicates, for the current function, how many sets of authentication information were included in the client channel definition file, and how many were excluded. Authentication information may be excluded because:
- the LDAPUSER and LDPAPWD attributes are not blank
- there are too many sets of information
- there was a data conversion error.
System Programmer Response:If some information was excluded, check that the authentication information objects were selected correctly.
CSQU049In client channel definitions madeExplanation:This indicates how many client channel definitions were made by the current function.
CSQU050ECommand of length length is too long. Command rejectedExplanation:In the COMMAND function, the assembled command had more than 32 762 characters.
System Action:The command is ignored, and no more commands are processed.
System Programmer Response:Check that the command is correctly formed according to the concatenation rules described in the WebSphere MQ for z/OS System Administration Guide.
CSQU051ECommand responses not received after n secondsExplanation:In the COMMAND function, get processing for a response was timed out whilst more responses were expected.
System Action:The next command will be processed, unless there have been too many timeouts.
System Programmer Response:Increase the value of RESPTIME, especially if the command is being sent to a remote queue manager, and check the remote queue definitions.
If the problem persists, check the definitions of the system-command input queue and the system-command reply queue; ensure that they are enabled for MQGET and MQPUT. If the definitions are correct, stop and restart the command server.
CSQU052EToo many timeoutsExplanation:In the COMMAND function, get processing for a response timed out four times.
System Action:No more commands are processed.
System Programmer Response:See message CSQU051E.
CSQU053IDISPLAY command response not recognizedExplanation:In the COMMAND function, the responses to a DISPLAY command were not as expected.
System Action:The DISPLAY command response is shown as is, rather than being formatted. The next command is processed.
System Programmer Response:Contact your IBM support center to report the problem.
CSQU054IExecuting function for object type objtypExplanation:The utility program is executing function function to process objects of the type indicated.
CSQU055ITarget queue manager is qmgr-nameExplanation:This indicates which queue manager your commands are directed to.
CSQU056IMaking commands in ddname data setExplanation:This indicates that commands for the COMMAND function with MAKEDEF, MAKEREP, MAKEALT, or MAKEDEL, or for the SDEFS function will be built in data set ddname.
CSQU057In commands readExplanation:This indicates how many commands were read from the command input data set by the current function.
CSQU058In commands issued and responses received, m failedExplanation:This indicates, for the current function, how many commands were sent and produced responses, and how many of these did not execute successfully.
CSQU059In cmd commands madeExplanation:This indicates how many commands (called cmd) were made for the current function.
CSQU060EIncorrect length data record. n bytes found, exp-length bytes expectedExplanation:In the LOAD function, the utility program encountered a record with the wrong length while reading from the input data set. The record was of length length instead of exp-length.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:Check that the data set was created by the COPY function and is not corrupted.
CSQU061EUnexpected end-of-data on ddname data set. Data record missingExplanation:The end-of-data was indicated when the LOAD function was expecting a data record.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:Check that the data set was created by the COPY function, and is not corrupted.
CSQU062EIncorrect format data recordExplanation:In the LOAD function, the utility program encountered a record that it does not recognize while reading from the input data set.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:Check that the data set was created by the COPY function, and is not corrupted.
CSQU070ICommand processing stoppedExplanation:In the COMMAND function, with FAILURE(STOP) specified, a command did not execute successfully.
System Action:No more commands are processed.
CSQU071EIncomplete commandExplanation:In the COMMAND function, end of data on the input data set was reached before the building of a command was complete.
System Action:The command is ignored. There are no more commands to process.
System Programmer Response:Check that the command is correctly formed according to the concatenation rules described in the WebSphere MQ for z/OS System Administration Guide.
CSQU080EMQCLOSE failed for queue q-name. MQCC=mqcc MQRC=mqrcExplanation:The MQCLOSE call for q-name was unsuccessful. If this is for the system-command input queue when using the COMMAND function, message CSQU055I follows showing the target queue manager that was being used.
System Action:The function is terminated.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU082EMQGET failed for queue q-name. MQCC=mqcc MQRC=mqrcExplanation:The MQGET call for q-name was unsuccessful.
System Action:The function is terminated, and any queue updates are backed out.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU083EMQOPEN failed for queue q-name. MQCC=mqcc MQRC=mqrcExplanation:The MQOPEN call for q-name was unsuccessful. If the queue is a model queue, the requested dynamic queue name is appended in parentheses. If this is for the system-command input queue when using the COMMAND function, message CSQU055I follows showing the target queue manager that was being used.
System Action:The function is terminated, and all queue updates are backed out.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU085EMQPUT failed for queue q-name. MQCC=mqcc MQRC=mqrcExplanation:The MQPUT call for q-name was unsuccessful. If this is for the system-command input queue when using the COMMAND function, message CSQU055I follows showing the target queue manager that was being used.
System Action:The function is terminated, and all queue updates are backed out.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Resubmit the job if required.
CSQU087IMAXUMSGS reached. A syncpoint has been forcedExplanation:Because MAXUMSGS was reached, a syncpoint was taken which commits the queue changes made so far.
System Action:The function continues, but no further functions will be processed.
System Programmer Response:None, unless the function fails for some reason after this message. In that case, note that some queue changes will have been committed, and you should make appropriate adjustments before rerunning the job.
CSQU090EOPEN failed for ddname data set. VSAM return code=rc reason code=reasonExplanation:The utility program received a VSAM OPEN error for the page set it was attempting to process (pointed to by ddname).
System Action:The page set is not processed.
System Programmer Response:See the DFSMS/MVS Macro Instructions for Data Sets for information about the return and reason codes from VSAM. If necessary, resubmit the job.
CSQU091Eddname data set is non-empty. Page set not formattedExplanation:Data set ddname was opened, but it is not empty.
System Action:The page set is not formatted.
System Programmer Response:Ensure that the data sets specified are empty, and resubmit the job if necessary.
CSQU092Ifunction completed for ddname data setExplanation:Processing of ddname data set for function function has completed.
System Action:Processing continues with the next page set.
CSQU093EPUT failed for ddname data set. VSAM return code=rc reason code=codeExplanation: