|
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.
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.