Invocation ID question

HSBCdev · Post by **HSBCdev** » Fri Oct 01, 2004 3:22 am

I've got a multi-instance job which will be called by many different job sequences. Do I have to make sure that the invocation id used in each job in each sequence is unique or can DataStage handle two different sequences calling a job with the same invocation id?

What do people normally do for invocation id? Do you put the sequence name as part of it so that you know it will be unique?

Thanks for your help.

Mike · Post by **Mike** » Fri Oct 01, 2004 6:55 am

The invocation ID has to be unique for your multi-instance job to run concurrently for the different calling sequences.

Mike

sonia jacob · Post by **sonia jacob** » Fri Oct 01, 2004 11:52 am

I used something like the Routine given below to set invocation ids to job.

********************************************
Cnt = 1

Loop Start

If Jobname.Cnt is running then
Increment Cnt;
Continue Loop;
Else
Exit Loop;
End if

End loop

Run JobName.Cnt
********************************************

you could put your code together with the help of DSAttachJob, DSGetJobInfo, DSJS.RUNNING, DSDetachJob

leomauer · Post by **leomauer** » Fri Oct 01, 2004 12:34 pm

If you run it manually you will set Invocation ID. If you run it using dsjob then you can use PID ($$) for it.

vmcburney · Post by **vmcburney** » Sun Oct 03, 2004 5:35 pm

I try and use a descriptive invocation id so when I go to the Director to view the logs I know which one to look at. It I have multiple instances for a partitioned load the instance id describes each partitions, eg. 1to10000, 100001to20000, 200001to300000. If it is a generic job used by different sequence job the id describes which sequence job it came from, so your idea of using the sequence job name is a good one.

HSBCdev · Post by **HSBCdev** » Mon Oct 04, 2004 5:12 am

Thanks all for your advice