A fix is available
APAR status
Closed as program error.
Error description
The 5C6-00D10312 abend leaves the BRCB with the address of a ROB in BRCB_pROB which has not been resumed. The next time there is an attempt to recover multiple structures in the same go (i.e. due to structure auto-recovery), CSQERRPB will wait for these ROBs to be resumed. However, that will never happen, so the structure recovery processing will wait indefinitely.
Local fix
The 5C6-00D10312 abends are occurring as MQ has been cold-started, so a manual RECOVER CFSTRUCT TYPE(PURGE) would be required to recover the structures.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: RECOVER CFSTRUCT fails when expected * * logs cannot be found, leading to * * symptoms: * * - Repeated abends/dumps if structure * * auto recovery is enabled * * - Command server hang when multiple * * structures are recovered by a single * * command. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the logs required by RECOVER CFSTRUCT processing are not available, an abend occurs to report this and processing continues. This abend is expected in these circumstances. If structure auto recovery is enabled, the queue manager will automatically retry the structure recovery, however the error is unlikely to be transient, leading to repeated abends reporting the unavailability of the required logs. If multiple structures are recovered by a single RECOVER CFSTRUCT command, and the logs are not available, under some timing conditions the structure recovery process will hang, requiring the queue manager to be restarted before recovery of the structures can be attempted again.
Problem conclusion
RECOVER CFSTRUCT processing is corrected to prevent the hang condition occurring when multiple structures are recovered, and the logs are not available. If RECOVER CFSTRUCT processing abends due to the logs not being available, new messages CSQE112E is issued to report this, and automatic recovery of the structure is prevented until the logs are located by the operator and a successful RECOVER CFSTRUCT command is executed. Two new error messages are added to the product documentation: WebSphere MQ 7.1.0 >WebSphere MQ >Reference >Messages >Messages and reason codes for z/OS >Messages for WebSphere MQ for z/OS >Coupling Facility manager messages (CSQE...) " 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. " " CSQE160I: csect-name Auto recovery for structure struct-name suspended Explanation The queue manager has detected that recovery for structure struc-name is not possible, and has suspended automatic recovery of the structure. System action Automatic recovery for structure struc-name is suspended. Automatic recovery will be resumed when a successful connection to the structure is established. System programmer response Check for any prior errors or abends reporting problems recovering the structure. Issue RECOVER CFSTRUCT(struct-name) to retry structure recovery. " 100Y 101Y 102Y 103Y 104Y 105Y CSQECFBR CSQECONN CSQEOPEN CSQERCFA CSQERCF1 CSQERCF2 CSQEROUT CSQERRPB CSQESTFA CSQESTOP CSQFEDIC CSQFEDIE CSQFEDIF CSQFEDIK CSQFEDIU CSQFMTXC CSQFMTXE CSQFMTXF CSQFMTXK CSQFMTXU
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI19446
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-06-05
Closed date
2014-07-29
Last modified date
2014-09-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI20061 UI20062 UI20063 UI20064 UI20065 UI20066
Modules/Macros
CSQECFBR CSQECONN CSQEOPEN CSQERCFA CSQERCF1 CSQERCF2 CSQEROUT CSQERRPB CSQESTFA CSQESTOP CSQFEDIC CSQFEDIE CSQFEDIF CSQFEDIK CSQFEDIU CSQFMTXC CSQFMTXE CSQFMTXF CSQFMTXK CSQFMTXU
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI20061
UP14/08/30 P F408 ¢
R101 PSY UI20062
UP14/08/30 P F408 ¢
R102 PSY UI20063
UP14/08/30 P F408 ¢
R103 PSY UI20064
UP14/08/30 P F408 ¢
R104 PSY UI20065
UP14/08/30 P F408 ¢
R105 PSY UI20066
UP14/08/30 P F408 ¢
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 September 2014