RE: scheduling a full SAVSYS

Using BRMS, you would use the "BRMS console". This is a program running on
the console to "interactively" use the system in restricted state. You must
sign on the system console with a user profile (ours is called CONSOLE) with
an initial program of QBRM/Q1ACCON and preferably an initial menu of
*SIGNOFF. 

In BRMS, create a control group for a system save (you don't use GO SAVE 21)
and create a scheduled job to perform the control group.

Our weekly save is a "restricted state" backup. The control group looks like
this. The control groups are definable so you can add additional steps if
necessary. Here is our control group WEEKLYLTO.
*SAVSECDTA
*SAVCFG
*IBM
*ALLUSR
*ALLDLO
*LINK

You would change the "Subsystems to Process" to *ALL QSYS *IMMED *NOLIMIT
*YES. This will end all subsystems, and restart them after the backup
completes. Starting the controlling subsystem invokes your system startup
program to start everything just like an IPL.

You could add an entry for *SAVSYS, which I think brings you very close to
the GO SAVE 21 functionality.

On the scheduled job side, create a job to perform the backup. The save
command looks like this:
STRBKUBRM CTLGRP(WEEKLYLTO) SBMJOB(*CONSOLE)

When the job runs, the CONSOLE user is signed on, and performs the actions
in restricted state.

Our console is in a double-locked computer room (must pass through two
doors) so we are comfortable leaving CONSOLE signed on all the time.

HTH,
Loyd

Loyd Goodbar
Senior programmer/analyst
BorgWarner
E/TS Water Valley
662-473-5713
-----Original Message-----
From: McBride, Catherine [mailto:CMcbride@xxxxxxxxx] 
Sent: Wednesday, October 13, 2004 12:45
To: 'midrange-l@xxxxxxxxxxxx'
Subject: scheduling a full SAVSYS

Anyone know of a way to pre-schedule a full SAVSYS?
(Go SAVE, option 21) 
OS400 V5.2, BRMS.
TIA,
    Cathy