|
Hi Scott,
Thanks for the link - I can't believe it has been over a year since I read
that article. Where has the time gone?!?! :-)
This does 95% of what I was looking for, but I notice it uses the general
purpose CPF9897 message to invoke the on-error code. Do you know if it is
possible to send custom-messages and still trap them using on-error? Or does
the on-error code only look for specific values? I was hoping I could throw
an escape message and catch it using on-error code. Thinking about it
though, I'm starting to doubt whether it would be possible. I suppose I
could always do something like:
throw code within procedure doSomething()...
throw('CPF9897' :'MSG0001');
try/catch code wrapping call to procedure doSomething()...
monitor;
doSomething();
on-error;
messageID = retrieveMessageID();
select;
when messageID = 'MSG0001';
trapError1();
when messageID = 'MSG0002';
trapError2();
other;
trapGeneralError();
endsl;
endmon;
Hmmm...
Cheers
Larry Ducie
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.