How to capture job start time, end time, name etc

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
mallikharjuna
Participant
Posts: 81
Joined: Thu Nov 30, 2006 7:46 am
Location: india

How to capture job start time, end time, name etc

Post by mallikharjuna »

How to save this jobname, endtime..etc in file?
MALLI
mallikharjuna
Participant
Posts: 81
Joined: Thu Nov 30, 2006 7:46 am
Location: india

Post by mallikharjuna »

Please let me know how to save this information in text file
MALLI
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

Use the DSODB database for those stats.
Last edited by PaulVL on Fri Aug 11, 2017 9:27 am, edited 1 time in total.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

:!:

Split this out from an old and previously hijacked discussion into one of its own. And from looking at previous topics started by the OP, they are on 11.x so updated the post accordingly.
-craig

"You can never have too many knives" -- Logan Nine Fingers
UCDI
Premium Member
Premium Member
Posts: 383
Joined: Mon Mar 21, 2016 2:00 pm

Post by UCDI »

a hands-on way is to open the job in director, print the current run to a file (set up a generic text file printer 'device'), and if you don't want all the juicy data in there, cut out the lines you need.

This file is just full of great info -- you can see how long each stage or sub-sequence ran, and you can see the job's parameters, and lots of other cool stuff for hands-on job profiling.
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

UCDI if the brute force way is acceptable...

$DSHOME/bin/dsjob -jobdetails <project> <job.invocation> > /path/joblog_<project>_<job>.log would be the way to script it, then grep/cut the timestamps from that.

Or ...

create a datastage job that runs against the DSODB database to extract your stats there. Much better use of the environment.

I would slap an application team that did a log scrape just for stats now that DSODB is there.
Post Reply