Sequence Issue

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
sush26283
Participant
Posts: 68
Joined: Thu May 20, 2010 11:55 am

Sequence Issue

Post by sush26283 »

I have a sequence job, which looks like this..

Job_activity1--->job_activity2--->....job_activityN

and at the trigger(all of them) I have the custom (conditional) with expression as Job1.$JobStatus = DSJS.RUNWARN, so that the trigger is initiated even if there is any warning.

I had this scheduled, but after it ran all fine I noticed that only Job_activity1(the first job) ran and it did not trigger the next to run.So, the whole sequence did not run but only the first part, and the job log shows as successful.

Can anyone tell me where am making the mistake, due to which the whole sequence did not run.

Thanks in advance
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

That trigger means the next job only runs when the previous job finishes with warnings. A successful run will not trigger the next job. You need to check for RUNOK or RUNWARN.
-craig

"You can never have too many knives" -- Logan Nine Fingers
sush26283
Participant
Posts: 68
Joined: Thu May 20, 2010 11:55 am

Post by sush26283 »

so what you are saying is that I should use the expression as Job1.$JobStatus = DSJS.RUNWARN or Job1.$JobStatus = DSJS.RUNOK in all of the job activity stages
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Yes. If you want to allow warnings to be ok.
-craig

"You can never have too many knives" -- Logan Nine Fingers
sush26283
Participant
Posts: 68
Joined: Thu May 20, 2010 11:55 am

Post by sush26283 »

Thank You Sir!!!
Post Reply