IBM Support

IT15639: After APAR IT04813 is installed MFT transfers cannot be canceled when the remote file se

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After APAR IT04813, if a WebSphere MQ Managed File Transfer
    protocol bridge agent, acting as the source agent, could not
    connect to a remote file server when parsing a new managed
    transfer request, the parsing of the command message would be
    aborted.  The managed transfer command message would be rolled
    back to the agent's SYSTEM.FTE.STATE queue and retried at a
    later time.
    
    If this situation occurred the managed transfer was not
    registered within the agent.  As a result, it could not be
    cancelled using the fteCancelTransfer command.  This can lead to
    a managed transfer request that cannot be cancelled but cannot
    proceed if the remote file server continues to be unaccessible.
    

Local fix

  • Option 1:
    Correct the issue with the remote file server such that the
    protocol bridge agent is able to establish a connection.
    
    Option 2:
    Stop the agent and issue the fteCleanAgent command with the -trs
    flag to clear any currently running managed transfers or delete
    new managed transfer requests.  Be aware that the fteCleanAgent
    command must be run on agent pairs (both source and destination)
    to avoid creating an inconsistent state for managed transfers
    between communicating agents.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
      - WebSphere MQ File Transfer Edition V7.0.4.5
      - WebSphere MQ Managed File Transfer V7.5.0.5 and later
      - IBM MQ Managed File Transfer V8.0.0.2 and later
      - IBM MQ Managed File Transfer V9
    
    who have the fix for APAR IT04813:
    
    http://www-01.ibm.com/support/docview.wss?uid=swg1IT04813
    
    and have protocol bridge agents acting as the source agent for a
    transfer where the agent is unable to connect to the remote
    FTP/FTPS/SFTP file server while parsing a managed transfer
    request XML command message.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a WebSphere MQ File Transfer Edition or Managed File
    Transfer protocol bridge agent, acting as a source agent for a
    transfer, attempts to parse the managed transfer request XML
    command message, it will attempt to connect to the remote file
    server hosting the specified source file(s).  This is to obtain
    information (such as the size) about the file, or files, to
    transfer and also to expand any wildcard characters specified as
    part of a source transfer item specification.  It is at the
    point of parsing the transfer request command message that the
    list of all files for the transfer must be established such that
    the listing can be registered within the agent's "state store"
    for the transfer.  As such any wildcards must be expanded at
    this time.
    
    An example of a wildcard transfer specification for source item
    is as follows:
    
      <source disposition="leave" recursive="false">
        <file>MyFTPServer:/home/tom/file*.txt</file>
      </source>
    
    The change made under APAR IT04813 causes the parsing of the
    managed transfer request command message to be aborted when a
    connection could not be established to the remote file server.
     When this occurred, the managed transfer request command
    message is rolled back to the agent's SYSTEM.FTE.STATE&#09;queue
    and parsing retried at a later point.  The processing was
    repeated until the protocol bridge agent could successfully
    connect to the remote file server.
    
    During this processing, the managed transfer request was not
    registered within the agent's state store because the full
    details were unknown, as the transfer request message was not
    parsed in full.  As such, this transfer request could not be
    cancelled using the fteCancelTransfer command.
    
    APAR IT04813 should have aborted the parsing when the request
    included a source item specification that contained a wildcard.
     However it also aborted the parsing of the transfer request
    command message when the source item specifications did not
    contain wildcard characters.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition and Managed File Transfer
    agent code has been update such that if a file system (including
    those hosted on remote file servers) are not accessible when an
    agent is parsing a managed transfer request XML command message,
    the parsing is only aborted if the message includes a source
    item specification that contains a wildcard character.
    
    When only non-wildcard characters are specified in the source
    item specifications, the agent will register the transfer within
    its state store using the values included within the transfer
    request message itself, without performing further checks on the
    file at that point in the transfer processing.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.6
    v7.5       7.5.0.8
    v8.0       8.0.0.6
    v9.0 CD    9.0.1
    v9.0 LTS   9.0.0.1
    
    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

    IT15639

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-14

  • Closed date

    2016-08-23

  • Last modified date

    2017-06-20

  • 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

  • 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:
20 June 2017