Utilities messages (CSQU...)

CSQU000I: csect-name IBM MQ for z/OS Vn
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

If you encounter this error when submitting JCL to run CSQUTIL functions, make sure that we have defined an adequate value for the REGION size parameter or set the REGION size to 0M in the JCL. For example:

//SCOPY EXEC PGM=CSQUTIL,REGION=0M //STEPLIB DD DISP=SHR,DSN=thlqual.SCSQANLE 
 //DD DISP=SHR,DSN=thlqual.SCSQAUTH ...

For more details about setting the REGION parameter, see Copy queues into a data set while the queue manager is running (COPY).

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 (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). Resubmit the job if required.

CSQU008E: MQBACK failed. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). Resubmit the job if required.

CSQU009E: MQCONN failed for conn-id. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). Resubmit the job if required.

CSQU010E: MQDISC failed for conn-id. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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.

For information about the initialization command handler and the CSQINPX or CSQOUTX data sets, see Initialization and configuration files. For information about the COMMAND statement, see Issuing commands to IBM MQ (COMMAND).

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.

CSQU021E: Data set ddname does not have a record format of VBS
Explanation: The program opened the data set ddname, but the data set did not have a record format of VBS.
System action: If the LOAD input data set cannot be opened, the utility program terminates.
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 and is of the correct record format.

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 might 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 stand-alone utility functions cannot process it.
System action: The function is terminated.
System programmer response: This might be the result of performing a fuzzy backup (as described in How to back up and recover page sets) 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 IBM MQ do not allow all functions to be used.
System action: The utility is terminated.

CSQU037I: function has been stabilized with version function
Explanation: The utility function identified by function has been stabilized with the functional capabilities of version version.
System action: Processing continues and additional messages might be output providing further information.
System programmer response: Review the use of the utility function.

CSQU038I

Use runmqsc -n on your client machine for client channel definitions from version 8.0.

Explanation

The MAKECLNT utility function of CSQUTIL, that generates a client channel definition table (CCDT), has been stabilized.

From version 8.0, use the runmqsc utility on the client machine to generate the CCDT instead.

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 cannot be made for queue managers other than the target, qmgr-name
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 (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). 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 LDAPPWD 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

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.

CSQU053E

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

Check the load libraries used are consistent with the queue manager being used.

Contact the 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 data length for message msg-no. act-length bytes found, exp-length bytes expected
Severity: 8
Explanation: In the LOAD or SLOAD function, when attempting to read the record for message number msg-no for the queue being processed, the actual record length was found to be different to the expected record length.
System action: Processing for the command is terminated.
System programmer response: Check that the data set was created by the COPY function.

CSQU061E

An error occurred accessing the in-ddname data set for message msg-no. Reason=reason-code

Explanation

When executing the LOAD, SLOAD or ANALYZE function and attempting to read message msg-no for queue being processed, an error was detected. The reason code specifies the specific error, as follows:

4: First record in the data set does not identify a queue
8: Unexpected end-of-file
12: Unknown record type

System action

Processing for the command is terminated.

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.

CSQU063E: The in-ddname data set is empty
Severity: 8
Explanation: When executing the LOAD, SLOAD or ANALYZE function, the input data set (DDname in-ddname) was empty.
System action: Processing for the command is terminated.
System programmer response: Check that the data set was successfully created by the COPY function.

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.

CSQU080E: MQCLOSE failed for queue q-name. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). Resubmit the job if required.

CSQU082E: MQGET failed for queue q-name. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). Resubmit the job if required.

CSQU083E: MQOPEN failed for queue q-name. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). Resubmit the job if required.

CSQU085E: MQPUT failed for queue q-name. MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form). 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 we 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.

CSQU096I

csect-name FORMAT TYPE(type) skipped for page set psid

Explanation

The type of formatting for page set psid has been skipped because it is not allowed.

FORMAT TYPE(REINTRODUCE) is never allowed for page set zero. For other values, an earlier message will be issued which explains the problem.

System action

This page set is skipped, but FORMAT processing continues with the next page set.

System programmer response

Use the START QMGR BACKMIG command to migrate page set zero if required, and if it is allowed. Investigate earlier messages if necessary.

CSQU097E: csect-name FORMAT TYPE(type) TARGVER(target-vrm) failed for page set psid. Page set last used at old-vrm
Explanation: An attempt was made to use the FORMAT command to reintroduce the page set psid at version target-vrm. The page set was last used at version old-vrm and this migration is not supported by the utility. See FORMAT for a description of supported conversions.
System action: This page set is skipped, but FORMAT processing continues with the next page set.
System programmer response: Use the correct version of the utility if that is supported. If not, it might be possible to add the page set with FORMAT TYPE(NEW) or FORMAT TYPE(RECOVER) using the target-vrm version of the utility.

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 MQSC commands for information about the correct syntax required for the statement, then 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 MQSC commands 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 MQSC commands 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 MQSC commands 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 MQSC commands 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 MQSC commands 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 Configure z/OS 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 MQSC commands for information about the correct syntax required for the statement, then 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 MQSC commands 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.

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.

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 CSQUTIL 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: Connect 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: Copy page set psid
Explanation: The utility program is copying page set psid.

CSQU130I: Copy 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 sourceq to targetq
Severity: 0
Explanation: When executing the LOAD or SLOAD function, identifies the name of the target queue being loaded, and the name of the queue on the input data set from which messages are being copied.

CSQU136I

msg-count messages (msg-from-msg-to) have been loaded (total size text-length)

Severity

Explanation

When executing the LOAD or SLOAD function, this error code indicates that a number of messages have been successfully loaded on to the target queue from the input data set.

msg-count is the number of messages loaded
msg-from-msg-to is the message number range in the messages for the queue on the input data set.
text-length is the total length of the message texts loaded (in MB or KB)

CSQU137I: Skipping queue q-name
Explanation: This indicates that queue q-name is being bypassed, because of the SKIPQS or FROMQ option used with the LOAD function.

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

msg-count messages (msg-from-msg-to) skipped (total size text-length). Reason=reason-code

Severity

Explanation

When executing the LOAD or SLOAD function, indicates that a number of messages have been ignored from the input data set.

msg-count is the number of messages ignored
msg-from-msg-to is the message number range in the messages for the queue on the input data set.
text-length is the total length of the message texts ignored (in MB or KB)

The reason code indicates why the messages were ignored:

4: messages skipped due to skipmsgs parameter in LOAD or SLOAD command
8: messages skipped due to an MQPUT error
12: messages skipped due to an error on MQOPEN
16: messages skipped due to an MQPUT error immediately following a sync point
20: messages skipped due to an error on MQCLOSE
24: messages skipped due to an error when taking a sync point
28: messages skipped due to MSGCOUNT limit (in the LOAD or SLOAD command) being reached

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 IBM MQ for z/OS codes 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: Processing queue queue-name
Severity: 0
Explanation: When executing the ANALYZE function, indicates the start of processing queue queue-name from the input data set.

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

CSQUTIL COPYPAGE or RESETPAGE functions were unable to recognize the data set as an IBM MQ Page set. This could be due to an invalid data set, or a back level version of IBM MQ libraries being used.

System action

Processing continues with the next page set.

System programmer response

Check the data set is a valid IBM MQ page set.

Check the IBM MQ libraries being used are the same as the libraries used by the queue manager.

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.

CSQU169E: MQPUT of message msg-no failed. MQCC=mqcc MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: When executing the LOAD or SLOAD function, an MQPUT failed for message number msg-no in the queue currently being processed on the input data. The mqcc and mqrc (mqrc-text provides the MQRC in textual form) indicate the reason for failure.
System action: Processing for the command is terminated.
System programmer response: Use the MQ completion code and reason code in the message, determine the cause of error and correct the problem. Then rerun the LOAD or SLOAD, starting with the queue being processed at the time of the error. If any messages had been successfully loaded from the input queue before the failure, use the SKIPMSGS parameter on the LOAD or SLOAD command to bypass those messages.

CSQU170I: msg-count messages (msg-from-msg-to) found (total size text-length)
Severity: 0
Explanation: When executing the ANALYZE function, this message is displayed for the queue being processed from the input data set. The number of messages and the total length of the message text are shown.

CSQU171E: Queue queue-name was not found in the input data set
Severity: 8
Explanation: The LOAD or SLOAD function being executed specified a source queue name of queue-name which was not found on the input data set.
System action: Processing for the command is terminated.
System programmer response: Specify the correct input file, correct queue name in the command, and try again.

CSQU172I: Processing function-name for data set ddname, current-page of total-pages pages processed, percentage% complete
Explanation: If a CSQUTIL function to process a page set is long-running, this message is issued periodically to indicate how many pages have been processed so far.

CSQU179E: The transmission queue cannot be switched because the channel initiator is not active
Severity: 8
Explanation: The utility program is unable to initiate a switch of transmission queue for the channel identified in the preceding CSQU183I message because the channel initiator is not active.
System action: Processing continues, however, the transmission queue for the affected channel is not switched.
System programmer response: Start the channel initiator, then either restart the channel or rerun the command to initiate the switch of transmission queue.

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
Severity: 8
Explanation: The module specified for channel initiator parameters is not in the correct format.
System action: The function is terminated.
System programmer response: Check the member name specified on the XPARM function.

CSQU182E

An error occurred obtaining the list of channels, reason mqrc (mqrc-text)

Severity

Explanation

The utility program was unable to identify the list of channels to process.

System action

Processing for the command is terminated.

System programmer response

Use the reason code to identify and resolve the error, then rerun the command if required.

See API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

CSQU183I: Channel channel-name
Severity: 0
Explanation: The utility program is processing the requested function for the channel named channel-name.
System action: Processing continues.
System programmer response: Check subsequent messages to determine whether the requested function was processed successfully.

CSQU184I: n channels processed
Severity: 0
Explanation: This message identifies the number of channels that were processed by the requested function.
System action: Processing continues.
System programmer response: None required.

CSQU185I: A switch of transmission queue is not required for this channel
Severity: 0
Explanation: This message identifies that a switch of transmission queue is not required for the channel identified in the preceding CSQU183I message. This indicates the channel uses the currently configured transmission queue.
System action: Processing continues.
System programmer response: None required.

CSQU186I

A switch of transmission queue is pending for this channel

Severity

Explanation

This message identifies that a switch of transmission queue is pending for the channel identified in the preceding CSQU183I message. This indicates the configured transmission queue for the channel has been changed, either by updating the DEFCLXQ queue manager attribute, or by altering the value of the CLCHNAME attribute of a transmission queue, since the channel last started.

The switch of transmission queue will occur the next time the channel starts or if the switch is initiated using the CSQUTIL function SWITCH CHANNEL.

A switch operation is also reported as pending if the operation was previously initiated, but the queue manager was stopped while messages were being moved from the old transmission queue to the new transmission queue. To resume the switch operation either start the channel or use CSQUTIL to initiate the switch.

System action

Processing continues.

System programmer response

None required.

CSQU187I: A switch of transmission queue is in progress for this channel
Severity: 0
Explanation: This message identifies that a switch of transmission queue isin progress for the channel identified in the preceding CSQU183I message.
System action: Processing continues.
System programmer response: Use console messages issued by the queue manager to determine the status of the switch operation, if required.

CSQU188I: From transmission queue xmit-qname
Severity: 0
Explanation: This message is issued with other messages, such as CSQU186I, CSQU187I, and CSQU195I. It identifies the name of the transmission queue a channel is switching, or will switch, from.
System action: Processing continues.
System programmer response: None required.

CSQU189I: To transmission queue xmit-qname
Severity: 0
Explanation: This message is issued with other messages, such as CSQU186I, CSQU187I, and CSQU195I. It identifies the name of the transmission queue a channel is switching, or will switch, to.
System action: Processing continues.
System programmer response: None required.

CSQU190I: There are num-msgs messages queued for this channel on xmitq-name
Severity: 0
Explanation: This message is issued with CSQU186I and identifies there are currently num-msgs messages queued for the channel on the transmission queue xmitq-name, that need to be moved when the transmission queue is switched.
System action: Processing continues.
System programmer response: None required.

CSQU191E

Unable to access transmission queue xmitq-name, reason mqrc (mqrc-text)

Severity

Explanation

This message is issued with CSQU186I if the transmission queue, xmitq-name, that is currently used by the channel, cannot be accessed for the reason mqrc (mqrc-text provides the MQRC in textual form). This transmission queue must be accessible to move messages for the channel to the new transmission queue.

System action

Processing for the command is terminated.

System programmer response

Use the reason code to identify and resolve the error, then rerun the command if required.

See API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

Alternatively, use the CSQUTIL function SWITCH CHANNEL with the MOVEMSGS(NO) option to switch transmission queue without moving messages. If this option is selected it is the responsibility of the system programmer to resolve any messages for the channel on the transmission queue, xmitq-name, after the switch has completed.

CSQU192E

The status of this channel is unavailable, reason mqrc (mqrc-text)

Severity

Explanation

The utility program was unable to identify the current status of the channel identified in the preceding CSQU183I message to determine if a switch of transmission queue is pending or in progress.

System action

Processing continues, but the transmission queue for the affected channel is not switched if this was requested.

System programmer response

Use the reason code to identify and resolve the error, then rerun the command if required.

See API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

CSQU193E

The transmission queue cannot be switched because the channel is active

Severity

Explanation

The utility program was unable to initiate a switch of transmission queue for the channel identified in the preceding CSQU183I message because the channel status was neither STOPPED nor INACTIVE.

If the cluster sender channel is showing STOPPED status, but message CSQU193E is still reporting, the channel cannot stop immediately. Message reallocation is taking place while a request to STOP CHANNEL channel-name is made.

The channel continues to reallocate messages, and stops once this process is complete. This process can take some length of time if there are a large number of messages on the queue assigned to this channel.

We should wait for sufficient time to ensure that message reallocation completes, then switch the transmission queue.

System action

Processing continues, but the transmission queue for the affected channel is not switched.

System programmer response

Stop the channel, then either restart the channel or rerun the command to initiate the switch of transmission queue.

CSQU194E

The switch of transmission queue failed, reason mqrc (mqrc-text)

Severity

Explanation

The utility program was unable to switch the transmission queue for the channel identified in the preceding CSQU183I message.

System action

Processing continues, but the transmission queue for the affected channel is not switched.

System programmer response

Use the reason code to identify and resolve the error, then rerun the command if required.

See API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

CSQU195I: Switching the transmission queue for this channel
Severity: 0
Explanation: A switch of transmission queue has been initiated for the channel identified in the preceding CSQU183I message.
System action: Processing continues.
System programmer response: Use subsequent messages to determine if the switch of transmission queue completes successfully

CSQU196I

Moving messages for this channel - num-msgs messages moved

Severity

Explanation

A switch of transmission queue requires that messages for a channel are moved from the old transmission queue to the new transmission queue. This message is periodically issued during a switch of transmission queue to report the progress of this operation for the channel identified in the preceding CSQU183I message.

System action

Processing continues.

System programmer response

If this message is repeatedly issued it might indicate the old transmission queue cannot be drained of messages for the channel, which means the switching process can not complete. Applications continue to put messages to the old transmission queue during the switching process to preserve ordering.

If the switching process cannot complete, this might indicate that messages are being put to the old transmission queue faster than they can be moved by the switching process, or uncommitted messages remain on the old transmission queue for the channel.

Use console messages issued by the queue manager, such as CSQM554I, and commands such as DISPLAY QSTATUS, to determine why the switch operation is unable to complete.

CSQU197I: Moving of messages complete - num-msgs messages moved
Severity: 0
Explanation: A switch of transmission queue requires that messages for a channel are moved from the old transmission queue to the new transmission queue. This message indicates the process of moving messages for the channel identified in the preceding CSQU183I message has completed. The number of messages that were moved to the new transmission queue is identified by num-msgs.
System action: Processing continues.
System programmer response: None required.

CSQU198I: The transmission queue has been switched successfully
Severity: 0
Explanation: A switch of transmission queue for the channel identified in the preceding CSQU183I message has completed successfully.
System action: Processing continues.
System programmer response: None required.

CSQU199E: Function requires command level required-cmdlevel, the queue manager's command level is qmgr-cmdlevel
Severity: 8
Explanation: The utility program was unable to perform the requested function, identified by function, because this is not supported by the queue manager to which it is connected. To perform the requested function the queue manager's command level must be required-cmdlevel or greater, but the queue manager's command level is qmgr-cmdlevel.
System action: Processing for the command is terminated.
System programmer response: Ensure the utility program connected to the required queue manager. If this was correct, the queue manager must be upgraded before the requested function can be used.

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 (mqrc-text)
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 API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form). 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 (mqrc-text)
Explanation: An MQINQ call for the dead-letter queue was unsuccessful.
System action: Processing continues.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU213I: Unable to convert message, MQCC=mqcc MQRC=mqrc (mqrc-text)
Explanation: An MQGET call encountered a data conversion problem.
System action: The message is rolled back and remains on the queue. Processing of the remaining messages on the queue continues. Use an alternative means to remove this message from the dead-letter queue.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU220E: Unable to connect to queue manager qmgr-name, MQCC=mqcc MQRC=mqrc (mqrc-text)
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 API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU221E: Unable to open queue manager, MQCC=mqcc MQRC=mqrc (mqrc-text)
Explanation: An MQOPEN call for the queue manager was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU222E: Unable to inquire queue manager, MQCC=mqcc MQRC=mqrc (mqrc-text)
Explanation: An MQINQ call for the queue manager was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU223E: Unable to close queue manager, MQCC=mqcc MQRC=mqrc (mqrc-text)
Explanation: An MQCLOSE call for the queue manager was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU224E

Unable to browse dead-letter queue q-name, MQCC=mqcc MQRC=mqrc (mqrc-text)

Explanation

An MQOPEN call for browsing the dead-letter queue was unsuccessful. This is typically because of one of the following reasons:

Another process has opened the queue for exclusive access.
An invalid queue name was specified.
The alias name for one of the following modules has been lost:
- CSQBSRV
- CSQAPEPL
- CSQBCRMH
- CSQBAPPL

System action

The utility is terminated.

System programmer response

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU225E: Unable to close dead-letter queue, MQCC=mqcc MQRC=mqrc (mqrc-text)
Explanation: An MQCLOSE call for the dead-letter queue was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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 (mqrc-text)
Explanation: An MQGET call for the dead-letter queue was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU228E: Unable to commit or backout dead-letter queue action, MQCC=mqcc MQRC=mqrc (mqrc-text)
Explanation: An MQCMIT or MQBACK call for the dead-letter queue was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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 (mqrc-text)
Explanation: An MQDISC call for the queue manager was unsuccessful.
System action: The utility is terminated.
System programmer response: Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

CSQU300I

Incorrect parameters provided. Usage information follows:

CSQUDSPM (-m QMgrName) (-o status | -s) (-o all) (-su) (-a)

-m QMgrName: Display information for this queue manager only

-o status : Display operational status of the queue manager, or queue managers

-s : Display operational status of the queue manager, or queue managers

-o all : Display all details of the queue manager, or queue managers

-su : Do not show information for queue managers that have an unknown version

-a : Display information for running queue managers only

Explanation

Incorrect parameters were passed to CSUDSPM.

System action

The utility stops processing.

System programmer response

Correct the parameters and resubmit the utility.

CSQU307I: No queue manager with the specified name exists
Explanation: The CSQUDSPM utility was run, specifying a queue manager name that could not be located.
System action: The utility stops processing.
System programmer response: Either correct the queue manager name, or run the utility without specifying a particular queue manager.

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.

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.

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.

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.

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.

CSQU510I: SQL error information
Explanation: An SQL error has occurred. Diagnostic information follows in message CSQU511I.
System action: See the preceding utility error message.
System programmer response: Look at the information in message CSQU511I to determine the reason for the SQL error.

CSQU511I

DSNT408I SQLCODE = -sql-code, explanation

Explanation

This message provides additional diagnostic information direct from Db2. It is followed by further CSQU511I messages, similar to the following example block:

   CSQU511I   DSNT408I SQLCODE = -805, ERROR:  DBRM OR PACKAGE NAME DSNV11P1..CSQ5B9-
   CSQU511I            00.1A47B13F08B31B99 NOT FOUND IN PLAN CSQ5B900. REASON 03    
   CSQU511I   DSNT418I SQLSTATE   = 51002 SQLSTATE RETURN CODE                      
   CSQU511I   DSNT415I SQLERRP    = DSNXEPM SQL PROCEDURE DETECTING ERROR           
   CSQU511I   DSNT416I SQLERRD    = -251  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION 
   CSQU511I   DSNT416I SQLERRD    = X'FFFFFF05'  X'00000000'  X'00000000'           
   CSQU511I            X'FFFFFFFF'  X'00000000'  X'00000000' SQL DIAGNOSTIC         
   CSQU511I            INFORMATION

System action

The utility program is terminated.

System programmer response

Use the diagnostic information to determine the reason for the SQL error and correct the problem.

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 messages and Db2 codes sections within the Db2 for z/OS product documentation 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.

CSQU524I: QMGR number=nn
Explanation: Informational message containing the number of the QMGR in the queue sharing group to accompany informational message CSQU522I. The QMGR number is stored in the Db2 tables, the XCF group member and the connections to the CF structures. It is generated when a QMGR is added to a queue sharing group using CSQ5PQSG.

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 queue sharing group 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

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 queue sharing group 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 queue sharing group 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 queue sharing group 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 Manage queue sharing groups 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 queue sharing group 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 the 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 might 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 queue sharing group 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

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 queue sharing group 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 queue sharing group qsg-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 the queue manager is already a member of a different queue sharing group identified by qsg-name.

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.

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 queue sharing group 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 IBM 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

Use 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 we are trying to remove was last stopped. Then resubmit the job.

When removing the last queue manager in a queue sharing group, we must use the FORCE option, rather than REMOVE. This removes the queue manager from the queue sharing group, whilst not performing the consistency checks of the queue manager logs being required for recovery. We should only perform this action if we are going to be deleting the queue sharing group; see Removing a queue manager from a queue sharing group for more information on managing queue sharing groups.

CSQU555E: QMGR qmgr-name release level is incompatible with queue sharing group 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. For information about migration and compatibility between releases, see Maintain and migrate.

CSQU556I

QSG qsg-name may contain unexpected characters

Explanation

The queue sharing group qsg-name being added specifies a queue sharing group name that either contains the '@' character, or is shorter than four characters and therefore has '@' characters appended to the short name to make the name four characters in length.

System action

Processing to add the queue sharing group continues. The utility will complete with return code 4.

System programmer response

Verify that the queue sharing group name specified by qsg-name is the intended name to be used for the queue sharing group. If not, use the utility to remove the queue sharing group, correct the queue sharing group name, and resubmit the request to add the queue sharing group.

The '@' character, although allowed in the qsg-name, is inadvisable as it is not supported as a character in an IBM MQ object name. Any definition such as queue manager alias definitions or other objects that need to refer to the qsg-name, will be unable to refer to the qsg-name. If possible, avoid using these characters.

CSQU557E: The QMGR and queue sharing group names must be different
Explanation: The attempt to add a queue manager to a queue sharing group failed because queue managers cannot have the same name as the queue sharing group to which they belong.
System action: The utility program is terminated.

CSQU558E

QMGR qmgr-name entry cannot be removed from queue sharing group qsg-name, SMDS for structure struc-name is not empty

Explanation

The queue manager named by qmgr-name cannot be removed from the queue sharing group named by qsg-name because it owns a shared message data set for structure struc-name which is not marked as empty, so it may still contain current message data. (The value shown for struc-name is the 12-character name as used by IBM MQ, not the external name used by z/OS which includes the queue sharing group name.)

System action

The utility program is terminated.

System programmer response

The queue manager cannot be removed until the owned shared message data set has been marked as empty, indicating that it has been closed normally by the owning queue manager at a time when it does not contain any message data. All shared messages with message data in the data set must have been read or marked as deleted first, and the owning queue manager must be connected to the structure in order to remove the deleted messages and free the data set space.

The current status of each shared message data set for the structure can be displayed using the command DISPLAY CFSTATUS(struc-name) TYPE(SMDS).

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 we are unable to resolve the problem, contact the IBM support 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 queue sharing group 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 Specify offload options for shared messages 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 been 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. If the structure is not allocated, then the structure will be allocated when the first queue manager starts.

System action

Processing continues.

System programmer response

Use the z/OS command DISPLAY XCF,STRUCTURE,STRNAME=<CFSTRNAME> to display the status (including size) 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.

CSQU567E

QMGR qmgr-name not added to Db2 table due to a number mismatch.

Explanation

The QMGR qmgr-name could not be added to Db2 tables due to a mismatch in the QMGR numbers as indicated by message CSQU568E issued earlier.

System action

The utility terminates.

System programmer response

Add the QMGRs in the order corresponding to their QMGR number values in the XCF group, as can be seen by message CSQU524I when running CSQ5PQSG queue sharing group utility with the "VERIFY QSG" parameter.

If the issue is linked to a persistent failing connection to the CSQ_ADMIN structure, the problem can be resolved by clearing the CF structure using the SETXCF FORCE command.

CSQU568E

QMGR number mismatch for QMGR qmgr-name in queue sharing group qsg-name: Db2 value=nn, XCF member value=nn, CSQ_ADMIN connection value=nn

Explanation

The QMGR number is stored in the Db2 tables, the XCF group member, and the connections to the CF structures. The QMGR number is created when a QMGR is added to a queue sharing group by using the queue sharing group utility (CSQ5PQSG).

This message indicates that there is a mismatch in the stored values for QMGR qmgr-name in queue sharing group qsg-name which will prevent the QMGR from starting.

System action

The utility terminates after all members in the XCF group have been processed.

System programmer response

If the QMGR number value is -1, the entry does not exist. Use the CSQ5PQSG utility with "ADD QMGR" parameter to add the missing entry.

If the QMGR number value is 0, the value has not been initialised (XCF group member and CSQ_ADMIN connection values only). Start the QMGR to initialize the value.

If QMGR number value is greater than 0, collect the items listed in the Coupling Facility problem determination guide and contact the IBM support center.

CSQU569E

Unexpected CSQ_ADMIN connection found for QMGR qmgr-name

Explanation

For each QMGR in the queue sharing group there should only be one connection to the CSQ_ADMIN structure. This message is issued for each additional connection found.

System action

The utility terminates after all members in the XCF group have been processed.

System programmer response

This situation should not occur. The connections can be displayed using the display XCF command for the CSQ_ADMIN structure.

Collect the items listed in the Coupling Facility problem determination guide and contact your IBM support center.

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 the 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 IBM 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 IBM 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 IBM 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 IBM 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.

CSQU581E

DSG dsg-name has incompatible QMGR levels in QSG qsg-name

Explanation

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

System action

The utility program is terminated.

System programmer response

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. Look at the fields QMGRNAME, MVERSIONL, MVERSIONH and investigate the queue managers with the lower values in MVERSIONH.

For information about migration and compatibility between releases, see Maintain and migrate.

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.

For information about migration and compatibility between releases, see Maintain and migrate.

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. We should do this as a conditional step in the same job as the utility migration request, as shown in the sample jobs CSQ4570T and CSQ4571T 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

For information about migration and compatibility between releases, see Maintain and migrate.

CSQU585E

QSG qsg-name entry cannot be migrated, not found in Db2 table table-name

Explanation

The queue sharing group, qsg-name, cannot be migrated because no entry was found for it 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 is connected to the correct Db2 data-sharing group. If necessary resubmit the job.

CSQU586I

QMGR qmgr-name entry being removed from queue sharing group qsg-name, needed for structure struc-name backup

Explanation

The queue manager named by qmgr-name is being force removed from the queue sharing group named by qsg-name and it has information about backups for structure struc-name. (The value shown for struc-name is the 12-character name as used by IBM MQ, not the external name used by Db2 which includes the queue sharing group name.)

If the queue manager qmgr-name is added back to the queue sharing group it will cause an inconsistent state that could prevent structure struct-name from being recovered should it fail before a structure backup is taken.

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

System action

The queue manager is removed from the queue sharing group, and the utility program ends with return code 4.

System programmer response

If CF structure struc-name is usable, take a backup of CF structure struc-name as soon as possible using another queue manager in the queue sharing group. Otherwise, if the queue manager qmgr-name is added back to the queue sharing group it should be restarted before recovering structure struc-name.

CSQU587I

QMGR qmgr-name entry being removed from queue sharing group qsg-name, SMDS for structure struc-name is not empty

Explanation

The queue manager named by qmgr-name is being removed from the queue sharing group named by qsg-name while it owns a shared message data set for structure struc-name that is not marked as empty, so it may still contain current message data. (The value shown for struc-name is the 12-character name as used by IBM MQ, not the external name used by z/OS which includes the queue sharing group name.)

System action

The queue manager is removed from the queue sharing group, and the utility program ends with return code 4.

Messages on the SMDS for queue manager qmgr-name will remain accessible as long as the SMDS is retained.

CSQU680E: Db2 and CF structure out of sync for list header list-header-number in structure struc-name
Severity: 8
Explanation: The row for the shared queue in Db2 represents a different queue than the one found in the CF structure for list header list-header-number in structure struc-name. This inconsistency causes the queue manager to abend with 5C6-00C51053 and issue message CSQE137E. Messages CSQU681I and CSQU682I are also issued, providing further details.
System action: The mismatch is reported and the utility continues processing.
System programmer response: Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your Db2 support center.

CSQU681I: Db2 entry for list header list-header-number in structure struc-name: queue-name
Severity: 0
Explanation: This message is issued with message CSQU680E. Queue-name is the name of the queue found in Db2 for list header list-header-number in structure struc-name.
System action: The mismatch is reported and the utility continues processing.
System programmer response: Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your Db2 support center.

CSQU682I: CF entry for list header list-header-number in structure struc-name: queue-name
Severity: 0
Explanation: This message is issued with message CSQU680E. Queue-name is the name of the queue found in the CF for list header list-header-number in structure struc-name.
System action: The mismatch is reported and the utility continues processing.
System programmer response: Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your Db2 support center.

CSQU683E: Missing CF entry for list header list-header-number in structure struc-name
Severity: 8
Explanation: The Db2 entry for list header list-header-number in structure struc-name indicates that a current copy is available in the CF, however, the copy is not found. This inconsistency causes return code 2085 for applications trying to use this queue.
System action: The mismatch is reported and the utility continues processing.
System programmer response: Starting or restarting one of the queue managers in the queue sharing group will resolve the problem. If the problem persists, collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact the IBM support center.

CSQU684I: Structure struc-name has not yet been allocated by a queue manager
Severity: 0
Explanation: The CF structure struc-name is not allocated. This happens when the first IXLCONN to the structure is issued, and should only be issued by a queue manager in the QSG.
System action: The utility continues processing.
System programmer response: None.

CSQU685I: Structure struc-name connected
Severity: 0
Explanation: The utility has successfully connected to CF structure struc-name.
System action: The utility continues processing.
System programmer response: None.

CSQU686E: Structure struc-name connection failed, IXLCONN RC=return-code reason=reason
Severity: 8
Explanation: The utility failed to connect to CF structure struc-name.
System action: The utility skips any further queues for this structure and continues processing.
System programmer response: Examine the return and reason codes to determine why the IXLCONN connect command failed.

CSQU687I: Structure struc-name disconnected
Severity: 0
Explanation: The utility has disconnected from CF structure struc-name.
System action: The utility continues processing.
System programmer response: None.

CSQU688E: Missing Db2 entry for list header list-header-number in structure struc-name
Severity: 0
Explanation: The CF entry for list header list-header-number in structure struc-name indicates that a current copy is available in Db2, however, the copy is not found. This inconsistency causes a problem if a new queue is defined for the same list header.
System action: The mismatch is reported and the utility continues processing.
System programmer response: Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact the IBM support center.

CSQU689E: Unexpected return code for structure struc-name, IXLLSTE RC=return-code reason=reason
Severity: 8
Explanation: The utility failed to read a list entry from the CF structure struc-name.
System action: The utility skips any further queues for this structure and continues processing.
System programmer response: Examine the return and reason codes to determine why the IXLLSTE read failed.

CSQU950I: csect-name IBM MQ for z/OS Vn
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 the IBM support center to report the problem.

Parent topic: Messages for IBM MQ for z/OS