Utilities messages (CSQU...)

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

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

The message is followed by a copy of the function statements from the SYSIN data set.

An attempt to obtain some storage failed.

The function is terminated, and any queue updates are backed out.

//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 Copying 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.

An attempt to release storage at address address back to the system failed.

The program usually ignores the error and continues with its function.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE or FREEMAIN request.

An MQCMIT call returned a completion code of MQCC_OK.

An MQBACK call returned a completion code of MQCC_OK.

The function is terminated.

Investigate the error that caused the backout to be done.

The utility program was unable to commit the last set of changes.

The updates are backed out, and the function is terminated.

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.

The utility program was unable to back out the last set of changes.

None, the function is already being terminated because of the error that led to attempting the backout.

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.

An attempt to connect to a queue manager or queue-sharing group named conn-id was unsuccessful.

The requested function is not performed.

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.

An attempt to disconnect from a queue manager or queue-sharing group named conn-id was unsuccessful.

The utility program terminates. (This is not an error, because the disconnection request is the last function that the utility program processes.)

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

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.

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

The initialization command handler ends, but the channel initiator continues.

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 WebSphere MQ (COMMAND).

The program was unable to open data set ddname.

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.

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.

The program opened the data set ddname, but the data set did not have a record format of VBS.

If the LOAD input data set cannot be opened, the utility program terminates.

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.

The input data set ddname is still open after a request was made to close it.

The program continues with its termination procedures.

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.

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.

The function is terminated.

Check that the page set has not been corrupted, and that the page set number corresponds to the DDname.

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.)

The function is terminated.

Check the queue name that was specified.

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.

The function is terminated.

This might be the result of performing a fuzzy backup (as described in How to back up and recover pagesets) or because the queue manager terminated abnormally. Restart the queue manager and then terminate it normally.

The utility cannot operate because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.

The utility is terminated.

The utility function identified by function has been stabilized with the functional capabilities of version version.

Processing continues and additional messages might be output providing further information.

Review the use of the utility function.

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.

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

The function is terminated, and any queue updates are backed out.

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.

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.

The function is terminated, and any queue updates are backed out.

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.

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.

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.

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

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.

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.

The channel or authentication information definition is not built.

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.

If some information was excluded, check that the authentication information objects were selected correctly.

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

In the COMMAND function, the assembled command had more than 32 762 characters.

The command is ignored, and no more commands are processed.

Check that the command is correctly formed according to the concatenation rules

In the COMMAND function, get processing for a response was timed out whilst more responses were expected.

The next command will be processed, unless there have been too many timeouts.

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.

In the COMMAND function, get processing for a response timed out four times.

No more commands are processed.

See message CSQU051E.

In the COMMAND function, the responses to a DISPLAY command were not as expected.

The DISPLAY command response is shown as is, rather than being formatted. The next command is processed.

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

Contact your IBM support center to report the problem.

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

This indicates which queue manager your commands are directed to.

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.

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

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

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

Incorrect data length for message msg-no. act-length bytes found, exp-length bytes expected

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.

Processing for the command is terminated.

Check that the data set was created by the COPY function.

Processing for the command is terminated.

Check that the data set was created by the COPY function, and is not corrupted.

In the LOAD function, the utility program encountered a record that it does not recognize while reading from the input data set.

The function is terminated, and any queue updates are backed out.

Check that the data set was created by the COPY function, and is not corrupted.

The in-ddname data set is empty

When executing the LOAD, SLOAD or ANALYZE function, the input data set (DDname in-ddname) was empty.

Processing for the command is terminated.

Check that the data set was successfully created by the COPY function.

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

No more commands are processed.

In the COMMAND function, end of data on the input data set was reached before the building of a command was complete.

The command is ignored. There are no more commands to process.

Check that the command is correctly formed according to the concatenation rules.

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.

The function is terminated.

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.

The MQGET call for q-name was unsuccessful.

The function is terminated, and any queue updates are backed out.

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.

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.

The function is terminated, and all queue updates are backed out.

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.

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.

The function is terminated, and all queue updates are backed out.

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.

Because MAXUMSGS was reached, a syncpoint was taken which commits the queue changes made so far.

The function continues, but no further functions will be processed.

None, unless the function fails for some reason after this message. In that case, note that some queue changes will have been committed, and you should make appropriate adjustments before rerunning the job.

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

The page set is not processed.

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

Data set ddname was opened, but it is not empty.

The page set is not formatted.

Ensure that the data sets specified are empty, and resubmit the job if necessary.

Processing of ddname data set for function function has completed.

Processing continues with the next page set.

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

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

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

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

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

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

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.

Processing is terminated.

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

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

The utility is terminated.

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

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.

The utility is terminated.

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

There are no function statements in the SYSIN data set.

The utility is terminated.

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

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, then resubmit the job.

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

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, and resubmit the job.

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

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, and resubmit the job.

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

The utility is terminated.

See MQSC commands for a list of valid functions, and resubmit the job.

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, and resubmit the job.

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

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, and resubmit the job.

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

The utility is terminated.

See Configuring z/OS for information about the correct syntax required for the statement, and resubmit the job.

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.

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, then resubmit the job.

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

The utility is terminated.

See MQSC commands for information about the correct syntax required for the statement, and resubmit the job.

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

The utility is terminated.

Check that the statement is correctly formed according to the concatenation rules.

The statement has more than 10 continuations.

The utility is terminated.

Check that the statement is correctly formed according to the concatenation rules.

The statement syntax is incorrect because a keyword is repeated.

The utility program is terminated.

Check the syntax in the input data set. See CSQUTIL for further information about the utility program.

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.

The function is terminated.

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.

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

The function is terminated.

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

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.

The function is terminated.

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

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

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

The utility program is executing function function-name.

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

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

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

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

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

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

The utility program is copying page set psid.

The utility program is copying queue q-name.

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

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

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

Loading queue sourceq to targetq

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.

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

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

This indicates how many queues were loaded successfully.

The utility program is emptying page set psid.

The utility program is emptying queue q-name.

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

This indicates how many queues were emptied.

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

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

The utility program experienced an error while executing function function.

The utility program terminates.

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

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

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.

The utility ends.

See IBM MQ for z/OS codes for information about the return code from the utility.

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

The utility ends.

Check any functions that failed.

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

Processing continues with the next page set.

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.

The function is terminated.

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

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

The function continues.

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

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

Processing continues with the next page set.

Processing queue queue-name

When executing the ANALYZE function, indicates the start of processing queue queue-name from the input data set.

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

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

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.

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

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

Processing continues with the next page set.

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

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

Processing continues with the next page set.

Check the dataset 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.

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

Processing continues with the next page set.

Specify a valid page set, and resubmit the job.

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.

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.

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

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.

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

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

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

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

Processing continues.

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

MQPUT of message msg-no failed. MQCC=mqcc MQRC=mqrc (mqrc-text)

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.

Processing for the command is terminated.

Using 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.

msg-count messages (msg-from-msg-to) found (total size text-length)

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.

Queue queue-name was not found in the input data set

The LOAD or SLOAD function being executed specified a source queue name of queue-name which was not found on the input data set.

Processing for the command is terminated.

Specify the correct input file, correct queue name in the command, and try again.

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.

The transmission queue cannot be switched because the channel initiator is not active

8

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.

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

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

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.

The function is terminated.

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

csect-name module-name is not a valid channel initiator parameter module

8

The module specified for channel initiator parameters is not in the correct format.

The function is terminated.

Check the member name specified on the XPARM function.

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

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

Processing for the command is terminated.

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).

Channel channel-name

The utility program is processing the requested function for the channel named channel-name.

Processing continues.

Check subsequent messages to determine whether the requested function was processed successfully.

n channels processed

This message identifies the number of channels that were processed by the requested function.

Processing continues.

None required.

A switch of transmission queue is not required for this channel

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.

Processing continues.

None required.

A switch of transmission queue is pending for this channel

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.

Processing continues.

None required.

A switch of transmission queue is in progress for this channel

This message identifies that a switch of transmission queue isin progress for the channel identified in the preceding CSQU183I message.

Processing continues.

Use console messages issued by the queue manager to determine the status of the switch operation, if required.

From transmission queue xmit-qname

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.

Processing continues.

None required.

To transmission queue xmit-qname

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.

Processing continues.

None required.

There are num-msgs messages queued for this channel on xmitq-name

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.

Processing continues.

None required.

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

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.

Processing for the command is terminated.

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.

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

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.

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

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).

The transmission queue cannot be switched because the channel is active

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.

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

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

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

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

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

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

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).

Switching the transmission queue for this channel

A switch of transmission queue has been initiated for the channel identified in the preceding CSQU183I message.

Processing continues.

Use subsequent messages to determine if the switch of transmission queue completes successfully

Moving messages for this channel - num-msgs messages moved

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.

Processing continues.

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.

Moving of messages complete - num-msgs messages moved

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.

Processing continues.

None required.

The transmission queue has been switched successfully

A switch of transmission queue for the channel identified in the preceding CSQU183I message has completed successfully.

Processing continues.

None required.

Function requires command level required-cmdlevel, the queue manager's command level is qmgr-cmdlevel

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.

Processing for the command is terminated.

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.

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

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.

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.

The utility terminates.

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

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

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.

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.

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.

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

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

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.

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

Processing continues.

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

An MQGET call encountered a data conversion problem.

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.

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

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

The utility is terminated.

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

An MQOPEN call for the queue manager was unsuccessful.

The utility is terminated.

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

An MQINQ call for the queue manager was unsuccessful.

The utility is terminated.

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

An MQCLOSE call for the queue manager was unsuccessful.

The utility is terminated.

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

The utility is terminated.

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

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

The utility is terminated.

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

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

The utility is terminated.

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

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

The utility is terminated.

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

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

The utility is terminated.

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

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

The utility is terminated.

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

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.

The utility is terminated.

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.

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

The utility is terminated.

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

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

The utility is terminated.

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

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

The utility is terminated.

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

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

The utility is terminated.

Investigate the problem reported in the preceding messages.

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

The utility is terminated.

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

Errors were detected in the rules table.

The utility is terminated.

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

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).

The utility is terminated.

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

An MQDISC call for the queue manager was unsuccessful.

The utility is terminated.

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

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

This identifies the utility function requested.

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

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

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.

The utility terminates.

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.

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

The utility program is terminated.

Specify the required parameters and rerun the job.

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

The utility program is terminated.

Correct the parameter and rerun the job.

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

The utility program is terminated.

Correct the parameters and rerun the job.

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.

The utility program is terminated.

Correct the parameter and rerun the job.

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

The utility program is terminated.

Correct the parameters and rerun the job.

An SQL error has occurred. Diagnostic information follows in message CSQU511I.

See the preceding utility error message.

Look at the information in message CSQU511I to determine the reason for the SQL error.

The utility program is terminated.

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

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.

The utility program is terminated.

Rerun the job later.

The queue-sharing group utility is not APF authorized.

The utility program is terminated.

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

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

The utility program is terminated.

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.

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

The utility program is terminated.

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

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

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

The utility program is terminated.

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.

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

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

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

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

Informational message containing the number of the QMGR in the QSG 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 QSG using CSQ5PQSG.

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.

The utility program is terminated.

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

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

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.

The utility program is terminated.

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.

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

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

The utility program is terminated.

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.

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.

The utility program is terminated.

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.

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

The utility program is terminated.

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.

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.

The utility program is terminated.

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.

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.

The utility program is terminated.

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

Resubmit the job if required.

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.

The utility program is terminated.

See message CSQU533E.

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

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

The utility program is terminated.

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

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.

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.

The utility program is terminated.

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.

The utility program is terminated.

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 Managing queue-sharing groups for information about removing such a queue manager from a queue-sharing group.

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

An internal routine returned a completion code specified by rc.

The utility program is terminated.

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

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

The utility program is terminated.

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

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.

Processing continues.

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.

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.

The utility program is terminated.

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.

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.

The utility program is terminated.

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.

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.

The utility program is terminated.

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.

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.

The utility program is terminated.

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.

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

The utility program is terminated.

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.

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

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

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

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

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.

The utility program is terminated.

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

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

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.

The utility program is terminated.

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

When removing the last queue manager in a queue sharing group, you 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. You should only perform this action if you 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.

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.

The utility program is terminated.

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 Migrating.

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.

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

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 a WebSphere 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.

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.

The utility program is terminated.

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 WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

The utility program is terminated.

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).

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

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.

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

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

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.

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

Rerun the job later.

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

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.

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

See Specifying offload options for shared messages for information about coupling facility structure sizes for use with queue-sharing groups.

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

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.

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

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.

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.

Processing continues.

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.

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.

The utility terminates.

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.

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 QSG 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 QSG qsg-name which will prevent the QMGR from starting.

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

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 your IBM support center.

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

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

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.

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

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

The utility program is terminated.

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.

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.

Processing continues.

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

Contact your IBM support center for assistance.

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.

Processing continues.

See message CSQU572E.

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.

Processing continues.

See message CSQU572E.

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

Processing continues.

See message CSQU572E.

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.)

Processing continues.

See message CSQU572E.

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.)

Processing continues.

See message CSQU572E.

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.)

Processing continues.

See message CSQU572E.

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.

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

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.

The utility program is terminated.

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 Migrating.

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

The utility program is terminated.

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 Migrating.

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.

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

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.

The utility program is terminated.

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.

For information about migration and compatibility between releases, see Migrating.

The queue-sharing group, qsg-name, cannot be migrated because no entry was found for it in the Db2 table, table-name.

The utility program is terminated.

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.

QMGR qmgr-name entry being removed from QSG qsg-name, needed for structure struc-name backup

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 WebSphere MQ, not the external name used by z/OS 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.

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

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.

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

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 WebSphere MQ, not the external name used by z/OS which includes the queue-sharing group name.)

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.

Db2 and CF structure out of sync for list header list-header-number in structure struc-name

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.

The mismatch is reported and the utility continues processing.

Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your IBM support center.

Db2 entry for list header list-header-number in structure struc-name: queue-name

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.

The mismatch is reported and the utility continues processing.

Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your IBM support center.

CF entry for list header list-header-number in structure struc-name: queue-name

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.

The mismatch is reported and the utility continues processing.

Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your IBM support center.

Missing CF entry for list header list-header-number in structure struc-name

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.

The mismatch is reported and the utility continues processing.

Starting or restarting one of the queue managers in the QSG 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 your IBM support center.

Structure struc-name has not yet been allocated by a queue manager

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.

The utility continues processing.

None.

Structure struc-name connected

The utility has successfully connected to CF structure struc-name.

The utility continues processing.

None.

Structure struc-name connection failed, IXLCONN RC=return-code reason=reason

The utility failed to connect to CF structure struc-name.

The utility skips any further queues for this structure and continues processing.

Examine the return and reason codes to determine why the IXLCONN connect command failed.

Structure struc-name disconnected

The utility has disconnected from CF structure struc-name.

The utility continues processing.

None.

Missing Db2 entry for list header list-header-number in structure struc-name

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.

The mismatch is reported and the utility continues processing.

Collect the items listed in Coupling facility problem determination and in Db2 manager problem determination and contact your IBM support center.

Unexpected return code for structure struc-name, IXLLSTE RC=return-code reason=reason

The utility failed to read a list entry from the CF structure struc-name.

The utility skips any further queues for this structure and continues processing.

Examine the return and reason codes to determine why the IXLLSTE read failed.

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

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

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

The utility ends.

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

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

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

Processing stops.

Correct the field specification and resubmit the job.

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

Processing continues.

Correct the field specification and resubmit the job.

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

Processing continues.

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

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

Processing continues.

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

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

Processing continues.

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

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

Processing continues.

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

The EXEC PARM field was not blank.

The utility is terminated.

Change the JCL, and resubmit the job.

The program was unable to open data set ddname.

The utility is terminated.

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.

There was a syntax error in the indicated line.

Processing stops.

Correct the error and resubmit the job.

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

The utility is terminated.

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.

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

The utility is terminated.

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.

An unexpected error message code was issued by the utility.

Processing continues.

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