Sequence Elapsed Times

kishorenvkb · Post by **kishorenvkb** » Wed Jun 23, 2010 1:46 pm

Hello Everyone,

We have created an after job sub routine, which would get the details like runtimes, record count, cpu... into a file, which will be later loaded into a Teradata table for analysis. This routine is called in all jobs in "After Job Subroutine".

The question is, how can I capture the sequence run times?

Thanks for the help in advance

Kishore

kduke · Post by **kduke** » Wed Jun 23, 2010 2:53 pm

You can do the same for sequences. What is the problem?

ray.wurlod · Post by **ray.wurlod** » Wed Jun 23, 2010 5:33 pm

Sequences don't have after-job subroutines. But you could make the final activity in the sequence a Routine activity that does the same thing.

kishorenvkb · Post by **kishorenvkb** » Thu Jun 24, 2010 1:06 pm

Exactly... there is no after-job subroutine's within the Sequence. Ray, adding the Rotuine Activity within the sequence cannot help me to capture the EndTimeStamp of the sequence as technically the sequence is not complete until after the Routine Activity is completed. Isn't it?

Thanks

chulett · Post by **chulett** » Thu Jun 24, 2010 1:30 pm

You can certainly consider them to be equivalent given the fact that the Routine Activity will be the last thing that the Sequence runs.

kishorenvkb · Post by **kishorenvkb** » Thu Jun 24, 2010 2:28 pm

Okay. I haven't done this before. Can we write something outside of the Datastage (or within a datastage) to go and collect the start and end time for the latest run of every sequence within the project? Can someone share a sample with me?

Thanks in advance.

ray.wurlod · Post by **ray.wurlod** » Thu Jun 24, 2010 5:07 pm

kishorenvkb wrote:Ray, adding the Rotuine Activity within the sequence cannot help me to capture the EndTimeStamp of the sequence as technically the sequence is not complete until after the Routine Activity is completed. Isn't it?

The same argument that applies to an after-job subroutine, isn't it?

The times to the nearest whole second are likely to be identical anyway.

You can always run a completely separate routine/sequence to retrieve this information once the sequence under investigation has completed successfully.

kishorenvkb · Post by **kishorenvkb** » Fri Jun 25, 2010 6:51 am

I cannot see anything that Ray wrote as I am not a member. Hopefully the members got some benefit out of this conversation.

Thanks anyways!

chulett · Post by **chulett** » Fri Jun 25, 2010 7:00 am

Yes, outside or inside DataStage is perfectly feasible. Check out the "dsjob -jobinfo" option from the command line or the DSGet* API function equivalent.

kishorenvkb · Post by **kishorenvkb** » Fri Jun 25, 2010 8:15 am

Thanks Chulett and Ray.

ray.wurlod · Post by **ray.wurlod** » Fri Jun 25, 2010 4:21 pm

kishorenvkb wrote:I cannot see anything that Ray wrote as I am not a member. Hopefully the members got some benefit out of this conversation.

Thanks anyways!

Your problem is easily remedied.