Re: Uncaught Errors in Interactive Programs and the Users that Ignore the Errors

In CL, one must never do the 'ignore everything' global MONMSG that you decry. But if, as has been said, you put a GOTO to an error handler in there, then you have a way to deal with unexpected errors.

In combination with MONMSG CPF0000 EXEC(GOTO ERRORHNDLR) one puts specific MONMSG commands where needed. This is for expected things. This would be, I assume, the basic approach you use in RPG. *PSSR being like the global MONMSG - albeit maybe a full-source MONITOR-ENDMON, too. Then individual error handling within the body of the code.

eh?
Vern

rob@xxxxxxxxx wrote:

I try to throw a lot more error handling into my programs. For example
Select; When mypsds.excp_msg<>*blanks; // Alert the troops! eSubject='Unable to delete journal receiver ' + %trim(parm.library) +
'/' + %trim(parm.journal); eMessage=eSubject; CheckPSDS=fndsigmsg(mypsds); excphdlr01(eSubject: eMessage: CheckPSDS); EndSl;
But if you're looking for some drastic trap to allow you to start doing the granular there are more experienced minds than mine on that.

Perhaps a search on error handling?



Rob Berendt