denzilsyb wrote:In ValidateJob, I have the trigger set to "OK"
You might want to explain exactly what this means. Do you mean you have the trigger set to "OK- (Conditional)" or some sort of Custom trigger where you wrote the condition?
-craig
"You can never have too many knives" -- Logan Nine Fingers
Hi,
Is this the first time you are compling a sequencer job and getting this error or you have complied successfully sequncer jobs in the past on this version of datastage?
Is this version 7.5?
ketfos wrote:Is this the first time you are compling a sequencer job and getting this error or you have complied successfully sequncer jobs in the past on this version of datastage?
Is this version 7.5?
This is not the first time, it is 7.1r1 on solaris 9. In another sequencer i have multiple jobs that go into a sequencer and out again into another job. that job compiles ok, but as soon as i add more than one email notification to the job, i get the above error.
chulett wrote:You might want to explain exactly what this means. Do you mean you have the trigger set to "OK- (Conditional)" or some sort of Custom trigger where you wrote the condition?
yeah - sorry; i set it to "OK - (conditional)". I have tried otherwise as well.
dnzl
"what the thinker thinks, the prover proves" - Robert Anton Wilson
Strange. The Sequence stage doesn't really serve a purpose in your job and could be removed. However, it shouldn't be causing any problems, either.
I don't see how adding another Notification Activity stage would be a problem. You could easily have multiple links from the Sequencer to multiple Notification Activity stages... either that or link from one NA to another NA in a serial fashion. Both ways should work just fine.
How are you adding the "one more notification stage"? Linked from the Sequencer? Do you set its trigger to "OK (Conditional)" as well?
-craig
"You can never have too many knives" -- Logan Nine Fingers
Check out your Notification Stage and see if you have the word 'OK' in the subject or body of the email to be sent. I ran into this issue before myself. I can't remember exactly, but I had to change how it was quoted. I think I changed from single quotes(') to double quotes(").