Sequencer Expression bug

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
kab123
Participant
Posts: 92
Joined: Tue May 18, 2004 4:05 pm

Sequencer Expression bug

Post by kab123 »

I have used a Trigger, UserStatus-(Conditional) expression type in my sequence Job with expression
[b]'Finished OK' Or 'Finished with warnings'[/b]..The Job aborted but still continue to execute next set of Jobs in the sequence..
Is this a bug Or am I giving something wrong ? any advise is appreciated

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

Post by chulett »

UserStatus <> Job Status and that's just text, not anything meaningful. You need a custom trigger to check for:

Code: Select all

JobActivityStage.$JobStatus = DSJS.RUNOK Or JobActivityStage.$JobStatus = DSJS.RUNWARN
Replace "JobActivityStage" with the actual name of the stage in your Sequence job.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It's not a bug. The problem is between the keyboard and the chair.

And, by the way, a Sequencer does not have any expressions. It only has one property, and that only takes two possible values - "Any" or "All".

Please be careful with terminology.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply