IBM Support

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

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 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"
    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"
    The timezone information is incorrect, as the time base was
    originally set to be UTC

Local fix

Problem summary

  • ****************************************************************
    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:
    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
    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
    The fix is targeted for delivery in the following PTFs:
    Version    Maintenance Level
    v9.1 LTS
    v9.2 LTS
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    IBM MQ MFT V9.1

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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


Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 August 2020