how to get correct value of job end time using dsjob comamnd

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
chvenkat.v
Participant
Posts: 94
Joined: Fri Dec 14, 2007 3:22 am

how to get correct value of job end time using dsjob comamnd

Post by chvenkat.v »

Hi Team,

I have used the dsjob command to get job end time.
But I am getting wrong data for the same.

I have run the dsjob command on 2011-02-04

STATUS REPORT FOR JOB: Job name
Generated: 2011-02-04 06:31:12
Job start time=2009-04-02 18:33:10
Job end time=2011-02-04 06:31:12
Job elapsed time=00:00:00
Job status=99 (Not running)

SO could you please help on this.

Thanks
venkat.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Odd. Should it have been sometime in 2009? What does the job show for those values in the Director? If you rerun the dsjob command, do you get a new (i.e. current) value for the end time? Does it work properly for other jobs? :?

I have absolutely no idea what might be going on (just trying to gather information) and suspect you'll need to either Clear the Status file, export/import and/or rerun the job to fix things, that or contact your official support provider for guidance if the issue continues.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Looks like it's reporting the date/time that dsjob was run. This is a bug, if reproducible, and should be reported to your official support provider.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Vinothbaskaran
Participant
Posts: 22
Joined: Mon Aug 25, 2008 4:01 am

Post by Vinothbaskaran »

Is it a multiple instance job by any chance?? I have seen this happening a few times only to find that it was multiple instance job.
Vinothbaskaran
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

99 means job is compiled. There is no start or end time on a just compiled job.
Mamu Kim
Vinothbaskaran
Participant
Posts: 22
Joined: Mon Aug 25, 2008 4:01 am

Post by Vinothbaskaran »

kduke wrote:99 means job is compiled. There is no start or end time on a just compiled job. ...
Exactly.. @Venkat: You are trying to get the timings of a multiple instance. So the start time is the when the job is last compiled and end time probably one of the instance which has finished recently.
Vinothbaskaran
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

OK, specifically - you are querying the 'base' Multi-Instance job (the one that always shows Compiled) rather than one of the actual instances. Use JobName.InvocationID in the dsjob command rather than just JobName.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply