how to get end timestamp in DSJOB

bobbysridhar · Post by **bobbysridhar** » Thu Apr 05, 2012 9:36 am

Hi,
I have to get Job end timestamp once the job completed successfully.
Is there anything in transformer stage we can do about it.

Thanks,
Sridhar

bobbysridhar · Post by **bobbysridhar** » Thu Apr 05, 2012 12:50 pm

Could somebody help me in this regard.
Either something we can do in transformer or after job subroutine

chulett · Post by **chulett** » Thu Apr 05, 2012 12:57 pm

The transformer would be 'too soon' as the job would still be running. Technically, the job is still running when it hits the 'After Job' section but you could get it there using the API - look at the documentation for DSGetJobInfo() and one of the InfoType values should get you the ending timestamp.

Or you could do it any way you like in a separate process that runs after the other job completes. It all depends on exactly what you need this timestamp for... I suspect it is related to your other question about partitioning by timestamp or renaming a file after job.

bobbysridhar · Post by **bobbysridhar** » Thu Apr 05, 2012 1:16 pm

It is not related to any of my previous posts. I have a target table(oracle) which keep track of all loaded accounts. In that I have a column for endtimestamp.

chulett · Post by **chulett** » Thu Apr 05, 2012 2:27 pm

Me, personally, I would never build anything like that into a job. I prefer a separate process that runs after all jobs have completed that queries them for things like their ending timestamp, links counts, etc and outputs all of that to a flat file. Then another process can simply pick up that file and load all of the 'audit records' (or whatever you want to call them) into the appropriate place.

If you went the separate path, then you could do this gathering of information in a Transformer routine since it would be checking other jobs. It would also be pretty straight-forward to do all of that in a UNIX script.

Multiple ways to skin this cat.

bobbysridhar · Post by **bobbysridhar** » Thu Apr 05, 2012 2:57 pm

Could you please let me know which process you implemented that runs after all jobs have completed.
Please let me know how to do it in UNIX also

ray.wurlod · Post by **ray.wurlod** » Thu Apr 05, 2012 4:38 pm

In UNIX use dsjob -jobinfo command. This reports about five lines of information including the start and end timestamps. You can parse these with UNIX commands such as grep and cut.

qt_ky · Post by **qt_ky** » Thu Apr 05, 2012 7:28 pm

I agree with Craig's approach. The last thing I would want is for the external job tracking table to have some problem, like that database goes down or the ID expires, then it brings your production ETL to a halt.

FYI: DataStage 8.7 has a web-based operations console (read-only).