Data manager messages (CSQI...)

CSQI002I

csect-name Page set psid value out of range

Severity

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.

System action

The command is ignored.

System programmer response

Reissue the command using the correct syntax. (See MQSC commands for information about the command.)

CSQI003I: csect-name 'PSID' not allowed with TYPE (usage-type)
Severity: 8
Explanation: A DISPLAY USAGE command was issued specifying both the PSID keyword and either TYPE(DATASET), or TYPE(SMDS), which is not allowed.
System action: The command is ignored.
System programmer response: Reissue the command using the correct syntax; see DISPLAY USAGE for additional information.

CSQI004I

csect-name Consider indexing queue-name by index-type for connection-type connection connection-name, num-msgs messages skipped

Severity

Explanation

The queue manager has detected an application receiving messages by message ID or correlation ID from a queue that does not have an index defined.

The type of index that should be established for the queue is indicated by index-type, and is either MSGID or CORRELID. The type of application that is affected is identified by connection-type, and is either BATCH, CHIN, CICS or IMS.

For batch applications connection-name contains the job name.
For the channel initiator connection-name contains the channel name.
For CICS applications connection-name contains the region and transaction names.
For IMS applications connection-name contains the IMS sysid, PSTID and PSB names.

The number of messages skipped while searching for the requested message, shown as num-msgs, is an indication of the impact of not having an index defined.

System action

Processing continues.

System programmer response

Investigate the application to determine whether an index is required for the queue.

The parameter to use with the DEFINE QLOCAL or ALTER QLOCAL command is INDXTYPE. Set it to MSGID or CORRELID, as indicated by the output you received for this message.

Applications that receive messages by message ID or correlation ID might encounter a performance degradation if an index is not defined and the depth of the queue is large.

CSQI005I

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

Severity

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.

This message can also be issued if the pageset has been marked suspended. If this is the case a CSQP059E: Page set n is suspended because it uses suspended buffer pool n message is issued.

Note: 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.

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
Severity: 0
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.
System action: Processing continues.

CSQI007I: csect-name BUILDING IN-STORAGE INDEX FOR QUEUE q-name
Severity: 0
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.
System action: The in-storage index is built.

CSQI010I

Page set usage ...

Severity

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 constrained by the maximum number of extents allowable for the type of VSAM data set allocation and your operating system version.) If the count is large, your page set allocation might be wrong, or you might 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 is 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.

is suspended, buffer pool buffer pool number, recovery RBA=rba: if the page set is suspended; rba is the restart RBA for the page set. For further information about suspended page sets see message CSQP059E: Page set n is suspended because it uses suspended buffer pool n.

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.

CSQI012E: csect-name COULD NOT COMPLETE COMMAND. STORAGE EXHAUSTED
Severity: 8
Explanation: A display of page set usage could not complete because all the available storage was exhausted.
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)
Severity: 0
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.

CSQI021I: csect-name PAGE SET psid IS EMPTY. MEDIA RECOVERY STARTED
Severity: 0
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.
System action: The queue manager rebuilds the page set.

CSQI022I: csect-name PAGE SET psid NEWLY ADDED
Severity: 0
Explanation: The queue manager has recognized that page set psid is new to the system.

CSQI023I: csect-name PAGE SET psid ONLINE AGAIN. MEDIA RECOVERY STARTED
Severity: 0
Explanation: A page set has been redefined to the queue manager after a period offline or suspended.
System action: Any updates to the page set that are necessary are applied.

CSQI024I

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

Severity

Explanation

This message gives the restart RBA (relative byte address) for the queue manager, but does not include any offline or suspended 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 or suspended page sets.

If you have offline or suspended page sets that you want 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 or suspended page sets back to the system.

CSQI025I

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

Severity

Explanation

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

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

CSQI026I: csect-name PAGE SET nn DEFINED, BUT HAS NEVER BEEN ONLINE
Severity: 0
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.
System action: Processing continues.

CSQI027I: csect-name PAGE SET nn TREATED AS A NEW PAGE SET
Severity: 0
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.
System action: Processing continues.

CSQI028E: csect-name PAGE SET CONFLICT FOR QUEUE queue
Severity: 8
Explanation: The named queue contains messages that are on a different page set from that associated with the storage class for the queue.
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
Severity: 0
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.
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
Severity: 0
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.
System action: Processing continues.

CSQI031I: csect-name THE NEW EXTENT OF PAGE SET psid HAS FORMATTED SUCCESSFULLY
Severity: 0
Explanation: Following the dynamic extension of page set psid, the new extent has been formatted successfully.
System action: Processing continues.

CSQI032I: csect-name NEW EXTENT(S) OF nnn PAGES DISCOVERED ON PAGE SET psid WILL NOW BE FORMATTED
Severity: 0
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.
System action: Processing continues.

CSQI033E

csect-name Block block-number of the message data for entry ID entry-id in CFSTRUCT(struc-name) was not found in Db2®

Severity

Explanation

A shared message was read which referred to message data in Db2, but the corresponding data was not found in the Db2 table.

block-number: identifies the block number within the message of the data block which was not found.
entry-id: identifies the coupling facility entry for the shared message.
struc-name: identifies the application structure.

System action

If the message was persistent, the structure is marked as failed, requiring recovery, and messages CSQI036I and CSQE035E are issued.

If the message was nonpersistent, the damaged message is deleted and message CSQI037I is issued.

In both cases, a dump is produced.

CSQI034E

csect-name Block block-number of the message data for entry ID entry-id in CFSTRUCT(struc-name) refers to SMDS(qmgr-id) control interval rci but the stored data does not match the entry id

Severity

Explanation

A shared message was read which referred to message data stored in a shared message data set (SMDS), but when the data was read from the referenced location in the data set, the entry ID in the block prefix did not match the entry ID of the message.

block-number: identifies the block number within the message of the data block which was not found.
entry-id: identifies the coupling facility entry for the shared message.
struc-name: identifies the application structure.
qmgr-id: identifies the queue manager which owns the shared message data set.
rci: identifies the relative control interval number within the data set where the message block was expected to start.

System action

If the message was being retrieved for backup purposes, a dump is produced and the queue manager terminates.

Otherwise, action is taken as follows:

If the message was persistent, the shared message data set and the structure are marked as failed, requiring recovery, and messages CSQI036I and CSQE035E are issued.
If the message was nonpersistent, the damaged message is deleted and message CSQI037I is issued.

In both cases, a dump is produced.

CSQI035E

csect-name Block block-number of the message data for entry ID entry-id in CFSTRUCT(struc-name) refers to SMDS but the data set ID is not valid

Severity

Explanation

A shared message was read which referred to message data stored in a shared message data set (SMDS), but the relevant queue manager id (identified by the last byte of the entry id) is not one which currently owns a shared message data set.

block-number: identifies the block number within the message of the data block which could not be read.
entry-id: identifies the coupling facility entry for the shared message.
struc-name: identifies the application structure.

System action

If the message was persistent, the structure is marked as failed, requiring recovery, and messages CSQI036I and CSQE035E are issued.

If the message was nonpersistent, the damaged message is deleted and message CSQI037I is issued.

In both cases, a dump is produced.

CSQI036I

csect-name CFSTRUCT(struc-name) has been marked as failed because the data for persistent message with entry ID entry-id could not be retrieved

Severity

Explanation

A damaged persistent message was found, so the structure has been marked as failed, requiring recovery.

struc-name: identifies the application structure.
entry-id: identifies the coupling facility entry for the shared message.

System action

The structure is marked as failed and message CSQE035E is issued.

CSQI037I

csect-name The nonpersistent message with entry ID entry-id has been deleted from CFSTRUCT(struc-name) because the data could not be retrieved

Severity

Explanation

A damaged nonpersistent message was found which could not be successfully retrieved, so it has been deleted.

entry-id: identifies the coupling facility entry for the shared message.
struc-name: identifies the application structure.

System action

The damaged message is deleted. No attempt is made to delete any associated SMDS message data.

CSQI038I

csect-name The damaged message with entry id entry-id in CFSTRUCT(struct-name) is for queue queue-name

Severity

Explanation

A damaged shared message entry has been found, as indicated by a previous message, and this message indicates the corresponding queue name.

struc-name: identifies the application structure.
entry-id: identifies the coupling facility entry for the shared message.
queue-name: identifies the queue for which the message cannot be retrieved.

System action

Processing continues. This message will be followed by message CSQI036I or CSQI037I, depending on whether the damaged message was persistent or not.

CSQI039E

csect-name LRSN required for structure recovery not available for one or more CF structures

Explanation

The LRSN required for structure recovery for one or more CF structures could not be located within the logs indexed in the BSDS.

Previous CSQE040I and CSQE041E messages might indicate which CF structures are causing this error to occur.

System action

Processing continues.

System programmer response

Use the BACKUP CFSTRUCT command, on any queue manager in the queue-sharing group, to make a new CF structure backup. You might consider setting up a procedure to take frequent backups automatically.

CSQI041I: csect-name JOB jobname USER userid HAD ERROR ACCESSING PAGE SET psid
Severity: 0
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.

CSQI042E: csect-name WLM IWMCONN request failed, rc=rc reason=reason
Severity: 8
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.
System action: Processing continues, but WLM services are not available.
System programmer response: See the z/OS 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
Severity: 8
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.
System action: Processing continues, but WLM services are not available.
System programmer response: See the z/OS 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
Severity: 0
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.
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

Severity

Explanation

The current log RBA is approaching the end of the log RBA.

System action

Processing continues, unless the RBA value reaches FFF800000000 (if 6-byte log RBAs are in use) or FFFFFFC000000000 (if 8-byte log RBAs are in use) when the queue manager terminates with reason code 00D10257.

System programmer response

Plan to stop the queue manager at a convenient time and reset the logs. See RESETPAGE for information on how to reset the logs using the CSQUTIL utility program and resetting the queue manager's log.

If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs. See Planning to increase the maximum addressable log range for further information.

CSQI046E

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

Severity

Explanation

The current log RBA is approaching the end of the log RBA.

System action

System programmer response

Stop the queue manager as soon as it is convenient and reset the logs. See RESETPAGE for information on how to reset the logs using the CSQUTIL utility program and resetting the queue manager's log.

If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs. See Planning to increase the maximum addressable log range for further information.

CSQI047E

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

Severity

Explanation

The current log RBA is too close to the end of the log RBA range.

System action

System programmer response

Stop the queue manager immediately and reset the logs. See RESETPAGE for information on how to reset the logs using the CSQUTIL utility program and resetting the queue manager's log.

If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs. See Planning to increase the maximum addressable log range for further information.

CSQI048I: csect-name WLM reached maximum enclave limit
Severity: 4
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.
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. For information about the system parameters for the CSQ6SYSP macro, see Using CSQ6SYSP.
System programmer response: See the z/OS 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

Severity

Explanation

During restart, the queue manager opened the indicated page set. The media recovery RBA from the page set itself and the check pointed 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 or suspended.

System action

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

CSQI050E

csect-name Page set psid value RESETPAGE needed

Severity

Explanation

The queue manager has detected that a page set contains RBA values higher than the maximum logged.

System action

During queue manager startup, restart is terminated abnormally with completion code X'5C6' and reason code X'00C94525'.

During DEFINE PSID command processing, the command fails.

System programmer response

Run CSQUTIL with the RESETPAGE utility against the page set or sets indicated in the messages and retry the failed operation.

CSQI051E: csect-name QDEPTHHI less than QDEPTHLO for queue queue
Severity: 8
Explanation: At start up a queue was found to have QDEPTHHI set to a value less than the value of QDEPTHLO.
System action: Processing continues.
System programmer response: Correct the queue definition so that QDEPTHHI is greater than or equal to QDEPTHLO.

CSQI052E

Invalid spacemap RBA found during restart for page set psid

Severity

Explanation

A space map page containing an invalid RBA was detected on the indicated page set during startup, indicating the page set is not in a consistent state.

This is normally as a result of the page set not being correctly processed during a past cold start operation or RESETPAGE operation.

System action

The page set is suspended. Queues using the page set will be inaccessible until the queue manager is started with the page set in a consistent state.

System programmer response

When psid specifies page set 0, contact IBM Service.

For page sets other than 0, plan to stop the queue manager as soon as it is convenient, then follow the procedure to restore the page set or sets to a consistent state:

Run CSQUTIL with SCOPY PSID(x) to save persistent messages on the page set to a data set
Format the page set with TYPE(NEW)
Start the queue manager and reload the messages from the data set using SCOPY LOAD

CSQI053E

Invalid page RBA found during restart for page set psid

Severity

Explanation

A page containing an invalid RBA was detected on the indicated page set during startup, indicating the page set is not in a consistent state.

This is normally as a result of the page set not being correctly processed during a past cold start operation or RESETPAGE operation.

System action

The page set is suspended. Queues using the page set will be inaccessible until the queue manager is started with the page set in a consistent state.

System programmer response

When psid specifies page set 0, contact IBM Service.

For page sets other than 0, plan to stop the queue manager as soon as it is convenient, then follow the procedure to restore the page set or sets to a consistent state:

Run CSQUTIL with SCOPY PSID(x) to save persistent messages on the page set to a data set
Format the page set with TYPE(NEW)
Start the queue manager and reload the messages from the data set using SCOPY LOAD

CSQI059E: Unable to increase cluster cache
Severity: 8
Explanation: The dynamic cluster cache cannot be increased because the queue manager cluster cache task encountered an error.
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

Severity

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.

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 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 Managing queue sharing groups have been followed.

CSQI061E: Queue manager queue sharing group numbers differ, log=log-num queue manager=qmgr-num
Severity: 8
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.
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 you cannot resolve the problem, contact your IBM support center for assistance.

CSQI062I: Queue q-name deleted by another queue manager during restart
Severity: 0
Explanation: During restart processing the queue manager detected that the named queue has been deleted by another queue manager in the queue sharing group.
System action: Processing continues.

CSQI063E: Queue q-name is both PRIVATE and SHARED
Severity: 0
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.
System action: Processing continues.
System programmer response: Delete one of the instances of the queue. See Shared queue problems for more information.

CSQI064E

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

Severity

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.

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.

CSQI065I

Buffer pool attributes ...

Severity

Explanation

This message displays the current state of buffer pool attributes, based on the page set number passed into the DISPLAY USAGE PSID command. It provides information about the number of available buffers, buffers free (stealable), shown as a number and as a percentage of the buffers in the pool, and the memory LOCATION for the specified buffer pool.


CSQI065I !MQ21 Buffer pool attributes ...  321                
  Buffer  Available  Stealable   Stealable  Page      Location
    pool    buffers    buffers  percentage  class             
_      0       5000       4989          99  FIXED4KB  ABOVE   
_      1       5000       4995          99  4KB       ABOVE   
_      2       5000       4999          99  4KB       BELOW   
_      3       5000       4995          99  4KB       BELOW   
_      4       5000       4999          99  4KB       BELOW   
_      5       1000        999          99  4KB       BELOW

Buffer pool

The number of the buffer pool.

Available buffers

The total number of available buffers defined for a specified buffer pool.

If location is SWITCHING_ABOVE or SWITCHING_BELOW, the value is the sum of the numbers above and below.

Stealable buffers

The number of buffers free (stealable) for a defined buffer pool.

Stealable percentage

The amount of buffers free (stealable), as a percentage, for a defined buffer pool.

Page class

The type of virtual storage pages used for backing the buffers in the buffer pool. The page class value is one of the following:

4KB: Buffers are backed by standard pageable 4 KB pages
FIXED4KB: Buffers are backed by permanently page-fixed 4 KB page

Location

The location value of the memory used by individual buffer pools. The location value is one of the following:

ABOVE: ABOVE is displayed when OPMODE(NEWFUNC, 800) is in effect. Memory is used above the bar for buffer pools.

BELOW: BELOW is the default. Memory is used below the bar for buffer pools.

SWITCHING_ABOVE: The buffer pool is in the process of switching to a location ABOVE the bar.

SWITCHING_BELOW: The buffer pool is in the process of switching to a location BELOW the bar.

CSQI070I

Data set usage ...

Severity

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. If the oldest current backup is not found, you must back up all of your structures.

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.

System programmer response

This information can be used to help manage data sets; see Tips for backup and recovery for more information.

CSQI965I: modulename Backward migration required for msgs on pageset ps-name
Explanation: During queue manager restart it has been detected that one or more of the page sets that have been connected has been used at a higher version of queue manager code.
System action: The queue manager will automatically perform special processing during restart to alter any messages stored on the indicated page set so they can be read by the current version of the queue manager.

CSQI968I: modulename Alias queue aq-name to TARGQ tq-name has TARGTYPE ttype which is not supported. aq-name has been deleted
Explanation: During object migration, an alias queue was found which had an invalid TARGTYPE, for example an alias queue to a topic object.
System action: The alias queue indicated is deleted.

CSQI969I

Data set ds-name for page set ps-name was used for a higher version of IBM MQ and cannot be added dynamically

Explanation

During dynamic connection to a pageset which was offline at queue manager restart, it has been detected that it requires backward migration processing.

The pageset is not dynamically added.

CSQI970E

csect-name object-type(object-name) COULD NOT BE MIGRATED

Explanation

Migration of the identified object could not be performed because of locks held by in-doubt transactions.

Some functions will not be available until migration of the object can be performed. For example, the object cannot be altered or deleted, and if it is a transmission queue, the associated channel may not start.

System action

The object is not migrated.

System programmer response

Use the DISPLAY CONN or the DISPLAY THREAD command to identify the list of in-doubt transactions and then resolve them via either the transaction coordinator or the RESOLVE INDOUBT command. Once the in-doubt transactions are resolved, either restart the queue manager or issue an ALTER command against the object to re-attempt its migration.

Message CSQI971I will be issued when the object has been successfully migrated.

CSQI971I

csect-name object-type(object-name) MIGRATED

Explanation

The identified object could not be migrated when the queue manager was first started at the current version because of locks held by in-doubt transactions (see message CSQI970E for more information).

This message is issued during a subsequent restart of the queue manager, or when the object is subsequently altered, to indicate that migration of the object has now occurred.

System action

The object is migrated.

System programmer response

none.