IT32935: Managed File Transfer agent restart changes the time zone of scheduled transfer time.

APAR status

• Closed as program error.

Error description

• When creating a transfer based off a previously created xml
  using the -td (transfer definition file) and -tb (time base)
  parameters, where -tb is set to "UTC", the following time
  schedule  format is created:
  
  <submit timebase="UTC"
  timezone="America/New_York">YYYY-MM-DDTXX:XX+0000</submit>.
  
  This is correct for a UTC time base because it is +0000.
  
  When it is actually scheduled on the agent the time is correct.
  
  If the agent stops and starts again, the scheduled transfer
  changes to:
  <submit timebase="UTC"
  timezone="America/New_York">YYYY-MM-DDTXX:XX-0400</submit>
  
  The timezone information is incorrect, as the time base was
  originally set to be UTC
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This affects users of IBM MQ Managed File Transfer who have
  agents that process scheduled transfers, where the scheduled
  transfers are created with a time base of UTC.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a scheduled transfer is created, the agent stores the
  details of that transfer in a message on the
  SYSTEM.FTE.EVENT.<agent name> queue. If the agent is restarted
  while the scheduled transfer is still active, then the agent
  will use the information in the message to rebuild the scheduled
  transfer.
  
  When the agent rebuilt a scheduled transfer after it was
  restarted, the timezone information in the message on the
  SYSTEM.FTE.EVENT.<agent name> queue was ignored - the scheduled
  transfer was recreated using the local timezone of the agent. As
  a result, if the scheduled transfer was originally created with
  a time base of UTC, it would run at an unexpected time.
  

Problem conclusion

• To resolve this issue, agents will now read the timezone
  information contained in the message on the
  SYSTEM.FTE.EVENT.<agent name> queue when rebuilding scheduled
  transfers following a restart. As a result, scheduled transfers
  will continue to run at the expected time after an agent is
  restarted.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.7
  v9.2 LTS   9.2.0.1
  
  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