IT39927: "Monitor Started" events are missing from the MQ Managed File Transfer resource monitor event log (resmonevent0.log)

APAR status

• Closed as program error.

Error description

• An IBM MQ 9.1 LTS Managed File Transfer agent has been created,
  and a resource monitor has been defined on it which monitors a
  queue resource looking for either complete messages in a group,
  or individual messages not in a group. When the agent starts,
  the resource monitor starts up and writes an entry for a
  "Monitor Started event" to the agent's resource monitor event
  log (resmonevent<number>.log). An example of this is shown
  below:
  
    ... MONITOR1      Monitor Started     Resource Monitor Started
  
  The agent is then migrated to use MQ 9.2 Managed File Transfer.
  After this has taken place, the monitor no longer writes a
  "Monitor started event" to the agent's resource monitor event
  log.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects uses of MQ Managed File Transfer, who have
  agents that use resource monitors.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The IBM MQ Managed File Transfer resource monitor logging
  functionality provides a mechanism for users to get information
  about what resource monitors running on an agent are doing. When
  this functionality is being used, a resource monitor will write
  information to an agent's resource monitor event log
  (resmonevent<number>.log) when it performs certain "events",
  such as:
  
  - Starting a poll.
  - Submitting a managed transfer request to an agent.
  
  A full list of "events" can be found in the:
  
    Logging MFT resource monitors
  
  topic in the MQ sections of IBM Documentation (the URI for this
  topic in the MQ 9.2 section of IBM Documentation is
  https://www.ibm.com/docs/en/ibm-mq/9.2?topic=resources-logging-m
  ft-resource-monitors).
  
  
  Now, when using MQ 9.1 Managed File Transfer, a resource monitor
  would log a "Monitor started event" to the resource monitor
  event log when it first started, as shown in the example below:
  
    ... MONITOR1      Monitor Started     Resource Monitor Started
  
  However, the code to generate this "event" was incorrectly
  removed from MQ 9.2 Managed File Transfer, and so the "event"
  never appeared in the resource monitor event log when using this
  version of the product.
  

Problem conclusion

• To resolve this issue, two changes have been made to MQ 9.2
  Managed File Transfer:
  
  Change 1:
  -------------
  The first change is to restore the code that generates the
  "Monitor started event". This ensures that a resource monitor
  will always write this "event" to the resource monitor event log
  (resmonevent<number>.log) when it starts up.
  
  Change 2:
  -------------
  In addition to this, the resource monitor event log
  functionality has been updated so that if two different internal
  threads try to write "events"  to the resource monitor event log
  at the same time (for either the same resource monitor, or
  different resource monitors), then the second thread will block
  until the first thread had finished writing its "event". Once
  the first thread has finished, then the second thread will write
  its "event" to the log. Prior to this change, the second thread
  would discard the "event" it was trying to write, which resulted
  in the resource monitor event log missing entries for some
  "events".
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.6
  v9.x CD    9.3.0.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