IT44910: MQ trace on server incorrectly captures user message data duringclient MQGET when using the "-d 0" flag on strmqtrc

APAR status

• Closed as program error.

Error description

• The "-d 0" flag on the  'strmqtrc' command  is documented to
  "Trace no user data".
  
  However this is not working as intended, and a small amount of
  user data is still captured in trace.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users who wish to capture an MQ trace but want to exclude all
  message data from the trace using the '-d 0' option on strmqtrc.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The 'strmqtrc' command is used to start trace for a queue
  manager or applications using some of the MQ APIs.
  
  One of the optional arguments which can be used with 'strmqtrc'
  is the '-d' argument, with a numeric value used to control the
  amount of user data which is captured and recorded in the output
  trace files.
  The documented values are:
  
    0  : Trace no user data
    -1 : Trace all user data
    NumOfBytes :
        (a) For a communication trace; trace the specified number
  of bytes of data including the transmission segment header
  (TSH).
        (b) For an MQPUT or MQGET call; trace the specified number
  of bytes of message data held in the message buffer.
        Values in the range 1 through 15 are not allowed.
  
  
  If the argument value '-d 0' is specified, then it was expected
  that no user data (ie. user message content) would be recorded
  in the trace file.  However there was a place in the MQ code
  where the wrong tracing function was being used, resulting in
  user data being emitted into the trace output files.
  

Problem conclusion

• The place in the MQ code where the wrong tracing function was
  being used, has been corrected to use the correct tracing
  function.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.20
  v9.2 LTS   9.2.0.25
  v9.3 LTS   9.3.0.20
  v9.x CD    9.3.5
  
  The latest available maintenance can be obtained from
  'IBM MQ Recommended Fixes'
  https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'IBM MQ
  Planned Maintenance Release Dates'
  https://www.ibm.com/support/pages/ibm-mq-planned-maintenance-rel
  
  ---------------------------------------------------------------
  

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.3

• Fixed component ID

  5724H7291

Applicable component levels