RE: full system save. Option 21

Not having had any extensive experience with data queues, I thought I have
seen where they are used for this type of thing.  Using the data queue method,
does the system console still need to be signed on for it to work?  And,
therefore, still requiring restricted access to the system console?

I see your point, though, with it offering more flexibility for scheduling.
It also allows for a remote administrator (like myself) to hold or reschedule
the scheduled job in case the branch needs to operate past the normally
scheduled time.  I like it!

- Dan
Dan Bale says "Ban Dale!"
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-------------------------- Original Message --------------------------

Dan

Can't speak for Robot or whatever, and I use the same method as you have
historically used.

A strategy I have seen suggested at various times and one which BRMS
appears to use (from what I've seen of it)  is to have a console job signed
on that waits on a data queue. When something is recieved on the data queue
then something happens. (DUH!)

In this case it runs the system (or other) save and as its signed on at the
console, it is able to run a SAVSYS. The job that sends the data queue
entry could be on the scheduler or wherever, giving a tad more flexibility
than the DLYJOB option.

Hope this helps

Regards
Evan Harris

>Does anyone know if the 3rd party backup products do anything more than stick
>a DLYJOB RSMTIME(&TIME) before it does the SAVE 21 stuff?  I did this years
>ago where the system console was in a locked room for which only the MIS
>manager & myself had a key.  Every afternoon I'd load the next day's backup
>tape in the tape drive, call up a special menu on the system console, take
 the
>option.  The first thing it did was to INZTAP the tape, this was also a
 sanity
>check that the drive was "ready".  I walked out of the computer room and
>locked the door.  Then it hit a DLYJOB RSMTIME(020000) before ENDSBS *ALL and
>running all of the SAVe commands.
>
>Not knowing any better to do otherwise, my method requires restricted access
>to the system console.  Do the 3rd party backup products do it any better
 than
>that?
>
>Dan Bale
>IT - AS/400
>Handleman Company
>248-362-4400  Ext. 4952
>D.Bale@Handleman.com
>   Quiquid latine dictum sit altum viditur.
>   (Whatever is said in Latin seems profound.)
>
>-------------------------- Original Message --------------------------
> > I would like to be able to schedule a job to run a full
> > system backup.  Is this possible?
>
>Not really, as the full system save runs in restricted state.
>
>Some 3rd party backup products (Robot/Save is the one that comes to mind)
>provides support to schedule a full system save.  I think you have to run a
>backup agent on your console and it checks the time and takes the system
>into restricted state prior to trying to run a full system save.
>
>david
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---