PH66518: CUSTOM(CAPEXPRY) BEING PICKED UP AND USED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The problem affects a private SYSTEM.CHANNEL.SYNCQ, where the
  value of LQCAPEXPRY is not always persisted to the pageset.
  While running at pre 9.4 releases this doesn't cause a problem
  because the live value is always calculated during startup based
  on the value of the CUSTOM field, however at 9.4 lResolvedExp is
  set prior to this happening, resulting in an old value of
  CUSTOM(CAPEXPRY) being picked up and used. The problem causes
  many +CSQX526E CSQXRCTL Message sequence error for channel in
  customer MQ network.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 4 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect values of MD.Expiry set       *
  *                      during MQPUT/MQPUT1 to private queues   *
  *                      following migration to MQ 9.4.0.        *
  *                                                              *
  *                      This can result in various symptoms     *
  *                      - Messages fail to be expired,          *
  *                      potentially leading to queues or        *
  *                      pagesets filling.                       *
  *                      - Messages expire at the wrong time     *
  *                      - Messages expiring unexpectedly        *
  ****************************************************************
  During forward migration processing for private queues, the
  effective value of CAPEXPRY is resolved based on the value (if
  any) set in an earlier release in the CUSTOM queue attribute.
  When CUSTOM was changed the last time the queue was altered (for
  example, to change the value of CAPEXPRY, or to remove it), a
  previous value can be found by the forward migration code and
  incorrectly used instead of the value stored in the CUSTOM
  field, leading to the effective value being set to the earlier
  value.
  When messages are subsequently put to the queue, the
  incorrect resolved value is used, leading to an incorrect value
  being set in MD.Expiry.
  

Problem conclusion

• Restart processing has been updated to ensure the value (if any)
  in the CUSTOM attribute is correctly used.
  

Temporary fix

Comments

• ×**** PE25/11/13 FIX IN ERROR. SEE APAR PH68970  FOR DESCRIPTION
  

APAR Information

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

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

  UO03442

Modules/Macros

• CSQICRE2 CSQIERS3
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R400 PSY UO03442

     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.