IT40168: fteDeleteAgent with the -f option does not remove resource monitor publications from coordination queue manager

APAR status

• Closed as program error.

Error description

• An IBM MQ Managed File Transfer (MFT) agent called AGENT1 has
  been created, and two directory resource monitors:
  
  - MONITOR1
  - MONITOR2
  
  have been defined on it. When the fteListMonitors command is
  run, it generates the following output:
  
  Agent Name:     Monitor Name:     Resource Type:
  AGENT1          MONITOR1          Directory
  AGENT1          MONITOR2          Directory
  
  
  The system where AGENT1 is running is subsequently shut down and
  decommissioned. After this has happened, the command:
  
  fteDeleteAgent -f AGENT1
  
  is run from another machine in the MFT topology, to remove
  information about AGENT1 from the coordination queue manager.
  
  If the fteListAgents command is subsequently run, the output no
  longer contains any information for AGENT1, which is good.
  However, when the fteListMonitors command is run, the output
  still contains the entries:
  
  Agent Name:     Monitor Name:     Resource Type:
  AGENT1          MONITOR1          Directory
  AGENT1          MONITOR2          Directory
  
  even though AGENT1 is no longer part of the MFT topology.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of IBM MQ Managed File Transfer who:
  
  - Have an agent configured to use one or more resource monitors.
  - And then run the fteDeleteAgent command with the -f option to
  delete that agent.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The coordination queue manager for an IBM MQ Managed File
  Transfer (MFT) topology acts as a central repository for
  information about that topology. Information about various
  aspects of the topology, such as:
  
  - The agents within the topology.
  - The resource monitors defined on the agents within the
  topology.
  - The managed transfers that have taken place between agents in
  the topology.
  
  are stored on the SYSTEM.FTE topic on the queue manager. in
  retained publications. Various tools, such as the IBM MQ
  Explorer Managed File Transfer plug-in, fteListAgents and
  fteListMonitors:
  
  - Connect to the coordination queue manager.
  - Subscribe to this topic, using a specified topic string, to
  retrieve the retained publications of interest.
  - And then extract information from them to display to the user.
  
  For more information on the SYSTEM.FTE topic, see "SYSTEM.FTE
  topic" in the MQ sections of IBM Documentation. The URI for the
  topic in the MQ 9.3 section of IBM Documenation is shown below:
  
  https://www.ibm.com/docs/en/ibm-mq/9.3?topic=reference-systemfte
  -topic
  
  
  If an agent was removed from the topology using the command:
  
  fteDeleteAgent -f <agent_name>
  
  (because the system where it was running had been shut down and
  decommissioned), then the command would connect to the
  coordination queue manager, and remove the retained publications
  containing status information for that agent from the SYSTEM.FTE
  topic (these retained publications were stored under the topic
  string "Agents/<agent_name>"). This meant that when the
  fteListAgents command was run and retreived the agent status
  publications from the coordination queue manager, its output
  would not contain any entries for this agent.
  
  However, the command did not remove the retained publications
  containing information about the monitors associated with that
  agent, which were stored under the topic string "Monitors/".
  This meant that when the fteListMonitors command was
  subsequently run, it would:
  
  - Connect to the coordination queue manager.
  - Get the retained publications for these monitors.
  - And display details of them to the user.
  
  This caused some confusion, as the fteListMonitors output
  indicated that the agent and its associated resource monitors
  were still part of the MFT topology, even though the agent was
  no longer running and did not appear in the output to the
  fteListAgents command.
  

Problem conclusion

• To resolve this issue, the fteDeleteAgent command has been
  updated so that if it is run with the -f option, it will remove
  the retained publications containing information about monitors
  associated with the agent from the SYSTEM.FTE topic. This
  ensures that the monitors no longer appear in the output of the
  fteListMonitors command.
  
  Note: In order to do this, the fteDeleteAgent command can be run
  from any other machine in the IBM MQ Managed File Transfer (MFT)
  topology that can establish a connection to the coordination
  queue manager. For example:
  
  - AGENT1 is running on MACHINE1.
  - AGENT2 is running on MACHINE2.
  - Both AGENT1 and AGENT2 use COORDQM as the coordination queue
  manager, which is running on MACHINE3
  - MACHINE1 is permanently deleted from the MFT topology.
  - The command fteDeleteAgent -f AGENT1 is then run from
  MACHINE2, to remove information about AGENT1 and its resource
  monitors from the coordination queue manager COORDQM on
  MACHINE3.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.12
  v9.2 LTS   9.2.0.7
  v9.3 LTS   9.3.0.1
  v9.x CD    9.3.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