I am getting the following error when my job is aborting in the sequence and I am not getting the email
Controller problem: Error calling DSRunJob(JOB_NAME), code=-2
[Job is not in the right state (compiled and not running)]
Will execute error activity: Exception_Handler
JobControl (DSSendMail): Parameter 4 ('[Job is not in the right state (compiled and not running)], Job aborted') does not start with a keyword
JobControl (@failure_email): Controller problem: Unhandled failure (-19) encountered calling routine DSSendMail
Error while executing error activity: Exception_Handler
I have ExceptionHandler---NotificationActivity-----Utilityaborttologroutine
in my Job sequence. Does this mean I am not using the Exception Handler stage properly.
That's a tricky one, because your job did not abort. It couldn't be started, because it was not in a runnable state. Is your execution rule "reset if required, then run"?
There is also a problem with what you're feeding to the Notification Activity, but do solve the first problem first. After all, what has been fed to the Notification Activity is an artifact of the failure mode.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thanks Ray..I did take care of the problem. My concern was why I couldnt get the email..but as you said my job didnt abort..it just cudnt start.That answers my doubts.
yeah..I got the emails when the job aborted first. Then I restarted the job again but my JobActivity was not set to 'reset if required and run' and hence the error. Is there anything I need watch out for. Please let me know.
When I Abort the job by passing wrong values as parameters I am getting an email saying the Job is aborted. But I am still getting the following error.
At what stage the sequence is getting failed. And what is the trigger you use in the stage. One of the reason the Unhandled failure arised, when the failure trigger not been handled.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Its failing in the jobactivity stage. I am passing the wrong parameters deliberately to abort it and check it. I have two triggers.on OK and one Warnings.
Now, please correct if I am wrong. The error message
is saying that the Routine UtilityWarningtoLog is being called or is it saying that it encountered problems calling that routine and hence it cant execute the Exception Handler.
It's telling you that you invoked UtilityWarningToLog (presumably in a Routine activity) and that UtilityWarningToLog returned 1 (which it does) and that you did not have a trigger to handle a return value of 1. With routines the rule is that the job sequence will report a failure unless the return value is 0, unless there is a specific handler for non-zero return values. It does the same with Execute Command activity; if the exit status is not zero a "failure" is detected. Since UtilityWarnToLog always returns 1 (inspect its code), either add a trigger to handle this, or clone the routine and change it so that it only returns 0.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Once I had such scenario from Comnand Activity, which replies 0 - Success, 1 - Warining, 2 - Error. Though I handled all the error code in the trigger section, it throwed me unhaldled error for reply 1. We manage to solve by giving 'Otherwise' trigger only for that condition.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
