PI72356: MQ V9 DOES NOT SUPPORT A TMF MQ CLIENT RUNNING ON HP NONSTOP SERVER. MESSAGE AMQ5378 OCCURS AT THE CLIENT.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Starting the connection from a 'WebSphere MQ Client for HP
  Integrity NonStop Server Version 8.0.0.1' (or higher) with TMF
  Gateway to MQ V9 on z/OS, the following messge appears in the MQ
  Client log:
  
  AMQ5378: Participation in TMF transactions is not supported by
  queue manager 'CSQ1'
  
  EXPLANATION:
  TMF/Gateway has detected WebSphere MQ for z/OS queue manager
  'CSQ1' does not support participation in TMF transactions.
  
  ACTION:
  The version of z/OS queue manager that you are connecting to
  does not support the TMF Gateway, please upgrade to a supported
  release.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of IBM MQ for z/OS Version 9 Release 0             *
  * Modification 0.                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When a HP Non-Stop TMF client connects to MQ for z/OS, the   *
  * client application can experience the following symptoms:    *
  * XA_OPEN fails to establish an XA transaction and MQ client   *
  * generates error message AMQ5378 in the client error log or   *
  * MQGET API calls fail with MQRC_SYNCPOINT_NOT_AVAILABLE       *
  * (2072).                                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * N/A                                                          *
  ****************************************************************
  The MQ client HP Non-Stop TMF application connects to a MQ for
  z/OS queue manager and requests to establish a transactional
  session sending a flow of XA_OPEN and XA_INFO messages. The
  XA_INFO message is a string with key/value pairs. The queue
  manager fails to properly parse the string and identify the key
  names responding to the client as it does not support HP
  Non-Stop TMF. The parsing failure is related to the CCSID that
  queue manager is running. In this case the queue manager was
  running with CCSID 278 where the '@' has code-point xEC instead
  of x7C as expected by the queue manager.
  
  Reason code MQRC_SYNCPOINT_NOT_AVAILABLE (2072) is generated
  because special logic for TMF is not executed to set the
  existing XA session to the correct state for MQGET.
  
  Queue managers running with any of the following CCSIDs can be
  affected by this problem:
  273, 277, 278, 280, 284, 290, 297, 803, 871, 935, 1026, 1122,
  1141, 1142, 1143, 1144, 1145, 1147, 1149, 1157, 1388, 1390,
  4899, 5026.
  

Problem conclusion

• The queue manager converts the XA_INFO string from the CCSID of
  the queue manager to a system CCSID used by the compiler. This
  fixes the parsing of the XA_INFO string and the client can
  initiate a TMF transaction with the queue manager. XA sessions
  are set to the correct state for TMF before processing MQGET API
  calls in syncpoint.
  

Temporary fix

Comments

APAR Information

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

  PI65866

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

  UI43182

Modules/Macros

• CSQMCPRH CSQMXARH N/A
  

Fix information

• Fixed component name

  MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R000 PSY UI43182

     UP17/01/10 P F701

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.