Scenario :
Job A :
Table A Containing 3 columns is populated fine with checks for Not null, and field length checks. There is a reject link, and it works fine to capture rejects.
JobB :
The Table A is checked for new records, or altered existing records in the transformer. The transformer has 2 output links. one for Updating Table B, and the other for inserting the new values from Table B.
Table A and Table B have similar definitions. Only difference is that Table B has a surrogate key, which is populate using the DSRoutine.
My Concern:
JobB is run after the successful run of JobA. I do not want to have a reject link in the JobB, as the validations have been performed in JobA. The requirement is to abort the job as soon as there is a warning. If there is a case of a warning coming up eg.tablespace, would there be a warning only without aborting the job?. I am assuming that any tablespace warnings/errors would be followed by the job getting aborted. Will it be the case or not ?
Solution :
pls. tell me
Job level Warning, but no abort!
Moderators: chulett, rschirm, roy
You can call UtilityAbortToLog for any special cases checked from the transformer.
It is other way, the job will be aborted due to these tablespace issues.tablespace warnings/errors would be followed by the job getting aborted
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Re: Job level Warning, but no abort!
Use a job sequence, where Job_B has one trigger ($JOBSTATUS = 2 of Finished with warnings) to the Terminator stage. Yet another way is to use a warning limit of 0 when you run the sequence. And of course, Kumar has already suggested a method.
gateleys
gateleys