• Subject: RE: More automated backup
  • From: Bob Crothers <bcrothers@xxxxxxxxxxxxx>
  • Date: Wed, 31 Dec 1997 22:01:02 -0500

Loyd,

Sounds like you have been around the block then.  From your 
first message I just had pictures of somebody who can barely 
spell CRTCLPGM trying to write their own backup routines and 
then relying on them.  I've seen it happen before.

The code I sent in my first message on how to check for QINTER 
ending ought to work pretty good.  And I saw somebody else gave 
you the exact Message ID to monitor for.

Re MONMSG, it is really quite simple.  You put the monmsg after 
the command you want to trap and error condition on.  Then if 
the message happens, the EXEC parm gets done.  If the message 
doesn't happen, the EXEC doesn't run.  There is another parm on 
MONMSG, "Compare Data" or something like that.  I don't think 
I've ever used it.

The ONLY message's you can monitor for however are esacpe 
messages.  When you do an F1 on the msg, it will say escape in 
the message type.  And it has to be sent to your program.  Eg: 
Look at the details and the "To Program" will be yours.  Also, 
these show on the command entry screen without having to F10 for 
"all messages".   That probably makes it as "clear as mud". <g>

And be very cautious about what you monitor for.  And tell 
people when it fails!!!

Can you give specific questions about MONMSG that you are having 
problems with?

Another thought on getting a clean backup would be to just use 
Save While Active.  This will let you save files while they are 
open for update. And it works well.

Regards,
Bob Crothers
Cornerstone Communications

-----Original Message-----
From:   lg - Loyd Goodbar [SMTP:lgoodbar@tecinfo.com]
Sent:   Wednesday, December 31, 1997 1:47 PM
To:     MIDRANGE-L@midrange.com
Subject:        Re: More automated backup

On Wed, 31 Dec 1997 08:28:31 -0500, Bob Crothers
<bcrothers@netdirect.net> wrote:

>BUT, it still does not eliminate the need for a FULL AND
>COMPLETE backup!  At minimum a SAVLIB *NONSYS but better would
>be option 11 from the backup menu.

I agree. This backup is for daily data (back office) only. Major
backups occur on a weekly and monthly basis. Problem is everyone 
is
still signed onto the system, and that doesn't guarantee a clean
backup. And, no one is in the office (back office, not casino) 
at 3:00
am. (The casino system has its own backup procedures provided by 
the
software vendor. We do full system saves every month.)

>Re your 2nd question on MONMSG confusing you.  No offence
>intended, but if you are fairly new to CL programs as this
>question suggests, it might not be a good idea to be learning
>with something as critical to your operation as your backups.

I have been using CL programs for quite a while, but not for 
reasons
that I'd need to use MONMSG. I intend to test my backups in the 
early
evening, before the "normal" AS/400 backup kicks in. I am still
assured a backup.

>Remember, leave the gambling to the casino floor.  The data
>center is NOT the place for making bets!

Agreed!

 - lg -

--
"Just don't give up, take it easy,
 and the rest will take care of itself." --Belldandy
lgoodbar@tecinfo.com  ICQ#504581 
 http://www.tecinfo.com/~lgoodbar/
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to 
"MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].