IT36805: MQ trace not generated after failure in opening trace files

APAR status

• Closed as program error.

Error description

• If MQ trace directory has incorrect permissions or ownership and
  MQ is unable to
  open trace files after enabling trace, then subsequently even
  restarting trace
  after fixing the permissions or ownership issue not generating
  trace files.
  
  The strmqtrc command is likely to report the following error to
  the user due to the MQ trace directory
  permission or ownership issue.
  
  AMQ7256W: Trace directory '/var/mqm/trace' has restricted
  permissions 'd---------'.
  
  Failure data capture (FDC) records indicating failure in opening
  trace files from MQ processes will also be generated.
  
  strmqm   31614  1 XY082050 xtrOpenTraceFile
  xecF_E_UNEXPECTED_SYSTEM_RC
  amqzxma0 31617  1 XY082050 xtrOpenTraceFile
  xecF_E_UNEXPECTED_SYSTEM_RC
  amqzfuma 31625  1 XY082050 xtrOpenTraceFile
  xecF_E_UNEXPECTED_SYSTEM_RC
  amqzmuc0 31628  1 XY082050 xtrOpenTraceFile
  xecF_E_UNEXPECTED_SYSTEM_RC
  amqzmur0 31639  1 XY082050 xtrOpenTraceFile
  xecF_E_UNEXPECTED_SYSTEM_RC
  amqzmuf0 31653  1 XY082050 xtrOpenTraceFile
  xecF_E_UNEXPECTED_SYSTEM_RC
  
  Restarting the trace (i.e. stop the trace using "endmqtrc -a"
  and start again with strmqtrc) after
  fixing permission or ownership issues, does not allow successful
  trace generation for existing MQ processes. MQ trace is
  generated for newly created MQ processes and commands executed,
  but not for processes that were already running when the
  previous attempt to start trace failed.
  

Local fix

• Restart the Queue Manager
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users enabling MQ trace in a system with MQ trace directory
  configured with incorrect permissions and ownership
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A defect in MQ trace file management caused MQ to not re-open
  trace files after initial failure in opening trace file, even
  after MQ trace is restarted.
  

Problem conclusion

• MQ code has been modified to re-open the MQ trace files if MQ
  trace is restarted by the user.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0 LTS   9.0.0.13
  v9.1 LTS   9.1.0.11
  v9.2 LTS   9.2.0.5
  v9.x CD    9.3.0
  
  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