IT34120: Running MQ Explorer with trace enabled does not generate all of the expected trace files.

APAR status

• Closed as program error.

Error description

• The IBM MQ 9.2.0.0 Explorer is installed onto a Windows system,
  and is started with the command:
  
  C:\Program Files\IBM\MQ\MQExplorer\eclipse\runwithtrace.cmd
  
   The command outputs the following information to the console:
  
  Trace will be written to the temporary directory
  C:\Users\User1\AppData\Local\Temp
  Launching ..\..\bin64\MQExplorer.exe  -vmargs -Xmx512M
  -Dosgi.framework.extensions=org.eclipse.equinox.weaving.hook
  "-Dcom.ibm.mq.commonservices=C:\Users\User1\AppData\Local\Temp\m
  q_trace.properties"
  
  This should result in the MQ Explorer generating two sets of
  trace files in the directory C:\Users\User1\AppData\Local\Temp\:
  
  - The first set of trace files are called
  AMQ<number>.<number>.TRC.<number>, and contain information
  from the user interface.
  
  - The second set of trace files, which contain information from
  the MQ classes for Java which are used by the MQ Explorer to
  communicate with the queue managers that it is administering,
  are called mqjavaclient_<PID>.cl0.trc (where <PID> is the
  process identifier for the MQ Explorer).
  
  However, the directory only contains trace files called
  AMQ*.TRC. There are no MQ classes for Java trace files.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the IBM MQ Explorer, who are asked
  to collect a trace of the user interface in order to investigate
  an issue.
  
  
  Platforms affected:
  Windows, Linux on x86-64
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The IBM MQ Explorer uses the MQ classes for Java to communicate
  with the queue managers that it is administering.
  
  When the user interface was started with the command:
  
  <MQ_INSTALLATION_PATH>\MQExplorer\eclipse\runwithtrace
  
  it wrote the following message to the console:
  
  Trace will be written to the temporary directory <temporary
  directory>
  Launching ..\..\bin64\MQExplorer.exe  -vmargs -Xmx512M
  -Dosgi.framework.extensions=org.eclipse.equinox.weaving.hook
  "-Dcom.ibm.mq.commonservices=<temporary
  directory>\mq_trace.properties"
  
  and then should have started generating two sets of trace files
  in the temporary directory specified:
  
  - The first set of trace files, called:
  
      AMQ<number>.<number>.TRC.<number>
  
  would contain information from the user interface.
  - The second set of trace files, called:
  
      mqjavaclient_<PID>.cl0.trc
  
  (where <PID> is the process identifier for the MQ Explorer)
  would contain information from the MQ classes for Java.
  
  However, as a result of some internal changes to the IBM MQ
  messaging client trace mechanism (which was used by the MQ
  classes for Java), the user interface would not create the
  mqjavaclient_<PID>.cl0.trc file. As a result, the MQ Explorer
  would only generate trace from the user interface layer, and not
  the MQ classes for Java.
  

Problem conclusion

• The IBM MQ messaging client trace mechanism has been updated to
  ensure that MQ classes for Java trace is generated when the MQ
  Explorer is started using the:
  
  <MQ_INSTALLATION_PATH>\MQExplorer\eclipse\runwithtrace
  
  command.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.1
  
  The latest available 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

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels