IT32925: Update JMQI trace to remove unnecessary values from the options field

APAR status

• Closed as program error.

Error description

• An IBM MQ Managed File Transfer agent trace is generated using
  the trace specification:
  
  *=all
  
  The resultant trace file contains information from the Java
  Message Queueing Interface (JMQI). The JMQI is used by the agent
  to communicate with its agent queue manager. The trace
  information generated by the JMQI shows the options that are
  passed into various MQ API calls, such as MQOPEN. The format of
  these options as shown below:
  
  options:8260(0x2044)
  option flags:'MQGMO_CURRENT_VERSION/MQGMO_NO_SYNCPOINT |
  MQGMO_ACCEPT_TRUNCATED_MSG | MQGMO_FAIL_IF_QUIESCING'
  
  which is a little confusing.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of:
  
  - The IBM MQ AMQP service.
  - The IBM MQ classes for Java.
  - The IBM MQ classes for JMS.
  - IBM MQ Managed File Transfer.
  - The IBM MQ resource adapter.
  - The IBM MQ Telemetry service
  
  who are asked to collect trace of an issue by IBM Support.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The Java Message Queueing Interface (JMQI) is used by the
  following components whenever they need to communicate with a
  queue manager:
  
  - The IBM MQ AMQP service.
  - The IBM MQ classes for Java.
  - The IBM MQ classes for JMS.
  - IBM MQ Managed File Transfer.
  - The IBM MQ resource adapter.
  - The IBM MQ Telemetry service.
  
  Trace information generated by the JMQI included the options
  that were passed to MQ API calls (such as MQOPEN and MQGET). An
  example of this is shown below:
  
  options:8260(0x2044) option
  flags:'MQGMO_CURRENT_VERSION/MQGMO_NO_SYNCPOINT |
  MQGMO_ACCEPT_TRUNCATED_MSG | MQGMO_FAIL_IF_QUIESCING'
  
  The inclusion of a string that ended with "_VERSION" in some
  cases, was felt to be confusing and make the trace difficult to
  analyse.
  

Problem conclusion

• The JMQI has been updated so that the trace entries which show
  the options that are passed to MQ API calls now look like this:
  
  options:8260(0x2044) option flags:'MQGMO_NO_SYNCPOINT |
  MQGMO_ACCEPT_TRUNCATED_MSG | MQGMO_FAIL_IF_QUIESCING'
  
  The trace entries no longer include any strings that contain
  "_VERSION". This makes the trace easier to understand.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.7
  v9.2 LTS   9.2.0.1
  v9.x CD    9.2.1
  
  The latest available MQ maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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:

Fix information

• Fixed component name

  IBM MQ MFT V9.1

• Fixed component ID

  5724H7272

Applicable component levels