PH63201: MQ ABEND S5C6-00D10348 ABEND AND CORRUPTED ACTIVE LOG

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Following a system crash as a result of a disk failure, and
  analyzing one of the dumps from this abend showed that the abend
  was occurring due to a rebuild processing not being able to find
  the Active log record. The disk failure resulted in the
  corruption of an active log data set . For dual copy
  Active/Archive logs setup, as was this case - an attempt should
  have been made to at least try to use the DUAL Copy Active or
  Archive Log to recover. This APAR addresses this issue for an
  attempt to FULL recovery. (Pre-GHE APAR) UHL LINK:
  https://jazza06.hursley.ibm.com:9443/ccm/resource/itemName/com.i
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 3 Modification 0 and Release 4       *
  *                 Modification 0.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend 5C6-00D10348 occurs in CSQJR005   *
  *                      during startup, due to a corrupted      *
  *                      active log. The queue manager fails to  *
  *                      start.                                  *
  ****************************************************************
  Following a DASD failure, an active log containing log records
  required for queue manager startup was corrupted. During queue
  manager startup, the CI containing a required log RBA was
  identified, but the CI in the log dataset was missing. The queue
  manager reread the CI several times, before determining that the
  required RBA could not be read and abending, preventing
  successful queue manager startup. The required RBA was available
  in the second copy of the logs, and had been offloaded to
  archive logs, however these were not searched.
  

Problem conclusion

• When the required CI cannot be read from the first copy of the
  logs, the queue manager will now retry reading the CI from the
  second copy of the active log, followed by the archive log
  datasets, before determining that the required RBA cannot not be
  read and abending.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UO04321 UO04322

Modules/Macros

• CSQJR005
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R300 PSY UO04322

     UP25/09/13 P F509 ¢

• R400 PSY UO04321

     UP25/09/13 P F509 ¢

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.