PH61748: WHEN GTF TRACING IS ENABLED IT IS POSSIBLE TO SEE MULTIPLE DIFFERENT ABENDS, INCLUDING S0F8-00000014 AND S5C6-00E7014F

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• With GTF enabled and there is a previous abend, there is an
  issue with recovery which could result in multiple abends
  including S0F8-00000014, S5C6-00E7014F and S60D-00000018.
  Recovery for the dumping code gets control and retried the abend
  to the requester of the dump. The requester also requested a
  retry to the caller of CSQWVCOL in CSQMCCSP. CSQMCCSP then
  completed its function successfully. When it went to return to
  its caller, it instead returned to the wrong place. This is
  because the retry to CSQMCCSP was done with an incorrect linkage
  stack depth. This resulted in an FRR not being deleted.
  

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: Various abends can occur following an   *
  *                      abend 0C4 in CSQWVCOL when writing a    *
  *                      trace entry to GTF trace. Observed      *
  *                      abends can include abend S0C4 and S0F8. *
  ****************************************************************
  While writing a trace entry to GTF trace, an abend 0C4 occurred
  when attempting to access the trace data to be written (for
  example, due to an invalid parameter being passed on an MQI
  call). As the abend had occurred during tracing, CSQWVFRR was
  called by CSQWSDWA and this set up recovery for the abend and
  indicated to the executing recovery routine that the necessary
  recovery processing was now complete. When the recovery routine
  returned to RTM, the expected retry processing took place but at
  an incorrect Linkage Stack level. This led to the subsequent
  abends in later processing.
  

Problem conclusion

• CSQWSDWA has been changed to determine the Linkage Stack level
  that should be passed to retry processing when retry is
  indicated.
  

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:

  UO03215 UO03216

Modules/Macros

• CSQWSDWA
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R300 PSY UO03216

     UP25/06/11 P F506

• R400 PSY UO03215

     UP25/06/11 P F506

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.