Data manager messages (CSQI...)

 

CSQI002I

csect-name Page set psid value out of range

Explanation:

One of the following commands has been issued:

• DEFINE STGCLASS

• DISPLAY STGCLASS

• DISPLAY USAGE

The value given for the page-set identifier was not in the range 0 through 99.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command using the correct syntax. (See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command.)

CSQI003I

csect-name 'PSID' not allowed with TYPE(DATASET)

Explanation:

A DISPLAY USAGE command was issued specifying both the PSID keyword and TYPE(DATASET), which is not allowed.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command using the correct syntax. (See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command.)

CSQI005I

csect-name PAGE SET nn OFFLINE. RECOVERY RBA = rba

Explanation:

This message indicates that the page set nn is currently not accessible by the queue manager. This might be because the page set has not been defined to the queue manager with the DEFINE PSID command.

rba is the restart RBA for page set nn.

This situation can cause problems, so you should take action to correct it as soon as possible.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

If the page set is required, bring it online; this can be done without stopping the queue manager. Use the FORMAT function of the utility program CSQUTIL, specifying TYPE(REPLACE). Then issue a DEFINE PSID command to bring the page set back into use. Note that all units of recovery (except those that are indoubt) that involved the offline page set will have been backed out by the queue manager when the page set was last used. These indoubt units of recovery may be resolved once the page set is back in use by the queue manager.

CSQI006I

csect-name COMPLETED IN-STORAGE INDEX FOR QUEUE q-name

Explanation:

During restart, in-storage indexes are built for non-shared queues that have the INDXTYPE attribute, which might take some time. This message records that index-building has been completed for the specified queue.

Severity:

0

System Action:

Processing continues.

CSQI007I

csect-name BUILDING IN-STORAGE INDEX FOR QUEUE q-name

Explanation:

During restart, in-storage indexes are built for non-shared queues that have the INDXTYPE attribute, which might take some time. This message records that an index is being built for the specified queue.

Severity:

0

System Action:

The in-storage index is built.

CSQI010I

Page set usage ...

Explanation:

This message is the response to the DISPLAY USAGE command. It provides information about the page set usage, as follows:

 Page ...
 set         
 _ n   page-set-information

  ·
  ·
  ·

 End of page set report

where n is the page set identifier. The columns of page-set-information are:

Buffer pool

The buffer pool used by the page set.

Total pages

The total number of 4 KB pages in the page set (this relates to the records parameter on the VSAM definition of the page set).

Unused pages

The number of pages that are not used (that is, available page sets).

Persistent data pages

The number of pages holding persistent data (these pages are being used to store object definitions and persistent message data).

Nonpersistent data pages

The number of pages holding nonpersistent data (these pages are being used to store nonpersistent message data).

Expansion count

The type of expansion used for the page set (SYSTEM, USER, or NONE), and the number of times the page set has been dynamically expanded since restart. (The maximum number of times the page set can be expanded is 123, provided that enough space is available.) If the count is large, your page set allocation may be wrong, or you may have some message processing problem.

Note:

The page numbers are approximate because other threads might be altering the status of pages in this page set while the command is being processed.

If a page set is unavailable, page-set-information will be one of:

has never been online

if the page set has been defined, but has never been used.

OFFLINE, recovery RBA=rba

if the page set is currently not accessible by the queue manager, for example because the page set has not been defined to the queue manager with the DEFINE PSID command; rba is the restart RBA for the page set.

is not defined

if the command was issued for a specific page set that is not defined to the queue manager.

Exceptionally, the last line of the report might be:

 Page set report terminated

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

Severity:

0

CSQI012E

csect-name COULD NOT COMPLETE COMMAND. STORAGE EXHAUSTED

Explanation:

A display of page set usage could not complete because all the available storage was exhausted.

Severity:

8

System Action:

The output terminates at this point. There might be more information that has not been displayed. If this is in response to a DISPLAY USAGE command without the PSID keyword, try it again, specifying a page set identifier. This could decrease the amount of information produced, enabling it all to be displayed.

CSQI020I

MAXSMSGS(number)

Explanation:

This message is issued in response to a DISPLAY MAXSMSGS command, and displays the maximum number of messages that a task can get or put within a single unit of recovery.

Severity:

0

CSQI021I

csect-name PAGE SET psid IS EMPTY. MEDIA RECOVERY STARTED

Explanation:

The queue manager has recognized a page set with a recovery RBA of zero. It will update the page set using information in the log data sets.

Severity:

0

System Action:

The queue manager rebuilds the page set.

CSQI022I

csect-name PAGE SET psid NEWLY ADDED

Explanation:

The queue manager has recognized that page set psid is new to the system.

Severity:

0

CSQI023I

csect-name PAGE SET psid ONLINE AGAIN. MEDIA RECOVERY STARTED

Explanation:

A page set has been redefined to the queue manager after a period offline.

Severity:

0

System Action:

Any updates to the page set that are necessary are applied.

CSQI024I

csect-name Restart RBA for system as configured = restart-rba

Explanation:

This message gives the restart RBA (relative byte address) for the queue manager, but does not include any offline page sets in the calculation of this restart point.

This value can be used to determine where to truncate logs, if you have no offline page sets.

If you have offline page sets that you wish to add to your system at some time in the future, use the restart RBA given in message CSQI025I. If you truncate your logs at rba you might make it impossible to add the offline page sets back to the system.

Severity:

0

CSQI025I

csect-name Restart RBA including offline page sets = restart-rba

Explanation:

This message gives the restart RBA (relative byte address) for the queue manager, including any offline page sets.

This value can be used to determine where to truncate logs, if you have offline page sets that you wish to add to the system in the future.

Severity:

0

CSQI026I

csect-name PAGE SET nn DEFINED, BUT HAS NEVER BEEN ONLINE

Explanation:

This message indicates that the page set nn has been defined, but it has never been used. Consequently, there is no restart RBA for the page set.

Severity:

0

System Action:

Processing continues.

CSQI027I

csect-name PAGE SET nn TREATED AS A NEW PAGE SET

Explanation:

This message indicates that the page set nn has been formatted using TYPE(NEW). It is treated as if it has been newly-added to the system, so all historical information relating to this page set is discarded. In particular, all queues that use storage classes that reference the page set will be cleared of all messages.

Severity:

0

System Action:

Processing continues.

CSQI028E

csect-name PAGE SET CONFLICT FOR QUEUE queue

Explanation:

The named queue contains messages that are on a different page set from that associated with the storage class for the queue.

Severity:

8

System Action:

This message might be issued more than once, each occurrence naming a different queue. The queue manager ends abnormally with reason code X'00C93800'.

System Programmer Response:

Contact your IBM support center for assistance.

CSQI029I

csect-name PAGE SET psid IS AN OLD COPY. MEDIA RECOVERY STARTED

Explanation:

The queue manager has recognized that the media recovery RBA held within the page set is older than the media recovery RBA checkpointed for the page set. This is because the queue manager was started with an old copy of the page set.

Severity:

0

System Action:

Any updates to the page set that are necessary are applied. Restart processing continues.

CSQI030I

csect-name PAGE SET nn TREATED AS A REPLACEMENT PAGE SET

Explanation:

This message indicates that the page set nn has been formatted using TYPE(REPLACE). No media recovery will be performed on the page set.

Severity:

0

System Action:

Processing continues.

CSQI031I

csect-name THE NEW EXTENT OF PAGE SET psid HAS FORMATTED SUCCESSFULLY

Explanation:

Following the dynamic extension of page set psid, the new extent has been formatted successfully.

Severity:

0

System Action:

Processing continues.

CSQI032I

csect-name NEW EXTENT(S) OF nnn PAGES DISCOVERED ON PAGE SET psid WILL NOW BE FORMATTED

Explanation:

During restart, it was discovered that page set psid had been extended dynamically, but that nnn pages had not been formatted. This formatting will now be done.

Severity:

0

System Action:

Processing continues.

CSQI041I

csect-name JOB jobname USER userid HAD ERROR ACCESSING PAGE SET psid

Explanation:

This message is issued when there is an error on a page set. The message identifies the job name, user ID, and page set identifier associated with the error.

Severity:

0

CSQI042E

csect-name WLM IWMCONN request failed, rc=rc reason=reason

Explanation:

A Workload Management Services (WLM) connect call failed. rc is the return code and reason is the reason code (both in hexadecimal) from the call.

Severity:

8

System Action:

Processing continues, but WLM services are not available.

System Programmer Response:

See the MVS Programming: Workload Management Services manual for information about the return and reason codes from the WLM call. When you have resolved the problem, you will need to restart the queue manager. If you are unable to solve the problem, contact your IBM support center for assistance.

CSQI043E

csect-name WLM call-name request for process process-name failed, rc=rc reason=reason

Explanation:

A Workload Management Services (WLM) call failed. rc is the return code and reason is the reason code (both in hexadecimal) from the call.

Severity:

8

System Action:

Processing continues, but WLM services are not available.

System Programmer Response:

See the MVS Programming: Workload Management Services manual for information about the return and reason codes from the WLM call. When you have resolved the problem, you will need to restart the queue manager. If you are unable to solve the problem, contact your IBM support center for assistance.

CSQI044I

csect-name Process process-name used by queue q-name was not found

Explanation:

The named queue is indexed by message tokens. An action was being performed for the queue that required the use of the Workload Management Services (WLM) IWMCLSFY service. However, the process specified by the queue does not exist, so the service name for WLM cannot be determined.

Severity:

0

System Action:

A blank service name is passed to the Workload Management Services (WLM) IWMCLSFY service.

System Programmer Response:

Correct the queue or process definitions.

CSQI045I

csect-name Log RBA has reached rba. Plan a log reset

Explanation:

The current log RBA is approaching the highest value that is allowed.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

Plan to stop the queue manager at a convenient time and reset the logs. See the WebSphere MQ for z/OS System Administration Guide for information about resetting logs, by using the RESETPAGE function of the utility program CSQUTIL.

CSQI046E

csect-name Log RBA has reached rba. Perform a log reset

Explanation:

The current log RBA is approaching the highest value that is allowed.

Severity:

8

System Action:

Processing continues.

System Programmer Response:

Stop the queue manager as soon as is convenient and reset the logs. See the WebSphere MQ for z/OS System Administration Guide for information about resetting logs, by using the RESETPAGE function of the utility program CSQUTIL.

CSQI047E

csect-name Log RBA has reached rba. Stop queue manager and reset logs

Explanation:

The current log RBA is too close to the highest value that is allowed.

Severity:

8

System Action:

Processing continues.

System Programmer Response:

Stop the queue manager immediately and reset the logs. See the WebSphere MQ for z/OS System Administration Guide for information about resetting logs, by using the RESETPAGE function of the utility program CSQUTIL.

CSQI048I

csect-name WLM reached maximum enclave limit

Explanation:

Workload Management Services (WLM) reported that no more enclaves could be created, so a message could not be notified to WLM. (An IWMECREA call gave a return code of 8 with a reason code of X'xxxx0836'.)

Note:

This message might be issued repeatedly during the scan of the indexes for WLM-managed queues.

Severity:

4

System Action:

The queue manager will attempt to notify the message to WLM again on the next scan of the indexes for WLM-managed queues. This will be after the interval specified by the WLMTIME system parameter; see the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.

System Programmer Response:

See the MVS Programming: Workload Management Services manual for information about the return and reason codes from the WLM call.

CSQI049I

Page set psid has media recovery RBA=rcvry-rba, checkpoint RBA=chkpt-rba

Explanation:

During restart, the queue manager opened the indicated page set. The media recovery RBA from the page set itself and the checkpointed RBA from the logs are as shown.

If the RBAs differ, it indicates that an old copy of the page set is being used. If the checkpoint RBA and the prior checkpoint RBA shown in message CSQR003I differ, it indicates that the page set has been offline.

Severity:

0

System Action:

Processing continues. Media recovery is performed if necessary to bring the page set up to date.

CSQI056E

Unable to increase cluster cache

Explanation:

The dynamic cluster cache cannot be increased because the queue manager cluster cache task encountered an error.

Severity:

8

System Action:

The cluster cache task terminates. The channel initiator will probably terminate.

System Programmer Response:

Investigate the problem reported in any preceding messages.

CSQI060E

QSG names differ, log=log-name queue manager=qmgr-name

Explanation:

The queue-sharing group name recorded in the log does not match the name being used by the queue manager.

Possible causes are:

• The queue manager was restarted using the log from another queue manager.

• The queue manager was restarted with the wrong QSGDATA system parameter.

• The queue manager was not removed correctly from its previous queue-sharing group.

Severity:

8

System Action:

Restart is terminated abnormally with completion code X'5C6' and reason code X'00C94505'.

System Programmer Response:

Restart the queue manager using the correct logs and BSDS, or change the QSGDATA system parameter. Note that we cannot change the name of the queue-sharing group that a queue manager uses, or remove it from a queue-sharing group, unless it has been shut down normally and the further procedures for removal described in WebSphere MQ for z/OS System Administration Guide have been followed.

CSQI061E

Queue manager QSG numbers differ, log=log-num queue manager=qmgr-num

Explanation:

The queue manager was restarted using the log from another queue manager. The queue-sharing group queue manager number recorded in the log does not match that being used by the queue manager.

Severity:

8

System Action:

Restart is terminated abnormally with completion code X'5C6' and reason code X'00C94506'.

System Programmer Response:

Restart the queue manager using the correct logs and BSDS. If the correct logs are being used, correct the entry for the queue manager in the DB2 CSQ.ADMIN_B_QMGR table. If we cannot resolve the problem, contact your IBM Support Center for assistance.

CSQI062I

Queue q-name deleted by another queue manager during restart

Explanation:

During restart processing the queue manager detected that the named queue has been deleted by another queue manager in the queue-sharing group.

Severity:

0

System Action:

Processing continues.

CSQI063E

Queue q-name is both PRIVATE and SHARED

Explanation:

During restart processing the queue manager detected that the named queue exists both as a locally-defined queue on this queue manager and as a shared queue in the queue-sharing group. Opening a queue with this name will therefore not be allowed.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

Plan to delete one of the instances of the queue. There are several things to consider in doing this, as described in the WebSphere MQ for z/OS Concepts and Planning Guide.

CSQI064E

Cannot get information from DB2. obj-type COPY objects not refreshed

Explanation:

During queue manager or channel initiator startup, objects of type obj-type with a disposition of COPY were being refreshed from those with a disposition of GROUP. However, the necessary information could not be obtained from DB2; this may be because DB2 is not available or no longer available, or because the connection to DB2 is suspended, or because there was an error in accessing DB2, or because a DB2 table was temporarily locked.

Severity:

8

System Action:

The COPY objects of type obj-type are not refreshed. Startup continues.

System Programmer Response:

Refer to the console log for messages giving more information about the error.

When the error condition has cleared, refresh the objects manually, or restart the queue manager or channel initiator.

CSQI070I

Data set usage ...

Explanation:

This message is the response to the DISPLAY USAGE command. It provides information about the data sets relating to various circumstances, as follows:

  Data set  RBA/LRSN  DSName
  data-set-type:
            rrr       dsname

  ·
  ·
  ·

  End of data set report

where:

data-set-type

The type of data set and circumstance, which can be:

Log, oldest with active unit of work

The log data set containing the beginning RBA of the oldest active unit of work for the queue manager.

Log, oldest for page set recovery

The log data set containing the oldest restart RBA of any page set for the queue manager.

Log, oldest for CF structure recovery

The log data set containing the LRSN which matches the time of the oldest current backup of any CF structure in the queue-sharing group.

rrr

The RBA or LRSN corresponding to the circumstance.

dsname

The name of the copy 1 data set. If no data set relates to a circumstance, this is shown as None; if the data set name cannot be determined, this is shown as Not found.

Severity:

0

System Programmer Response:

This information can be used to help manage data sets; see the WebSphere MQ for z/OS System Administration Guide for details.