How to deal with Job Log ?

xinhuang66 · Post by **xinhuang66** » Thu Jan 11, 2007 8:49 pm

How can I send out all job logs by email after job finished/abort...

thanks

I_Server_Whale · Post by **I_Server_Whale** » Thu Jan 11, 2007 8:56 pm

You can use the 'Notification_Activity' in a job sequence with the option 'Include Job Status in Email' checked.

narasimha · Post by **narasimha** » Thu Jan 11, 2007 8:58 pm

Use the Notification activity in the Job Sequence.
Check the "Include job status in email", you should get what you want.

narasimha · Post by **narasimha** » Thu Jan 11, 2007 9:02 pm

Dooh.. late...

xinhuang66,
Moving forward, please post in appropriate forum.

ray.wurlod · Post by **ray.wurlod** » Thu Jan 11, 2007 9:20 pm

General probably IS the appropriate forum, since the answer will be the same irrespective of job type.

If you want the entire log, use an after-job subroutine. Perhaps use ExecSH to invoke dsjob, or "roll your own" using the DataStage API.

Better, use a downstream activity in the job sequence, because the "job finished" event has not yet been logged when the after-job subroutine is executing.

narasimha · Post by **narasimha** » Thu Jan 11, 2007 9:31 pm

ray.wurlod wrote:General probably IS the appropriate forum, since the answer will be the same irrespective of job type.

Gave it a thought, don't know why I still posted it

Guess I had a long day..

xinhuang66 · Post by **xinhuang66** » Thu Jan 11, 2007 11:32 pm

narasimha wrote:Use the Notification activity in the Job Sequence.
Check the "Include job status in email", you should get what you want.

Job status information is not enough..

what I want to get is the job log information for the finished job ?

Is developing a job routine the only way to get it ??

thanks

narasimha · Post by **narasimha** » Thu Jan 11, 2007 11:43 pm

xinhuang66 wrote: what I want to get is the job log information for the finished job ?

Is developing a job routine the only way to get it ??

Yes, as Ray already specified above.

ray.wurlod · Post by **ray.wurlod** » Fri Jan 12, 2007 2:08 am

You don't need to develop a routine, though it would be more flexible. ExecSH (or ExecSHSilent) is supplied with the product - all you have to supply is the command line for dsjob command to dump the log.

chulett · Post by **chulett** » Fri Jan 12, 2007 7:07 am

And to help with that, as with most commands, you can execute dsjob without any arguments to get the 'usage' statement. That and read the Server Job Developer's Guide pdf, down near the end there is a chapter on the Command Line Interface which rather thoroughly explains all of the various options - including the ones needed to farm job logs.

They even mention what 'DSGet*' function each one is equivalent to, so you could use that as a guide if you desired to approach this from a custom routine rather than a scripted standpoint.