Re: MONMSG not monitoring

Another option is to put the necessary code within your CL backup program to
receive the inquiry messages using RCVMSG and handle it all within your
program.

You can then use the SNDRPY command to send a reply to the inquiry message
and answer it so the the program can retry, end, or whatever.  Then perform
a CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES) so the job will produce a job log
and send yourself, the QSYSOPR message queue, or both a message indicating
that the backup job ended in error.

The only potential problem is that SNDRPY must gain exclusive control of the
QSYSOPR message queue in order to reply to the message.  To prevent this
problem, you could change the device description of the tape drive to use a
message queue other than QSYSOPR (maybe call it BACKUP), one that you know
no one will have allocated or in break mode.

HTH,

Steve Landess
Austin, Texas
(512) 423-0935


----- Original Message -----
From: "Bob Crothers" <Bob2@xxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, March 11, 2003 12:26 PM
Subject: RE: MONMSG not monitoring


> Tom,
>
> You could write you own very simple break handling pgm for this. Then
> put QSYSOPR into break pgm mode before the backup and take it out after
> the backup.
>
> Bob
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> > bounces@xxxxxxxxxxxx] On Behalf Of Tom Jedrzejewicz @ San Pedro
> > Sent: Tuesday, March 11, 2003 12:51 PM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: RE: MONMSG not monitoring
> >
> > Thanks.  I did not know you could find the monitorable messages on
> > the
> > help, was it recently added?
> >
> > Regarding the problem . . . Given that this is the only thing going
> > on
> > on the system after hours the purchase of software to manage QSYSOPR
> > is
> > overkill.  Any thoughts regarding the wisdom of adding an entry to
> > the
> > SYSRPYL for this message?  At that point the *escape message should
> > get
> > back to the program, right?
> >
> > Take care.
> >
> > >>> Buck.Calabro@xxxxxxxxxxxx 03/11/03 09:12AM >>>
> > >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
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> > THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY
> > TO WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS
> > PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE
> > LAW.  If the reader of this message is not the intended recipient, or
> > the employee or agent responsible for delivering the message to the
> > intended recipient, you are hereby notified that any dissemination,
> > distribution, copying, downloading, storing or forwarding of this
> > communication is prohibited.  If you have received this communication
> > in error, please notify us immediately via email and delete the
> > message from your computer files and/or data base.  Thank you.
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>