PH52145: WHEN TRACKING ECSA STORAGE STATUS USERS UNEXPECTEDLY FIND STORAGE FLAGGED AS OG ( OWNER GONE )

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• MQ Development indicates when an application address space
  connects to MQ there are several control blocks assigned from
  ECSA while running MQ code on the application TCB. MQ manages
  storage pools to allocate these control blocks efficiently, but
  if the existing pool storage has no available blocks then an
  additional area of storage is getmained and added to the pool.
  The pools are owned and managed by MQ, and are used for
  connections across multiple application address spaces.
  
  To ensure that the ECSA storage is tracked correctly by z/OS,
  we attempt to register the owner as the MQ address space when
  the block is getmained. This is done using the OWNER(SECONDARY)
  option on the getmain request. However, some changes to the
  usage of the secondary address space mean that some of these
  getmain requests can be issued without the secondary being set
  to the qmgr address space.
  
  This causes the storage to be marked as being owned by the
  application address space, and common storage tracking will
  show it as owner gone once the application address space ends.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 2 Modification 0 and Release 3       *
  *                 Modification 0.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When running an application that        *
  *                      connects to MQ, it's possible for some  *
  *                      extended common storage control blocks  *
  *                      to be left with status "OWNER GONE"     *
  *                      after the application ends.             *
  ****************************************************************
  The code responsible for adding control blocks to MQ storage
  pools from the extended common storage area sets the owner of
  the blocks to the application address space, rather than the
  queue manager address space, in some cases.
  

Problem conclusion

• The code has been changed to always set the owner of extended
  common storage control blocks being added to MQ storage pools to
  the queue manager address space.
  

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:

  UI95507 UI95508

Modules/Macros

• CSQSVBK  CSQYAGCS
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R200 PSY UI95508

     UP24/02/14 P F402

• R300 PSY UI95507

     UP24/02/14 P F402

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.