IBM Support

PH20874: MAINFRAME (ZOS) AGENT IN DIFFERENT TIMEZONE THAN SERVER INCORRECTLY REPORTS LASTMODIFIED TIMESTAMP OF RESOURCES

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

  • Consider the following situation. If you install a ZOS agent in
    Japan which uses JST and then create a ZOS version on a server
    located in New York which uses EST, then the server will
    incorrectly record the last modified timestamp of the resources
    in the the version's package manifest. The server will interpret
    the timestamp in the locale time of the server. You will note in
    the component version, that the timestamp on artifacts are
    incorrect.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Consider the following situation. If you install a ZOS agent *
    * in                                                           *
    * Japan which uses JST and then create a ZOS version on a      *
    * server                                                       *
    * located in New York which uses EST, then the server will     *
    * incorrectly record the last modified timestamp of the        *
    * resources                                                    *
    * in the the version's package manifest. The server will       *
    * interpret                                                    *
    * the timestamp in the locale time of the server. You will     *
    * note in                                                      *
    * the component version, that the timestamp on artifacts are   *
    * incorrect.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.1.1.0                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.1.1.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH20874

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    627

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-01-09

  • Closed date

    2020-10-15

  • Last modified date

    2020-10-15

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"627"}]

Document Information

Modified date:
16 October 2020