PH47945: MQ: INCORRECT CHL STATUS OF DIS CLUSQMGR WITH MULTIPLE CONNECTION NAMES BEFORE THE FIRST FLOW

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a sender type channel has multiple connection names in the
  CONNAME field, then sessions negotiations are performed one
  connection at a time with an internal 'retryable' flag set. The
  CHSTATUS STATUS is updated throughout this process.
  
  For CLUSSDR channels, the status is also propagated to the
  associated CLUSQMGR object at certain points. The CLUSQMGR
  object is only updated if the internal 'retryable' flag is off.
  The flag is turned off after a session has been negotiated with
  a remote end, but the CLUSQMGR object status is not updated
  until after the first flow. This will usually be after sending
  a batch or after a heartbeat flow.
  
  APAR PI85984 added code to update the CLUSQMGR object status
  after the first flow, but this logic doesn't address the window
  between a successful session negotiation and the first flow.
  For channels with a single connection name, the CLUSQMGR object
  status is correctly updated immediately after the session
  negotiation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 1 Modification 0 and                 *
  *                 Release 2 Modification 0 and                 *
  *                 Release 3 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: DISPLAY CLUSQMGR incorrectly reports    *
  *                      a running Cluster Sender Channel with   *
  *                      STATUS(INACTIVE) when the Cluster       *
  *                      Receiver Channel has multiple CONNAMES  *
  *                      in its definition before any data has   *
  *                      flowed across the channel pair.         *
  ****************************************************************
  After starting a Cluster Sender Channel where the target Cluster
  Receiver Channel has multiple CONNAMES defined there is a window
  of time before any data is sent across the channel pair where
  a valid DISPLAY CLUSQMGR command will incorrectly report the
  Cluster Sender Channel with STATUS(INACTIVE). In this same
  window a valid DISPLAY CHSTATUS command will report the Cluster
  Sender Channel with STATUS(RUNNING).
  

Problem conclusion

• The code has been corrected to ensure that memory containing the
  channel state printed by the DISPLAY CLUSQMGR command is
  correctly updated during Cluster Sender Channel startup. The
  DISPLAY CLUSQMGR command will now correctly display the status
  of the Cluster Sender Channel after it has been started.
  

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:

  UI90699 UI90700 UI90701

Modules/Macros

• CSQXRCCC
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R100 PSY UI90701

     UP23/03/08 P F303

• R200 PSY UI90700

     UP23/03/08 P F303

• R300 PSY UI90699

     UP23/03/08 P F303

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.