IBM Support

IT33387: IBM MQ Explorer MFT capture log shows an incorrect destination path

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • An IBM MQ MFT v9.1.5 transfer was initiated using a MFT Protocol
    Bridge Agent (PBA) as the source agent.
    The credentials configured to connect to the remote file server
    were incorrect, which resulted in the requested transfer
    failing.
    
    When this happened, the MQ	 Explorer and the MFT transfer
    capture log both incorrectly displayed the destination path for
    the transfer, with the source path being appended to the
    destination path.
    
    
    For example:
      Source file was located at:
        N:/home/ibmsys/MQFTE/SourceDIR/*.pgp
    
      Destination path to transfer the file to was specified as:
        D:\MQFTE\DestinationDIR
    
    In MQ Explorer and the capture log ("progress" action), the
    destination path was incorrect shown as:
    
      D:/MQFTE/DestinationDIR/N:/home/ibmsys/MQFTE/SourceDIR/*.pgp
    
    The capture log XML output snippet was:
    
    <item mode="binary">
      <source disposition="leave" type="file">
        <file size="0">N:/home/ibmsys/MQFTE/SourceDIR/*.pgp</file>
      </source>
      <destination type="file">
        <file
    size="-1">D:/MQFTE/DestinationDIR/N:/home/ibmsys/MQFTE/SourceDIR
    /*.pgp</file>
      </destination>
      <status resultCode="1">
        <supplement>BFGBR0088E: No credential mapping has been found
    for user 'IBMUSER'. </supplement>
      </status>
    </item>
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using IBM MQ MFT Protocol Bridge Agent.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an IBM MQ MFT Protocol Bridge Agent (PBA) is used as the
    source agent in a transfer, and the supplied user credentials
    are incorrect, a requested transfer will fail, which is
    expected.
    However when this occurred, the MQ Explorer and MFT capture log
    displayed an incorrect destination path for the transfer.
    
    In the destination path displayed, the source path is appended
    to the destination path.
    
    For example:
    
    Source file specified:
      "someserver.com:/home/user/MQFTE/SourceDIR/*.pgp"
    
    Destination path specified:
      "/home/user/DestinationDIR"
    
    In the MQ Explorer and in the capture log ("progress" action),
    the destination path would be incorrectly displayed as:
    
    
    /home/user/DestinationDIR/someserver.com:/home/user/MQFTE/Source
    DIR/*.pgp
    
    Similarly, when SFTP server connection was refused , as before,
    the destination path was incorrectly formed and in the mean time
    if the ConnectException was resolved, then the transfer
    progressed and delivered the file to invalid destination.
    

Problem conclusion

  • IBM MQ MFT Protocol Bridge Agent has been updated such that when
    
    1. A BridgeCredential exception is thrown while resolving the
    transfer file names (such as in the case where the user
    credentials to connect to the remote file server are incorrect),
    the destination path will contain only the destination transfer
    name in the path.
    
    For example:
    Source file specified:
      "someserver.com:/home/user/MQFTE/SourceDIR/*.pgp"
    
    Destination path specified:
      "/home/user/DestinationDIR"
    
    If there was a BridgeCredential exception and subsequent failed
    transfer, then the MQ Explorer and capture log would show the
    destination path as:
      /home/user/DestinationDIR/
    
    2. A java.net.ConnectException or
    java.net.NoRouteToHostException is thrown while resolving the
    PBA source transfer file names,
       the transfer will fail and a new message BFGRP0038I will be
    shown on MQExplorer, which describes the cause of failure.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.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

    IT33387

  • Reported component name

    IBM MQ MFT V9.1

  • Reported component ID

    5724H7272

  • Reported release

    915

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-30

  • Closed date

    2021-01-29

  • Last modified date

    2021-01-29

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

  • Fixed component ID

    5724H7272

Applicable component levels

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

Document Information

Modified date:
30 January 2021