I don't believe in causing jobs to abort. I feel it is far better to retain control over what is happening.
That said, there are several solutions, including limiting the number of rows on an output link from a Transformer stage that might handle this particular value, or conditionally calling a routine that invokes DSLogFatal() function.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
And I prefer to capture them all and then conditionally abort the job if the error file is not empty and that is the requirement. That way all problems are known, not just the first one.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Database triggers? A 'before insert' trigger that raises an error when that value is seen could work, I suppose, depending on your warning level. Or you could just call DSLogFatal() in the job itself.
-craig
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:Database triggers? A 'before insert' trigger that raises an error when that value is seen could work, I suppose, depending on your warning level. Or you could just call DSLogFatal() in the job itself. ...
Thanks Craig!!!
Where can I find full documentation for all the functions like DsLogFatal or other DS routines, procedures ?
Go into your Programs -> IBM Information Server -> Documentation and, from the list, choose your appropriate language for "Programmer's Guide" in the "Websphere DataStage" section.