PH13647: MQ V910: CSQX053E WHEN MQ CLIENT AT V700 SENDS INVALID MQOPEN FLOW

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• MQ v910 on z/OS
  
  An extra checking in V910 is causing the  FFSTs to be generated
  when a Java client at v700 code  sends invalid MQOPEN flows
  to a queue-manager. Errors received starting SVRCONN channel:
  
  CSQX053E -MQB1 CSQXFFST Error information recorded in CSQSNAP
  data set
  
  CSQX504E -MQB1 CSQXRESP Local protocol error,
  channel COPS.SVRCONN  type=0000000B   data=00000000
  
  
  Eyecatchers in the CSQSNAP DD include:
    XFFSrriBadDataReceived
    XFFSrriConvertValidate
    TSH received
  
  The Client problem is described by IV36766.
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a Java client at version V7.0.0.0  *
  *                      connects to a V9.1.0 z/OS queue manager *
  *                      an MQOPEN of a queue will fail with     *
  *                      'CSQX504E Local protocol error'.        *
  ****************************************************************
  The Java V7.0.0.0 code does not send a valid flow for the
  MQOPEN API call. This invalid data is tolerated by the V7.0.1
  queue manager, but at V9.1.0, additional tests will detect the
  invalid flow and terminate the channel connection, reporting
  a CSQX504E error. In addition an FFST is captured on the z/OS
  server side indicating "rriBadDataReceived".
  
  This issue is addressed in the Java Client Fix Pack 1
  (V7.0.0.1 and above), but it may be impractical for a customer
  to deploy the client-side fix throughout their enterprise.
  

Problem conclusion

• Following the application of the PTF for this APAR, customers
  may elect to enable less stringent checking of MQOPEN flows from
  clients to prevent the failure from occurring on the server.
  
  This checking will only be disabled when activated using the
  appropriate CHISERVP service parameter under the direction of
  the IBM MQ Service team. Without this activation, the server
  behaviour will remain unchanged.
  
  Please contact IBM MQ Service if you wish to activate this
  capability.
  

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:

  UI64336

Modules/Macros

• CMQXRMCV
  

Fix information

• Fixed component name

  IBM MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R100 PSY UI64336

     UP19/10/01 P F909

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.