|
Buck, I dont see "QRNXMSG" mentioned in the archives. Did that thread pertain to where to send an *escape msg using qmhsndpm? >From my testing, all *escape messages sent to a procedure call stack entry result in error number 202. And the pgm status data struct contains the msgid of the msg. So my error handling code looks something like this. monitor ; DoSomethingProc( ) ; on-error 202 ; // send failed *escape msg back to caller endmon ; The problem with this is that all errors are covered by the 202 error code. And that kind of defeats the purpose of "exception" handling. Is there a way for an ile proc to signal an error number based exception. thanks, Steve Richter
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.