IBM Support

IC99851: PATH SEPARATOR CONVERSION PROBLEM WHEN USING IBM WEBSPHERE MQ MANAGED FILE TRANSFER V7.5 PROTOCOL BRIDGE AGENTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When transferring a file from a Windows file server using a
    WebSphere MQ Managed File Transfer protocol bridge agent, where
    the path to the source file is specified using backslashes (\),
    an issue can occur resulting in the protocol bridge agent being
    unable to separate the filename from the file path. The transfer
    is successful and the file data is transferred, however
    depending on the platform on which the protocol bridge agent is
    running, the destination agent either:
    
    1) creates the directory structure to the file on the
    destination system as it exists on the file server, if the
    protocol bridge agent was running on a Windows platform, or
    
    2) creates a file in the directory specified in the transfer
    request but the name of the file is the complete path to the
    file as it exists on the file server, if the protocol bridge
    agent was running on a Unix platform.
    
    Example:
    -----------
    Consider the following invocation of the fteCreateTransfer
    command that is used to transfer a file, using a protocol bridge
    agent, from the file server named MyFileServer to a normal
    WebSphere MQ Managed File Transfer agent running on a Unix
    system.
    
    fteCreateTransfer -sa PBAGENT -sm MFTQM -da AGENT -dm MFTQM -t
    text -de overwrite -dd /files/transfers/receive
    MyFileServer:\documents\myfile.txt
    
    The expected behaviour is that a file named "myfile.txt" is
    created on the destination system in the directory
    /files/transfers/receive. However this does not always happen.
    
    If the protocol bridge agent (PBAGENT) is running on a Windows
    platform, the transfer results in the directory structure from
    the file server being created at the destination, like so:
    
    /files/transfers/receive/documents/myfile.txt
    
    If the protocol bridge agent (PBAGENT) is running on a Unix
    platform, the transfer results in the file with name
    "\documents\myfile.txt" in the directory
    /files/transfers/receive/, like so:
    
    /files/transfers/receive\documents\myfile.txt
    

Local fix

  • Specify the path to the source file on the file server using
    forward-slashes (/).
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users with WebSphere MQ Managed File Transfer
    protocol bridge agents who transfer files from Windows file
    servers and who specify the destination for the transfer as a
    directory and use back-slashes (\) in the file path for source
    file.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When specifying a source file (that existed on a file server)
    for a transfer, and transferring it to a directory on the
    destination system, the protocol bridge agent was unable to
    split the filename information from the file path in the case
    where the path was specified using backslashes. As such, the
    complete file path as specified was interpreted as the filename
    to use at the destination system. Therefore, when building the
    file path that the WebSphere MQ Managed File Transfer
    destination agent should have used to write the file data, the
    destination directory for the transfer was concatenated with the
    whole file path to the source file rather than just the filename
    portion of it.
    
    Different behaviour then resulted depending on whether the
    protocol bridge agent was running on a Windows or Unix platform,
    as described in the Problem Description for this APAR.
    
    When the protocol bridge agent was running on a Windows
    platform, the backslashes in the file path were being converted
    to forward-slashes. That resulted in the directory structure for
    the source file on the file server being replicated on the
    destination system when the file data was written.
    
    However, when the protocol bridge agent was running on a Unix
    platform, the backslashes in the file path were not being
    converted to forward-slashes. That resulted in the backslashes,
    in the destination file path generated, being interpreted as
    part of the filename itself.
    
    Both of these behaviours are incorrect. The destination file
    should have the same name as the source file on the file server
    and be written to the destination directory specified in the
    managed transfer request message. Continuing the example from
    this APAR's Problem Description, the destination file should be
    named "myfile.txt" in the directory "/files/transfers/receive",
    like so:
    
    /files/transfers/receive/myfile.txt
    

Problem conclusion

  • The WebSphere MQ Managed File Transfer protocol bridge agent
    code has been updated so that the source filename can be
    extracted from the complete file path specified in the managed
    transfer request message when backslashes are used. This is then
    used, without the full source file path, when generating the
    destination file path for the destination agent and concatenated
    with the destination directory specified.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.4
    
    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

    IC99851

  • Reported component name

    WMQ FTE

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-05

  • Closed date

    2014-03-24

  • Last modified date

    2014-05-01

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCUHLE","label":"WMQ Managed File Transfer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 May 2014