Re: Error messages from API's

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!