• Subject: RE: global MONMSG to catch everything
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 5 Oct 1999 14:05:40 -0400

Dan,

I trap for CPFxxxx and QWMxxxx in my CL programs that use QMQRY.  On the
more recent releases, you can prompt the STRQMQRY command (the one used by
the utility), press F1 for help, then F2 for extended help.  The help text
gives a list of messages you can trap for.

As for RPG error trapping, you can code an error indicator in the LO columns
(RPG/400) or use %error (RPG IV) on every I/O operation to trap them
"locally."  In addition, you can use a *PSSR subroutine to catch those
"unexpected" errors "globally."

Buck Calabro
Aptis; Albany, NY
mailto:Buck.Calabro@aptissoftware.com

> -----Original Message-----
> From: Dan Bale 
> Sent: Tuesday, October 05, 1999 11:35 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: global MONMSG to catch everything
> 
> Bob, Barbara, thanks for your responses!
> 
> Bob, good point about RPG inquiry messages.  Is there a way to trap those
> in the
> CL program?  RPG0000, RPX0000?  Or do you have to trap it in the RPG
> program?
> 
> Fortunately, there's no RPG program involved in this case.  However, I
> _am_
> using SQLSTM (Execute SQL Statement, a utility from News400).  Is there an
> SQL0000 message that I can use?  Or will CPF0000 catch these as well?
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].