From 24x7 point of view your application runs just fine if it does not return an error (process exit code) code to the operation system, 24x7 can capture that error code (see ProcessGetExitCode statement). You can also update your application to write errors to some log file that can be later scaned for error messages (see example scripts in 24x7 on-line help and Example Jobs database). You can also setup job timeout (must run either as a syncronious job or from a JAL script using RunAndWait statement) so that 24x7 will forcedly terminate your program in case if it timed out. Another option is building a JAL script that will monitor your program execution, search for dialog boxes and close them if found (see WindowFind, WindowGetActive and other Window and Process statements). : Can i trap the error message or the return parameters from application that : failed to run as schedule. For example, i used 24X7 to run an Visual Basic : application. The application was supposed to get various data from the SQL : server, perform some computation and then update the SQL server. Due to : server failure. I've got an error dialogue box which then stopped the : entire job dependencies. If i click 'OK' after reading the dialogue box, : the following job will continue and 24X7 does not capture the error in the : log. : Is there a way to trap the error so that error evaluation can be done? : Is there a way to get rid the dialogue box? : Please advise. : Regards, : Gary
|