CMOD9 System Log hitlist discrepancy between thick client and arsdoc query

[daniel.goetz]

Hi everyone, I don't know if anyone else has experienced, but when we query the OD System Log on CMOD 9.0.0.2 based on TIME_STAMP 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. 

When performing a query, for example between 10/17 10am - 10/17 2pm as '2013-10-17 10:08:31.601816' and '2013-10-17 14:08:31.601816', using these exact values in both arsdoc query and the thick client query, we get different results.


Command:
arsdoc query -v -goetzd -p $dir/mystash -h ARCHIVE -G "System Log" -i "where ODDAT_TIME_STAMP between  '2013-10-17 10:08:31.601816' and '2013-10-17 14:08:31.601816'"

Results:

Code: [Select]

2013-10-17 16:48:15.776265: ARS6108I Starting arsdoc.  Version:  9.0.0.2

2013-10-17 16:48:15.777625: ARS6165I arsdoc query -v -u goetzd -h ARCHIVE -G System Log -i where ODDAT_TIME_STAMP between  '2013-10-17 10:08:31.601816' and '2013-10-17 14:08:31.601816'

2013-10-17 16:48:15.778307: ARS6822I Attempting login for userid 'goetzd' on server 'ARCHIVE' ...

2013-10-17 16:48:15.784794: ARS6080I Login successful

2013-10-17 16:48:15.785305: ARS6836I Querying for application group 'System Log' on server 'ARCHIVE' ...

2013-10-17 16:48:15.788504: ARS6082I Query successful

2013-10-17 16:48:15.788854: ARS6063I Searching for documents in 'System Log' ...

2013-10-17 16:48:15.788950: ARS6117I Querying database with SQL string 'where ODDAT_TIME_STAMP between  '2013-10-17 10:08:31.601816' and '2013-10-17 14:08:31.601816''

2013-10-17 16:48:15.791047: ARS6084I Search successful
10/17/13 06:16:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 06:46:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 07:16:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 07:46:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 08:16:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 08:46:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 09:16:46,ARSSOCKD,4,201,Activities: Current(0),N,0,
10/17/13 09:46:46,ARSSOCKD,4,201,Activities: Current(0),N,0,

2013-10-17 16:48:15.792856: ARS6026I arsdoc completed.

Attached to this post is the screenshot of my results from the thick client.

The thick client results are fine, but the arsdoc query results are from four hours earlier, so those times are correct. 

Has anyone else experienced this?

Thank you,
Daniel Goetz

[Ed_Arnold]

Hello Daniel! 

This is just a guess:  In my dot-profile I export the local timezone with this statement:

export TZ=EST5EDT

Does that help?

Ed Arnold

[daniel.goetz]

Hi Ed,

Thank you for your suggestion.   We checked the TZ setting, and we're definitely running as TZ=EST5EDT.  This is both in my personal .profile (AIX) and system-wide in /etc/environment

I unset TZ, and the returned results were still four hours off, except it displayed the UTC time instead of the time filtered through TZ=EST5EDT.

We opened PMR 56311,7TD,000 almost three weeks ago on this issue, and unfortunately, IBM hasn't budged from their position.  L2 support and CMOD development continue to assert that, "ARSDOC is not the same as the thick client and that the system is working as designed."

We never had this issue before.  On our CMOD8416 installation, we use TIME_STAMP all the time for our arsdoc query -G "System Log" queries.

Thanks,
Daniel

[pankaj.puranik]

We have experienced it too.
When I do a query sitting in the US (EST time zone), i get different results when compared to my colleagues who work from India (IST time zone).
Both these queries were fired from the thich client.

[Jaydeep Mehta]

Hi  We are also facing that same issue on CMOD 9.5 .
Our DB time in EDT only and as we checked our application session/env timezone also in EDT as below but it is updating system table in GMT timezone.

So any know Fix on this  problem .

Thanks in advance..

Regards
JD