RE: Error messages from API's

then to resend the msg, use the QMHRSNEM api.

Steve Richter


-----Original Message-----
From: mi400-admin@midrange.com [mailto:mi400-admin@midrange.com]On
Behalf Of Leif Svalgaard
Sent: Thursday, April 11, 2002 9:51 AM
To: mi400@midrange.com
Subject: Re: [MI400] Error messages from API's


From: Veening, Bert <bert.veening@Centric.nl>
> I am in the process of creating an MI program calling QSNDDTAQ which must
> function as a CPP. Unfortunately, QSNDDTAQ does not accept the standard
> error parameter  like most other API's and this results in bombing
whenever
> an error occurs. I can write my CPP in CL and do a MONMSG, 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?

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.