Trapping error messages

jamesmc

Member
Howdy folks,

I know I can trap error messages by using the error-status:error attribute but this doesn't seem to work on some errors that I am experiencing.

My program can call any other program depending on the processing that it is doing, but if it calls a program, for example, that fails a CRC check and needs compiling my entire run seems to end even though I have the no-error on the RUN (I know that this error will still echo to the screen) and I am capturing the error-status immediately after.

My aim is to be able to have a program that can call any other program and still continue running even if the called program fails (for CRC problems or any other problem that might stop the program running that I can't account for by code like data files missing etc). I don't want to turn off any CRC checking.

Please help.

James.
 
Top