Db2 manager messages (CSQ5...)

The queue manager has successfully established a connection to the named Db2 subsystem.

Processing continues.

None.

The queue manager's attempt to establish a connection to the named Db2 subsystem failed.

Queue manager startup is terminated.

This is normally an authorization error.

Consult the Db2 for z/OS Messages and Codes manual for an explanation of the codes and attempt to resolve the problem.

The queue manager is waiting for an eligible Db2 subsystem to become active so that a connection can be established. Alternatively, RRS is inactive or was started after the Db2 subsystems.

The queue manager waits for an eligible Db2 subsystem to become active.

Check whether the Db2 subsystem(s) are active. If not then start them. If they are active, ensure RRS is active and check that it was started prior to the Db2 subsystems.

During startup the queue manager was unable to find its entry in the Db2 administration tables, or the entry was incorrect.

The queue manager terminates with completion code X'6C6' and reason code X'00F50013'.

Check that a queue manager record exists in the Db2 tables for the Db2 data-sharing group specified. Check the QSGDATA system parameter specifies the correct Db2 data-sharing group. If so, check that a queue manager entry exists in the CSQ.ADMIN_B_QMGR table.

If you are migrating from a previous release of IBM® MQ, check also that you have updated the Db2 tables to the format for the current release. For information about migration and compatibility between releases, see Migrating.

The release level of the queue manager that is being started is incompatible with that of other members of the queue-sharing group.

The queue manager terminates with completion code X'6C6' and reason code X'00F50029'.

Verify that the correct load libraries are being used and that the queue-sharing group information in the system parameters has been specified correctly. Also use the queue-sharing group utility (CSQ5PQSG) to verify that the queue manager has been defined correctly in the Db2 administration tables, using the MIGRATE QSG option. Ensure that you use the same version of IBM MQ for the utility, as was used for running the queue manager.

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

If the MIGRATE QSG results show queue managers that no longer exist, but are still in the Db2 tables, use the REMOVE QMGR option or, if necessary, the FORCE QMGR option.

A mismatch has been detected between the Db2 data-sharing group specified on the QSGDATA system parameter and the queue manager entry in the CSQ.ADMIN_B_QMGR table.

The queue manager terminates with completion code X'6C6' and reason code X'00F50006'.

The queue-sharing group name specified on the QSGDATA system parameter must match that in which the queue manager is defined in the Db2 CSQ.ADMIN_B_QMGR table.

A non-zero or unexpected return code was returned from an RRSAF request. The Db2 plan involved was plan-name.

If the error occurs during queue manager startup or reconnect processing, the queue manager might terminate with completion code X'6C6' and reason code X'00F50016'. Otherwise, an error message is issued and processing is retried.

Determine the cause of the error using the RRS return and reason code from the message.

Consult the Db2 for z/OS Messages and Codes manual for an explanation of the codes and attempt to resolve the problem.

The Db2 subsystem to which the queue manager has connected is not a member of the Db2 data-sharing group specified on the QSGDATA system parameter.

The queue manager terminates with completion code X'6C6' and reason code X'00F50007'.

Ensure that the Db2 subsystem to which the queue manager has connected is a member of the data-sharing group specified on the QSGDATA system parameter.

Issue the Db2 command DIS GROUP to the Db2 subsystem and check the data-sharing group name matches the data-sharing group name on the QSGDATA system parameter.

A non-zero or unexpected SQL return code was returned from a Db2 SQL request.

The requested operation fails. Processing continues, but the failed request may result in further errors occurring. In some circumstances, the queue manager terminates with completion code X'6C6' and reason code X'00F50014'.

Determine the reason for the SQL error and correct the problem.

Consult the Db2 for z/OS Messages and Codes manual to determine the reason for the SQL error.

The queue manager received an unexpected return code from an IXCQUERY request.

The queue manager terminates with completion code X'6C6' and reason code X'00F50017'.

Determine the reason for the unexpected error and correct the problem.

Consult the z/OS MVS™ Programming: Sysplex Services Reference manual for an explanation of the return and reason code from the IXCQUERY request.

This message may occur if one or more of the queue managers in a Queue Sharing Group (QSG) do not have a member entry in the XCF group for the QSG.

Enter the following z/OS® command substituting the QSG name for xxxx:

D XCF,GRP,CSQGxxxx,ALL 

This will list the members of the XCF group. If any queue managers are defined as a member of the QSG, but do not have an entry in the XCF Group, use the ADD QMGR command of the CSQ5PQSG utility to restore the XCF group entry for that queue manager. The utility should be run for each queue manager which does not have an entry in the XCF group.

The queue manager received an unexpected return code from an IXCJOIN request.

The queue manager terminates with completion code X'6C6' and reason code X'00F50019'.

Determine the reason for the unexpected error and correct the problem.

Consult the z/OS MVS Programming: Sysplex Services Reference manual for an explanation of the return and reason code from the IXCJOIN request.

The queue manager received an unexpected return code from an IXCQUIES request.

The queue manager terminates with completion code X'6C6' and reason code X'00F50021'.

Determine the reason for the unexpected error and correct the problem.

Consult the z/OS MVS Programming: Sysplex Services Reference manual for an explanation of the return and reason code from the IXCQUIES request.

The queue manager received an unexpected return code from an IXCSETUS request.

The queue manager terminates with completion code X'6C6' and reason code X'00F50018'.

Determine the reason for the unexpected error and correct the problem.

Consult the z/OS MVS Programming: Sysplex Services Reference manual for an explanation of the return and reason code from the IXCSETUS request.

The queue manager received an abnormal termination notification from the Db2 subsystem to which it is connected.

The queue manager will clean up its connection to the Db2 subsystem and attempt to reconnect. If a Db2 group attach name was specified on the QSGDATA system parameter a connection to a different Db2 may occur.

Determine the reason for the Db2 abnormal termination. Correct the problem and attempt to restart the Db2 subsystem.

The queue manager received a STOP FORCE termination notification from the Db2 subsystem to which it is connected.

The queue manager will clean up its connection to the Db2 subsystem and attempt to reconnect. If a Db2 group attach name was specified on the QSGDATA system parameter a connection to a different Db2 may occur.

Determine the reason for the Db2 forcible stop. Restart the Db2 subsystem.

The queue manager received a STOP QUIESCE termination notification from the Db2 subsystem to which it is connected.

The queue manager will quiesce all Db2 server tasks and disconnect from the Db2 subsystem so that it can shut down. It will then attempt to reconnect. If a Db2 group attach name was specified on the QSGDATA system parameter a connection to a different Db2 may occur.

Restart the Db2 subsystem so that shared queue operations can resume.

The queue manager has successfully disconnected from the Db2 subsystem.

If the disconnect is due to a Db2 STOP MODE(QUIESCE) the queue manager will attempt to reconnect to the Db2 subsystem.

None.

The queue manager attempted to access one of its Db2 tables. Db2 has returned an SQL code indicating the table does not exist.

The request fails and processing continues.

Check that all MQ tasks to set up the Db2 environment completed successfully and that the correct Db2 data-sharing group name was specified on the QSGDATA system parameter.

The queue manager has attempted to access one of its Db2 tables. Db2 has returned an SQL code indicating that the index for the specified table has not been built.

The request fails and processing continues.

Check that all MQ tasks to set up the Db2 environment completed successfully and that the correct Db2 data-sharing group name was specified on the QSGDATA system parameter.

The outstanding connection pending request to Db2 has been terminated due to a STOP QMGR request.

The pending connect to Db2 is canceled and queue manager termination continues.

None.

An attempt by the queue manager to access one of its tables was returned an SQL code indicating that access to the named resource failed.

The request fails and processing continues.

This message will be followed by message CSQ5009E which contains full details of the information returned from Db2 which should be used in conjunction with messages on the Db2 log to diagnose the problem.

The most likely cause of this problem is contention for a Db2 resource, especially on a heavily-used system. If so, the problem is temporary; retry the action that gave the error.

If not, and the problem persists, determine from the message and the Db2 log the resource concerned and perform the recovery actions necessary to unlock the resource. Such a problem could be caused by a Db2 failure while updating one of the Db2 tables, which will be indicated in the Db2 log.

During startup and shutdown processing the queue manager attempts to update its status in the CSQ.ADMIN_B_QMGR table. This attempt failed.

None. Startup/shutdown processing continues.

None.

A call to the SQL function specified by function returned a non-zero code specified by SQL-code.

Processing continues.

Note the values contained in the message, and contact your IBM support center. Consult the Db2 for z/OS Messages and Codes manual for more information about the error code.

The queue manager tried to access Db2, but RRS is not available.

If this occurs during queue manager initialization, the queue manager waits for RRS to become available.

If this occurs at other times, the queue manager terminates its connection to Db2, and then tries to reconnect. Some queue-sharing group functions will not be available until RRS is restarted and the connection to Db2 is reestablished.

Start (or restart) RRS.

An SQL call returned a non-zero code indicating that a deadlock or timeout condition occurred.

The request fails and processing continues.

Retry the command or application involved. If the problem persists, contact your IBM support center. Consult the Db2 for z/OS Messages and Codes manual for more information about the error code.

The queue manager tried to access Db2, but RRS has reached the limit of allowed concurrent connections (IDENTIFYs).

If this message occurs during queue manager initialization, the queue manager waits for an RRS connection to become available.

If this message occurs at other times, the queue manager terminates its connection to Db2, and then tries to reconnect. Some queue-sharing group functions are not available until RRS is restarted and the connection to Db2 is reestablished.

Adjust the RRS connection limit if required, then start (or restart) RRS.

Ensure that the Db2 system parameter controlling the maximum number of concurrent users and connections is correct. The Db2 parameter is Max Batch connect (CTHREAD) on the thread management panel DSNTIPE.

See the Db2 for z/OS documentation for an explanation of this Db2 parameter to resolve the problem.

An operation requested for the named Db2 table failed. For example, the table might be full, or there might be insufficient storage available to perform the request.

This is most likely to occur when writing data to one of the tables that IBM MQ uses to store large shared messages.

Message CSQ5009E is issued giving details of the associated SQL error codes. The requested operation fails and processing continues. The message or other data is not written to the table.

Investigate the cause of the problem as indicated by the SQL codes in message CSQ5009E.

If the table is one of the tables used for storing large shared messages, and the problem is due to insufficient storage, try the operation again later, as the condition might be temporary. If the problem is because the table is full, remove some of the messages; for example, start an application that retrieves and processes the messages. Use the MQ DISPLAY GROUP command to check if there are any obsolete messages in the table space, and delete them. If necessary, increase the size of the table.

This is issued in response to a SUSPEND QMGR FACILITY( Db2) command if it completed successfully.

All Db2 activity is suspended for the queue manager named, and the connection to Db2 is broken.

Use the RESUME QMGR FACILITY( Db2) command when ready to resume Db2 activity.

The RESUME QMGR FACILITY( Db2) command completed successfully, reestablishing the connection to Db2.

Db2 activity is resumed for the queue manager named.

A SUSPEND or RESUME QMGR FACILITY( Db2) command was issued, but such a request is already pending.

None.

Wait until the pending request completes, then reissue the command if necessary.

A SUSPEND QMGR FACILITY( Db2) command was issued, but the connection to the named Db2 subsystem is already suspended.

None.

A RESUME QMGR FACILITY( Db2) command was issued, but the connection to the named Db2 subsystem is not suspended.

None.

An attempt was made to start the queue manager in new function mode, but some queue managers in the queue-sharing group are either not at a version that is sufficient to coexist with the new functions provided in this level of code, have not been started in new function mode, or do not have compatible QSGDATA parameters.

Processing continues, but certain functions will be unavailable.

Ensure that all of the queue managers in the queue-sharing group have been started in new function mode at the appropriate version, then restart the queue manager. See z/OS: OPMODE for more information on running in new function mode

The queue manager has detected a service task service-task that is taking too long to process a request that started at hh.mm.ss.nnnnnn.

Processing continues, but certain functions might be unavailable.

Investigate if there are any problems with Db2 or RRS that prevent them responding to IBM MQ requests. For example, the Db2 CTHREAD limit has been exceeded, or Db2 is running slowly because it is short of resources like CPU, I/O capacity, or storage; or Db2 is waiting for log space.

An SQL error has occurred. Additional diagnostic information direct from Db2 follows.

See the preceding Db2 manager error message.

Determine the reason for the SQL error and correct the problem.

This message is the initial response to the DISPLAY GROUP command. It is followed by message CSQ5102I which is a formatted report of the queue managers in the group.

Processing continues normally.

Processing continues normally.

Processing continues normally.

Queue manager is not in a queue-sharing group

A command that requires a queue-sharing group was entered, but the queue manager is not in a group.

The command is not actioned.

call-name call failed, rc=rc reason=reason

During processing for a DISPLAY GROUP command, a coupling facility services call used to get information failed. rc is the return code and reason is the reason code (both in hexadecimal) from the call.

Processing is terminated. A following message is issued to identify which type of information was being obtained.

See the z/OS MVS Programming Sysplex Services Reference. manual for information about the return and reason codes from the call.

Information not available for group group-name - reason

Processing is terminated.

Resolve the problem accordingly.