PM80025: WMQ V7.0.1 CSQ5PQSG DOES NOT DETECT INCONSISTENCIES BETWEEN XCF GROUP INFO AND CSQ_ADMIN FAILED-PERSISTENT CONNECTIONS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• By mistake DB2 tables of the queue sharing group were dropped.
  Trying to fix the problem, the following actions were performed:
  ==
  1/ recreated the QSG tables
  2/ restarted the first queue manager CSQ1 in the Queue Sharing
  Group
     this ended and abended with an ABEND5C6
  3/ did a verify QSG
  4/ added the QSG again using CSQ5PQSG
  6/ added the queue manager CSQ1 using CSQ5PQSG
  7/ restarted CSQ1 which again abended with ABEND5C6
  8/ restarted CSQ1 without parameter QSGDATA - it started without
  errors
     but it deleted all objects with QSGDISP(COPY)
  9/ restarted CSQ1 with QSGDATA and it abended again due to
     CSQ_ADMIN version differences (CSQE029E)
  11/ setxcf force of CSQ_ADMIN which completed without errors
  12/ restarted CSQ1 which reallocated CSQ_ADMIN but CSQ1 ended
  with 5C6-00C5101A
  13/ restarted CSQ1 resulted in same ABEND
      CSQV086E MQI1 QUEUE MANAGER ABNORMAL TERMINATION
  REASON=00E50702
  ==
  .
  Analysis of the dump showed that they were inconsistencies
  between information in the CSQ_ADMIN  structure and
  XCF group knowledge of the QSG queue managers .
  .
  CSQ5PQSG VERIFY QSG should be changed to check the XCF group
  info and also the failed-persistent connections in the CSQ_ADMIN
  structure to make sure that the queue-manager ids are
  consistent.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1 and Release 1       *
  *                 Modification 0.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When manipulating the QSG members using *
  *                      the CSQ5PQSG utility, the QMGR may      *
  *                      abend with 5C6-00C5101A and message     *
  *                      CSQV086E with reason=00E50702.          *
  *                      This can occur in particular when       *
  *                      rebuilding DB2 tables without changing  *
  *                      the XCF group or XCF group members.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When rebuilding the DB2 tables without clearing out the XCF
  group members, an inconsistency can be created between the DB2
  and XCF data.
  The QMGR number is stored in the DB2 CSQ.ADMIN_B_QMGR table,
  the XCF group member and the connection to the CSQ_ADMIN
  structure. When the QMGR starts, the three values are compared,
  and if there is a mismatch, the QMGR abends with 5C6-00C5101A.
  The CSQ5PQSG utility however does no validation on these QMGR
  numbers, and allows DB2 entries to be added that have a
  different value compared to the ones that still exist in the
  XCF group members or failed persistent connections.
  

Problem conclusion

• The CSQ5PQSG utility was changed to add checks on the QMGR
  number stored in DB2 and the XCF when adding QMGRs to a QSG.
  The "VERIFY QSG" function was also changed to report any
  mismatches.
  
  
  Following messages are added:
  
  CSQU524I: QMGR number=nn
  
  Explanation:
  "
  Informational message containing the number of the QMGR in the
  QSG to accompany informational message CSQU522I.
  The QMGR number is stored in the DB2 tables, the XCF group
  member and the connections to the CF structures. It is
  generated when a QMGR is added to a QSG using CSQ5PQSG.
  "
  
  
  CSQU567E: QMGR qmgr-name not added to DB2 table due to a number
            mismatch.
  
  Explanation:
  "
  The QMGR qmgr-name could not be added to DB2 tables due to a
  mismatch in the QMGR numbers as indicated by message CSQU568E
  issued earlier.
  "
  
  System action:
  "
  The utility terminates.
  "
  
  System programmer response:
  "
  Add the QMGRs in the order corresponding to their QMGR number
  values in the XCF group, as can be seen by message CSQU524I when
  running CSQ5PQSG queue sharing group utility with the
  "VERIFY QSG" parameter.
  If the issue is linked to a persistent failing connection to the
  CSQ_ADMIN structure, the problem can be resolved by clearing the
  CF structure using the SETXCF FORCE command.
  "
  
  
  CSQU568E: QMGR number mismatch for QMGR qmgr-name in QSG
            qsg-name: DB2 value=nn, XCF member value=nn,
            CSQ_ADMIN connection value=nn
  
  Explanation:
  "
  The QMGR number is stored in the DB2 tables, the XCF group
  member and the connections to the CF structures. It is created
  when a QMGR is added to a QSG using the queue sharing group
  utility (CSQ5PQSG).
  This message indicates that there is a mismatch in these values
  for QMGR qmgr-name in QSG qsg-name which will prevent the QMGR
  from starting.
  "
  
  System action:
  "
  The utility terminates after all members in the XCF group have
  been processed.
  "
  
  System programmer response:
  "
  If the QMGR number value is -1, the entry does not exist. Use
  the CSQ5PQSG utility with "ADD QMGR" parameter to add the
  missing entry. If the QMGR number value is 0, it means the value
  has not been initialised (XCF group member and CSQ_ADMIN
  connection values only). Starting the QMGR will initialise the
  value. If QMGR number values greater than 0 mismatch, collect
  the items listed in the Coupling Facility problem determination
  guide and contact your IBM  support center.
  "
  
  
  CSQU569E: Unexpected CSQ_ADMIN connection found for QMGR
            qmgr-name
  
  Explanation:
  "
  For each QMGR in the QSG there should only be one connection to
  the CSQ_ADMIN structure. This message is issued for each
  additional connection found.
  "
  
  System action:
  "
  The utility terminates after all members in the XCF group have
  been processed.
  "
  
  System programmer response:
  "
  This situation should not occur. The connections can be
  displayed using the display XCF command for the CSQ_ADMIN
  structure.
  Collect the items listed in the Coupling Facility problem
  determination guide and contact your IBM  support center.
  "
  
  
  In the Info Center, following update is made:
  
  WebSphere MQ
   > Reference
    > Administration reference
     > Using the WebSphere MQ Utilities for z/OS
  
  The queue-sharing group utility (CSQ5PQSG)
  
  In the "PARM" section, under "ADD QMGR", the following paragraph
  will be changed:
  
  "
  Add a queue manager record into the CSQ.ADMIN_B_QMGR table.
  This only completes successfully if a corresponding
  queue-sharing group record exists in the CSQ.ADMIN_B_QSG table
  and the queue manager entry does not exist in the
  CSQ.ADMIN_B_QMGR table as the member of a different
  queue-sharing group.
  "
  
  to:
  
  "
  Add a queue manager record into the CSQ.ADMIN_B_QMGR table.
  This only completes successfully if a corresponding
  queue-sharing group record exists in the CSQ.ADMIN_B_QSG table,
  the queue manager entry does not exist in the CSQ.ADMIN_B_QMGR
  table as the member of a different queue-sharing group and there
  is no member entry in the XCF group with a different QMGR number
  value than the one created by the utility when adding the record
  to the CSQ.ADMIN_B_QMGR table.
  If there are members in the XCF group without the corresponding
  entries in the DB2 table, the utility can be used to add them.
  However, the queue managers need to be added in the order that
  is indicated by the CSQU524I messages issued by the queue
  sharing group utility (CSQ5PQSG) run with the "VERIFY QSG"
  parameter.
  "
  
  010Y
  011N
  012Y
  013Y
  014Y
  100Y
  102Y
  103Y
  104Y
  105Y
  CSQFSTXC
  CSQFSTXE
  CSQFSTXF
  CSQFSTXK
  CSQFSTXU
  CSQ5PQSG
  CSQ5PVER
  

Temporary fix

Comments

• ×**** PE13/11/22 PTF IN ERROR. SEE APAR PI05816  FOR DESCRIPTION
  

APAR Information

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

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

  UK92232 UK92233 UK92234 UK92235 UK92236 UK92237 UK92238 UK92239
  UK92240 UK92241

Modules/Macros

• CSQFSTXC CSQFSTXE CSQFSTXF CSQFSTXK CSQFSTXU
  CSQ5PQSG CSQ5PVER
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK92232

     UP13/05/16 P F305

• R012 PSY UK92234

     UP13/05/16 P F305

• R013 PSY UK92235

     UP13/05/16 P F305

• R014 PSY UK92236

     UP13/05/16 P F305

• R100 PSY UK92237

     UP13/05/16 P F305

• R102 PSY UK92238

     UP13/05/16 P F305

• R103 PSY UK92239

     UP13/05/16 P F305

• R104 PSY UK92240

     UP13/05/16 P F305

• R105 PSY UK92241

     UP13/05/16 P F305

• R011 PSN

     UP

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.