RE: MONMSG not monitoring

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>The following code is run from the console daily for our backup . . .
>DLYJOB     RSMTIME('23:30:00') 
>ENDSYS     DELAY(120)          
>MONMSG     MSGID(CPF0000)      
>DLYJOB     DLY(180)            
>INZTAP     DEV(TAP01) NEWVOL(DAILY) NEWOWNID(CFP) +
>             CHECK(*NO)                            
>MONMSG     MSGID(CPF0000 CPA0000)
>DLYJOB     DLY(60)
>--> followed by the various save commands
>STRSBS     SBSD(QCTL)  
>
>occasionally there will be a problem with the tape, or a failure to put
>one in, or a write-protected tape.  Last night, the INZTAP failed, and
>the system waited for .  The following message was in the log.
>
> Message ID . . . . . . :   CPA4086       Severity . . . . . . . :   99
> Message type . . . . . :   Inquiry                                    
>My question is . .  why did the MONMSG on the INZTAP not trap this
>error and continue on?  I want to add code to have an email generated,
>but if the error is not caught that code is useless.

Hi Tom!
  MONMSG only traps the messages indicated in the command help.  It doesn't
trap inquiry messages destined for the system operator (like 'Make the tape
drive ready' or 'Change the paper on the printer')  To see the messages that
can be trapped, go to a command line, type INZTAP, press F1 for help and F2
for complete help.  You'll see a list of messages there.

What you really need is to have a break handling program on QSYSOPR in
addition to the error trapping in your CL.  There are commercial products
which perform this very task.  Robot is one that springs to mind, but there
are others.
  --buck