Utilities messages (CSQU...)

 

CSQU000I
csect-name IBM WebSphere MQ for z/OS version
Explanation:

This is part of the header to the report issued by the utility program.

CSQU001I
csect-name Queue Manager Utility - date time
Explanation:

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.

CSQU002E
Unable to get storage of size n bytes, return code=ret-code
Explanation:

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.

CSQU003E
Unable to free storage at address, return code=ret-code
Explanation:

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.

CSQU005I
COMMIT successfully completed
Explanation:

An MQCMIT call returned a completion code of MQCC_OK.

CSQU006I
BACKOUT successfully completed
Explanation:

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.

CSQU007E
MQCMIT failed. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU008E
MQBACK failed. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU009E
MQCONN failed for conn-id. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU010E
MQDISC failed for conn-id. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU011I
Commands from CSQINPX - date time
Explanation:

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.

CSQU012I
Initialization command handling completed
Explanation:

The initialization command handler, which processes the CSQINPX command data set, completed successfully.

CSQU013E
Initialization command handling failed, RC=return-code
Explanation:

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.

CSQU020E
Unable to OPEN ddname data set
Explanation:

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.

CSQU023E
Unable to CLOSE ddname data set
Explanation:

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.

CSQU030E
Page nn in data set ddname is invalid
Explanation:

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.

CSQU031E
Queue q-name with disposition QMGR or COPY does not exist
Explanation:

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.

CSQU032E
Page set psid is invalid
Explanation:

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.

CSQU036E
Utility not available - restricted functionality
Explanation:

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.

CSQU040E
Unable to GET from ddname data set
Explanation:

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.

CSQU043E
Unable to PUT to ddname data set
Explanation:

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.

CSQU044I
Commands made for qmgr-name only, not for other queue managers
Explanation:

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.

CSQU045I
n data records read
Explanation:

This indicates how many data records were read from the input data set specified by the DATA keyword for the current function.

CSQU046I
making client channel definitions in ddname data set using CCSID ccsid
Explanation:

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.

CSQU047E
Unable to convert data for client channel definitions. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU048I
n authentication objects included, m excluded
Explanation:

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.

CSQU049I
n client channel definitions made
Explanation:

This indicates how many client channel definitions were made by the current function.

CSQU050E
Command of length length is too long. Command rejected
Explanation:

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.

CSQU051E
Command responses not received after n seconds
Explanation:

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.

CSQU052E
Too many timeouts
Explanation:

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.

CSQU053I
DISPLAY command response not recognized
Explanation:

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.

CSQU054I
Executing function for object type objtyp
Explanation:

The utility program is executing function function to process objects of the type indicated.

CSQU055I
Target queue manager is qmgr-name
Explanation:

This indicates which queue manager your commands are directed to.

CSQU056I
Making commands in ddname data set
Explanation:

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.

CSQU057I
n commands read
Explanation:

This indicates how many commands were read from the command input data set by the current function.

CSQU058I
n commands issued and responses received, m failed
Explanation:

This indicates, for the current function, how many commands were sent and produced responses, and how many of these did not execute successfully.

CSQU059I
n cmd commands made
Explanation:

This indicates how many commands (called cmd) were made for the current function.

CSQU060E
Incorrect length data record. n bytes found, exp-length bytes expected
Explanation:

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.

CSQU061E
Unexpected end-of-data on ddname data set. Data record missing
Explanation:

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.

CSQU062E
Incorrect format data record
Explanation:

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.

CSQU070I
Command processing stopped
Explanation:

In the COMMAND function, with FAILURE(STOP) specified, a command did not execute successfully.

System Action:

No more commands are processed.

CSQU071E
Incomplete command
Explanation:

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.

CSQU080E
MQCLOSE failed for queue q-name. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU082E
MQGET failed for queue q-name. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU083E
MQOPEN failed for queue q-name. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU085E
MQPUT failed for queue q-name. MQCC=mqcc MQRC=mqrc
Explanation:

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.

CSQU087I
MAXUMSGS reached. A syncpoint has been forced
Explanation:

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.

CSQU090E
OPEN failed for ddname data set. VSAM return code=rc reason code=reason
Explanation:

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.

CSQU091E
ddname data set is non-empty. Page set not formatted
Explanation:

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.

CSQU092I
function completed for ddname data set
Explanation:

Processing of ddname data set for function function has completed.

System Action:

Processing continues with the next page set.

CSQU093E
PUT failed for ddname data set. VSAM return code=rc reason code=code
Explanation:

The utility program received a VSAM PUT error for the page set it was attempting to process (pointed to by ddname).

System Action:

Processing for the page set is terminated, and the function continues with the next page set.

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.

CSQU094E
CLOSE failed for ddname data set. VSAM return code=rc reason code=reason
Explanation:

The utility program received a VSAM CLOSE error for the page set it was attempting to process (pointed to by ddname).

System Action:

Processing for the page set is terminated, and the function continues with the next page set.

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.

CSQU095E
No page sets identified. function terminated
Explanation:

A request to format or reset a page set was unsuccessful because there were no page set data sets with DD names in the range CSQP0000 through CSQP0099.

System Action:

Processing is terminated.

System Programmer Response:

Add DD statements for the required page set data sets, and resubmit the job.

CSQU100E
ddname DD statement missing
Explanation:

Data set ddname does not have a DD statement in the JCL.

System Action:

The utility is terminated.

System Programmer Response:

Add the required statement to the JCL, and resubmit the job.

CSQU101E
DD statement missing for page set psid
Explanation:

A page set is referenced, but there is no DD statement for it in the JCL. The DD name required is CSQP00nn, where nn is the page set number.

System Action:

The utility is terminated.

System Programmer Response:

Add the required statement to the JCL, and resubmit the job.

CSQU102E
No functions requested
Explanation:

There are no function statements in the SYSIN data set.

System Action:

The utility is terminated.

CSQU103E
Either keyword keyword1 or keyword2 must be specified
Explanation:

The statement syntax is incorrect because it requires that one of the keywords keyword1 or keyword2 be specified, but not both.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ Script (MQSC) Command Reference manual for information about the correct syntax required for the statement, and resubmit the job.

CSQU104E
Invalid value value for keyword keyword
Explanation:

The statement syntax is incorrect because the value given for keyword keyword is not valid.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement, and resubmit the job.

CSQU105E
Incompatible keywords or values for function function
Explanation:

The statement syntax is incorrect because a keyword or its value that is specified conflicts with another keyword or its value.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement, and resubmit the job.

CSQU106E
Invalid function function
Explanation:

The statement syntax is incorrect because the function function is not recognized.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for a list of valid functions, and resubmit the job.

CSQU107E
Invalid function statement syntax
Explanation:

The syntax of the function statement is incorrect:

  • there are too many keywords or values

  • required keywords are missing

  • it cannot be parsed.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement, and resubmit the job.

CSQU108E
Value missing for keyword keyword
Explanation:

Keyword keyword should be followed by a value, but the value is missing.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement, and resubmit the job.

CSQU109E
Value not allowed for keyword keyword
Explanation:

Keyword keyword should not be followed by a value, but a value is specified.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement, and resubmit the job.

CSQU110E
Required keyword missing for keyword keyword
Explanation:

The statement syntax is incorrect because keyword keyword can be specified only if some other keyword is also specified, but that other keyword is missing.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ Script (MQSC) Command Reference manual for information about the correct syntax required for the statement, and resubmit the job.

CSQU111E
Invalid keyword keyword for function function
Explanation:

The statement syntax is incorrect because the keyword keyword is not valid for function function.

System Action:

The utility is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the correct syntax required for the statement, and resubmit the job.

CSQU112E
Incomplete statement
Explanation:

End of data on the input data set was reached before the building of a statement was complete.

System Action:

The utility is terminated.

System Programmer Response:

Check that the statement is correctly formed according to the concatenation rules described in the WebSphere MQ for z/OS System Administration Guide.

CSQU113E
Too many statement continuations
Explanation:

The statement has more than 10 continuations.

System Action:

The utility is terminated.

System Programmer Response:

Check that the statement is correctly formed according to the concatenation rules described in the WebSphere MQ for z/OS System Administration Guide.

CSQU114E
Keyword keyword repeated
Explanation:

The statement syntax is incorrect because a keyword is repeated.

System Action:

The utility program is terminated.

System Programmer Response:

Check the syntax in the input data set. See the WebSphere MQ for z/OS System Administration Guide for further information about the utility program.

CSQU115E
Unable to find queues for page set psid - command responses not received
Explanation:

In the COPY or EMPTY function, the queue manager could not determine which queues are in page set psid because the response to a command was not received in time.

System Action:

The function is terminated.

System Programmer Response:

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.

CSQU116I
No storage classes found for page set psid
Explanation:

The page set specified has no storage classes associated with it.

System Action:

The function is terminated.

System Programmer Response:

Define a storage class for the page set, and rerun the job if required.

CSQU117I
No queues found for page set psid
Explanation:

The page set specified has no queues associated with it that are eligible for the requested function. For the COPY and EMPTY functions, there are no local queues; for the SCOPY function, there are no local queues with messages.

System Action:

The function is terminated.

System Programmer Response:

If required, correct the page set specified, and rerun the job.

CSQU120I
Connecting to conn-id
Explanation:

The utility program is connecting to the named queue manager or queue-sharing group.

CSQU121I
Connected to queue manager qmgr-name
Explanation:

The utility program connected successfully to queue manager qmgr-name.

CSQU122I
Executing function-name
Explanation:

The utility program is executing function function-name.

CSQU123I
Processing ddname data set, mode FORCE
Explanation:

The current function of the utility program is handling data set ddname using the FORCE option.

CSQU124I
Processing ddname data set
Explanation:

The current function of the utility program is handling data set ddname.

CSQU125I
n page sets attempted
Explanation:

This indicates how many page sets the current function attempted to process.

CSQU126I
n page sets processed successfully
Explanation:

This indicates how many page sets were processed successfully by the current function.

CSQU127I
Executing function using input from ddname data set
Explanation:

The utility program is executing function function using input from ddname.

CSQU128I
Executing function outputting to ddname data set
Explanation:

The utility program is executing function function, and is writing the output to ddname.

CSQU129I
Copying page set psid
Explanation:

The utility program is copying page set psid.

CSQU130I
Copying queue q-name
Explanation:

The utility program is copying queue q-name.

CSQU131I
n messages copied successfully
Explanation:

This indicates how many messages were copied successfully when copying a queue.

CSQU133I
n queues attempted
Explanation:

This indicates how many queues the program attempted to copy while copying a page set.

CSQU134I
n queues copied successfully
Explanation:

This indicates how many queues were copied successfully while copying a page set.

CSQU135I
Loading queue q-name
Explanation:

The utility program is loading queue q-name.

CSQU136I
n messages loaded successfully
Explanation:

This indicates how many messages were loaded onto a queue.

CSQU138I
n queues loaded successfully
Explanation:

This indicates how many queues were loaded successfully.

CSQU139I
Emptying page set psid
Explanation:

The utility program is emptying page set psid.

CSQU140I
Emptying queue q-name
Explanation:

The utility program is emptying queue q-name.

CSQU141I
n messages deleted successfully
Explanation:

This indicates how many messages were deleted while emptying a queue.

CSQU142I
n queues emptied successfully
Explanation:

This indicates how many queues were emptied.

CSQU143I
n function statements attempted
Explanation:

This indicates the number of function statements attempted by the utility program.

CSQU144I
n function statements executed successfully
Explanation:

This indicates the number of function statements executed successfully by the utility program.

CSQU145I
function statement failed
Explanation:

The utility program experienced an error while executing function function.

System Action:

The utility program terminates.

System Programmer Response:

Check the other messages issued to determine where the error occurred, and what caused it.

CSQU146I
n messages skipped
Explanation:

This indicates how many messages in data set created by the COPY function were skipped before starting to load the queue, when the SKIPMSGS option is used with the LOAD function.

CSQU147I
csect-name Utility terminated, return code=ret-code
Explanation:

The utility has terminated because a severe error or forced syncpoint occurred meaning that no further functions should be run. ret-code is the return code from the utility.

System Action:

The utility ends.

System Programmer Response:

See the WebSphere MQ for z/OS System Administration Guide for information about the return code from the utility.

CSQU148I
csect-name Utility completed, return code=ret-code
Explanation:

The utility completed, all required functions having been attempted. ret-code is the return code from the utility.

System Action:

The utility ends.

System Programmer Response:

Check any functions that failed.

CSQU150I
function completed for data set ddname1 to data set ddname2
Explanation:

Processing for data set ddname1 has completed, with output to ddname2.

System Action:

Processing continues with the next page set.

CSQU151I
No matching CSQSnnnn and CSQTnnnn DD statements. function terminated
Explanation:

A COPYPAGE or RESETPAGE function was unsuccessful because there were no matching pairs of page set data sets with names CSQS0000 through CSQS0099 and CSQT0000 through CSQT0099.

System Action:

The function is terminated.

System Programmer Response:

Add DD statements for the required page set data sets, and resubmit the job.

CSQU152I
ddname1 DD statement missing. No action taken for ddname2 data set
Explanation:

Only one of the source-target pair of page set data sets (CSQSnnnn and CSQTnnnn) was specified.

System Action:

The function continues.

System Programmer Response:

Add DD statements for the required page set data sets, and resubmit the job.

CSQU154E
Target data set ddname is smaller than source data set. Function terminated
Explanation:

A COPYPAGE or RESETPAGE function could not process a page set data set because the target data set ddname was too small.

System Action:

Processing continues with the next page set.

CSQU155I
Loading from queue q-name
Explanation:

The utility program is loading the queue named in message CSQU135I with messages copied from queue q-name.

CSQU156E
GET failed for ddname data set. VSAM return code=rc reason code=code
Explanation:

The utility program received a VSAM GET error for the page set it was attempting to process (pointed to by ddname).

System Action:

Processing for the page set is terminated, and the function continues with the next page set.

System Programmer Response:

See the DFSMS/MVS Macro Instructions for Data Sets manual for information about the return and reason codes from VSAM. If necessary, resubmit the job.

CSQU157I
Processing data set ddname1 to ddname2
Explanation:

The current function is handling data set ddname1, with output to ddname2.

CSQU158E
Target data set ddname2 is not newly formatted
Explanation:

The COPYPAGE and RESETPAGE functions can only be used with a newly formatted target page set.

System Action:

Processing continues with the next page set.

System Programmer Response:

Specify a valid target page set, and resubmit the job.

CSQU159E
Source data set ddname1 is not a page set
Explanation:

The COPYPAGE and RESETPAGE functions can only be used with an MQ page set.

System Action:

Processing continues with the next page set.

System Programmer Response:

Specify a valid source page set, and resubmit the job.

CSQU160E
Data set ddname is not suitable for use with the function
Explanation:

The function should only be used with page sets for a queue manager that terminated normally.

System Action:

Processing continues with the next page set.

System Programmer Response:

Specify a valid page set, and resubmit the job.

CSQU161I
ddname contains pp pages and was formatted as page set nn
Explanation:

This is part of the response to the PAGEINFO function for data set ddname.

It shows the size of the page set, and the page set number that was assumed when it was formatted. The number is derived from the DD name used when formatting, which was CSQP00nn.

CSQU162I
ddname is used as page set psid for queue manager qmgr-name
Explanation:

This is part of the response to the PAGEINFO function for data set ddname.

The page set has been used by the queue manager shown. The page set number is not necessarily the same as that with which it was formatted, as shown in message CSQU161I.

CSQU163I
ddname has page set recovery RBA = rba
Explanation:

This is part of the response to the PAGEINFO function for data set ddname.

CSQU164I
ddname System recovery RBA for all page sets successfully processed = rba
Explanation:

This is part of the response to the PAGEINFO function. Note that this RBA relates only to those page sets processed; it does not relate to the whole queue manager unless all the page sets for the queue manager are included.

CSQU165I
Processing ddname data set, TYPE(type)
Explanation:

This current function of the utility program is handling data set ddname with the options shown.

CSQU166I
Processing ddname data set, TYPE(type), mode FORCE
Explanation:

This current function of the utility program is handling data set ddname with the options shown.

CSQU167I
ddname has never been initialized by a queue manager
Explanation:

This is part of the response to the PAGEINFO function for data set ddname.

CSQU168E
Requested page sets are for more than one queue manager
Explanation:

The page sets for which information was requested are associated with more than one queue manager. No system recovery RBA can therefore be determined.

System Action:

Processing continues.

System Programmer Response:

Specify a set of page sets for a single queue manager, and resubmit the job.

CSQU180E
csect-name Unable to load module module-name, reason=ssssrrrr
Explanation:

The utility program was unable to load the requested channel initiator parameter module. ssss is the completion code and rrrr is the reason code (both in hexadecimal) from the z/OS LOAD service.

System Action:

The function is terminated.

System Programmer Response:

Check the member name specified on the XPARM fumction, and ensure that the module is in the library specified by the DDNAME keyword.

CSQU181E
csect-name module-name is not a valid channel initiator parameter module
Explanation:

The module specified for channel initiator parameters is not in the correct format. It was not generated using the CSQ6CHIP channel initiator parameter macro.

System Action:

The function is terminated.

System Programmer Response:

Check the member name specified on the XPARM fumction, and that the specified member created using the CSQ6CHIP macro.

CSQU200I
csect-name Dead-letter Queue Handler Utility - date time
Explanation:

This is part of the header to the report issued by the utility program.

CSQU201I
Processing queue q-name
Explanation:

The dead-letter queue handler has parsed the rules table without detecting any errors and is about to start processing the queue identified in the message.

CSQU202I
Dead-letter queue handler ending. Successful actions: n1 retries, n2 forwards, n3 discards
Explanation:

The dead-letter queue handler is ending because there are no more messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler detected an error. The message indicates how many dead-letter queue messages were successfully handled.

System Action:

The utility terminates.

System Programmer Response:

If the utility ended because of an error, investigate the problem reported in the preceding messages.

CSQU203I
n messages remain on the dead-letter queue
Explanation:

The message indicates how many messages are left on the dead-letter queue when the dead-letter queue handler ends.

CSQU210I
Message does not have a valid MQDLH
Explanation:

The dead-letter queue handler retrieved a message from the dead-letter queue, but the message was not prefixed by a valid dead-letter queue header (MQDLH). This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH.

System Action:

The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue.

This message is issued only once the first time such a message is encountered.

System Programmer Response:

Remove all the invalid messages from the dead-letter queue. Do not write messages to the dead-letter queue unless they are prefixed by a valid MQDLH.

CSQU211I
Unable to put message, line n MQRC=mqrc
Explanation:

The dead-letter queue handler tried to redirect a message to another queue as requested, but the MQPUT call was unsuccessful.

System Action:

The retry count for the message is incremented; processing continues.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqrc. The line number n of the rules table used to determine the action for the message will help identify the queue to which the message was being put.

CSQU212I
Unable to inquire dead-letter queue, MQCC=mqcc MQRC=mqrc
Explanation:

An MQINQ call for the dead-letter queue was unsuccessful.

System Action:

Processing continues.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU220E
Unable to connect to queue manager qmgr-name, MQCC=mqcc MQRC=mqrc
Explanation:

The dead-letter queue handler could not connect to the requested queue manager.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU221E
Unable to open queue manager, MQCC=mqcc MQRC=mqrc
Explanation:

An MQOPEN call for the queue manager was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU222E
Unable to inquire queue manager, MQCC=mqcc MQRC=mqrc
Explanation:

An MQINQ call for the queue manager was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU223E
Unable to close queue manager, MQCC=mqcc MQRC=mqrc
Explanation:

An MQCLOSE call for the queue manager was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU224E
Unable to browse dead-letter queue q-name, MQCC=mqcc MQRC=mqrc
Explanation:

An MQOPEN call for browsing the dead-letter queue was unsuccessful. This is typically because another process has opened the queue for exclusive access, or because an invalid queue name was specified.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU225E
Unable to close dead-letter queue, MQCC=mqcc MQRC=mqrc
Explanation:

An MQCLOSE call for the dead-letter queue was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU226E
Line n: keyword(value) invalid or outside permitted range
Explanation:

The value supplied for the specified keyword in line n of the rules table was outside the valid range of values or otherwise invalid.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table and restart the dead-letter queue handler.

CSQU227E
Unable to get message from dead-letter queue, MQCC=mqcc MQRC=mqrc
Explanation:

An MQGET call for the dead-letter queue was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU228E
Unable to commit or backout dead-letter queue action, MQCC=mqcc MQRC=mqrc
Explanation:

An MQCMIT or MQBACK call for the dead-letter queue was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU229E
Rules table is invalid or missing
Explanation:

The rules table contained no valid message templates or was not supplied at all.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table as indicated in the preceding messages and restart the dead-letter queue handler.

CSQU230E
Unable to obtain storage
Explanation:

The dead-letter queue handler was unable to obtain storage.

This problem would typically arise as a result of some wider problem. For example, if there is a persistent problem that is causing messages to be written to the dead-letter queue and the same problem (for example, queue full) is preventing the dead-letter queue handler from taking the requested action with the message, ever-increasing amounts of storage would be required.

System Action:

The utility is terminated.

System Programmer Response:

Increase the storage available to the utility. Investigate whether some wider problem exists, and if the dead-letter queue contains a large number of messages.

CSQU231E
Line n: parameter keyword exceeds maximum length
Explanation:

The value for the specified parameter in line n of the rules table is too long.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table and restart the dead-letter queue handler.

CSQU232E
Line n: parameter keyword is duplicated
Explanation:

Two or more parameters of the same type were supplied in line n of the rules table.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table and restart the dead-letter queue handler.

CSQU233E
Line n: syntax error
Explanation:

There is a syntax error in line n of the rules table.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table and restart the dead-letter queue handler.

CSQU234E
Unable to release storage
Explanation:

The dead-letter queue handler was unable to release storage.

System Action:

The utility is terminated.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQU235E
Line n: keyword value invalid or outside permitted range
Explanation:

The value supplied for the specified parameter in line n of the rules table was outside the valid range of values or otherwise invalid.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table and restart the dead-letter queue handler.

CSQU236E
n error(s) in rules table
Explanation:

Errors were detected in the rules table.

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table as indicated in the preceding messages and restart the dead-letter queue handler.

CSQU237E
Line n: invalid keyword combination
Explanation:

There is an invalid combination of parameters in line n of the rules table. For example: no ACTION specified, ACTION(FWD) specified without FWDQ, HEADER specified without ACTION(FWD).

System Action:

The utility is terminated.

System Programmer Response:

Correct the rules table and restart the dead-letter queue handler.

CSQU249E
Unable to disconnect from queue manager, MQCC=mqcc MQRC=mqrc
Explanation:

An MQDISC call for the queue manager was unsuccessful.

System Action:

The utility is terminated.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQU500I
csect-name Queue-sharing Group Utility - date time
Explanation:

This is part of the header to the report issued by the utility program.

CSQU501I
function function requested
Explanation:

This identifies the utility function requested.

CSQU502I
Queue manager=qmgr-name
Explanation:

This identifies the queue manager name for which the function is requested.

CSQU503I
QSG=qsg-name, DB2 DSG=dsg-name, DB2 ssid=db2-name
Explanation:

This identifies the queue-sharing group, DB2 data-sharing group, and DB2 subsystem names for which the function is requested.

CSQU504E
Unable to load module-name, reason=ssssrrrr
Explanation:

The utility was unable to load a required module. ssss is the completion code and rrrr is the reason code (both in hexadecimal) from the z/OS LOAD service.

System Action:

The utility terminates.

System Programmer Response:

Check the console for messages indicating why the module was not loaded. See the MVS Programming: Assembler Services Reference manual for information about the codes from the LOAD request.

Ensure that the module is in the required library, and that it is referenced correctly. The utility attempts to load this module from the library data sets under the STEPLIB DD statement.

CSQU505E
No EXEC PARM parameters
Explanation:

No parameters for the utility were specified in EXEC PARM field.

System Action:

The utility program is terminated.

System Programmer Response:

Specify the required parameters and rerun the job. See the WebSphere MQ for z/OS System Administration Guide for information about the parameters required by the utility.

CSQU506E
Invalid EXEC PARM function parameter
Explanation:

The function requested for the utility, as the first parameter in EXEC PARM field, was invalid.

System Action:

The utility program is terminated.

System Programmer Response:

Correct the parameter and rerun the job. See the WebSphere MQ for z/OS System Administration Guide for information about the parameters required by the utility.

CSQU507E
Wrong number of EXEC PARM parameters for function
Explanation:

The number of parameters for the utility specified in EXEC PARM field was incorrect for the function requested.

System Action:

The utility program is terminated.

System Programmer Response:

Correct the parameters and rerun the job. See the WebSphere MQ for z/OS System Administration Guide for information about the parameters required by the utility.

CSQU508E
Invalid EXEC PARM parameter n
Explanation:

The nth parameter for the utility specified in EXEC PARM field was invalid for the function requested, or omitted but required by the function requested.

System Action:

The utility program is terminated.

System Programmer Response:

Correct the parameter and rerun the job. See the WebSphere MQ for z/OS System Administration Guide for information about the parameters required by the utility.

CSQU509E
Too many EXEC PARM parameters
Explanation:

The number of parameters for the utility specified in EXEC PARM field was too many for the function requested.

System Action:

The utility program is terminated.

System Programmer Response:

Correct the parameters and rerun the job. See the WebSphere MQ for z/OS System Administration Guide for information about the parameters required by the utility.

CSQU512E
Utility terminated, DB2 tables in use
Explanation:

The queue-sharing group utility cannot run because the DB2 tables it uses are reserved by another job. The most likely reason is that another instance of the utility is running, or that a queue manager in the queue-sharing group is in the process of starting.

System Action:

The utility program is terminated.

System Programmer Response:

Rerun the job later.

CSQU513E
Utility terminated, not APF authorized
Explanation:

The queue-sharing group utility is not APF authorized.

System Action:

The utility program is terminated.

System Programmer Response:

Ensure that the library data sets under the STEPLIB DD statement comply with the rules for APF authorization, and rerun the job.

CSQU514E
RRSAF function call-name failed, RC=rc
Explanation:

The RRS function specified by call-name returned an unexpected reason code specified by rc.

System Action:

The utility program is terminated.

System Programmer Response:

Consult the DB2 for z/OS Messages and Codes manual for an explanation of the RRSAF reason code.

Take corrective action if necessary and resubmit the job.

CSQU515E
Unable to access DB2 tables, RC=rc reason=reason
Explanation:

The call to CSQ5ARO2 module failed with a return code specified by rc and reason code specified by reason.

System Action:

The utility program is terminated.

System Programmer Response:

Resubmit the job. If the problem persists, note the error codes in the message and contact your IBM support center.

CSQU517I
XCF group xcf-name already defined
Explanation:

Informational message indicating that the XCF group name specified by xcf-name already exists.

CSQU518E
XCF IXCQUERY member error, RC=rc reason=reason
Explanation:

An unexpected return code specified by rc with reason code specified by reason was returned from an IXCQUERY request.

System Action:

The utility program is terminated.

System Programmer Response:

See the z/OS MVS Sysplex Services Reference manual for an explanation of the IXCQUERY return and reason codes.

Take corrective action if necessary and resubmit the job.

CSQU520I
Summary information for XCF group xcf-name
Explanation:

Informational message indicating that summary data for the XCF group specified by xcf-name follows.

CSQU521I
Group contains n members:
Explanation:

Informational message indicating that the group specified by message CSQU517I contains n members.

CSQU522I
Member=xcf-name, state=sss, system=sys-name
Explanation:

Informational message indicating that the XCF group member specified by xcf-name has a state of sss and last executed on system sys-name.

CSQU523I
User data=xxx
Explanation:

Informational message containing the 32 bytes of XCF user data to accompany informational message CSQU522I.

CSQU525E
DB2 db2-name is not a member of data-sharing group dsg-name
Explanation:

There was an inconsistency between the DB2 ssid and data-sharing group name provided in the EXEC PARM field. DB2 ssid specified by db2-name is not a member of the DB2 data-sharing group specified by dsg-name.

System Action:

The utility program is terminated.

System Programmer Response:

Ensure that the DB2 ssid specified is a member of the DB2 data-sharing group specified.

CSQU526I
Connected to DB2 db2-name
Explanation:

The utility program connected successfully to DB2 subsystem db2-name.

CSQU527E
No eligible DB2 currently active
Explanation:

If a DB2 ssid was specified in the EXEC PARM field this indicates that the DB2 subsystem is not currently active on the z/OS system on which the utility job executed.

If a DB2 data-sharing group name was specified in the EXEC PARM field then no eligible DB2 subsystem was active on the z/OS system on which the utility job executed.

System Action:

The utility program is terminated.

System Programmer Response:

If a DB2 ssid was specified in the EXEC PARM field then ensure that it is active on the z/OS system on which the utility job will execute.

If a DB2 data-sharing group name was specified in the EXEC PARM field then ensure that at least one eligible DB2 subsystem is active on the z/OS system on which the utility job will execute.

CSQU528I
Disconnected from DB2 db2-name
Explanation:

The utility program disconnected successfully from DB2 subsystem db2-name.

CSQU529E
QSG qsg-name entry cannot be removed, n members are still defined
Explanation:

A request to remove the queue-sharing group name in qsg-name failed because n members are still defined to it.

System Action:

The utility program is terminated.

System Programmer Response:

All members of the queue-sharing group must be removed from it before the queue-sharing group itself can be deleted. Use the preceding CSQU522I message to identify which queue-sharing group members are still defined to the queue-sharing group.

Note:
Members in a state of ACTIVE or FAILED cannot be removed from a queue-sharing group.
CSQU530E
QMGR qmgr-name entry cannot be removed from QSG qsg-name, status is sss
Explanation:

The queue manager named by qmgr-name cannot be removed from the queue-sharing group named by qsg-name because it is in an incorrect XCF member state as specified by sss.

System Action:

The utility program is terminated.

System Programmer Response:

In order to remove a queue manager from the queue-sharing group it must have XCF member state CREATED or QUIESCED.

If the XCF member state is ACTIVE then stop the queue manager with a STOP QMGR command and resubmit the job.

If the XCF member state is FAILED then start the queue manager and stop it normally using the STOP QMGR command and resubmit the job.

CSQU531E
QSG qsg-name entry cannot be removed, not found in DB2 table table-name
Explanation:

An attempt to remove the queue-sharing group qsg-name failed because no entry for it was found in the DB2 table table-name.

System Action:

The utility program is terminated.

System Programmer Response:

Ensure that the queue-sharing group qsg-name was originally defined in the table table-name.

Check that the utility job connected to the correct DB2 data-sharing group. If necessary resubmit the job.

CSQU532E
QSG qsg-name entry cannot be deleted, DB2 entries still exist for it
Explanation:

An attempt to remove the queue-sharing group qsg-name was returned a DB2 constraint failure because queue manager entries still exist in the CSQ.ADMIN_B_QMGR table.

System Action:

The utility program is terminated.

System Programmer Response:

Examine the CSQ.ADMIN_B_QMGR table to determine which queue managers are still defined to the queue-sharing group qsg-name.

Use the REMOVE QMGR function of the CSQ5PQSG utility to remove the entries and then resubmit the job.

CSQU533E
SQL error. DB2 table=table-name, code=sqlcode, state=sss, data=sqlerrcd
Explanation:

An unexpected SQL error was returned from DB2. An operation on the table named by table-name was returned an SQLCODE specified by sqlcode with STATE specified by sss and SQLERRCD values specified by sqlerrcd.

System Action:

The utility program is terminated.

System Programmer Response:

See the DB2 for z/OS Messages and Codes manual for an explanation of the SQL codes.

Resubmit the job if required.

CSQU534E
SQL services error, DB2 table=table-name RC=rc
Explanation:

An SQL error occurred during an operation on the table specified by table-name, as reported in the preceding CSQU533E message. A return code of rc was returned from the internal service routine.

System Action:

The utility program is terminated.

System Programmer Response:

See message CSQU533E.

CSQU535I
QSG qsg-name entry successfully removed from DB2 table table-name
Explanation:

Informational message indicating that the queue-sharing group named by qsg-name was successfully removed.

CSQU536E
Unable to add QSG qsg-name entry, entry already exists in DB2 table table-name
Explanation:

An attempt to add the queue-sharing group qsg-name failed because an entry already exists in the DB2 table table-name.

System Action:

The utility program is terminated.

CSQU537I
csect-name QSG qsg-name entry successfully added to DB2 table table-name
Explanation:

The request to add the queue-sharing group qsg-name to the DB2 table table-name completed successfully.

CSQU538E
Member record found for QMGR qmgr-name XCF group xcf-name
Explanation:

Informational message indicating that a member record for the queue manager named in qmgr-name already exists in the XCF group named by xcf-name.

CSQU539E
No QMGR qmgr-name entry found in QSG qsg-name
Explanation:

An attempt to remove the queue manager named by qmgr-name from the queue-sharing group named by qsg-name failed because no entry was found in the DB2 tables.

System Action:

The utility program is terminated.

CSQU540E
Unable to remove QMGR qmgr-name - not terminated normally, or needed for recovery
Explanation:

The queue manager named by qmgr-name cannot be removed from the queue-sharing group because it is currently active, or because it terminated abnormally during its last execution, or because it is needed for backup and recovery purposes.

System Action:

The utility program is terminated.

System Programmer Response:

If the queue manager is active then stop the queue manager with a STOP QMGR command and resubmit the job.

If the queue manager terminated abnormally during its last execution then start the queue manager and stop it normally using the STOP QMGR command and resubmit the job.

If neither of these cases applies, or if it still cannot be removed, it must be needed for backup and recovery purposes. See the WebSphere MQ for z/OS System Administration Guide for information about removing such a queue manager from a queue-sharing group.

CSQU541E
QSG array manipulation error, RC=rc
Explanation:

An internal error occurred during manipulation of the queue-sharing group array data.

An internal routine returned a completion code specified by rc.

System Action:

The utility program is terminated.

System Programmer Response:

Resubmit the job. If the problem persists, note the error codes in the message and contact your IBM support center.

CSQU542E
Update unsuccessful for QSG qsg-name, RC=rc
Explanation:

An attempt to update the DB2 row for the queue-sharing group named by qsg-name failed with return code rc.

rc shows the type of failure:

00F5000C

Queue-sharing group row no longer exists

00F50010

Internal error

00F50018

Referential constraint failure

00F50028

Internal error
System Action:

The utility program is terminated.

System Programmer Response:

Resubmit the job. If the problem persists contact your IBM support center.

CSQU543E
Delete unsuccessful for QMGR qmgr-name, RC=rc
Explanation:

The attempt to delete the queue manager qmgr-name failed with return code rc.

rc shows the type of failure: 00F5000C, queue manager row no longer exists.

System Action:

Processing continues.

System Programmer Response:

This may be an indication that the request was made against the wrong DB2 data-sharing group or that a previous attempt terminated prematurely. For the former, the utility should be executed against the correct DB2 data-sharing group. For the latter, no further action need be taken.

CSQU544E
IXCDELET request for QMGR qmgr-name unsuccessful, RC=rc reason=reason
Explanation:

During an attempt to delete queue manager qmgr-name, an IXCDELET request was returned an IXC return code of rc and reason code of reason.

System Action:

The utility program is terminated.

System Programmer Response:

See the z/OS MVS Sysplex Services Reference manual for an explanation of the IXCDELET return and reason codes.

Take corrective action if necessary and resubmit the job.

CSQU545E
IXCCREAT request for QMGR qmgr-name unsuccessful, RC=rc reason=reason
Explanation:

During an attempt to add queue manager qmgr-name, an IXCCREAT request was returned an IXC return code of rc and reason code of reason.

System Action:

The utility program is terminated.

System Programmer Response:

See the z/OS MVS Sysplex Services Reference manual for an explanation of the IXCCREAT return and reason codes.

Take corrective action if necessary and resubmit the job.

CSQU546E
Unable to add QMGR qmgr-name entry, already exists in DB2 table table-name
Explanation:

The attempt to add an entry for queue manager qmgr-name to the DB2 table table-name failed because a row already exists for the queue manager.

System Action:

The utility program is terminated.

System Programmer Response:

Examine the DB2 table specified by table-name and determine whether the entry for the queue manager specified by qmgr-name is for the correct queue-sharing group. If it is, no further action is required.

CSQU547E
Unable to add QMGR qmgr-name entry, no QSG qsg-name entry exists in DB2 table table-name
Explanation:

The attempt to add queue manager qmgr-name failed because there is no queue-sharing group entry for the queue-sharing group qsg-name in the DB2 table table-name.

System Action:

The utility program is terminated.

System Programmer Response:

In order to add a queue manager to a queue-sharing group the DB2 CSQ.ADMIN_B_QSG table must contain a queue-sharing group record for the queue-sharing group named by qsg-name.

Examine the DB2 tables and if necessary run the CSQ5PQSG utility ADD QSG function prior to resubmitting this job.

CSQU548E
QMGR qmgr-name cannot be added to QSG qsg-name, no unassigned QMGR number
Explanation:

The attempt to add queue manager qmgr-name to the queue-sharing group qsg-name failed because all queue manager numbers are in use.

System Action:

The utility program is terminated.

System Programmer Response:

A maximum of 32 queue managers can be defined to a queue-sharing group at any one time. If the queue-sharing group named by qsg-name already contains 32 queue managers then the only course of action is to create a new queue-sharing group or remove an existing queue manager.

CSQU549I
QMGR qmgr-name entry successfully added to QSG qsg-name
Explanation:

The request to add queue manager qmgr-name to the queue-sharing group qsg-name completed successfully.

CSQU550I
QMGR qmgr-name entry successfully removed from QSG qsg-name
Explanation:

The request to remove queue manager qmgr-name from the queue-sharing group qsg-name completed successfully.

CSQU551I
QSG qsg-name entry successfully added
Explanation:

The request to add queue-sharing group qsg-name completed successfully.

CSQU552I
QSG qsg-name entry successfully removed
Explanation:

The request to remove queue-sharing group qsg-name completed successfully.

CSQU553E
QMGR qmgr-name exists in DB2 table table-name as a member of a different QSG
Explanation:

An attempt to add the queue manager specified by qmgr-name into a queue-sharing group failed because the DB2 table specified by table-name indicates that the queue manager is already a member of a different queue-sharing group.

System Action:

The utility program is terminated.

System Programmer Response:

A queue manager can be a member of only one queue-sharing group at any one time. >Examine the CSQ.ADMIN_B_QMGR table to determine which queue-sharing group the queue manager is already a member of.

Either remove the queue manager from the queue-sharing group it is in and resubmit the job or take no further action.

CSQU554E
QMGR qmgr-name entry cannot be removed from QSG qsg-name, needed for structure struc-name backup
Explanation:

The queue manager named by qmgr-name cannot be removed from the queue-sharing group named by qsg-name because it has information about backups for structure struc-name. (The value shown for struc-name is the 12-character name as used by WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

If the queue manager is needed for more than one structure, this message will be issued for each one.

System Action:

The utility program is terminated.

System Programmer Response:

Using another queue manager in the queue-sharing group, take a backup of the structure. Ensure that the EXCLINT time value used in the BACKUP CFSTRUCT command is less than the time since the queue manager that you are trying to remove was last stopped. Then resubmit the job.

CSQU555E
QMGR qmgr-name release level is incompatible with QSG qsg-name in DB2 table table-name
Explanation:

An attempt to add the queue manager specified by qmgr-name into a queue-sharing group failed because the DB2 table specified by table-name indicates that another queue manager in the queue-sharing group is at an incompatible release level.

System Action:

The utility program is terminated.

System Programmer Response:

Only queue managers with compatible release levels can be members of the same queue-sharing group. See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.

CSQU560I
Full name of admin structure is admin-strname
Explanation:

This shows the full external name of the administration structure as used by z/OS, which includes the queue-sharing group name.

CSQU561E
Unable to get attributes for admin structure, IXLMG RC=rc reason code=reason
Explanation:

An attempt to add a queue manager to a queue-sharing group failed; it was not possible to check the attributes of the administration structure because there was an XES IXLMG service error. The full name of the administration structure is given in the following CSQ570I message.

System Action:

The utility program terminates. The queue manager is not added to the queue sharing group.

System Programmer Response:

Investigate the return and reason codes from the IXLMG service (both shown in hexadecimal), which are described in the z/OS MVS Programming: Services Reference manual. If you are unable to resolve the problem, contact your IBM service center.

CSQU562E
Admin structure attributes temporarily unavailable
Explanation:

An attempt to add a queue manager to a queue-sharing group failed; it was not possible to check the attributes of the administration structure because they were currently unavailable. The full name of the administration structure is given in the following CSQ570I message.

System Action:

The utility program terminates. The queue manager is not added to the queue sharing group.

System Programmer Response:

Rerun the job later.

CSQU563I
Admin structure is defined in CF cf-name, allocated size mm KB, maximum entries nn
Explanation:

This shows the current attributes of the administration structure for the queue sharing group. It is defined in the coupling facility named cf-name.

CSQU564E
Queue managers cannot be added to QSG qsg-name, admin structure too small
Explanation:

An attempt to add a queue manager to a queue-sharing group failed; the current administration structure allocation is too small for a queue-sharing group with the requested number of queue managers. The full name of the administration structure is given in the following CSQ570I message.

System Action:

The utility program terminates. The queue manager is not added to the queue sharing group.

System Programmer Response:

See the WebSphere MQ for z/OS Concepts and Planning Guide for information about coupling facility structure sizes for use with queue-sharing groups.

The administration structure allocation must be increased before a new queue manager can be added to the queue-sharing group. This may involve one or more of the following steps:

  • Update the administration structure definition using the IXLMIAPU utility.

  • Refresh the currently active CFRM policy.

  • Dynamically alter the current allocation of the administration structure using the z/OS SETXCF START,ALTER command.

Rerun the job when the administration structure allocation has benn increased.

CSQU565E
Unable to get attributes for admin structure, CF in failed state
Explanation:

An attempt to add a queue manager to a queue-sharing group failed; it was not possible to check the attributes of the administration structure because it is in a failed state. The full name of the administration structure is given in the following CSQ570I message.

System Action:

The utility program terminates. The queue manager is not added to the queue sharing group.

System Programmer Response:

Use the z/OS DISPLAY XCF,STRUCTURE command to display the status of all structures in the currently active CFRM policy.

If the administration structure has failed, starting a queue manager in the queue-sharing group will cause the structure to be allocated according to the current CFRM policy.

CSQU566I
Unable to get attributes for admin structure, CF not found or not allocated
Explanation:

In attempting to add a queue manager to a queue-sharing group, it was not possible to check the attributes of the administration structure because it has not yet been defined to the CFRM policy, or is not currently allocated in a coupling facility. The full name of the administration structure is given in the following CSQ570I message.

System Action:

Processing continues.

System Programmer Response:

Use the z/OS DISPLAY XCF,STRUCTURE command to display the status of all structures in the currently active CFRM policy.

Ensure a structure definition exists in the CFRM policy. It will be needed before the queue manager can be started.

CSQU570I
QSG qsg-name successfully verified
Explanation:

The request to verify information for queue-sharing group qsg-name completed successfully. All the information is consistent.

CSQU571E
QSG qsg-name entry cannot be verified, not found in DB2 table table-name
Explanation:

An attempt to verify the queue-sharing group qsg-name failed because no entry for it was found in the DB2 table table-name.

System Action:

The utility program is terminated.

System Programmer Response:

Ensure that the queue-sharing group qsg-name was originally defined in the table table-name. Check that the utility job connected to the correct DB2 data-sharing group.

If necessary resubmit the job.

CSQU572E
Usage map map-name and DB2 table table-name inconsistent
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in the usage map map=name and the DB2 table table-name. The following messages give more details about the inconsistency.

System Action:

Processing continues.

System Programmer Response:

Check that the utility job connected to the correct DB2 data-sharing group. If necessary resubmit the job.

Contact your IBM support center for assistance.

CSQU573E
QMGR qmgr-name in table entry entry-number not set in usage map
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in a usage map and the corresponding DB2 table. The inconsistency is described in the message; preceding message CSQU572E identifies the usage map and table.

System Action:

Processing continues.

System Programmer Response:

See message CSQU572E.

CSQU574E
QMGR qmgr-name in usage map has no entry in table
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in a usage map and the corresponding DB2 table. The inconsistency is described in the message; preceding message CSQU572E identifies the usage map and table.

System Action:

Processing continues.

System Programmer Response:

See message CSQU572E.

CSQU575E
Structure struc-name in table entry entry-number not set in usage map
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in a usage map and the corresponding DB2 table. The inconsistency is described in the message; preceding message CSQU572E identifies the usage map and table. (The value shown for struc-name is the 12-character name as used by WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

System Action:

Processing continues.

System Programmer Response:

See message CSQU572E.

CSQU576E
Structure struc-name in usage map has no entry in table
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in a usage map and the corresponding DB2 table. The inconsistency is described in the message; preceding message CSQU572E identifies the usage map and table. (The value shown for struc-name is the 12-character name as used by WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

System Action:

Processing continues.

System Programmer Response:

See message CSQU572E.

CSQU577E
Queue q-name in table entry entry-number not set in usage map for structure struc-name
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in a usage map and the corresponding DB2 table. The inconsistency is described in the message; preceding message CSQU572E identifies the usage map and table. (The value shown for struc-name is the 12-character name as used by WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

System Action:

Processing continues.

System Programmer Response:

See message CSQU572E.

CSQU578E
Queue q-name in usage map for structure struc-name has no entry in table
Explanation:

While verifying a queue-sharing group, an inconsistency was found between the information in a usage map and the corresponding DB2 table. The inconsistency is described in the message; preceding message CSQU572E identifies the usage map and table. (The value shown for struc-name is the 12-character name as used by WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

System Action:

Processing continues.

System Programmer Response:

See message CSQU572E.

CSQU580I
DSG dsg-name is ready for migration
Explanation:

The request to migrate the data-sharing group dsg-name to use new DB2 tables successfully verified that the data-sharing group is ready to be migrated.

System Programmer Response:

Perform the migration. You should do this as a conditional step in the same job as the utility migration request, as shown in the sample job CSQ45ATB in the SCSQPROC library.

CSQU581E
DSG dsg-name has incompatible QMGR levels
Explanation:

The data-sharing group dsg-name cannot be migrated to use new DB2 tables because the levels of the queue managers using the data-sharing group are incompatible.

System Action:

The utility program is terminated.

System Programmer Response:

In order to perform the migration, all the queue managers in all the queue-sharing groups that use the data-sharing group must have installed a PTF and been started, to bring them to the necessary level. Examine the CSQ.ADMIN_B_QMGR DB2 table to determine the levels of the queue managers and those which need to be upgraded.

See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for full information about migration between releases and the PTF.

CSQU582E
DSG dsg-name has already been migrated
Explanation:

The data-sharing group dsg-name cannot be migrated to use new DB2 tables because it has already been migrated.

System Action:

The utility program is terminated.

System Programmer Response:

As part of the migration, the CSQ.OBJ_B_CHANNEL DB2 table will have its row size increased above 4 KB. The utility found that such a row size slready exists. Examine the CSQ.OBJ_B_CHANNEL DB2 table to verify that the migration has already occurred.

See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for full information about migration between releases.

CSQU583I
QSG qsg-name in DSG dsg-name is ready for migration
Explanation:

The request to migrate the queue-sharing group qsg-name in data-sharing group dsg-name to use new DB2 tables successfully verified that the queue-sharing group is ready to be migrated.

System Programmer Response:

Perform the migration. You should do this as a conditional step in the same job as the utility migration request, as shown in the sample job CSQ45ATB in the SCSQPROC library.

CSQU584E
QSG qsg-name in DSG dsg-name has incompatible QMGR levels
Explanation:

The queue-sharing group qsg-name in data-sharing group dsg-name cannot be migrated to use new DB2 tables because the levels of the queue managers using the data-sharing group are incompatible.

System Action:

The utility program is terminated.

System Programmer Response:

In order to perform the migration, all the queue managers in all the queue-sharing groups that use the data-sharing group must have installed a PTF and been started, to bring them to the necessary level. Examine the CSQ.ADMIN_B_QMGR DB2 table to determine the levels of the queue managers and those which need to be upgraded.

See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for full information about migration between releases and the PTF.

CSQU950I
csect-name IBM WebSphere MQ for z/OS version
Explanation:

This is part of the header to the report issued by the utility program.

CSQU951I
csect-name Data Conversion Exit Utility - date time
Explanation:

This is part of the header to the report issued by the utility program.

CSQU952I
csect-name Utility completed, return code=ret-code
Explanation:

The utility completed. The return code is 0 if all the input was processed successfully, or 8 if any errors were found.

System Action:

The utility ends.

System Programmer Response:

If the return code is non-zero, investigate the errors that were reported.

CSQU954I
n structures processed
Explanation:

This indicates how many data structures were processed by the utility program.

CSQU956E
Line line-number: structure array field has incorrect dimension
Explanation:

The dimension specified for a structure array field was not correct.

System Action:

Processing stops.

System Programmer Response:

Correct the field specification and resubmit the job.

CSQU957E
Line line-number: structure has field following a variable length field
Explanation:

There was an error in the indicated line. A variable length field must be the last field of a structure.

System Action:

Processing continues.

System Programmer Response:

Correct the field specification and resubmit the job.

CSQU958E
Line line-number: structure field name has unsupported type 'float'
Explanation:

There was an error in the indicated line. A field had a type of 'float', which is not supported.

System Action:

Processing continues.

System Programmer Response:

Correct the field specification and resubmit the job, or provide your own routine for converting such fields.

CSQU959E
Line line-number: structure field name has unsupported type 'double'
Explanation:

There was an error in the indicated line. A field had a type of 'double', which is not supported.

System Action:

Processing continues.

System Programmer Response:

Correct the field specification and resubmit the job, or provide your own routine for converting such fields.

CSQU960E
Line line-number: structure field name has unsupported type 'pointer'
Explanation:

There was an error in the indicated line. A field had a type of 'pointer', which is not supported.

System Action:

Processing continues.

System Programmer Response:

Correct the field specification and resubmit the job, or provide your own routine for converting such fields.

CSQU961E
Line line-number: structure field name has unsupported type 'bit'
Explanation:

There was an error in the indicated line. A field had a type of 'bit', which is not supported.

System Action:

Processing continues.

System Programmer Response:

Correct the field specification and resubmit the job, or provide your own routine for converting such fields.

CSQU965E
Invalid EXEC PARM
Explanation:

The EXEC PARM field was not blank.

System Action:

The utility is terminated.

System Programmer Response:

Change the JCL, and resubmit the job.

CSQU968E
Unable to OPEN ddname data set
Explanation:

The program was unable to open data set ddname.

System Action:

The utility is terminated.

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.

CSQU970E
Line line-number: syntax error
Explanation:

There was a syntax error in the indicated line.

System Action:

Processing stops.

System Programmer Response:

Correct the error and resubmit the job.

CSQU971E
Unable to GET from ddname data set
Explanation:

The program was unable to read a record from the ddname data set.

System Action:

The utility is terminated.

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.

CSQU972E
Unable to PUT to ddname data set
Explanation:

The program was unable to write the next record to the ddname data set.

System Action:

The utility is terminated.

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.

CSQU999E
Unrecognized message code ccc
Explanation:

An unexpected error message code was issued by the utility.

System Action:

Processing continues.

System Programmer Response:

Note the code ccc (which is shown in hexadecimal) and contact your IBM support center to report the problem.