One of the following commands has been issued:
The value given for the page-set identifier was not in the range 0 through 99.
8
The command is ignored.
Reissue the command using the correct syntax. (See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command.)
A DISPLAY USAGE command was issued specifying both the PSID keyword and TYPE(DATASET), which is not allowed.
8
The command is ignored.
Reissue the command using the correct syntax. (See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command.)
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.
0
Processing continues.
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.
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.
0
Processing continues.
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.
0
The in-storage index is built.
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:
If a page set is unavailable, page-set-information will be one of:
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.
0
A display of page set usage could not complete because all the available storage was exhausted.
8
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.
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.
0
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.
0
The queue manager rebuilds the page set.
The queue manager has recognized that page set psid is new to the system.
0
A page set has been redefined to the queue manager after a period offline.
0
Any updates to the page set that are necessary are applied.
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, you must 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.
0
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.
0
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.
0
Processing continues.
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.
0
Processing continues.
The named queue contains messages that are on a different page set from that associated with the storage class for the queue.
8
This message might be issued more than once, each occurrence naming a different queue. The queue manager ends abnormally with reason code X'00C93800'.
Contact your IBM support center for assistance.
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.
0
Any updates to the page set that are necessary are applied. Restart processing continues.
This message indicates that the page set nn has been formatted using TYPE(REPLACE). No media recovery will be performed on the page set.
0
Processing continues.
Following the dynamic extension of page set psid, the new extent has been formatted successfully.
0
Processing continues.
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.
0
Processing continues.
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.
0
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.
8
Processing continues, but WLM services are not available.
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.
A Workload Management Services (WLM) call failed. rc is the return code and reason is the reason code (both in hexadecimal) from the call.
8
Processing continues, but WLM services are not available.
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.
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.
0
A blank service name is passed to the Workload Management Services (WLM) IWMCLSFY service.
Correct the queue or process definitions.
The current log RBA is approaching the highest value that is allowed.
4
Processing continues.
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.
The current log RBA is approaching the highest value that is allowed.
8
Processing continues.
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.
The current log RBA is too close to the highest value that is allowed.
8
Processing continues.
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.
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'.)
4
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.
See the MVS Programming: Workload Management Services manual for information about the return and reason codes from the WLM call.
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.
0
Processing continues. Media recovery is performed if necessary to bring the page set up to date.
The dynamic cluster cache cannot be increased because the queue manager cluster cache task encountered an error.
8
The cluster cache task terminates. The channel initiator will probably terminate.
Investigate the problem reported in any preceding messages.
The queue-sharing group name recorded in the log does not match the name being used by the queue manager.
Possible causes are:
8
Restart is terminated abnormally with completion code X'5C6' and reason code X'00C94505'.
Restart the queue manager using the correct logs and BSDS, or change the QSGDATA system parameter. Note that you 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.
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.
8
Restart is terminated abnormally with completion code X'5C6' and reason code X'00C94506'.
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(R) CSQ.ADMIN_B_QMGR table. If you cannot resolve the problem, contact your IBM Support Center for assistance.
During restart processing the queue manager detected that the named queue has been deleted by another queue manager in the queue-sharing group.
0
Processing continues.
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.
0
Processing continues.
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.
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.
8
The COPY objects of type obj-type are not refreshed. Startup continues.
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.
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:
0
This information can be used to help manage data sets; see the WebSphere MQ for z/OS System Administration Guide for details.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0409 |