2 of 2 people found this helpful
We can use a workaround to handle the scenarios like yours 'taking an action when the Specific statement output' is not present in output, like below:
1. Set the job status to NOTOK regardless of desired output statement presence in output.
2. Search of Specific statement output, if exists take an appropriate action and set the job status to OK.
3. Set OnDo on NOTOK status and take the desired action.
Hope this helps. Thanks.
Good Idea. Works well as long as the action is to manipulate the job status or add/remove conditions. Won't work for other actions I guess. Time for an RFE!!
3 of 3 people found this helpful
We have had a similar requirement in our environment. The workaround we developed was to save the output of the job in a temporary folder, then have the next job do a text search for the desired value.
If the value is not found, we change the job flow accordingly.
Job1 imports data into a database table. (Save output to JOB1.txt)
Job2 performs a text search on JOB1.txt for the word 'commit'.
If 'commit' is found, continue to Job3.
If 'commit' is not found, send an error email to interested users and rerun Job1.
We found this necessary because the database import program will (very rarely) give us a return code of 0 without actually performing the commit.
1 of 1 people found this helpful
Being able to do this "out of the box" would be nice. Another one for the RFE list!