Invacation ID

[sanath1234]

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 .

[sanath1234]

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 .

[ArndW]

One CPU? Not only is that not visible from any job design, but it is irrelevant.

[kaps]

Problem is resolved. It seems that this job was first created as normal job and later converted to Multi-instance job. When it was not a multi-instance job two other jobs were invoking this job and hence the problem.

We compiled the calling jobs and reran which solved the problem.

Thanks

[gateleys]

Problem is resolved. It seems that this job was first created as normal job and later converted to Multi-instance job. When it was not a multi-instance job two other jobs were invoking this job and hence the problem.

We compiled the calling jobs and reran which solved the problem.

Thanks

Ah! And I thought the ID was "In Vacation" when I looked at the subject of the post.

[ray.wurlod]

"In Vacation" - that would also explain why it wasn't doing anything!

[kaps]

Guys- It's just a typo...I noticed it before itself but don't know how to change the subject...

Anyway good comments on that !