DB2 manager messages (CSQ5...)

CSQ5001I

csect-name Connected to DB2 DB2-name

Explanation:

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

System Action:

Processing continues.

System Programmer Response:

None.

CSQ5002E

csect-name Connection to DB2 using connect-name failed, RC=return-code reason=reason

Explanation:

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

System Action:

Queue manager startup is terminated.

System Programmer Response:

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.

CSQ5003A

csect-name Connection to DB2 using connect-name pending, no active DB2

Explanation:

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.

System Action:

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

System Programmer Response:

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.

CSQ5004E

csect-name DB2 table entry for queue manager in queue-sharing group qsg-name is missing or incorrect

Explanation:

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

System Action:

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

System Programmer Response:

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 WebSphere MQ, check also that you have updated the DB2 tables to the format for the current release. See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.

CSQ5005E

csect-name Queue manager release level is incompatible with queue-sharing group

Explanation:

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

System Action:

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

System Programmer Response:

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; be sure to use the same version of WebSphere MQ for the utility as was used for running the queue manager. See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.

CSQ5006E

csect-name Data-sharing groups differ

Explanation:

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.

System Action:

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

System Programmer Response:

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.

CSQ5007E

csect-name RRSAF function function failed for plan plan-name, RC=return-code reason=reason syncpoint code=sync-code

Explanation:

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

System Action:

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

System Programmer Response:

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.

CSQ5008E

csect-name DB2 DB2-name is not a member of data-sharing group dsg-name

Explanation:

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.

System Action:

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

System Programmer Response:

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.

CSQ5009E

csect-name SQL error for table table-name, code=SQL-code state=SQL-state, data=d1 d2 d3 d4 d5

Explanation:

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

System Action:

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

System Programmer Response:

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.

CSQ5010E

csect-name XCF IXCQUERY member error, RC=return-code reason=reason

Explanation:

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

System Action:

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

System Programmer Response:

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.

CSQ5011E

csect-name XCF IXCJOIN group error, RC=return-code reason=reason

Explanation:

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

System Action:

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

System Programmer Response:

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.

CSQ5012E

csect-name XCF IXCQUIES group error, RC=return-code reason=reason

Explanation:

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

System Action:

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

System Programmer Response:

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.

CSQ5013E

csect-name XCF IXCSETUS error, RC=return-code reason=reason

Explanation:

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

System Action:

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

System Programmer Response:

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.

CSQ5014I

csect-name Connection to DB2-name lost, DB2 terminated abnormally

Explanation:

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

System Action:

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.

System Programmer Response:

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

CSQ5015I

csect-name Connection to DB2-name lost, DB2 shut down forcibly

Explanation:

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

System Action:

System Programmer Response:

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

CSQ5016I

csect-name Connection to DB2-name quiescing, DB2 terminating

Explanation:

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

System Action:

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.

System Programmer Response:

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

CSQ5019I

csect-name Disconnected from DB2 DB2-name

Explanation:

The queue manager has successfully disconnected from the DB2 subsystem.

System Action:

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

System Programmer Response:

None.

CSQ5020E

csect-name SQL error, table table-name not defined in DB2

Explanation:

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

System Action:

The request fails and processing continues.

System Programmer Response:

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.

CSQ5021E

csect-name SQL error, table table-name index not built in DB2

Explanation:

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.

System Action:

The request fails and processing continues.

System Programmer Response:

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.

CSQ5022I

csect-name Pending connection to DB2 using connect-name ended, queue manager terminating

Explanation:

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

System Action:

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

System Programmer Response:

None.

CSQ5023E

csect-name SQL error, table table-name locked by another DB2

Explanation:

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

System Action:

The request fails and processing continues.

System Programmer Response:

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.

CSQ5024E

csect-name Unable to update queue manager status, RC=return-code

Explanation:

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

System Action:

None. Startup/shutdown processing continues.

System Programmer Response:

None.

CSQ5025E

csect-name SQL error, function function code=SQL-code

Explanation:

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

System Action:

Processing continues.

System Programmer Response:

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.

CSQ5026E

csect-name Unable to access DB2, RRS is not available

Explanation:

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

System Action:

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.

System Programmer Response:

Start (or restart) RRS.

CSQ5027E

csect-name SQL error for table table-name, deadlock or timeout occurred (code=SQL-code)

Explanation:

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

System Action:

The request fails and processing continues.

System Programmer Response:

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.

CSQ5028E

csect-name Unable to access DB2, RRS connection limit exceeded

Explanation:

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

System Action:

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

System Programmer Response:

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

CSQ5029E

csect-name Operation on DB2 table table-name failed

Explanation:

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

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

System Action:

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.

System Programmer Response:

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

If the table is one of those used for storing large shared messages, and the problem is due to insufficient storage, retry the operation later, as the condition may be temporary. If the problem is because the table is full, take action to 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 tablespace, and delete them. If necessary, increase the size of the table.

CSQ5032I

csect-name Connection to DB2 db2-name in data-sharing group dsg-name is suspended

Explanation:

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

System Action:

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

System Programmer Response:

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

CSQ5033I

csect-name Connection to DB2 db2-name in data-sharing group dsg-name is resumed

Explanation:

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

System Action:

DB2 activity is resumed for the queue manager named.

CSQ5034I

csect-name Suspend or resume DB2 request pending

Explanation:

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

System Action:

None.

System Programmer Response:

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

CSQ5035I

csect-name Connection to DB2 db2-name in data-sharing group dsg-name already suspended

Explanation:

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

System Action:

None.

CSQ5036I

csect-name Connection to DB2 db2-name in data-sharing group dsg-name not suspended

Explanation:

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

System Action:

None.

CSQ5100I

DISPLAY GROUP report ...

Explanation:

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.

System Action:

Processing continues normally.

CSQ5102I

Queue managers in group group-name

Explanation:

This message is part of the responses to the DISPLAY GROUP command. It provides information about each queue manager in the group, as follows:

 Name Num Prefix  Status    Ver DB2    Connection
 name num cpf     qmgr-stat vrm db2-id conn-stat

  ·
  ·
  ·

 End of queue managers report

where:

name

The name of the queue manager.

num

The internally generated number of the queue manager in the group.

cpf

The command prefix of the queue manager.

qmgr-stat

The current status of the queue manager:

ACTIVE: The queue manager is running.
INACTIVE: The queue manager is not running, having terminated normally.
FAILED: The queue manager is not running, having terminated abnormally.
CREATED: The queue manager has been defined to the group, but has not yet been started.
UNKNOWN: The status cannot be determined.

vrm

The function level of the queue manager. The value is a 3-digit number, where:

v: is the version number
r: is the release number
m: is the modification number.

db2-id

The name of the DB2 subsystem or group attachment to which the queue manager connects.

conn-stat

The current status of the connection to DB2:

ACTIVE: The queue manager is running and connected to DB2.
PENDING: The queue manager is running but not connected because DB2 has terminated normally.
FAILED: The queue manager is running but not connected because DB2 has terminated abnormally.
INACTIVE: The queue manager is not running and not connected to DB2.
UNKNOWN: The status cannot be determined.

Exceptionally, the last line might be either:

 Report terminated, too many lines

if the report was generated in response to a command from a z/OS console and more than 253 response lines were generated. Only 253 response lines are returned.

 Report terminated

if there was an error in obtaining the information. The error is described in the following messages.

System Action:

Processing continues normally.

CSQ5103I

Obsolete messages in DB2 for group group-name

Explanation:

Messages are normally deleted automatically from DB2, but in exceptional circumstances obsolete messages can remain. This identifies such messages, as follows:

 LEID msg-id

  ·
  ·
  ·

 End of messages report

where:

msg-id: is the identifier of the message.

Exceptionally, the last line might be either:

 Report terminated, too many lines

if the report was generated in response to a command from a z/OS console and more than 253 response lines were generated. Only 253 response lines are returned.

 Report terminated

if there was an error in obtaining the information.

System Action:

Processing continues normally.

System Programmer Response:

Delete the obsolete messages from DB2. For example, use SPUFI to issue the SQL command

 DELETE FROM CSQ.ADMIN_B_MESSAGES
    WHERE QSGNAME = 'group-name' AND
    LEID = 'msg-id';

CSQ5113I

Queue manager is not in a queue-sharing group

Explanation:

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

Severity:

System Action:

The command is not actioned.

CSQ5116E

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

Explanation:

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.

Severity:

System Action:

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

System Programmer Response:

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

CSQ5117E

Information not available for group group-name - reason

Explanation:

During processing for a DISPLAY GROUP command, information could not be obtained for the group, for the reason indicated:

ERROR: A coupling facility services call failed, as indicated in the preceding CSQ5116E message.
CHANGED: The group size has changed.

Severity:

System Action:

Processing is terminated.

System Programmer Response:

Resolve the problem accordingly.