IC81171: WMQFTE C:D BRIDGE TRANSFER PERFORMED OVER MIDNIGHT KEEPS STAYING IN COMPLETION STATE "IN PROGRESS" UNTIL SOURCE AGENT RESTARTS.

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.2

APAR status

• Closed as program error.

Error description

• Customer experiences problems with managed transfers using FTE
  V7.0.4 along with Connect:Direct Bridge
  
  Most of the transfers work as expected, but 1 or 2 times per
  day, a transfer does not return and stays in Completion State
  "In Progress" in MQ FTE.
  
  In the Connect:Direct log, these transfers are successful, and
  the partner receives the files successfully, but they are not
  removed from the source directory.
  
  The transfer reports "completed" - NOT before the customer
  restarts the source agent (which also removes the file from the
  source directory).
  
  Customer reports:
  The transfer which did not end correctly was started at 0:10.
  As before, Connect.Direct transferred the file correctly to
  the partner's z/OS system, but the FTE transfer did not
  return. At 9:10 am customer restarted the source agent and the
  Status for this transfer changed from "In Progress" to
  "Completed". The source file was also deleted at this point.
  
  The problem is reproducable within the first hour of the day
  (CET).
  

Local fix

• L3 could find that this problem matches a defect development
  found and fixed after the 7.0.4 release.
  
  The problem occurs when a transfer takes place over the midnight
  boundary - and possibly also the midday boundary. It's due to
  the agent erroneously using a 12-hour time format instead of a
  24-hour time format.
  

Problem summary

• When intepreting the start time of a transfer processed by
  Connect:Direct, the agent was incorrectly expecting the time to
  be in a 12 hour time format.  This could cause delays in
  reporting start and completion of transfers, especially those
  which start between 00:00 and 01:00.
  
  Transfers would still complete, but reporting would be delayed
  by up to 12 hours.
  
  USERS AFFECTED:
  Users of the Connect:Direct bridge
  
  PLATFORMS AFFECTED:
  All
  

Problem conclusion

• The code has been altered to ensure that the code inteprets the
  Connect:Direct timestamp correctly as a 24 hour value. This
  removes the possible reporting delay.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 7.0.4.2.
  

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

  WMQ FILE TRANSF

• Fixed component ID

  5724R1000

Applicable component levels

• R704 PSY

     UP