Report on jobs currently running in DS server

kcbland · Post by **kcbland** » Wed Jul 26, 2006 6:47 pm

I forgot to mention, but not to rub things in, but when I architect ETL solutions I push for an externalized audit repository of tables. I use custom job control that pushes process metadata into those audit tables so that jobs status, start time, end time, comments, parameter values, link values, and other asundry items are all available realtime.

It makes it easy to hang a dashboard off the ETL process metadata so that anyone can see what's going on without having DS clients. It makes an OPs console system much easier to put together, as well keep permanent process metadata history.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 26, 2006 11:15 pm

anton wrote:
chulett wrote:Actually, it is what you were asking for. Specifically, the automation part he mentions. ...
sorry, guys, i am not convinced.

and i am not willing to buy into something that has no proven its value to me.

thanks for trying.

That's OK, it's a free country, or so they tell us.

DSD.RUN is only for server jobs and job sequences. Parallel jobs run osh in the conductor and section leader processes, so there's no convenient way to identify distinct parallel jobs from a ps -ef listing.

kduke · Post by **kduke** » Thu Jul 27, 2006 6:50 am

Good point. In the osh is there anything that identifies the job like link name?

If so then I would try get list jobs and links with a SQL statement into sequential file like:

project,job,link

I would grep for the link name then only run dsjob on the limited list. dsjob on every job in every project is a waste of time.

ray.wurlod · Post by **ray.wurlod** » Thu Jul 27, 2006 7:08 am

kduke wrote:Good point. In the osh is there anything that identifies the job like link name?

No.