RE: MONMSG not monitoring -- MIDRANGE-L

If you want a cheap way to guarantee your SBS will be started, add a
STRSBS     SBSD(QCTL)  to the job scheduler at the "drop dead" time your
system has to be up.

That way, no matter what happens to the save job, the subsystems will
always start up and you can telnet in or whatever to see what's wrong.

Art Tostaine, Jr.
CCA, Inc.
Jackson, NJ 08527


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Jedrzejewicz @
San Pedro
Sent: Tuesday, March 11, 2003 9:51 AM
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.