Invacation ID

kaps · Post by **kaps** » Tue Oct 23, 2007 12:45 pm

We have a Job sequence which calls a Multi-Instance server job. We are calling this job 8 times by passing
different Invocation ID's at the same time. But two of those jobs does not get the Invocation_ID which is causing one job to fail.

I don't understand why it's not picking up the Invocation_Id's.

Is there any limitations on how many jobs we can kick off at the same time ?

Please advise.

roy · Post by **roy** » Tue Oct 23, 2007 12:53 pm

Hi,
The only limit is your resources, but going over the capabilities of your server CPU-wise might result in jobs failing when they should not fail.

How exactly are you calling the multiple jobs?
There should be no problem as for asigning your invocation id to the multiple instance jobs, unless it is a bug in your design/programing.

IHTH (I Hope This Helps),

kaps · Post by **kaps** » Tue Oct 23, 2007 1:43 pm

My job design is given below...

SeqAct1---->SeqAct2

In SeqAct1, I am calling that multi-instance job giving the Invocation ID

Server has 8 cpu's. what am I missing ?

Thanks

ray.wurlod · Post by **ray.wurlod** » Tue Oct 23, 2007 3:30 pm

What are you giving as the invocation ID values?

kaps · Post by **kaps** » Tue Oct 23, 2007 4:05 pm

Invocation ID's are just a string....few cases seperated underscore...

XXXXXX
XXXX_XX
XXXXX
XXXXXX
XXXXx_XX
XXXXX

Anything wrong with this ?

Thanks

ray.wurlod · Post by **ray.wurlod** » Tue Oct 23, 2007 4:31 pm

Provided that they are all distinct values, no. Your examples do not form a distinct set, though I understand that you have obfuscated the actual values. XXXXXX appears twice for example. So does XXXXX. If the same invocation ID is given twice (or more) the first instance will start but the second and later instances will fail to start, returning an error "job is already running".

kaps · Post by **kaps** » Tue Oct 23, 2007 5:07 pm

Ray

I just gave some examples. Invocation ID's are unique.

I am getting the following error while running the Master sequencer job.

edw_intagm_Intrmdy_Agrmnt_Queue_seq..JobControl (@ja_edw_common_ClearStopQMsg): Controller problem: Error calling DSRunJob(edw_common_ClearStopQMsg), code=-2
[Job is not in the right state (compiled and not running)]

This problem happens I believe when the Master Sequence trying to start the Multi-instance job without passing Invocation ID's.

I appreciate any help..

Thanks

ArndW · Post by **ArndW** » Tue Oct 23, 2007 5:22 pm

Kaps - that error happens when you try to run a job that is running; which means that your Invocation ID is not unique.

JoshGeorge · Post by **JoshGeorge** » Tue Oct 23, 2007 5:23 pm

Controller problem: Error calling DSRunJob - Is because - edw_common_ClearStopQMsg - this job is not in a runable state. You have to do a re-set and run. Check if your compiled base job was called previously and currently not in runnable state or a perticular instance was aborted and you are trying to invoke the job with the same invocation id.

ArndW · Post by **ArndW** » Tue Oct 23, 2007 5:37 pm

JoshGeorge - in the context of the user working with instanciation, the job is almost certainly not "runnable" because it is already running; not because it aborted on the last run.

ray.wurlod · Post by **ray.wurlod** » Tue Oct 23, 2007 6:08 pm

You should have mentioned the -2 error code (DSJE.BADSTATE) earlier!

Do you invoke your jobs with "reset if required, then run" in the job sequence?

JoshGeorge · Post by **JoshGeorge** » Tue Oct 23, 2007 7:18 pm

ArndW - Missed the -2 part.
Finding is right, invoking the job with a different invocation id should resolve the issue.

kaps · Post by **kaps** » Fri Oct 26, 2007 10:20 am

Ray

No. I just have the execute option of RUN.
Am I missing something there ?

Thanks

ArndW · Post by **ArndW** » Fri Oct 26, 2007 4:58 pm

The "reset if required" will do exactly that, reset a job if the previous run has failed so that it is in a runnable state. It won't help you if are trying to re-run an instance that is already running, but worth changing nonetheless.

sanath1234 · Post by **sanath1234** » Sun Oct 28, 2007 11:34 pm

kaps wrote:We have a Job sequence which calls a Multi-Instance server job. We are calling this job 8 times by passing
different Invocation ID's at the same time. But two of those jobs does not get the Invocation_ID which is causing one job to fail.

I don't understand why it's not picking up the Invocation_Id's.

Is there any limitations on how many jobs we can kick off at the same time ?

Please advise.

After going thru all yur conversations job u disigned is only using one cpu .

DSXchange

Invacation ID

Invacation ID

Re: Invacation ID