IBM Support

IO18076: A timestamp value that is stored in GMT is not returned in GMT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There is ambiguity in the CM backend when storing user
    timestamp properties (as opposed to system properties which are
    always in GMT). Therefore when II4C loads a value it implicitly
    picks up the local JVM timezone due to the usage of
    java.sql.Date.
    
    II4C gets system attributes out as a timestamp from the cursor
    that we get from library server. Since library server generates
    this timestamps as GMT, II4C makes sure these timestamps stay
    in GMT.
    
    With regards to user defined timestamps we get those out as
    strings and perform no manipulation of these timestamps values.
    
    So, the way they go into library server is the same way they
    come out.
    

Local fix

  • Adding hours to timestamps where Date fields have been mapped
    to CM 8 time stamps in order to off set  this discrepancy.
    
    Potential fix by adding a feature in CM to allow a users to
    retrieve a timestamp in GMT from Content Manager when an option
    is specified in the cmbicmsrvs.ini or connect string.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * 999                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A timestamp value that is stored in GMT is not returned in   *
    * GMT.                                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * A timestamp value that is stored in GMT is not returned in   *
    * GMT.                                                         *
    ****************************************************************
    

Problem conclusion

  • Allow user-defined timestamps to be retrieved in GMT by
    specifying an option. User-defined timestamps must be stored in
    GMT to use this option.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IO18076

  • Reported component name

    II4C CM CONNECT

  • Reported component ID

    5724B43A1

  • Reported release

    843

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-05

  • Closed date

    2014-08-01

  • Last modified date

    2014-08-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • 999
    

Fix information

  • Fixed component name

    II4C CM CONNECT

  • Fixed component ID

    5724B43A1

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCTVDL","label":"Db2 Information Integrator for Content"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"843","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 August 2014