|
Veening, Bert <bert.veening@Centric.nl> wrote: > > . . . , but I would like > > to catch the error in my MI program and have it send an escape message of > > its own (preferably resending the message from QSNDDTAQ). Can anybody shed > > any light on this problem? to which Leif Svalgaard replied: > > DCL EXCM * EXCID(H'XXXX') BP(ERROR-OCCURRED) CV("CPF") IMD; > ... > > ERROR-OCCURRED: > do what you need here... > > The XXXX is the error code after the CPF, e.g. for CPF5001 it would be > 5001. For MCH errors the rules are slightly different. If the exception is rather common, and the MI program is large, you should probably also declare the EXCM to have an initial "ignore" state, and use the appropriate MI instructions to turn it on just before the statements where it's needed, then turn it off once it is no longer needed. -- James H. H. Lampert Professional Dilettante http://www.hb.quik.com/jamesl http://members.hostedscripts.com/antispam.html http://www.thehungersite.com Read My Lips: No More Atrocities!
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.