|
Hello, Kaylan: First, you can monitor for a specific message, e.g.: MONMSG MSGID(CPF9801) Or you can monitor for a list of specific messages, e.g.: MONMSG MSGID(CPF9801 CPF9802 CPF9810) Next, you can monitor for a whole group of related messages, using a "generic" designation such as: MONMSG MSGID(CPF9800) -- this will trap any message that begins with CPF98xx. Next, you can monitor for a truly generic message, such as: MONMSG MSGID(CPF0000) -- this will trap any message that begins with CPFxxxx. -- typically this is used in a "global message monitor" statement at the start of the program, e.g.: MONMSG MSGID(CPF0000 MCH0000) EXEC(GOTO ERROR) For these message IDs to be considered a "generic pattern" it must end in "00" or "0000". Finally, it is my understanding that, if a CPF message occurs and is not "handled" in the CL program, in other words, there was no active MONMSG that matched the message ID either exactly or as a generic pattern, then it is converted into a CPF9999 and that exception is raised ... so you can also monitor for CPF9999. But, due to this extra processing that occurs before it is converted to CPF9999, you may get additional messages, such as the one that tells you there was an unhandled exception and asks if you want a "dump" etc. At least, that's my understanding or interpretation of "how it all works" ... Hope that helps ... ;-) Regards, Mark S. Waterbury ----- Original Message ----- > From: "kalyan ram" <mrkalyanch@xxxxxxxxx> > To: "Rpg MessageList" <midrange-l@xxxxxxxxxxxx> > Sent: Thursday, December 22, 2005 10:56 AM > Subject: Difference between CPF0000 and CPF9999 > > Hi, > > Can anybody explain the difference between CPF0000 and CPF9999 error handling. > > Both are used for default error handling....Is there any difference between these two? > > Thanks > Kalyan Ram C. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.