Fixes are available
APAR status
Closed as program error.
Error description
Some WebSphere MQ File Transfer Edition commands may report an agent's status as "unreachable" when the agent status cannot be determined from the information currently available on the coordination queue manager. This is inaccurate, as these commands do not attempt to communicate with the agent, and so do not offer any indication of whether the agent is contactable. More information on common causes of this situation is available in the following technote: http://www-01.ibm.com/support/docview.wss?uid=swg21616381
Local fix
Problem summary
**************************************************************** USERS AFFECTED: The APAR affects all users of WebSphere MQ File Transfer Edition and all users of WebSphere MQ Managed File Transfer. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The WebSphere MQ Explorer FTE/MFT plug-in and the fteShowAgentDetails and fteListAgents commands used to report an agent's status as "unreachable" when the agent status could not be determined from the information held on the coordination queue manager. This was inaccurate, as these mechanisms did not attempt to communicate with the agent, and so were unable to determine if the agent could be contacted.
Problem conclusion
The product has has been changed to alter the UNREACHABLE state to UNKNOWN. The previously defined UNKNOWN status has been changed to UNDEFINED. UNKNOWN status now means that agent status updates were not received at the expected time intervals by the coordination queue manager. The agent might have stopped running due to an error, or have been shut down abruptly, or be running but experiencing communication problems. If an agent's status is shown as UNKNOWN, run the ftePingAgent command to determine if the agent can be contacted and is running. UNDEFINED status means that the agent's status cannot be determined. It might have published a status which is not recognised. For more information on this APAR, as well as details about why an agent status can be shown as either UNREACHABLE or UNKNOWN, please see the following video : https://www.youtube.com/watch?v=L_DjWYjiRRA --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.5 v7.5 7.5.0.5 v8.0 8.0.0.2 The latest available FTE maintenance can be obtained from 'Fix List for WebSphere MQ File Transfer Edition 7.0' http://www-01.ibm.com/support/docview.wss?uid=swg27015313 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
IT05697
Reported component name
WMQ FILE TRANSF
Reported component ID
5724R1000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-20
Closed date
2014-12-04
Last modified date
2016-02-03
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
WMQ FILE TRANSF
Fixed component ID
5724R1000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
03 February 2016