The value shown for struc-name in the coupling facility manager messages that follow is the 12-character name as used by WebSphere MQ. The external name of such CF structures for use by z/OS is formed by prefixing the MQ name with the name of the queue-sharing group to which the queue manager is connected.
The queue manager has successfully connected to structure struc-name.
Processing continues. The queue manager can now access the CF structure.
The queue manager has disconnected from CF structure struc-name.
Processing continues.
The queue manager has received XES event event-type for CF structure struc-name.
Processing continues.
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.
The queue manager issued a peer level recovery event for CF structure struc-name.
Processing continues. The queue manager will begin peer level recovery processing.
Peer level recovery has started phase one of its processing, following the failure of another queue manager in the queue-sharing group.
Processing continues.
Determine why a queue manager within the queue-sharing group failed.
Peer level recovery has started phase two of its processing.
Processing continues.
Peer level recovery has completed phase one of its processing.
Processing continues.
Peer level recovery has completed phase two of its processing.
Processing continues.
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.
Processing continues. The connection will be recovered by the failed queue manager when it restarts.
Investigate the cause of the error, as reported in the preceding messages.
The queue manager has disconnected from CF structure struc-name.
Processing continues.
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.
The queue manager is building its own data for the administration structure.
Processing continues.
The queue manager has built its own data for the administration structure.
Processing continues.
The queue manager failed to connect to CF structure struc-name.
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 may terminate, or may continue processing but with functions that require the structure inhibited.
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.
The queue manager has successfully connected to CF structure struc-name, but the XES IXLCONN call returned with a warning.
Processing continues.
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.
The queue manager cannot use the named CF structure because its size is less than the minimum that MQ requires.
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'00C53000'.
Increase the size of the CF structure to at least the minimum size required. See the WebSphere MQ for z/OS System Setup Guide 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.
The queue manager cannot join the queue-sharing group because the version of z/OS or OS/390 being used supports only CF level level1, but MQ requires at least level level2.
CF support is not active.
Upgrade z/OS or OS/390 and the coupling facility as necessary.
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).
The unit-of-work in error cannot be processed and the descriptor is marked as being in error. Processing continues.
Take a dump of the indicated list in your coupling facility administration structure for queue manager qmgr-name and contact your IBM support center.
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.
The queues that use the CF structure are not usable.
Either upgrade the coupling facility, or use a CF structure which is in a CF running level level2 or above.
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.
The queues that use the CF structure are not usable.
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.
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.
All the messages on the queues that use the CF structure are deleted.
The queue manager cannot use the named CF structure because the version number of the structure differs from that of the queue-sharing group.
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'.
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. (In these commands, the structure name is formed by prefixing struc-name with the queue-sharing group name.)
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.
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 Appendix A. API completion and reason codes for more information about these codes.)
Restart any queue managers identified by message CSQE032I. When all the queue managers identified in messages CSQE031I or CSQE032I have built their data for the administration structure (as shown by message CSQE019I), restart the application.
Some functions are not yet available because the indicated queue manager has not completed building its data for the administration structure.
Processing continues. The functions will be available when all the queue managers identified by messages CSQE031I and CSQE032I have issued message CSQE019I.
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.
Processing continues.
Start the indicated queue manager. The functions will be available when all the queue managers identified by messages CSQE031I or CSQE032I have issued message CSQE019I.
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.
Processing continues. The connection will be recovered by the failed queue manager when it restarts.
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.
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.
Processing continues. The connection will be recovered by the failed queue manager when it restarts.
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.
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.
Processing continues, but queues that use this CF structure will not be accessible.
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.
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.
Processing continues.
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.
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 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.
Processing continues.
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.
A BACKUP or RECOVER CFSTRUCT command was issued for a CF structure that is in use by another process. The most likely cause is that another BACKUP or RECOVER CFSTRUCT command is already in progress.
Processing of the command is terminated.
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.
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.
Processing of the command is terminated.
Check that the correct CF structure name was entered on the command.
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.
Messages CSQE031I and CSQE032I are sent to the z/OS console to identify such queue managers. Processing of the command is terminated.
Restart any queue managers identified by message CSQE032I. When all the queue managers identified in messages CSQE031I or CSQE032I have built their administration structure data (as shown by message CSQE019I), reissue the command.
The queue manager has successfully started a task to process the RECOVER CFSTRUCT command for the named CF structure.
Processing continues.
The queue manager has successfully started a task to process the BACKUP CFSTRUCT command for the named CF structure.
Processing continues.
A BACKUP CFSTRUCT command was issued for a CF structure, but the backup could not be performed.
Processing of the command is terminated.
Examine the reason code to determine why the CF structure could not be backed-up. The codes are described in the z/OS MVS Programming: Sysplex Services Reference manual.
A BACKUP or RECOVER CFSTRUCT command was issued for a CF structure that has never been used, and so does not contain any messages or data.
Processing of the command is terminated.
Check that the correct CF structure name was entered on the command.
A BACKUP or RECOVER CFSTRUCT command was issued for a CF structure whose functional capability is incompatible with this command; for example, the CF structure level is not high enough to support recovery, or the RECOVER attribute is set to NO.
Processing of the command is terminated.
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 RECOVER attribute is set to YES. Check that the correct CF structure name was entered on the command.
A RECOVER CFSTRUCT command was issued for a CF structure, but no backup information could be found.
Processing of the command is terminated.
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.
The named CF structure is being backed-up in response to a BACKUP CFSTRUCT command. The backup begins at the indicated RBA.
Processing continues.
The named CF structure has been backed-up successfully. The backup ends at the indicated RBA, and n is its approximate size in megabytes.
Processing continues.
The named CF structure is being recovered from the log of queue manager qmgr-name. The log range to be used is shown.
Processing continues.
The named CF structure has been recovered successfully. The structure is available for use again.
Processing continues.
CF structure recovery is starting in response to a RECOVER CFSTRUCT command. It must read the log range shown in order 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.
Processing continues.
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.
Processing continues.
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.
CF structure recovery has completed reading the logs. The individual structures can now be recovered.
Each CF structure is recovered independently, as shown by messages CSQE130I and CSQE131I.
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.
Processing continues.
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.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0407 |