That's correct, by calling OnErrorGoto procedure you are taking over the default error handling. If you wish to restore the default error handling you can call OnErrorStop. For example, at the end of your error handling block add OnErrorStop abnd then RaiseError with your customer error message. : Question on error handling: In most of my JAL scripts, I am using the : following format for error handling: OnErrorGoto ERROREND : {script here} : {condition i want checked) : RaiseError("This is the error message I want when a condition I want : fails") : ERROREND: GetLastError(message) : Dim subj, "error subject" : Mailsend(profile, pass, subj, message, recipients) : Exit : In this scenario, it seems that the 24x7 GUI only sees those errors as : "alerts" or : warnings. I wish to use the 'retry job on fail' condition within the GUI, : however, : I do not believe the GUI is receiving an ERRROR event as I have described. : How do I get the GUI to give a actual ERROR state so that the retry logic in : the job : will start?
|