Getting a list of job name and start time

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
tkbharani
Premium Member
Premium Member
Posts: 71
Joined: Wed Dec 27, 2006 8:12 am
Location: Sydney

Getting a list of job name and start time

Post by tkbharani »

I am working on to get a list of DataStage Job/Sequence name whose start time is >= April 2013. Repository has jobs/sequence which are running daily and some which are decommissioned(Not running, but exist). I am in process of identifying which have run for past 2 months.

What we did-
1. Using "dsjob -ljobs" command get list of jobs
2. Loop through all listed jobs again to get multiple instance job names with instances using -linvocations
3. Loop through each job to get information on start time etc using "dsjob -jobinfo"
4. Write script to filter only Job name, start time

Is there a better way of getting this information using LOGGING_CATEGORY1466CB5F or DS_JOBS of UV. Please advice
Thanks, BK
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I'm not sure of how you would define 'better', since you've got something completed which is running.

You could write a small BASIC routine or function using defined Routine calls which only needs to loop through all the jobs once and would be more efficient, but it would return the same values as what you've alread completed.
tkbharani
Premium Member
Premium Member
Posts: 71
Joined: Wed Dec 27, 2006 8:12 am
Location: Sydney

Post by tkbharani »

I thought, if xmeta is storing start time of each jobs, then it is matter of writing select SQL pointing to xmeta LOGGING table. Is there a way to fetch same information(Jobname, StartTime) from xmeta tables ?
Thanks, BK
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

The DataStage API calls are documented, xmeta is not. While there is a way to do it, it might not work in the future and I'd stick with documented methods.
Post Reply