Coupling Facility manager messages (CSQE...)

The value shown for struc-name in the coupling facility manager messages that follow is the 12-character name as used by IBM® MQ. The external name of such CF structures for use by z/OS® is formed by prefixing the IBM MQ name with the name of the queue-sharing group to which the queue manager is connected.

CSQE005I: Structure struc-name connected as conn-name, version=version
Explanation: The queue manager has successfully connected to structure struc-name.
System action: Processing continues. The queue manager can now access the CF structure.

CSQE006I: Structure struc-name connection name conn-name disconnected
Explanation: The queue manager has disconnected from CF structure struc-name.
System action: Processing continues.

CSQE007I: event-type event received for structure struc-name connection name conn-name
Explanation: The queue manager has received XES event event-type for CF structure struc-name.
System action: Processing continues.
System programmer response: Examine the event code to determine what event was issued. The event codes are described in the z/OS MVS Programming: Sysplex Services Reference manual.

CSQE008I: Recovery event from qmgr-name received for structure struc-name
Explanation: The queue manager issued a peer level recovery event for CF structure struc-name.
System action: Processing continues. The queue manager will begin peer level recovery processing.

CSQE011I: Recovery phase 1 started for structure struc-name connection name conn-name
Explanation: Peer level recovery has started phase one of its processing, following the failure of another queue manager in the queue-sharing group.
System action: Processing continues.
System programmer response: Determine why a queue manager within the queue-sharing group failed.

CSQE012I: Recovery phase 2 started for structure struc-name connection name conn-name
Explanation: Peer level recovery has started phase two of its processing.
System action: Processing continues.

CSQE013I: Recovery phase 1 completed for structure struc-name connection name conn-name
Explanation: Peer level recovery has completed phase one of its processing.
System action: Processing continues.

CSQE014I: Recovery phase 2 completed for structure struc-name connection name conn-name
Explanation: Peer level recovery has completed phase two of its processing.
System action: Processing continues.

CSQE015I: Recovery phase 2 not attempted for structure struc-name connection name conn-name
Explanation: Phase two of peer level recovery processing was not attempted because of a previous error in phase one on one of the participating queue managers.
System action: Processing continues. The connection will be recovered by the failed queue manager when it restarts.
System programmer response: Investigate the cause of the error, as reported in the preceding messages.

CSQE016E: Structure struc-name connection name conn-name disconnected, RC=return-code reason=reason
Explanation: The queue manager has disconnected from CF structure struc-name.
System action: Processing continues.
System programmer response: Examine the return and reason codes to determine why the CF structure was disconnected. The codes are described in the z/OS MVS Programming: Sysplex Services Reference manual.

CSQE018I: Admin structure data building started
Explanation: The queue manager is building its own data for the administration structure.
System action: Processing continues.

CSQE019I: Admin structure data building completed
Explanation: The queue manager has built its own data for the administration structure.
System action: Processing continues.

CSQE020E: Structure struc-name connection as conn-name failed, RC=return-code reason= reason codes=s1 s2 s3
Explanation: The queue manager failed to connect to CF structure struc-name.
System action: This depends on the component that caused the connection request (queue manager or channel initiator) and the reason for connecting to the CF structure. The component might terminate, or might continue processing but with functions that require the structure inhibited.
System programmer response: Examine the return and reason codes to determine why the connect failed. Codes s1 s2 s3 are the XES IXLCONN diagnosis codes, which are described in the z/OS MVS Programming: Sysplex Services Reference manual.

CSQE021I: Structure struc-name connection as conn-name warning, RC=return-code reason=reason codes=s1 s2 s3
Explanation: The queue manager has successfully connected to CF structure struc-name, but the XES IXLCONN call returned with a warning.
System action: Processing continues.
System programmer response: Examine the return and reason codes to determine why the connect warning message was issued. Codes s1 s2 s3 are the XES IXLCONN diagnosis codes, which are described in the z/OS MVS Programming: Sysplex Services Reference manual.

CSQE022E

Structure struc-name unusable, size is too small

Explanation

The queue manager cannot use the named (coupling facility) (CF) structure because its size is less than the minimum that IBM MQ requires.

System action

The queue manager disconnects from the coupling facility (CF) structure, which becomes unusable. If it is an application structure, the queues that use the structure are not usable. If it is the administration structure, the queue manager terminates with completion code X'6C6' and reason code X'00C53000'.

System programmer response

Increase the size of the CF structure to at least the minimum size required. See Planning your coupling facility and offload storage environment for guidance on required structure sizes.

If the structure is allocated and the coupling facility Resource Manager policy allows the size of it to be increased, use the z/OS command SETXCF START,ALTER,STRNAME=ext-struc-name,SIZE=newsize. If the policy does not so allow, or there is insufficient space in the coupling facility that hosts the structure, the policy must be altered; then the structure can be rebuilt using the z/OS command SETXCF START,REBUILD,STRNAME=ext-struc-name. (In these commands, ext-struc-name is formed by prefixing struc-name with the queue-sharing group name.)

If the structure is not allocated, alter the policy to specify a larger INITSIZE for the structure.

CSQE024E: Incorrect coupling facility level level1, required level2
Explanation: The queue manager cannot join the queue-sharing group because the version of z/OS being used supports only CF level level1, but MQ requires at least level level2.
System action: CF support is not active.
System programmer response: Upgrade z/OS and the coupling facility as necessary.

CSQE025E: Invalid UOW for qmgr-name in list list-id cannot be recovered, key=uow-key
Explanation: A unit-of-work descriptor was read during recovery processing that contained unexpected data. The descriptor was for the indicated queue manager; it was in the coupling facility list list-id and had key uow-key (shown in hexadecimal).
System action: The unit-of-work in error cannot be processed and the descriptor is marked as being in error. Processing continues.
System programmer response: Take a memory dump of the indicated list in your coupling facility administration structure for queue manager qmgr-name and contact your IBM support center.

CSQE026E: Structure struc-name unusable, incorrect coupling facility level level1, required level2
Explanation: The queue manager cannot use the named CF structure because it has been allocated in a CF which supports level level1, but MQ requires at least level level2.
System action: The queues that use the CF structure are not usable.
System programmer response: Either upgrade the coupling facility, or use a CF structure which is in a CF running level level2 or above.

CSQE027E: Structure struc-name unusable, vector size n1 incorrect, required n2
Explanation: The queue manager cannot use the named CF structure because it has been allocated a list notification vector of size n1, but MQ requires at least size n2. This is probably because there is not enough available hardware storage area (HSA) for the vector.
System action: The queues that use the CF structure are not usable.
System programmer response: You cannot adjust the amount of HSA defined for your processor. Instead, retry the application (or other process) which was attempting to open the shared queue. If the problem persists, contact your IBM support center for assistance.

CSQE028I: Structure struc-name reset, all messages discarded
Explanation: When it tried to connect to the named CF structure, the queue manager detected that the structure had been deleted, so a new empty structure has been created.
System action: All the messages on the queues that use the CF structure are deleted.

CSQE029E

Structure struc-name unusable, version v1 differs from group version v2

Explanation

The queue manager cannot use the named CF structure because the version number of the structure differs from that of the queue-sharing group.

System action

The queue manager disconnects from the CF structure, which becomes unusable. If it is an application structure, the queues that use the structure are not usable. If it is the administration structure, the queue manager terminates with completion code X'6C6' and reason code X'00C51057'.

System programmer response

Check that the configuration of your queue manager, queue-sharing group, and data-sharing group is correct. If so, deallocate the CF structure using the z/OS commands SETXCF FORCE,CON and SETXCF FORCE,STRUCTURE. When you use these commands, the structure name is formed by prefixing struc-name with the queue-sharing group name.

You might need to stop and restart the queue manager(s).

Note:

You can also use the D XCF command, for example D XCF,STR,STRNAME=MQ7@CSQ_ADMIN to show information about the structure and any connections.

CSQE030I: Serialized application cannot start, admin structure data incomplete
Explanation: A serialized application attempted to start, but it could not do so because one or more queue managers in the queue-sharing group has not completed building its data for the administration structure. Messages CSQE031I and CSQE032I precede this message to identify such queue managers.
System action: The application is not started. The MQCONNX call that it issued to connect to the queue manager fails with a completion code of MQCC_FAILED and a reason code of MQRC_CONN_TAG_NOT_USABLE. (See API completion and reason codes for more information about these codes.)
System programmer response: The administration structure is automatically rebuilt. The rebuild can occur on any member of the QSG. Restart the application after the administration structure is successfully rebuilt, which is shown by message CSQE037I on the system performing the rebuild.

CSQE031I: Admin structure data from qmgr-name incomplete
Explanation: Some functions are not yet available because the indicated queue manager has not completed building its data for the administration structure.
System action: Processing continues. The functions will be available when all the queue managers identified by messages CSQE031I and CSQE032I have issued message CSQE019I.

CSQE032I: Admin structure data from qmgr-name unavailable
Explanation: Some functions are not yet available because the indicated queue manager is not active and therefore its data for the administration structure is not available.
System action: Processing continues.
System programmer response: The rebuild of the administration structure can occur on any member of the QSG. The functions will be available after the administration structures have been successfully rebuilt. Check the log for the messages CSQE036I and CSQE037I, which will indicate the start and completion of the administration structure rebuild.

CSQE033E: Recovery phase 1 failed for structure struc-name connection name conn-name, RC=return-code reason= reason
Explanation: An error occurred during phase one of peer level recovery processing. The recovery attempt is terminated. return-code and reason are the diagnosis codes (in hexadecimal) from an XES IXL call.
System action: Processing continues. The connection will be recovered by the failed queue manager when it restarts.
System programmer response: See the z/OS MVS Programming: Sysplex Services Reference manual for information about the XES IXL diagnosis codes. Restart the queue manager that failed; if it is unable to recover, contact your IBM support center.

CSQE034E: Recovery phase 2 failed for structure struc-name connection name conn-name, RC=return-code reason=reason
Explanation: An error occurred during phase two of peer level recovery processing. The recovery attempt is terminated. return-code and reason are the diagnosis codes (in hexadecimal) from an XES IXL call.
System action: Processing continues. The connection will be recovered by the failed queue manager when it restarts.
System programmer response: See the z/OS MVS Programming: Sysplex Services Reference manual for information about the XES IXL diagnosis codes. Restart the queue manager that failed; if it is unable to recover, contact your IBM support center.

CSQE035E

csect-name Structure struc-name in failed state, recovery needed

Explanation

The queue manager attempted to use CF structure struc-name, but it is in a failed state. The failure occurred previously; it was not caused by the current use of the structure.

System action

Processing continues, but queues that use this CF structure will not be accessible.

System programmer response

Check the console for messages from XES relating to the earlier failure, and investigate the cause. See the z/OS MVS Programming: Sysplex Services Reference manual for information about diagnosing problems in XES.

When the problem is resolved, issue a RECOVER CFSTRUCT command specifying TYPE(NORMAL) for this and any other failed CF structure.

CSQE036I: Admin structure data building started for qmgr-name
Explanation: The queue manager is building the indicated queue manager's data for the administration structure.
System action: Processing continues.

CSQE037I: Admin structure data building completed for qmgr-name
Explanation: The queue manager has built the indicated queue manager's data for the administration structure.
System action: Processing continues.

CSQE038E

Admin structure is full

Explanation

The queue manager cannot write to the administration structure in the coupling facility (CF) because it is full.

System action

The queue manager periodically retries the write attempt. If after a number of retries the structure is still full, this message is reissued and the queue manager terminates with a completion code X'5C6' and a reason code 00C53002.

System programmer response

Increase the size of the CF structure to at least the minimum size required. See the Defining coupling facility resources for guidance on required structure sizes.

If the structure is allocated and the coupling facility Resource Manager policy allows the size of it to be increased, use the z/OS command SETXCF START,ALTER,STRNAME=ext-struc-name,SIZE=newsize. If the policy does not allow this change, or there is insufficient space in the coupling facility that hosts the structure, the policy must be altered, then the structure can be rebuilt using the z/OS command SETXCF START,REBUILD,STRNAME=ext-struc-name. (In these commands, ext-struc-name is formed by prefixing CSQ_ADMIN with the queue-sharing group name.)

If the structure is not allocated, alter the policy to specify a larger INITSIZE for the structure.

CSQE040I

Structure struc-name should be backed up

Explanation

The latest backup for the named CF structure is not very recent. Unless backups are taken frequently, the time to recover persistent messages on shared queues may become excessive.

The message is issued at checkpoint time if the queue manager was the one that took the last backup, or if it has used the structure since the last backup was taken.

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 are recommended to set up a procedure to take frequent backups automatically.

CSQE041E

Structure struc-name backup is more than a day old

Explanation

The latest backup for the named CF structure is more than one day old. Unless backups are taken frequently, the time to recover persistent messages on shared queues might become excessive.

The message is issued at checkpoint time if the queue manager was the one that took the last backup, or if it has used the structure since the last backup was taken.

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. It is suggested you set up a procedure to take frequent backups automatically.

CSQE042E

csect-name Structure struc-name unusable, no EMC storage available

Explanation

The queue manager cannot use the named CF structure because its size is less than the minimum that IBM MQ requires. Specifically, the coupling facility allocation algorithms were unable to make any event monitor control (EMC) storage available during the allocation.

System action

The queue manager disconnects from the CF structure, and the CF structure becomes unusable. If it is an application structure, the queues that use the structure are not usable. If it is the administration structure, the queue manager terminates with completion code X'6C6' and reason code X'00C53003'.

System programmer response

Disconnect all connectors from the structure, and then issue


SETXCF FORCE,STR,STRNAMEname

to get the structure deallocated from the CF before you resize the structure.

Increase the size of the CF structure to at least the minimum size required. See Planning your coupling facility and offload storage environment for further information.

If the structure is allocated and the Coupling Facility Resource Manager policy allows the size of it to be increased, use the z/OS system command:


SETXCF START,ALTER,STRNAME=ext-struc-name,SIZE=newsize

If the CFRM policy does not allow an increase in size, or there is insufficient space in the coupling facility that hosts the structure, the policy must be altered. The structure can then be rebuilt using the z/OS system command:


SETXCF START,REBUILD,STRNAME=ext-struc-name

In these commands, ext-struc-name is formed by prefixing struc-name with the queue-sharing group name.

If the structure is not allocated, alter the CFRM policy to specify a larger INITSIZE for the structure.

CSQE101I

csect-name Unable to backup or recover structure struc-name, structure in use

Explanation

A BACKUP or RECOVER CFSTRUCT command was issued, or automatic recovery started, for a CF structure that is in use by another process. The most likely cause is that another BACKUP or RECOVER CFSTRUCT command, or automatic recovery, is already in progress on one of the active queue managers in the queue-sharing group.

This message can also be issued when new connections to the CF structure are being prevented by the system.

System action

Processing of the command, or automatic recovery for the identified structure, is terminated.

System programmer response

Check that the correct CF structure name was entered on the command. If so, wait until the current process ends before reissuing the command if required.

If there is no other BACKUP or RECOVER CFSTRUCT already in progress, check for previous messages that indicate why connections to the CF structure are being prevented.

CSQE102E: csect-name Unable to recover structure struc-name, not in failed state
Explanation: A RECOVER CFSTRUCT command was issued for a CF structure that is not in a failed state. Only a CF structure that has previously failed can be recovered.
System action: Processing of the command is terminated.
System programmer response: Check that the correct CF structure name was entered on the command.

CSQE103E: csect-name Unable to recover structures, admin structure data incomplete
Explanation: A RECOVER CFSTRUCT command was issued, but recovery could not be performed because one or more queue managers in the queue-sharing group has not completed building its data for the administration structure.
System action: Messages CSQE031I and CSQE032I are sent to the z/OS console to identify such queue managers. Processing of the command is terminated.
System programmer response: The administration structure is automatically rebuilt. The rebuild can occur on any member of the QSG. Reissue the command after the administration structure is successfully rebuilt, which is shown by message CSQE037I on the system performing the rebuild.

CSQE104I: csect-name RECOVER task initiated for structure struc-name
Explanation: The queue manager has successfully started a task to process the RECOVER CFSTRUCT command for the named CF structure.
System action: Processing continues.

CSQE105I: csect-name BACKUP task initiated for structure struc-name
Explanation: The queue manager has successfully started a task to process the BACKUP CFSTRUCT command for the named CF structure.
System action: Processing continues.

CSQE106E: csect-name Unable to backup structure struc-name, reason=reason
Explanation: A BACKUP CFSTRUCT command was issued for a CF structure, but the backup could not be performed.
System action: Processing of the command is terminated.
System programmer response: Examine the reason code to determine why the CF structure could not be backed-up. The codes are described in IBM MQ for z/OS codes and the z/OS MVS Programming: Sysplex Services Reference manual.

CSQE107E: csect-name Unable to back up or recover structure struc-name, structure has never been used
Explanation: A BACKUP or RECOVER CFSTRUCT command was issued, or automatic recovery started, for a CF structure that has never been used, and so does not contain any messages or data.
System action: Processing of the command, or automatic recovery for the identified structure, is terminated.
System programmer response: Check that the correct CF structure name was entered on the command.

CSQE108E: csect-name Unable to backup or recover structure struc-name, structure does not support recovery
Explanation: A BACKUP or RECOVER CFSTRUCT command was issued, or automatic recovery started, for a CF structure with a functional capability that is incompatible with this process; for example, the CF structure level is not high enough to support recovery, or the RECOVER attribute is set to NO.
System action: Processing of the command, or automatic recovery for the identified structure, is terminated.
System programmer response: Ensure that the CF structure is at a level of functional capability that allows the use of the BACKUP or RECOVER CFSTRUCT command and that its MQ RECOVER attribute is set to YES. You can check the values using the DIS CFSTRUCT(*) ALL command. Check that the correct CF structure name was entered on the command.

CSQE109E: csect-name Unable to recover structure struc-name, no backup information available
Explanation: A RECOVER CFSTRUCT command was issued or automatic recovery started for a CF structure, but no backup information could be found.
System action: Processing of the command, or automatic recovery for the identified structure, is terminated.
System programmer response: Check that the correct CF structure name was entered on the command. If so, issue a BACKUP CFSTRUCT command to ensure that backup information is available.

CSQE110E

csect-name PURGE not allowed for structure struc-name

Explanation

A RECOVER CFSTRUCT command was issued for CF structure struc-name using TYPE(PURGE). This CF structure is a system application structure. To prevent loss of messages on system queues TYPE(PURGE) is not allowed for system application structures.

System action

Processing of the command is terminated.

System programmer response

Reissue the command without the TYPE(PURGE) option.

If structure recovery fails contact your IBM support center.

CSQE111I: csect-name Structure struct-name will be set to failed state to allow recovery of failed SMDS data sets
Severity: 0
Explanation: The RECOVER CFSTRUCT command was issued for a structure which is not in the failed state, but at least one of the related SMDS data sets is currently marked as failed, requiring recovery. The structure will be put into the failed state to make it unavailable for normal use so recovery can proceed.
System action: The structure is marked as failed and recovery processing continues.

CSQE112E

csect-name Unable to recover structure struct-name, failed to read required logs.

Explanation

A RECOVER CFSTRUCT command or automatic structure recovery was unable to read the logs required to recover a structure.

System action

Processing of the command is terminated.

Automatic recovery of the structure will not be attempted.

System programmer response

Check that the logs containing the RBA range indicated in message CSQE130I are available, and reissue the command.

Check for any prior errors or abends reporting problems using the logs.

Issue RECOVER CFSTRUCT(struct-name) to retry structure recovery.

CSQE120I: Backup of structure struc-name started at RBA=rba
Explanation: The named CF structure is being backed-up in response to a BACKUP CFSTRUCT command. The backup begins at the indicated RBA.
System action: Processing continues.

CSQE121I: csect-name Backup of structure struc-name completed at RBA=rba, size n MB
Explanation: The named CF structure has been backed-up successfully. The backup ends at the indicated RBA, and n is its approximate size in megabytes.
System action: Processing continues.

CSQE130I: Recovery of structure struc-name started, using qmgr-name log range from RBA=from-rba to RBA=to-rba
Explanation: CF structure recovery is starting in response to a RECOVER CFSTRUCT command. It must read the log range shown to determine how to perform recovery. The logs are read backwards, from the latest failure time of the structures to be recovered to the earliest last successful backup time of those structures.
System action: Processing continues.

CSQE131I

csect-name Recovery of structure struc-name completed

Explanation

The named CF structure has been recovered successfully. The structure is available for use again.

CF structure recovery was started in response to a RECOVER CFSTRUCT command. The log range determined how to perform recovery. The logs are read backwards, from the latest failure time of the structures to be recovered to the earliest last successful backup time of those structures.

System action

Processing continues.

CSQE132I

Structure recovery started, using log range from LRSN=from-lrsn to LRSN=to-lrsn

Explanation

CF structure recovery is starting in response to a RECOVER CFSTRUCT command. It must read the log range shown to determine how to perform recovery. The logs are read backwards, from the latest failure time of the structures to be recovered to the earliest last successful backup time of those structures.

See Recovering a CF structure for more information.

System action

Processing continues.

CSQE133I

Structure recovery reading log backwards, LRSN= lrsn

Explanation

This is issued periodically during log reading by CF structure recovery to show progress. The log range that needs to be read is shown in the preceding CSQE132I message.

System action

Processing continues.

System programmer response

If this message is issued repeatedly with the same LRSN value, investigate the cause; for example, MQ might be waiting for a tape with an archive log data set to be mounted.

CSQE134I

Structure recovery reading log completed

Explanation

CF structure recovery is started in response to a RECOVER CFSTRUCT command. It must read the log range shown to determine how to perform recovery. The logs are read backwards, from the latest failure time of the structures to be recovered, to the earliest last successful backup time of those structures.

CF structure recovery has completed reading the logs. The individual structures can now be recovered.

System action

Each CF structure is recovered independently, as shown by messages CSQE130I and CSQE131I.

CSQE135I: Recovery of structure struc-name reading log, RBA=rba
Explanation: This is issued periodically during log reading for recovering the named CF structure to show progress. The log range that needs to be read is shown in the preceding CSQE130I message.
System action: Processing continues.
System programmer response: If this message is issued repeatedly with the same RBA value, investigate the cause; for example, MQ might be waiting for a tape with an archive log data set to be mounted.

CSQE136I

Error returned by Db2® when clearing queue queue-name, list header number=list header number, structure number=strucnum

Severity

Explanation

Shared queue messages greater than 63 KB in size have their message data held as one or more binary large objects (BLOBs) in a Db2 table. An error was returned by Db2 when clearing these messages from the table.

Note that the list header number, and structure number, are output in hexadecimal format.

System action

Processing continues.

System programmer response

The messages have been deleted from the coupling facility but message data might remain in Db2 as orphaned BLOBs. This message is normally preceded by message CSQ5023E. Examine the Db2 job log to determine why the error occurred. The orphaned messages can be deleted by issuing the 'DISPLAY GROUP OBSMSGS(YES)' command after 24 hours.

CSQE137E

csect-name Db2 and CF structure out of sync for queue queue-name, list header number=list header number, structure number=strucnum

Severity

Explanation

The queue manager has identified a discrepancy between the information stored about a queue in the coupling facility and the corresponding information in Db2.

Note that the list header number, and structure number, are output in hexadecimal format.

System action

Processing continues, but applications are unable to open the affected queue until the discrepancy is resolved by the System Programmer.

System programmer response

If the queue manager has recently been recovered from a backup then the recovery process should be reviewed to ensure that everything was correctly restored, including any Db2 tables associated with the queue manager.

If the cause of the problem cannot be determined then contact your IBM support center for assistance.

CSQE138I: csect-name Structure struc-name is already in the failed state
Explanation: A RESET CFSTRUCT ACTION(FAIL) command was issued for a CF structure that is already in the failed state.
System action: Processing of the command is terminated.

CSQE139I: csect-name Unable to fail structure struc-name, structure in use
Explanation: A RESET CFSTRUCT ACTION(FAIL) command was issued for a CF structure that is in use by another process
System action: Processing of the command is terminated.
System programmer response: Check that the correct CF structure name was entered on the command. If so, wait until the process ends before reissuing the command if required.

CSQE140I: csect-name Started listening for ENF 35 events for structure structure-name
Severity: 0
Explanation: The queue manager has registered to receive ENF 35 events and will attempt to reconnect to the identified structure if it is notified that a coupling facility resource has become available.
System action: Processing continues.

CSQE141I: csect-name Stopped listening for ENF 35 events for structure structure-name
Explanation: The queue manager has de-registered from receiving ENF 35 events for the identified structure, and will not attempt to reconnect to it if notified that a coupling facility resource has become available.
System action: Processing continues.

CSQE142I: csect-name Total loss of connectivity reported for structure structure-name
Explanation: The queue manager has been notified that no systems in the sysplex have connectivity to the coupling facility in which the identified structure is allocated.
System action: If automatic recovery has been enabled for the identified structure one of the queue managers in the queue-sharing group will attempt to recover the structure in an alternative coupling facility, if one is available.
System programmer response: Investigate and resolve the loss of connectivity to the coupling facility on which the structure is allocated.

CSQE143I: csect-name Partial loss of connectivity reported for structure structure-name
Explanation: The queue manager has lost connectivity to the coupling facility in which the identified structure is allocated, and has been notified that the coupling facility is still available on other systems in the sysplex.
System action: A system-managed rebuild will be scheduled to rebuild the structure in an alternative coupling facility, if one is available.
System programmer response: Investigate and resolve the loss of connectivity to the coupling facility on which the structure is allocated.

CSQE144I: csect-name System-managed rebuild initiated for structure structure-name
Explanation: The queue manager has initiated a system-managed rebuild for the identified structure on an alternative coupling facility.
System action: Processing continues and when the process has completed, you receive message CSQE005I.

CSQE145E: csect-name Auto recovery for structure structure-name is not possible, no alternative CF defined in CFRM policy
Severity: 8
Explanation: The queue manager has lost connectivity to the coupling facility in which the identified structure is allocated, but cannot automatically recover the structure because there is no alternative coupling facility in the CFRM preference list.
System action: Processing continues without connectivity to the structure. Any queues that reside on the application structure remain unavailable.
System programmer response: Investigate and resolve the loss of connectivity to the Coupling Facility on which the structure is allocated.

CSQE146E: csect-name System-managed rebuild for structure structure-name failed, reason=reason
Severity: 8
Explanation: The queue manager attempted to initiate a system-managed rebuild for the identified structure but the rebuild could not be performed.
System action: Processing continues without connectivity to the structure. Any queues that reside on the application structure remain unavailable.
System programmer response: Examine the reason code to determine why the system-managed rebuild could not be completed. The codes are described in the z/OS MVS™ Programming: Sysplex Services Reference manual.

CSQE147I: csect-name System-managed rebuild for structure structure-name is already in progress
Explanation: The queue manager attempted to initiate a system-managed rebuild for the identified structure but determined that another queue manager in the queue-sharing group has initiated it already.
System action: Processing continues.

CSQE148I: csect-name Loss of connectivity processing for structure structure-name deferred
Explanation: The queue manager has lost connectivity to the coupling facility in which the identified structure is allocated, but MVS has requested that the queue manager should not take action until a subsequent notification is received.
System action: Processing continues without connectivity to the structure. Any queues that reside on the application structure remain unavailable.

CSQE149I: csect-name Waiting for other queue managers to disconnect from structure structure-name
Explanation: The queue manager has lost connectivity to the coupling facility, in which the identified structure is allocated, but cannot delete the structure or initiate a system-managed rebuild because one or more queue managers that also lost connectivity remain connected to it.
System action: The queue manager will periodically retry the attempted operation until all of the queue managers have disconnected.

CSQE150I: csect-name System-managed rebuild already completed for structure structure-name
Explanation: A system-managed rebuild for the identified structure is unnecessary as another request to rebuild the structure has been completed.
System action: Processing continues.

CSQE151I

csect-name Loss of admin structure connectivity toleration enabled

Explanation

If any queue manager in the queue-sharing group loses connectivity to the administration structure the structure will be rebuilt in an alternative CF, if one is available.

If the structure cannot be rebuilt, some shared queue functions on queue managers that have lost connectivity will be unavailable until connectivity to the structure has been restored. Access to private queues will not be affected.

System action

Processing continues.

CSQE152I

csect-name Loss of admin structure connectivity toleration disabled

Explanation

If the queue manager loses connectivity to the administration structure no attempt to rebuild it is made. The queue manager terminates with abend code 5C6-00C510AB.

This can occur if the CFCONLOS queue manager attribute is set to TERMINATE.

System action

Processing continues.

CSQE153I

csect-name Auto recovery for structure struct-name has been scheduled

Explanation

The queue manager has detected that the identified structure which has automatic recovery enabled, has failed, or connectivity to it has been lost on all systems in the sysplex.

The queue manager has scheduled an attempt to recover the structure.

System action

One of the active queue managers in the queue-sharing group will attempt to recover the identified structure.

CSQE154I: csect-name Structure struct-name has been deleted
Explanation: The queue manager has successfully deleted the identified structure from the coupling facility.
System action: Processing continues.

CSQE155I: csect-name Structure struct-name has already been deleted
Explanation: The queue manager attempted to delete the identified structure from the coupling facility. It could not be deleted because it was not allocated.
System action: Processing continues.

CSQE156I: csect-name Structure struct-name has already been reallocated
Explanation: The queue manager lost connectivity to the identified structure. When attempting to delete the structure the queue manager found that the structure had been reallocated since connectivity was lost.
System action: Processing continues.

CSQE157E: csect-name Unable to recover structure struc-name, no suitable CF available
Severity: 8
Explanation: A RECOVER CFSTRUCT command was issued or automatic recovery started for the identified structure, but there was no suitable Coupling Facility available in which to allocate it.
System action: Processing of the command, or automatic recovery for the identified structure, is terminated.
System programmer response: Ensure that a suitable Coupling Facility in the CFRM preference list for the identified structure is available, then reissue the command.

CSQE158E: csect-name Recovery of structure struc-name failed, reason=reason
Severity: 8
Explanation: Recovery of the identified (coupling facility) CF structure has failed.
System action: Processing continues, but queues that use the identified (coupling facility) CF structure will not be accessible.
System programmer response: Refer to coupling facility codes (X'C5') for information about the reason code. Use this information to solve the problem, then reissue the RECOVER CFSTRUCT command for structures that do not have automatic recovery enabled.

CSQE159I: csect-name Waiting for structure rebuild to complete for structure structure-name
Explanation: The queue manager has lost connectivity to the coupling facility, in which the identified structure is allocated, but cannot delete the structure or initiate a system-managed rebuild, because a structure rebuild is currently in progress.
System action: The queue manager will periodically retry the attempted operation, until the structure rebuild is finished.

CSQE160I

csect-name Auto recovery for structure struc-name is suspended

Explanation

The queue manager detected that recovery for structure struc-name is not possible. Automatic recovery of the structure is suspended.

System action

Automatic recovery for structure struc-name is suspended. Automatic recovery is resumed when a successful connection to the structure is established.

System programmer response

Check for any previous errors or abends reporting problems recovering the structure.

Issue RECOVER CFSTRUCT(struct-name) to retry structure recovery.

CSQE161E: csect-name QSG state is inconsistent; no XCF data for queue manager qmgr-number
Explanation: A RECOVER CFSTRUCT command or automatic structure recovery could not read all the log data required for recovery, because there was no XCF data for one of the queue managers in the QSG. qmgr-number is the number of the affected queue manager in the MQ Db2 tables.
System action: Processing of the command is terminated. Automatic recovery of the structure will not be attempted.
System programmer response: If the queue manager with number qmgr-number in the MQ Db2 tables has been force removed from the QSG then added back into the QSG, start the queue manager and issue the RECOVER CFSTRUCT command again. Otherwise, reset the structure to an empty state by issuing the RECOVER CFSTRUCT TYPE(PURGE) command.

CSQE201E

Media manager request failed with return code ccccffss processing req request for control interval rci in SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname

Severity

Explanation

An error occurred when attempting the indicated media manager request (READ, UPDATE or FORMAT) for the data set.

ccccffss

is the media manager return code in hexadecimal. The last byte ss indicates the overall type of error:

08: Extent error
0C: Logic error
10: Permanent I/O error
14: Undetermined error

The cccc field identifies the specific error and the ff field identifies the function which returned the error. See the z/OS DFSMSdfp Diagnosis manual for further details of media manager return codes.

req

specifies the type of request:

READ: Read one or more control intervals.
UPDATE: Rewrite one or more control intervals.
FORMAT: Format one or more control intervals.

rci

identifies the relative control interval (RCI) number of the control interval being accessed, in hexadecimal.

qmgr-name

identifies the queue manager which owns the shared message data set.

struc-name

identifies the application structure associated with the shared message data set.

dsname

shows the full name of the shared message data set.

System action

This typically results in the SMDS status being set to FAILED (if it is the data set owned by the current queue manager) or the SMDSCONN status being set to ERROR (if it is a data set owned by a different queue manager).

System programmer response

If the problem is a permanent I/O error caused by damage to the data set and recovery logging was enabled, the data set can be recovered by the recreating it from a backup and reapplying the logged changes using the RECOVER CFSTRUCT command.

If the data set is temporarily unavailable (for example because of a device connectivity problem) but is not damaged, then when the data set is available again, it can be put back into normal use by using the RESET SMDS command to set the status to RECOVERED.

CSQE202E

Media manager service failed with return code ret-code, feedback code feedback-code, processing function for SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname

Severity

Explanation

A media manager support services (MMGRSRV) function gave an unexpected error.

ret-code

indicates the MMGRSRV return code, in hexadecimal.

08: Media Manager Services error.
14: Indeterminate error

feedback-code

indicates the 8-byte MMGRSRV internal feedback code, in hexadecimal.

For CONNECT processing, the first byte of this feedback code is the same as the VSAM OPEN error information returned in ACBERFLG.

function

indicates the type of function requested, which can be any of the following:

CONNECT: Open the data set.
DISCONNECT: Close the data set.
EXTEND: Extend the data set being written by the current queue manager, or obtain access to recently added extents for a data set which has been extended by another queue manager.
CATREAD: Obtain the highest allocated and highest used control interval numbers from the catalog entry for the current data set.
CATUPDT: Update the highest used control interval in the catalog entry for the current data set, after formatting new extents.

qmgr-name

identifies the queue manager which owns the shared message data set.

struc-name

identifies the application structure associated with the shared message data set.

dsname

shows the full name of the shared message data set.

System action

System programmer response

This message is normally preceded by a system message such as IEC161I from VSAM or DFP indicating the nature of the error.

CSQE211I

Formatting is in progress for count pages in SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname

Severity

Explanation

The data set is being formatted from the current highest used page to the highest allocated page. This message occurs either when a new extent has been allocated or immediately after opening an existing data set which has not been fully formatted (that is, the highest used page is less than the highest allocated page).

count: indicates the number of pages which need to be formatted (in decimal).
qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

Formatting continues.

CSQE212I

Formatting is complete for SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname

Severity

Explanation

Formatting of the data set has completed and the highest used page has been successfully updated in the catalog.

dsname: identifies the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.

System action

The newly formatted space is made available for use.

CSQE213I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname is now percentage% full

Severity

Explanation

The data set is nearly full.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
percentage: shows the percentage of data blocks in the data set which are currently in use.

This message is issued when the data set becomes 90% full, 92% full, and so on, up to 100%. After this message has been issued for a particular percentage, it is not issued again until the usage has changed in either direction by at least 2%. If the usage then decreases to 88% or less (as a result of messages being deleted or as a result of the data set being expanded) a final message is issued to indicate the new usage percentage.

System action

If expansion is allowed, the data set is expanded. If the data set reaches 100% full, then requests to put new messages that require space in the data set are rejected with return code MQRC_STORAGE_MEDIUM_FULL.

System programmer response

You can check the usage in more detail using the DISPLAY USAGE command with the SMDS keyword.

CSQE215I

Further expansion of SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname is not possible because the maximum number of extents have been allocated

Severity

Explanation

The media manager interface has indicated that the data set has reached the maximum number of extents, and cannot be expanded any further.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

This message can be issued when the data set is opened, or following an expansion attempt, which might have been successful, as indicated by previous messages.

System action

The expansion option for the data set is changed to DSEXPAND(NO) to prevent further expansion attempts.

System programmer response

The only way to expand the data set further is to make it temporarily unavailable by using the RESET SMDS command to mark the status as FAILED, copy it to a new location using larger extents, then make it available again using the RESET SMDS command to mark the status as RECOVERED.

CSQE217I

Expansion of SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname was successful, count pages added, total pages total

Severity

Explanation

The data set was expanded, and one or more new extents have been successfully added.

qmgr-name: identifies the queue manager, which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
count: indicates the number of new pages that have been allocated (in decimal).
total: indicates the total number of pages currently allocated (in decimal).

System action

The queue manager formats the newly allocated space.

CSQE218E

Expansion of SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname was unsuccessful

Severity

Explanation

An attempt was made to expand the data set, but it was unsuccessful, typically because insufficient space was available.

qmgr-name: identifies the queue manager, which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The expansion option for the data set is changed to DSEXPAND(NO) to prevent further expansion attempts.

System programmer response

Check for messages from VSAM or DFP that explain why the request was unsuccessful, and do the required actions.

If space is made available later, change the expansion option back to allow expansion to be tried again.

CSQE219I

Extents refreshed for SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname, count pages added, total pages total

Severity

Explanation

The data set was extended by another queue manager. The current queue manager used media manager services to update the extent information for the open data set to read message data within the new extents.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
count: indicates the number of new page that have been allocated (in decimal).
total: indicates the total number of pages currently allocated (in decimal).

System action

The new extents are made visible to the current queue manager.

CSQE222E

Dynamic allocation of SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname failed with return code ret-code, reason code eeeeiiii

Severity

Explanation

An attempt was made to allocate the data set using the data set name formed by taking the generic DSGROUP name and inserting the queue manager name, but the DYNALLOC macro returned an error.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
ret-code: shows the return code from DYNALLOC, in decimal.
eeeeiiii: shows the reason code, consisting of the error and information codes returned by DYNALLOC, in hexadecimal.

System action

System programmer response

Check the job log for dynamic allocation error messages giving more details about the problem.

After any changes, use the START SMDSCONN command to trigger a new attempt to use the data set.

When the reason code is '02540000', indicating that the allocation failed due to a required ENQ being unavailable, the queue manager will automatically retry the allocation request on subsequent attempts to access the SMDS.

When the reason code is '02380000', indicating that the allocation failed because there was not enough space in the MVS task I/O table (TIOT), increase the size of the TIOT using the ALLOCxx PARMLIB member.

CSQE223E

Dynamic deallocation of SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname failed with return code ret-code, reason code eeeeiiii

Severity

Explanation

An attempt was made to deallocate the data set but the DYNALLOC macro returned an error.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
ret-code: shows the return code from DYNALLOC, in decimal.
eeeeiiii: shows the reason code, consisting of the error and information codes returned by DYNALLOC, in hexadecimal.

System action

No further action is taken, but problems can occur if an attempt is made to use the data set, either from another job or from the same queue manager.

System programmer response

Check the job log for dynamic allocation error messages giving more details about the problem.

CSQE230E

csect-name SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname saved space map cannot be used the time stamp time1 does not match the last CLOSE time stamp time2 in the SMDS object

Severity

Explanation

The shared message data set owned by this queue manager appears to have been closed normally last time it was used, with a saved space map, but the time stamp in the data set does not match the time stamp stored in the SMDS object in Db2 the last time this queue manager closed the data set. This means that the saved space map may not be consistent with the current messages in the coupling facility, so it needs to be rebuilt.

The most probable cause for this message is that the data set has been copied or restored from a copy which was not completely up to date.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
time1: shows the time stamp found in the data set header.
time2: shows the time stamp found in the SMDS object in Db2.

System action

The existing saved space map is ignored and the space map is rebuilt by scanning the messages in the coupling facility structure which refer to the data set.

The rebuild scan process keeps track of the most recent message in the coupling facility that refers to the data set, and at the end of the scan it checks that the matching message data is found in the data set. If so, it is assumed that all changes up to at least that time are present in the data set, so no data has been lost, and the data set can be opened normally. Otherwise, message CSQI034E is issued and the data set is marked as failed.

CSQE231E

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname cannot be used because it is not a VSAM linear data set with control interval size 4096 and SHAREOPTIONS(2 3)

Severity

Explanation

The specified data set is not a VSAM linear data set, or the control interval size is not the default value 4096, or the wrong sharing options have been specified.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

If the data set was initially empty, the sharing options are not checked until the data set has been initialized, closed, and reopened.

System action

The data set is closed and the SMDS status is set to FAILED.

System programmer response

Delete the incorrect data set, and create a one of the same name with the correct attributes.

After any changes, use the START SMDSCONN command to trigger a new attempt to use the data set.

CSQE232E

csect-name SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname cannot be used because the identification information (field-name) in the header record is incorrect

Severity

Explanation

When the data set was opened, there was existing information in the header record (so the data set was not newly formatted) but the information did not match the expected data set identification. The identification information includes a marker CSQESMDS for a shared message data set followed by the names of the queue sharing group, the application structure and the queue manager which owns the shared message data set.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
field-name: identifies the first header identification field which did not have the expected value.

System action

The data set is closed and the connection is marked as AVAIL(ERROR). If the data set status is ACTIVE or RECOVERED, indicating that it was currently in use, the status is changed to FAILED.

System programmer response

If the data set was already in use, this probably indicates that it has been overwritten in some way, in which case any persistent messages can be recovered using the RECOVER CFSTRUCT command.

If the data set was not yet in use, or was currently empty, ensure that it is either formatted or emptied before trying to use it again. After any changes, use the START SMDSCONN command to trigger a new attempt to use the data set.

To display the data set header record, you can use the Access Method Services PRINT command, for example as follows:


 PRINT INDATASET('dsname') TOADDRESS(4095)

The format of the identification information within the data set header record is as follows:

Table 1. Format of identification information within the data set header record.
Offset: Dec	Offset: Hex	Type	Length	Field	Description
8	8	Character	8	MARKER	Marker 'CSQESMDS'
16	10	Character	4	QSG	QSG name
20	14	Character	12	CFSTRUCT	Structure name
32	20	Character	4	SMDS	Owning queue manager
36	24	Integer	4	VERSION	Header version 1

CSQE233E

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname cannot be used because the header record indicates a newly formatted data set but it was already being used

Severity

Explanation

When the data set was opened, the identification information in the header record was zero, indicating a new empty data set, but the data set was already in use, so it should not now be empty.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The data set is closed and marked as FAILED.

System programmer response

Any persistent messages can be recovered using the RECOVER CFSTRUCT command.

CSQE234I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname was empty so it requires formatting

Severity

Explanation

When the data set was opened, it was found to be empty, with no existing data and no pre-formatted space. In this case, VSAM does not allow shared access to the data set. The queue manager needs to initialize the data set.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The data set is pre-formatted up to the end of the existing extents. There is a short delay before the data set is fully available.

CSQE235I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname was not fully formatted so it requires additional formatting

Severity

Explanation

This occurs if the existing data set extents have not been fully formatted when the data set is opened.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The data set is formatted up to the end of the existing extents. There is a short delay before the data set is fully available.

CSQE236I

SMDS(qmgr-name) CFSTRUCT( struc-name) data set dsname cannot be used because there is not enough main storage available to build the space map

Severity

Explanation

The queue manager needs to build a space map in main storage to manage the free space in the data set, but it was unable to obtain sufficient main storage.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The data set is not opened.

System programmer response

Consider increasing the queue manager's MEMLIMIT.

If necessary, use the START SMDSCONN command to request another attempt to open the data set.

For more details see Address space storage.

CSQE237I

SMDS(qmgr-name) CFSTRUCT( struc-name) data set dsname cannot be extended because there is not enough main storage available to build the space map

Severity

Explanation

The queue manager needs to build space map blocks in main storage to manage the additional space in the extended data set, but it was unable to obtain sufficient main storage.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The new extents of the data set are not available for use.

System programmer response

Consider increasing the queue manager's MEMLIMIT.

If necessary, use the START SMDSCONN command to request another attempt to open the data set.

For more details see Address space storage.

CSQE238I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname is too small to use because the initial space allocation is less than two logical blocks

Severity

Explanation

The minimum supported data set size requires at least one logical block for control information and one logical block for data, but the data set is smaller than two logical blocks.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The data set is not opened.

System programmer response

Delete the data set and recreate it with a larger space allocation.

After making changes, use the START SMDSCONN command to request another attempt to open the data set.

CSQE239I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname has become full so new large messages can no longer be stored in it

Severity

Explanation

A message written to a shared queue contains data which is large enough to require offloading to a data set, but there is insufficient space in the data set. Further requests are likely to fail until existing messages have been read and deleted from the data set.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

Any requests encountering this problem are rejected with MQRC_STORAGE_MEDIUM_FULL. This message is not issued again until the data set has been below 90% full since the previous time it was issued.

System programmer response

This problem means that the backlog of unprocessed large shared messages exceeds the size of the data set, but the data set could not be extended in time to avoid the problem.

Ensure that applications to remove large messages from the shared queues are running. Check also for previous problems relating to extending the data set, for example if there was insufficient space on eligible volumes.

CSQE241I

SMDS(qmgr-name) CFSTRUCT(struc-name) now has STATUS(status)

Severity

Explanation

The status of the shared message data set for the specified queue manager and application structure has been changed to the indicated value, either by automatic status management or by a RESET SMDS command.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
status: shows the new status value. For details of specific status values, see the DISPLAY CFSTATUS command with the TYPE(SMDS) option.

System action

All queue managers connected to the structure are notified of the status change. The queue managers take appropriate action if necessary, for example opening or closing the data set.

CSQE242I

SMDS(qmgr-name) CFSTRUCT(struc-name) now has ACCESS(access)

Severity

Explanation

The access availability setting for the shared message data set for the specified queue manager, and application structure has been changed to the indicated value, either by automatic status management or by a RESET SMDS command.

qmgr-name: identifies the queue manager, which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
access: shows the new access availability setting. For details of specific settings, see the DISPLAY CFSTATUS command with the TYPE(SMDS) option.

System action

All queue managers connected to the structure are notified of the change. The queue managers take appropriate action if necessary, for example opening or closing the data set.

CSQE243I

SMDS(qmgr-name) CFSTRUCT(struc-name) now has DSBUFS(value)

Severity

Explanation

The number of shared message data set buffers to be used by the specified queue manager for this application structure has been changed to the indicated value. This message can either occur as a result of an ALTER SMDS command or when a previously specified DSBUFS target value cannot be achieved, in which case a warning message is issued, and the DSBUFS option is automatically set to the actual value achieved.

qmgr-name: identifies the queue manager, which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
value: shows the new DSBUFS setting, which can either be a decimal number, giving the number of buffers to be used, or DEFAULT, indicating that the default DSBUFS value specified on the CFSTRUCT definition for the application structure is to be used. For more information, see the ALTER SMDS and DISPLAY SMDS commands.

System action

The queue manager identified by the SMDS keyword is notified, if active, and adjusts the size of its buffer pool as indicated.

CSQE244I

csect-name SMDS(qmgr-name) CFSTRUCT(struc-name) now has DSEXPAND(value)

Severity

Explanation

The option to allow automatic expansion of a specific shared message data set has been changed as indicated. This message can occur either as a result of an ALTER SMDS command or when expansion was attempted but failed, in which case the option is automatically changed to DSEXPAND(NO) to prevent further expansion attempts. In the latter case, when the problem has been fixed, the ALTER SMDS command can be used to turn automatic expansion on again.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
value: shows the new DSEXPAND setting, which is DEFAULT, YES or NO. For more information, see the ALTER SMDS and DISPLAY SMDS commands.

System action

The queue manager identified by the SMDS keyword is notified, if that queue manager is active. If the change results in expansion being enabled, and the data set is already in need of expansion, an immediate expansion is attempted.

CSQE245I

CFSTRUCT(struc-name) now has OFFLDUSE(offload-usage)

Severity

Explanation

The OFFLOAD method for an application structure was recently changed and the queue manager has now determined that there are no more messages stored using the old offload method, so there is no longer any need for the old offload method to remain active. The offload usage indicator, displayed as the OFFLDUSE keyword on the DISPLAY CFSTATUS command, has been updated to indicate that only the new offload method is now in use.

For a transition from OFFLOAD(SMDS to OFFLOAD(DB2), this message occurs when all active data sets have been changed to the EMPTY state, which occurs if the data set is closed normally at a time when it does not contain any messages. In this case, the offload usage indicator is changed from BOTH to DB2, and the queue managers will no longer use the SMDS data sets, which can be deleted if no longer required.

For a transition from OFFLOAD(DB2) to OFFLOAD(SMDS), this message occurs when the queue manager disconnects normally from the structure at a time when there are no large messages for the structure stored in Db2. In this case, the offload usage indicator is changed from BOTH to SMDS.

struc-name: identifies the application structure.
offload-usage: shows the new offload usage indicator.

System action

All queue managers connected to the structure are notified of the change. The queue managers take appropriate action if necessary, for example opening or closing data sets.

CSQE246I

csect-name SMDSCONN(qmgr-name) CFSTRUCT(struc-name) now has STATUS(status)

Severity

Explanation

The current queue manager was unable to connect to a shared message data set, usually for reasons indicated by a previous message. The error status for the data set connection has now been set to indicate the type of problem which occurred. It will be reset next time an attempt is made to open the data set.

This message is only issued for error status values, which are shown instead of normal status if the data set has been closed because of an error. No message is issued for normal status values (CLOSED, OPENING, OPEN or CLOSING).

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
status: shows the new error status. For details of the possible status values, see the STATUS keyword on the DISPLAY SMDSCONN command.

System action

The SMDSCONN availability is set to AVAIL(ERROR) and message CSQE247I is issued.

No further attempt is made to connect to the data set until the availability value is changed back to AVAIL(NORMAL). This can occur as a result of the queue manager being restarted, or data set availability changing, or in response to the START SMDSCONN command. If this happens while the queue manager is running, another message CSQE247I is issued showing AVAIL(NORMAL).

CSQE247I

csect-name SMDSCONN(qmgr-name) CFSTRUCT(struc-name) now has AVAIL(availability)

Severity

Explanation

The availability setting for the connection between the current queue manager and a shared message data set has been changed to the indicated value. This can be changed either by automatic status management, for example if the queue manager is unable to open the data set, or by one of the commands STOP SMDSCONN or START SMDSCONN.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
availability: shows the new availability setting. For details of the possible values, see the AVAIL keyword on the DISPLAY SMDSCONN command.

System action

The current queue manager takes appropriate action if necessary, for example opening or closing the data set.

CSQE252I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname space map will be rebuilt by scanning the structure

Severity

Explanation

The data set space map needs to be reconstructed either following queue manager abnormal termination or data set recovery, so there will be a delay while this scan is completed.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The queue manager will scan the contents of the structure to determine which blocks in the data set are being referenced so that it can reconstruct the space map.

CSQE255I

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname space map has been rebuilt, message count msg-count

Severity

Explanation

The scan to rebuild the data set space map has completed.

qmgr-name: identifies the queue manager which owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.
msg-count: indicates the number of large messages currently stored in the data set.

System action

The data set is made available for use.

CSQE256E

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname space map rebuild processing failed because a referenced message data block is beyond the end of the data set

Severity

Explanation

During the scan to rebuild the data set space map, a message was found in the structure which referenced a message data block with a control interval number greater than the size of the current data set. It is likely that the data set has been truncated.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The data set is closed and marked as FAILED.

System programmer response

This message indicates that the data set has been damaged, for example by copying it to a smaller data set, causing one or more message data blocks to be lost.

If the original copy is still available, the problem can be fixed without loss of data by reallocating the data set at the original size, copying in the original data, and then using the RESET SMDS command to mark the data set as RECOVERED.

Otherwise, any persistent messages can be recovered by recreating the data set at the original size and recovering the structure and the data set using the RECOVER CFSTRUCT command.

CSQE257E

SMDS(qmgr-name) CFSTRUCT(struc-name) data set dsname is smaller than the size recorded in the space map. The saved space map cannot be used

Severity

Explanation

The data set contained a saved space map, but the current size of the data set is smaller than the size recorded in the space map. It is likely that the data set has been truncated.

qmgr-name: identifies the queue manager that owns the shared message data set.
struc-name: identifies the application structure associated with the shared message data set.
dsname: shows the full name of the shared message data set.

System action

The saved space map is ignored and an attempt is made to rebuild the space map for the truncated data set. If all active message data is within the current extents of the data set the rebuild attempt will be successful, otherwise it will fail with message CSQE256E.

CSQE274E

The SMDS buffer pool for CFSTRUCT(struc-name) could not be created because insufficient storage was available

Severity

Explanation

Insufficient main storage was available to allocate the SMDS data buffer pool for the structure.

struc-name: identifies the application structure associated with the shared message data set.

System action

The data sets for this structure cannot be opened.

System programmer response

Consider increasing the queue manager's MEMLIMIT.

For more details about address space storage, see Address space storage.

CSQE275E

The SMDS buffer pool for CFSTRUCT(struc-name) has been created with actual-buffers rather than the requested buffer-count because insufficient storage was available

Severity

Explanation

Insufficient main storage was available to allocate the requested number of buffers in the SMDS data buffer pool for the structure. A smaller number of buffers were successfully allocated.

struc-name: identifies the application structure associated with the shared message data set.
actual-buffers: shows the number of buffers allocated.
buffer-count: shows the requested number of buffers.

System action

The buffer pool is created with a smaller number of buffers.

System programmer response

If the specified number of buffers is enough, change the requested value to match, to avoid similar problems in future.

Consider increasing the queue manager's MEMLIMIT.

For more details see Address space storage.

CSQE276I

The SMDS buffer pool for CFSTRUCT(struc-name) has been increased to buffer-count buffers

Severity

Explanation

The request to alter the SMDS buffer pool size has completed normally.

struc-name: identifies the application structure associated with the shared message data set.
buffer-count: shows the requested number of buffers.

System action

The additional buffers are made available for use.

CSQE277I

The SMDS buffer pool for CFSTRUCT(struc-name) has been increased to actual-buffers buffers rather than the requested buffer-count because insufficient storage was available

Severity

Explanation

The request to alter the SMDS buffer pool size has completed but the target number of buffers was not reached because insufficient main storage was available

struc-name: identifies the application structure associated with the shared message data set.
actual-buffers: shows the number of buffers allocated.
buffer-count: shows the requested number of buffers.

System action

The additional buffers are made available for use.

CSQE278I

The SMDS buffer pool for CFSTRUCT(struc-name) has been decreased to buffer-count buffers

Severity

Explanation

The request to reduce the SMDS buffer pool size has completed normally.

struc-name: identifies the application structure associated with the shared message data set.
buffer-count: shows the requested number of buffers.

System action

The storage for the excess buffers is released back to the system.

CSQE279I

The SMDS buffer pool for CFSTRUCT(struc-name) has been decreased to actual-buffers buffers rather than the requested buffer-count because the rest of the buffers are in use

Severity

Explanation

The request to reduce the SMDS buffer pool size could not reach the target number of buffers because the current number of buffers in use exceeded that number, and active buffers cannot be released.

struc-name: identifies the application structure associated with the shared message data set.
actual-buffers: shows the number of buffers allocated.
buffer-count: shows the requested number of buffers.

System action

If the number of buffers was at least partly reduced, the storage for the excess buffers is released back to the system.

CSQE280I

SMDS usage ...

Severity

Explanation

This message is issued in response to a DISPLAY USAGE command with TYPE(SMDS). It shows the data set space usage information for the shared message data sets owned by the current queue manager for each application structure which is currently using SMDS support. The information is in the following format:


Application  Offloaded  Total  Total data  Used data  Used structure  messages  blocks  blocks  blocks  part _name
n          n          n          n          n% ⋮  
End of SMDS report

The columns of information are as follows:

Application structure: This is the name of the application structure.
Offloaded messages: This shows the number of shared messages in the structure for which the message data has been stored in the data set owned by this queue manager.
Total blocks: This is the current total size of the owned data set in logical blocks, including blocks used to store the space map.
Total data blocks: This is the number of blocks in the owned data set which can be used to store data, excluding those used to store the space map.
Used data blocks: This is the number of blocks in the owned data set which are currently in use (that is, one or more pages of those blocks contain active message data).
Used part: This is the ratio of the number of used data blocks to the total data blocks, expressed as a percentage.

CSQE285I

SMDS buffer usage ...

Severity

Explanation

This message is issued in response to a DISPLAY USAGE command with TYPE(SMDS). It shows the shared message data set buffer pool usage information for each application structure which is currently using SMDS support. The information is in the following format:


Application  Block  --------- Buffers ---------  Reads  Lowest  Wait  structure  size  Total  In use  Saved  Empty  saved  free  rate _name            
nK          n          n          n          n         n%           n          n%   
End of SMDS buffer report

The columns of information are as follows:

Application structure: This is the name of the application structure.
Block size: This shows the size of each buffer in Kbytes. This is equal to the logical block size of the shared message data set.
Buffers: Total: This is the actual number of buffers in the pool.
Buffers: In use: This is the number of buffers which are currently being used by requests to transfer data to or from the data set.
Buffers: Saved: This is the number of buffers which are free but currently contain saved data for recently accessed blocks.
Buffers: Empty: This is the number of buffers which are free and empty. When a new buffer is required, empty buffers are used first, but if there are no empty buffers, the least recently used saved buffer is reset to empty and used instead.
Reads saved: This is the percentage of read requests (during the current statistics interval) where the correct block was found in a saved buffer, avoiding the need to read the data from the data set.
Lowest free: This is the smallest number of free buffers during the current statistics interval, or zero if all buffers were used but no request had to wait for an empty buffer, or a negative number indicating the maximum number of requests which were waiting for a free buffer at the same time. If this value is negative, it indicates the number of additional buffers that would have been needed in order to avoid waits for a free buffer.
Wait rate: This is the fraction of requests to acquire a buffer which had to wait for a free buffer, expressed as a percentage. The numbers are reset when statistics are collected.