CMOD9.5 System Log timestamp discrepancy between thick client and SL table

[Jaydeep Mehta]

Hello ,

when we query the OD System Log and System Load  on CMOD 9.5 based on TIME_STAMP_DT using the new format, the time_stamp is giving us back the results as if we entered the values in GMT0 instead of EST5EDT.  The thick client is fine in this regard but when we trying to query with arsdoc with session timestamp EST5EDT we didn't get any result because in SL table it is in GMT format.


We have Checked the Our AIX Session ENV  and Database both set in EDT time zone .
But we not able to identify why system log and system load storing time_stamp_dt and load_date_dt column in GMT time zone .

Any one has any idea about this .??

Thanks in Advance

Regards
Jaydeep Mehta

[Jaydeep Mehta]

I found the solution for below issue From CMOD 9.0 onward  System Log and Sytem Load Using new TIME_STAMP_DT column
and updating value into GMT or UTC format only. TIME_STAMP is  showing -1 value .

From the upgrade guide:
http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21686051

Also, if this upgrade was done from an 8.5 version, have you updated with the new date/time fields?

As can be seen, the new field Date/Time (TZ) now has extended ability to store up to 6 digits of precision (microsecond) � which is now used by the Content Manager OnDemand System Log and System Load application groups in order to represent more granular timing of activity on the system. In order to use these new types for the System Log/Load facility, use the �u option to the arssyscr command to update the existing application group(s). Although it is recommended that customers use these new fields, it is not required to update these application groups immediately upon installing OnDemand V9.0 � the update of System Log/Load can happen at any time.


So we need to do arsdoc query on UCT format to get the result from SL or SA table .