Fixes are available
APAR status
Closed as program error.
Error description
After installing FTE tool using WebSphere MQ 7.5 on Linux, FTE agent failed to connect to the command queue manager when there was no connection detail provided in the fteAnt script. From the log, it generated the bellow error. Error: BFGCL0002E: A messaging problem prevented the command from completing successfully. The WebSphere MQ completion code was 2, and the reason code was 2035. A connection could not be established to queue manager. LOCAL FIX: NONE.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of WebSphere MQ 7.5 Managed File Transfer who are executing Apache Ant scripts which utilise any of the following FTE supplied Ant tasks: - fte:call - fte:cancel - fte:filecopy - fte:filemove - fte:ping Platforms affected: MultiPlatform **************************************************************** PROBLEM SUMMARY: The fteAnt command handler, used to submit commands to an agent, was incorrectly using the default values for the agent's channel and port instead of those stored in the command.properties file. This resulted when connection details were not supplied by either the com.ibm.wmqfte.ant.commandQueueManager property when the fteAnt command is invoked or the cmdqm attribute within an fteAnt XML script. In this case, it was expected that the values defined within the command.properties configuration file would take precedence over the default values. Default values are only expected to be used if the command.properties file is missing or incomplete.
Problem conclusion
The WebSphere MQ File Transfer Edition code has been updated to ensure that connection details for the command queue manager of an Agent are obtained from the command.properties configuration file if they have not already been specified using the following mechanisms: 1) In the Apache Ant XML script, or 2) Using the com.ibm.wmqfte.ant.commandQueueManager property when the fteAnt command is invoked. Default values for the connection properties are only used when they have not been specified within the Apache Ant XML script, or using the com.ibm.wmqfte.ant.commandQueueManager property, and are not present in the command.properties configuration file. As a result, the documented order of precedence is now honoured when determining the channel and port to use to connect to the command queue manager. --------------------------------------------------------------- The fix is targeted for delivery in the following: Version v7.5 -------- -------------------- Fix available in: 7.5.0.2 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 number
IC90498
Reported component name
WMQ FTE
Reported component ID
5724H7242
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-26
Closed date
2013-05-07
Last modified date
2013-07-08
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 FTE
Fixed component ID
5724H7242
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 January 2022