IT34168: Managed transfers are incorrectly marked as "Successful" rather than "Partially Successful"

APAR status

• Closed as program error.

Error description

• In an IBM MQ Managed File Transfer topology, a standard agent is
  acting as the source agent for managed transfers, and a protocol
  bridge agent is the destination agent.
  
   The managed transfer requests processed by the agents include
  multiple transfer item. Occasionally, a managed transfer is
  processed where:
  
  -At least one of the items is transferred successfully, and when
  the protocol bridge agent tries to re-read the file to confirm
  that it has been written successfully, the file is no longer on
  the file server. This causes the transfer item to be marked as
  "Successful" with the supplementary information
  
  BFGTR0077I: The destination agent was unable to determine the
  size of the file <file name> that it had written.
  
  - And at least one of the transfer items fails.
  
  In this situation, the managed transfer should have been marked
  as "Partially Successful". However, it is incorrectly marked as
  "Successful".
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of MQ Managed File Transfer, who have
  protocol bridge agents acting as the destination agent for
  managed transfers that contain multiple transfer items.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Every transfer item in a managed transfer has two pieces of
  audit information associated with them:
  
  - The local audit information is generated by the source agent.
  - The destination agent generates remote audit information.
  
  At the end of a managed transfer, the source agent looks at the
  audit information for each transfer item to determine the
  overall state of the managed transfer.
  
  - If the local and remote audit information of all of the
  transfer items indicates that the items were processed
  successfully, then the managed transfer is marked as
  "Successful".
  - If the local and remote audit information indicates that at
  least one of the transfer items was processed successfully, and
  at least one of the transfer items failed, then the managed
  transfer is marked as "Partially successful".
  - If the local and remote audit information for all of the
  transfer items indicates that all of the items failed to be
  transferred, then the managed transfer is marked as "Failed".
  
  Now, when a protocol bridge agent is acting as the destination
  agent for a managed transfer, it will write a destination file
  to the specified location, and then get the size of the file to
  include in the remote audit information. As there is no locking
  when a protocol bridge agent writes a file to a file server,
  this means that it is possible for an external process to move
  the file in between the destination agent writing it and
  checking its size. In this situation, the destination agent will
  generate some remote audit information for the transfer item
  indicating that the destination file was written successfully,
  along with the supplementary information:
  
  BFGTR0077I: The destination agent was unable to determine the
  size of the file '<destination filename>' that it had written
  
  
  Protocol bridge agents would use some state information
  associated with the current transfer frame to determine if the
  condition mentioned above had occurred. This meant that:
  
  - If a protocol bridge agent was acting as the destination agent
  for a managed transfer containing multiple transfer items.
  - And the agent was unable to determine the size of at least one
  of the transfer items that it had written while processing the
  current transfer frame.
  
  then the agent would generate "Success" remote audit information
  for all of the transfer items in the frame, regardless of
  whether the transfer items were successfully transferred or not.
  As a result, the source agent would mark the managed transfer as
  "Successful".
  

Problem conclusion

• To resolve this issue, destination agents now use state
  information associated with individual transfer items in order
  to determine whether to generate "Success" or "Failed" remote
  audit information for that item. This means that if a protocol
  bridge agent is acting as the destination agent for a managed
  transfer containing multiple transfer items, then:
  
  - The agent will generate "Success" remote audit information for
  each transfer item that is successfully transferred.
  - The agent will also generate "Success" remote audit
  information for those transfer items where it is unable to
  determine the file size.
  - For all other transfer items, the agent will generate "Failed"
  remote audit information.
  
  As a result of these changes, managed transfers containing
  multiple transfer items, where the destination agent is a
  protocol bridge agent, will be marked as:
  
  - "Successful" if all of the transfer items are successfully
  transferred to the file server.
  - "Partially Successful", if at least one of the transfer items
  failed, and at least one of the transfer items was either
  successful or the protocol bridge agent could not determine the
  size of the file it had written.
  - "Failed" if none of the transfer items were transferred
  successfully.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.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 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