different invocation id

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
iskapalli
Participant
Posts: 76
Joined: Wed Jul 25, 2007 12:36 am

different invocation id

Post by iskapalli »

Hi,

in production one sequence is running with three differnt invocation ids in production(4 nodes)

I think one job will run and remaining jobs will fail

please confirm that
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Based on the information you have provided, you are not correct.

All three invocations will run.

The fact that they can have invocation IDs already tells us that they are configured for multi-instance running.

However, the design itself may cause failure. For example, if all three try to write to the same hard-coded file name at the same time, then that will cause a failure.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
iskapalli
Participant
Posts: 76
Joined: Wed Jul 25, 2007 12:36 am

Post by iskapalli »

thanks for your reply

suppose schedule time is 6:30. it is triggering at time (no second different).

even that time also will jobs will run?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Multi-instance jobs were implemented in DataStage so that multiple instances of the same job could run at the same time. As Ray stated, if the jobs aren't correctly designed they may still fail. For example, if they write to the same sequential output file at the same time they would deliver incorrect results, but if they write to the same database table at the same time they will function as designed.
Post Reply