Dan, CPF0000 is the only one you need. But, it will not catch inquiry messages from inside an RPG program. Such as divide by zero, array index problems, etc. Bob -----Original Message----- From: Dan Bale [SMTP:firstname.lastname@example.org] Sent: Monday, October 04, 1999 10:40 AM To: MIDRANGE-L@midrange.com Subject: Re: global MONMSG to catch everything Thanks to all who responded. Besides the CPF0000 & MCH0000, isn't there a third global message? (_THAT_ was the main question of my original post.) I'm thinking CPA0000, or CPD0000??? Anybody know? Or is it just CPF & MCH? I guess I should have been a little more clear. The global MONMSG actually did have a GOTO to an error-processing tag, however, since this is a batch job that only _I_ run, all I did with it was: Global: MONMSG MSGID(CPF0000 MCH0000) EXEC(GOTO BadBoy) <<<< snipped code >>>> RETURN BadBoy: SNDMSG MSG('Hey, pgm $DSPFD$M@C bombed with + library ' *cat &library *cat ' with + some message that was not monitored.') + TOUSR(QCS2) DSPJOBLOG OUTPUT(*PRINT) ENDPGM Since I'm the only one who uses this application, I don't need to get fancy with the "standard error handling" stuff (although I realize I need to get up to snuff on this). I just need a message to tell me to go look at the job log. Dan Riehl, thanks for the tutorial on the web site. Good article! - Dan Bale _________________________ Original Messages __________________________ Date: Fri, 1 Oct 1999 17:01:02 -0400 From: "oludare" <email@example.com> Subject: Re: global MONMSG to catch everything Yes, it is foolproof but you'll have to do it for every CL program. My suggestion for you is to do this for all programs, including CLs and RPGs: CHGMSGQ QSYSOPR *DFT Remember to change *DFT to *BREAK when the operator is around to answer messages. Goodluck, Oludare ------------------------------ Date: Fri, 1 Oct 1999 14:17:52 -0700 From: Kirk Goins <KirkG@pacinfosys.com> Subject: RE: global MONMSG to catch everything In a previous life I was a SysAdmin who came behind one or more persons that used the MONMSG CPF0000 as a global Ignore All Errors. It works wonderful, too good if that is all you do. To use this globally it should goto an error routine that handles the error. They didn't, and at times it was only when a user called saying the data wasn't there or wrong did I know I had a problem. SW upgrades were fun since programs appeared to run correctly. The Long and Short of it all, it will work be very very careful... ------------------------------ Date: Fri, 01 Oct 1999 16:32:15 -0500 From: Dan Riehl <firstname.lastname@example.org> Subject: Re: global MONMSG to catch everything Check www.400school.com There is a tutorial about MONMSG and how to use it most effectively.... >From the main page click the "Tutorial" button. +--- | 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: email@example.com +--- +--- | 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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.