PI44085: WMQ SUPPLY SERVICE PARAMETER TO AVOID EXTRA CHECKING AT VERSION 800 OF WEBSPHERE MQ WHEN A CLIENT SENDS INVALID MQOPEN FLOWS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This apar documents the provision of a service parm to avoid
  extra checking in V800 that causes FFSTs to be generated when
  a client sends invalid MQOPEN flows to a queue-manager.
  .
  Additional symptoms:
   +CSQX053E CSQ1 CSQXFFST Error information recorded in CSQSNAP
    data set
   +CSQX504E CSQ1 CSQXRESP Local protocol error,
    channel CSQ2.TO.CSQ1
    type=0000000B data=00000000
   +CSQX599E CSQ1 CSQXRESP Channel CSQ2.TO.CSQ1 ended abnormally
    connection
   .
   Eyecatchers in the CSQSNAP DD include:
    XFFSrriBadDataReceived
    XFFSrriConvertValidate
    TSH received
  .
  The Client problem is described by IV36766.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
  *                 Release 0 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a Java client at version V7.0.0.0  *
  *                      connects to a V8.0.0 z/OS queue manager *
  *                      an MQOPEN of a queue will fail with     *
  *                      'CSQX504E Local protocol error'.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Java V7.0.0.0 code does not send a valid flow for the MQOPEN
  API call. This invalid data is tolerated by V7.0.1 (and V7.1.0
  with toleration PTF enabled) queue managers, but at V8.0.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 WebSphere MQ Service team. Without this activation, the
  server behavior will remain unchanged.
  
  Please contact WebSphere MQ Service if you wish to activate this
  capability.
  000Y
  CMQXRMCV
  

Temporary fix

Comments

APAR Information

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

  PM93412

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

  UI32246

Modules/Macros

• CMQXRMCV
  

Fix information

• Fixed component name

  WMQ Z/OS 8

• Fixed component ID

  5655W9700

Applicable component levels

• R000 PSY UI32246

     UP15/12/15 P F512

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.