RE: MONMSG not monitoring

>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.
>


>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.

You can also change qsysopr msgq to *dft mode when this program run so that
the system will answer those messages with the default answer. (Normally
Cancel......) This way the system will start up again at least.

Regards,

Stefan Tageson
Intentia Consulting Sverige AB
Propellergatan 1, SE-211 19 Malmö, Sweden
Phone: +46 (0)40 691 35 00
Cell: +46 (0)733 913 813
Fax: +46 (0)40 691 3900
E-mail: stefan.tageson@xxxxxxxxxxx