Multi instance Job fails with Status 99(Not Runing)

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
bman
Participant
Posts: 33
Joined: Wed Oct 10, 2007 5:42 pm

Multi instance Job fails with Status 99(Not Runing)

Post by bman »

Hi

I have a problem with one of my multiinstance job flow. I have a multi instance flow as below,


Sequence 1:

JobSequence1 --> JobSequence2 -->SequenceSequence
(-----Job 1-----) (-----Job 2------) (-----Sequence2---- )


Sequence2:

LoopStart --> JobSequnece3 ----> Routine ----> JobSequnece2 --> EndLoop
(---------) (-----Job3---------) (--check & Exit-- ) (----Job2-------)

The Sequence and Jobs are in Multi instance mode. A script calls the Sequence1 with Sequence name as Sequence name.Invocation id. All th ejob runs fine when ran single instance. When we multiple instance of the Sequence 1, Job behaves wierdly.

For eg,
If I run 3 instances at a time, two will run fine but one will fail in sequence1 with an error Job 1 has finished, status = 99 (Not running).

Some times the Sequence 2 fails with similiar error ?

Is there anything I am missing to make the flow multi instance ?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Have you thoroughly checked that the invocation IDs are absolutely unique everywhere, including in the controlled jobs?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
bman
Participant
Posts: 33
Joined: Wed Oct 10, 2007 5:42 pm

Post by bman »

Hi Ray,

Invocation id is unique as it is same as th einput file name. I have run the job just keeping te Jobsequence1 and removng all the downstream jobs but I am getting the same error
bman
Participant
Posts: 33
Joined: Wed Oct 10, 2007 5:42 pm

Post by bman »

I would like add one mor epoint here..
Only the Sequence is getting aborted with Status code 99( not running error). As per the job log it has succesfully completed the run
deanwalker
Participant
Posts: 82
Joined: Tue Jan 22, 2008 10:37 am
Location: UK

Post by deanwalker »

Is Log Auto-purging enabled for either the Project or Jobs ?
If so, please disable and retest. If this solves your problem then there is a patch that you can request.
snt_ds
Premium Member
Premium Member
Posts: 280
Joined: Wed Oct 18, 2006 11:53 am
Location: Pune, India

Post by snt_ds »

Hi,

Could you please let me know the patch number for this issue of
status = 99 (Not running)?

If auto purging is disabled,then the problem is solved.

Thanks.
Post Reply