How to capture job start time, end time, name etc
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 81
- Joined: Thu Nov 30, 2006 7:46 am
- Location: india
How to capture job start time, end time, name etc
How to save this jobname, endtime..etc in file?
MALLI
-
- Participant
- Posts: 81
- Joined: Thu Nov 30, 2006 7:46 am
- Location: india
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
"You can never have too many knives" -- Logan Nine Fingers
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.
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.
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.
$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.