PI55159: WMQ V8: INVALID CF-STRUCTURE BACKUP SIZE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After define/add new SMDS CF structure, the backup structure
  process shows for one of the structures a size of 104817 MB
  and takes longer then expected, although the Structure is almost
  empty (in the reported case we had 20 msgs 10x1KB and 10x100KB):
  
  CSQE121I  CSQELBK1 Backup of structure xxxxxxxxx
            coompleted at RBA=0716C09EBEA2, size 104817
  
  This is caused by orphanded BLOBs in DB2.
  The orphaned entries belonged to structure which was deleted
  in the past.
  One of the new defined structures got the same id as the deleted
  structure before and the orphaned entires are there.
  

Local fix

• DISPLAY GROUP OBSMSGS(YES)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
  *                 Release 0 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Invalid Coupling Facility structure     *
  *                      backup size.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  MQ stores shared messages either in the Coupling Facility or in
  DB2 BLOBs - these Binary Large Objects are used for messages
  with large amounts of data.
  A number of BLOBs for a particular structure number have been
  orphaned, the associated Coupling Facility structure no longer
  exists.
  A new Coupling Facility structure is created using the next free
  structure number, which happens to be the same as the one
  associated with the orphaned BLOBs.
  The shared queue associated with the new Coupling Facility
  structure is almost empty, but when a structure backup is
  performed it is much larger and takes much longer than expected.
  This happens because the orphaned BLOBs, which share the same
  structure number as the newly defined Coupling Facility
  structure , are logged as part of the backup.
  

Problem conclusion

• Delete CFSTRUCT processing has been updated to delete any
  associated BLOBs. This will reduce the risk of orphaned BLOBs
  for a non-existent Coupling Facility structure.
  000Y
  CSQMUCFS
  

Temporary fix

Comments

APAR Information

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

  PI49644

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

  UI34589

Modules/Macros

• CSQMUCFS
  

Fix information

• Fixed component name

  WMQ Z/OS 8

• Fixed component ID

  5655W9700

Applicable component levels

• R000 PSY UI34589

     UP16/02/03 P F602

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.