DSXchange

Hi,

Has anyone come across an issue related to time differences between -logsum and -logdetail commands in a dsjob command line execution?

I ran a -logsum command and obtained the following:

Command: dsjob -server xyz -user xyz -password xyz -logsum ProjectName JobName

Result:

.
.
.
635 STARTED Thu Aug 12 04:46:35 2004
Starting Job LDWE72AI. (...)
.
.
.


Tha I ran a -logdetail command and obtained the following:

Command: dsjob -server xyz -user xyz -password xyz -logdetail ProjectName JobName 635

Result:

.
.
.
Event Id: 635
Time : Thu Aug 12 05:46:35 2004
Type : STARTED
User : xyz
Message :
Starting Job JobName.
.
.
.

Why the discrepancy of exactly 1 hour between the logsum and logdetail? They should be exactly the same... . And this happens in both development and production servers. Any hints?

Thanks & regards to you all...
Henrique

Time Zone? Now, as to the why...

Can you please look at the log in Director log view and tell us which timestamp is reported in the detail view?

Note the event number. Connect to TCL (Administrator client Command window, or telnet session into DataStage). Execute the following query where nnn is the job number (from DS_JOBS) and n is the event number.

Hi Ray,

I ran the command and the result was the expected.

The date came out as bla, bla, bla...Thu Aug 12 04:46:35 2004...bla, bla, bla...

Any ideas?

Thanks,
Henrique

This shows that the timestamp actually in the log (it's stored as a Char(19)) is the same as the one dsjob reports with -logsum.
Something is adding one hour when using -logdetail. It does kinda look like a daylight saving shift, but it does kinda look also like a bug.
Has anyone else reproduced this? Does the Director client do the same thing (that is, show different timestamps in summary and detail - double click the event to get the detail)?