IBM Support

IT13143: UPDATES TO MFT ERROR MESSAGES AND ERROR HANDLING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A number of IBM MQ MFT messages are either unclear, inaccurate
    or have output which is written to an unexpected location.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ V8 Managed File Transfer
    component who encounter set-up and configuration problems, and
    are using the MQ Managed File Transfer diagnostic output to
    assist in resolving these problems.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This APAR corrects and clarifies a number of IBM MQ Managed File
    Transfer messages.
    
    Message 1:
    ---------------
    BFGMQ1007W: The coordination queue manager cannot be contacted
    or has refused a connection attempt. The WebSphere MQ reason
    code was 2343.
    The agent's presence will not be published.
    BPXM023I (USERID) 179
    BFGCL0254I: Agent configured successfully. The agent has not
    been registered with the coordination queue manager.
    
    The MQ reason code 2343 mentioned in the warning was not
    actually seen during the connection attempt in this scenario, as
    a connection to the coordination queue manager had already been
    made.  Instead the error was due to a problem publishing to the
    queue manager's SYSTEM.FTE topic.
    
    Message 2:
    ---------------
    BFGMQ1041E:  An attempt to connect to queue manager {0} has been
    rejected because of  invalid authentication details. If this
    queue manager has authentication enabled, user ID and password
    details must be supplied.
    
    This message did not contain the userID of the user that could
    not be authenticated, which would have been useful to resolve
    the issue
    
    Message 3:
    ---------------
    BFGMQ1041E:  An attempt to connect to queue manager MQQM has
    been rejected because of invalid authentication details. If this
    queue manager has authentication enabled, user ID and password
    details must  be supplied.
    
    In some circumstances this message was seen when the connection
    to the queue manage had been made successfully, but there was
    insufficient permission to publish to the SYSTEM.FTE topic.
    
    Message 4:
    ---------------
    When running the fteSetupCoordination command with the -f
    parameter to update an existing credentials file, if an error
    occurred the diagnostic information supplied by IBM MQ Managed
    File Transfer did not always include the details of the
    exception thrown.
    
    Message 5:
    ---------------
    A number of IBM MQ Managed File Transfer commands, such as
    fteCreateMonitor, were not writing errors to stderr.log, instead
    the error output was being logged to stdout.log.
    
    For example, when fteCreateMonitor was run twice for the same
    monitor, the message:
    
    	BFGCL0249E: The monitor could not be created as one already
    exists with the given name on that agent.
    
    was written to stdout.log when it should have be written to
    stderr.log
    

Problem conclusion

  • To resolve this issue, the following changes have been made:
    
    Message 1:
    -----------------
    The new message shown below will now be generated in this
    situation:
    
    BFGMQ1043: An attempt to publish agent's presence to the
    coordination queue manager failed. The WebSphere MQ reason code
    was '{0}'.  The publish attempt on SYSTEM.FTE topic has failed
    so the agent's presence will not be published.
    
    Message 2:
    -----------------
    The BFGMQ1041E error message has been enhanced to include the
    userID that could not be authenticated, as show below:
    
    BFGMQ1041E:  An attempt to connect to queue manager '{0}' with
    user ID '{1}' has been rejected because of invalid
    authentication details. Valid user ID and password details must
    be supplied in the credentials file.
    
    Message 3:
    ---------------
    An additional message has been added to cover the scenario where
    a connection to the queue manager by the IBM MQ Managed File
    Transfer agent has been made successfully, but there is
    insufficient permission to publish to the SYSTEM.FTE topic:
    
    BFGMQ1042E:  An attempt to publish agent information on
    SYSTEM.FTE topic has been rejected because user ID '{0}' has
    insufficient authority.
    
    Message 4:
    ---------------
    When running the fteSetupCoordination command with the -f
    parameter to update an existing credentials file, if an error
    occurs the diagnostic information supplied by IBM MQ Managed
    File Transfer has been updated to include the details of the
    exception thrown.
    
    Message 5:
    ---------------
    IBM MQ Managed File Transfer has been updated so that when the
    return code for an operation indicates an error occurred, this
    information is now written to stderr.log.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.5
    
    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

    IT13143

  • Reported component name

    WMQ MFT V8.0

  • Reported component ID

    5724H7252

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-12

  • Closed date

    2016-05-03

  • Last modified date

    2016-05-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 MFT V8.0

  • Fixed component ID

    5724H7252

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 May 2016