IBM Support

IT16093: MFT fteAnt command not using channel or port definitions from resulting in MQRC 2538


You can track all active APARs for this component.


APAR status

  • Closed as program error.

Error description

  • IBM MQ MFT fteAnt command was not using the
    connectionQMgrChannel and connectionQMgrPort properties from the when the cmdqm attribute did not specify
    these parameters in the Apache ANT script being run.  As such,
    the MFT ANT code attempted to connect to the command queue
    manager using the default channel name, "SYSTEM.DEF.SVRCONN" and
    the default port value, 1414.
    If the command queue manager was not available using these
    connection details, then the MQ reason code 2538
    (MQRC_HOST_NOT_AVAILABLE) is returned to the MFT ANT code.  As
    such, the fteAnt file transfer fails with following error:
    BFGCL0411E: A messaging problem prevented the command from
    completing successfully. The IBM MQ completion code was 2, the
    reason code was  2538 and diagnostic message code was AMQ9205.
    A connection could not be established to queue manager ???, on
    host '???' using port 1414 and channel SYSTEM.DEF.SVRCONN.

Local fix

  • Specify the full command queue manager connection details in the
    cmdQm attribute within the Apache ANT script.  The cmdQM
    attribute, available on the tasks:
      - fte:filecopy
      - fte:filemove
      - fte:cancel
      - fte:call
      - fte:ping
    has the form:
      - qmgrname is the name of the queue manager
      - host is the host name of the system where the queue manager
    is running
      - port is the port number that the queue manager is listening
      - channel is the server-connection channel to use

Problem summary

  • ****************************************************************
    This issue affects users of IBM MQ Managed File Transfer V8 and
    V9 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:
    When using the fteAnt command to run an Apache ANT script, if
    commands need to be sent to an agent (such as when using the
    fte:ping or fte:filecopy ANT tasks) the MFT ANT code must
    connect to a command queue manager within the MFT topology.
    In the case where all of the connection details to the command
    queue manager were not supplied by either the property (passed in when
    the fteAnt command is invoked), or the cmdqm attribute specified
    on a task definition in Apache ANT script, the default values
    for the channel and port were used to connect to the command
    queue manager, instead of those stored in the
    As an example, this could have occurred when the cmdqm attribute
    was specified within the Apache ANT script without detailing the
    command queue name and host, but not the channel and port, like
      <fte:ping cmdqm="" ...
    When the cmdqm attribute does not specify all of the connection
    details, it is expected that the values defined within the configuration file would take precedence over
    the default values. Default values are only expected to be used
    if the file is missing or incomplete.

Problem conclusion

  • The IBM MQ Managed File Transfer code has been updated to ensure
    that connection details for a command queue manager are obtained
    from the configuration file if they have not
    already been specified using the following mechanisms:
      1) In the Apache Ant XML script itself via the "cmdqm"
    attribute on a task definition,
      2) Using the property
    when the fteAnt command is invoked.
    Default values for the connection properties to the command
    queue manager are only used when they have not been specified
    within the Apache ANT script via the "cmdqm" attribute, or using
    the property, and are not
    present in the 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 PTFs:
    Version    Maintenance Level
    v9.0 CD    9.0.1
    v9.0 LTS
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    IBM MQ MFT V9.0

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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.0

  • Fixed component ID


Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 December 2020