APAR status
Closed as program error.
Error description
After submitting an IBM MQ Managed File Transfer (MFT) transfer request using the fteCreateTransfer command where an invalid destination queue manager is specified, the source agent for the transfer becomes stuck in a recovery loop and the transfer cannot be cancelled. During this time, no other transfers can progress. If the source agent connects to its configured queue manager using the CLIENT transport then the agent will loop in and out of recovery processing with the following message repeatedly written to its event log: BFGAG0183I: The agent received MQI reason code 2087. Agent recovery will be initiated. If the source agent connects to its configured queue manager using the BINDINGS transport, then the agent JVM will be repeatedly restarted by the MFT process controller. In this case, the event log will contain multiple headers with the MFT environment information and the following message will be written: BFGAG0170W: The agent has ended because the queue manager is unavailable. The agent will be restarted when the queue manager becomes available.
Local fix
Stop the source agent using the command: fteStopAgent -i <agent_name> and clean the agent of all transfer: fteCleanAgent -trs <agent_name>
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of IBM MQ Managed File Transfer. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When an IBM MQ Managed File Transfer source agent processes a new transfer request, it will attempt to negotiate the start of the transfer with the partner, destination agent. To do this, it will send a message to the SYSTEM.FTE.COMMAND queue of the destination agent by opening this queue on the queue manager named in the transfer request via the -dm (destination_agent_qmgr_name) argument. If the MQOPEN calls fails with the reason code MQRC_UNKNOWN_REMOTE_Q_MGR (2087) because an invalid destination agent queue manager was specified, then the source agent would trigger recovery processing. The source agent would stop all running transfers and then restart as part of recovery processing. Once the recovery processing completed, it would retry processing the new transfer request that contained the invalid destination agent queue manager. The MQOPEN call would again fail with the reason code MQRC_UNKNOWN_REMOTE_Q_MGR, resulting in a further agent recovery processing. This would happen continuously and the agent would be unable to process any transfers, even the valid ones. Prior to MQ MFT V9.0.4.0, the source agent would treat the reason code MQRC_UNKNOWN_REMOTE_Q_MGR as an unrecoverable and fail the transfer. From MQ MFT V9.0.4.0, the reason code MQRC_UNKNOWN_REMOTE_Q_MGR was incorrectly being treated as a recoverable error.
Problem conclusion
IBM MQ Managed File Transfer (MFT) has been updated such that the MQ reason code MQRC_UNKNOWN_REMOTE_Q_MGR (2087) is treated as an unrecoverable error. If the reason code is encountered when processing a new transfer request, the transfer will fail and the source agent will not invoke recovery processing. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.1 CD 9.1.4 v9.1 LTS 9.1.0.4 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 number
IT29902
Reported component name
IBM MQ MFT V9.1
Reported component ID
5724H7272
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-08-02
Closed date
2019-09-05
Last modified date
2019-09-05
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
05 September 2019