How to find the job run times?

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
vij
Participant
Posts: 131
Joined: Fri Nov 17, 2006 12:43 am

How to find the job run times?

Post by vij »

Hi,

I would like to find out the list of datastage jobs that run before 6 months from the current date. I can hardcode the date/time value..

is there a way I can use some where clause in the below SQL in the adminstrator tool to get that information?

Eg., SELECT COUNT(*) FROM DS_JOBS

please let me know.

Thanks in advance,
Vij
vij
Participant
Posts: 131
Joined: Fri Nov 17, 2006 12:43 am

Post by vij »

Is it possible to get this from dsjob command? and also I am not sure if I am in the correct path in unix to execute the dsjob command.

I tried the dsjob -logsum command, but I got the below error message:

ksh: dsjob: not found
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

So... you're trying to identify jobs that have not run in the last six months? :?

That information won't be in DS_JOBS but rather in each individual job's RT_STATUSnnn hashed file, I believe. And it is not something that is openly documented but certain people here probably know exactly where that would be.
-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 »

Not RT_CONFIGnnn, but either of RT_LOGnnn or RT_STATUSnnn.

Depends how you want to go about it. You can use the DataStage API (from DataStage or from an external C program), or you can use shell script using dsjob commands.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not sure where the RT_CONFIGnnn mention came from, but good point about the two sources - RT_STATUSnnn for the most recent information (which seems to be all that is needed here) and RT_LOGnnn for runs as far back as you have logs.
-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 »

chulett wrote:Not sure where the RT_CONFIGnnn mention came from.
(off line)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

Download EtlStats and get row counts for all jobs in a project. There is a job to load ETL_JOB table. You can do an other join fromETL_JOB to ETL_JOB_HIST to get your list. If you want a more complete list there is a job to get row counts from log files. Run it too. This will get row counts on job which have been compiled but the log has not been cleared recently.

Do a search on EtlStats on what it is and how to install it.
Mamu Kim
Post Reply