IBM Support

IT20852: The source file for a managed transfer is deleted, even though the managed transfer is marked as failed.

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

  • When using WebSphere MQ File Transfer Edition, or the MQ Managed
    File Transfer component, a managed transfer is submitted to move
    a single file from the source agent system to the destination
    agent system. The managed transfer has the source disposition
    option:
    
    -sd delete
    
    specified, and one or both of the options:
    
    -postsrc
    -postdest
    
    to invoke programs at the end of the managed transfer.
    
    When the managed transfer finishes, it is marked as "FAILED".
    However, the source file for the managed transfer is deleted.
    
    Additional Symptom(s) Search Keyword(s):
    postDestinationCall
    postSourceCall
    

Local fix

  • Resolve the failure of the post-destination call.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - WebSphere MQ File Transfer Edition
    - The WebSphere MQ V7.5 Managed File Transfer component.
    - The IBM MQ V8.0 Managed File Transfer component.
    - The IBM MQ V9.0 Managed File Transfer component.
    
    who have managed transfer requests containing one or more
    transfer items, where
    
    - The managed transfer request specifies either a
    post-destination or post-source call (using the -postdest and
    -postsrc options)
    - The source disposition for one or more of the transfer items
    needs to be set to "delete" (using the -sd option)
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a managed transfer request is being processed, the
    following steps takes place:
    
    1. The source agent for the managed transfer receives the
    managed transfer request.
    2. The source agent contacts the appropriate destination agent,
    to check that it is OK to participate in the managed transfer.
    3. If the destination agent is able to proceed, then the source
    agent starts sending all of the data for the transfer items to
    the destination agent.
    4. The destination agent receives the data, and starts writing
    the destination file for each transfer item.
    5. After all of the data has been processed, the destination
    agent sends back a message to the source agent, indicating which
    transfer items it processed successfully and which ones it
    failed to process.
    6. The source agent receives the response from the destination
    agent.
    7. The source agent processes the source disposition for each
    transfer item that was successful.
    8. Finally, the source agent checks how many transfer items were
    processed successfully, to determine the overall state of the
    managed transfer. The managed transfer will be marked as:
    
    - "Successful", if all of the transfer items were processed
    successfully.
    - "Partially successful", if one or more of the transfer items
    were processed successfully and one or more of the transfer
    items failed.
    - "Failed", if all of the transfer items could not be
    transferred.
    
    
    When a post-destination call is specified on the managed
    transfer request, then the destination agent runs the required
    program just before step 5 if at least one transfer item was
    successfully processed. The response message that the
    destination agent sends back to the source agent will include
    information about whether the post-destination call worked or
    failed, as well as details of the transfer items that worked and
    failed.
    
    When the source agent received this response, it would perform
    step 7 and process the source disposition for those transfer
    items that were successful. After doing that, the source agent
    then checked if the post-destination call performed by the
    destination agent worked or not. If the post-destination call
    failed, then the source agent immediately marked the managed
    transfer as "Failed".
    
    If the post-destination call worked, then the source agent would
    proceed to step 8 and run any post-source programs that were
    specified in the managed transfer request.  If the post-source
    call worked, then the transfer would be marked as:
    
    - "Successful" if all of the transfer items were successfully
    processed.
    - "Partially Successful" if one or more of the transfer items
    were successfully transferred, and one or more of the transfer
    items failed.
    
    However, if the post-source call failed, then the managed
    transfer would be marked as "Failed".
    
    This meant that if a post-destination or post-source call
    failed, then the managed transfer would be marked as "Failed"
    even though:
    
    - One or more of the transfer items had been successfully
    transferred.
    - And the source disposition for those items had been processed.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition product, and the MQ
    Managed File Transfer component, have been updated so that:
    
    - If a managed transfer includes a post-destination or
    post-source call.
    - And either the post-destination or post-source call fails
    
    then the managed transfer will be marked as "Partially
    successful", and the the source disposition for those transfer
    items that were successfully processed will be honored.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.7
    v7.5       7.5.0.9
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    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

    IT20852

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-02

  • Closed date

    2017-06-29

  • Last modified date

    2017-06-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

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

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

Document Information

Modified date:
29 June 2017