RE: Trying to avoid dozens of MONMSG's

At a previous job we had folks doing that (CPF0000) Simon and WHAT a mess !
Users would call saying they didn't get a report or something didn't update
in the nightly jobs, etc. They would be told "well nothing bombed", etc.

And in reality, yes something had bombed but it didn't tell anyone in an
obvious way. That of course got changed...

Chuck

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Tuesday, July 26, 2005 6:05 PM
To: Midrange Systems Technical Discussion
Subject: Re: Trying to avoid dozens of MONMSG's


On 27/07/2005, at 12:49 AM, rob@xxxxxxxxx wrote:

> I have a CLP that does numerous lines like:
> CHGAUT OBJ('/QSYS.LIB/PAIAVI81F.LIB/*') AUTL(SSA26F)
> Occasionally I'll get a message (like on a new library with no files 
> yet).
> CPFA093-Name matching pattern not found.
>
> Instead of adding a LOT of MONMSG's I thought I'd try:
> ADDRPYLE SEQNBR(9101) MSGID(CPFA093) RPY('I')
> CHGJOBD JOBD(GDISYS/FIXSEC) INQMSGRPY(*SYSRPYL)

Interesting approach ... but so WRONG! You don't want to monitor for 
the real exception but instead will let the system default exception 
handler catch it and then you'll tell it to ignore the exception?  
That's as bad, if not worse, than the fools who avoid errors by 
sticking MONMSG CPF0000 as a global exception monitor with no EXEC 
specified.