APAR status
Closed as program error.
Error description
An IBM MQ Managed File Transfer topology consists of: - A coordination queue manager running on an MQ Appliance. - A number of agents running different versions of IBM MQ Managed File Transfer for z/OS. The agent systems are upgraded to IBM MQ Managed File Transfer for z/OS V9.0.3.0. After doing this, then running the commands: - fteCreateTemplate - fteDeleteTemplates - fteListAgents - fteListMonitors - fteListScheduledTransfers - fteListTemplates - fteShowAgentDetails (which connect directly to the coordination queue manager on the IBM MQ Appliance) on the z/OS system results in the following error: BFGCL0002E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was 2, and the reason code was 2298. A connection could not be established to queue manager <queue manager name>, on host '<hostname>' using port <port number> and channel <channel name>.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of: - IBM MQ Managed File Transfer for z/OS V9.0.3 (and later). - IBM MQ Managed File Transfer for z/OS V9.1 who have an IBM MQ Managed File Transfer topology where commands that are run on z/OS connect to a coordination queue manager using the CLIENT transport. Platforms affected: z/OS **************************************************************** PROBLEM DESCRIPTION: A licensing change in IBM MQ Advanced for z/OS VUE, V9.0.3 and later, means that IBM MQ Advanced for z/OS VUE Managed File Transfer agents can now create a CLIENT connection to their agent queue manager, providing the queue manager is also running on z/OS. Prior to this, agents running on z/OS had to connect to their agent queue manager using the BINDINGS transport. The check to enforce this went into common code that was used whenever one of the following commands: - fteCreateTemplate - fteDeleteTemplates - fteListAgents - fteListMonitors - fteListScheduledTransfers - fteListTemplates - fteShowAgentDetails connected to a coordination queue manager for an IBM MQ Managed File Transfer topology. This meant that, after IBM MQ Managed File Transfer for z/OS V9.0.3, the commands mentioned above would only be able to connect to a coordination queue manager using the CLIENT transport if the coordination queue manager was running on z/OS. If the queue manager was not running on z/OS, then the command would fail and report the following error: "BFGCL0002E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was 2, and the reason code was 2298. A connection could not be established to queue manager [queue manager name] on host '[hostname]' using port [port number] and channel [channel name]."
Problem conclusion
IBM MQ Managed File Transfer for z/OS has been updated so that it is now possible to run the commands: - fteCreateTemplate - fteDeleteTemplates - fteListAgents - fteListMonitors - fteListScheduledTransfers - fteListTemplates - fteShowAgentDetails on z/OS and have them connect to a queue manager, running on any platform, using the CLIENT transport. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.1 CD 9.1.1 v9.1 LTS 9.1.0.2 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
PH02080
Reported component name
IBM MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
901
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-08-23
Closed date
2018-09-28
Last modified date
2018-11-30
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 Z/OS
Fixed component ID
5655MF900
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":"901","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 November 2018