|
> It is an RPG ILE flaw that you can't > easily throw your own errors and have > the MONITOR block catch it. QMHSNDPM doesn't do what you want? Some examples and caveats: http://archive.midrange.com/rpg400-l/200204/msg00764.html http://archive.midrange.com/rpg400-l/200303/msg00501.html And this thread http://archive.midrange.com/rpg400-l/200303/msg00075.html I apologise if I misunderstand the requirement. The send message API can throw any message, but the monitor/exception trap will probably materialise a 202 error, no matter what you send. You need to inspect the program status data structure and/or job log to see the actual message sent. But if you send an escape message up the stack, the caller can certainly trap it... --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.