RE: system save

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Thank you Ken,

You confirmed what I thought, that there still is no alternative for a
SAVSYS other than to log on to the console.

We have perhaps strayed from the original question, which was whether a
system save can be run from the job scheduler.  (No, the job scheduler
would initiate a batch process which would not be able to dedicate the
system.)  The logical follow-up question is, "Can we schedule a system
save in some other way?"  (Yes, although it does involve having a
console signed on).

Thanks,
Andy

> On Behalf Of Graap, Ken
> Subject: RE: system save
>
> Andy -
>
> My understanding of these solutions is that you SIGNON to the system
> console
> and then initiate the backup process. It controls the interaction with
the
> system console. Part of this process could be delaying the backup
until a
> later time.
>
> One security issue that might arise from this is that your operator
> profile
> is signed on to the system console in an unattended mode. This might
or
> might not be an issue for you. If your computer room is secured it
> probably
> isn't a big issue and I also believe that the third part solutions
provide
> some kind of console locking future that requires a password for
access.
>
> I use BRMS to save our system. I have chosen not to implement an
> unattended
> SAVSYS. I'm able to schedule an attended IPL/PTF apply/SAVSYS process
once
> a
> month and the staff just takes turns being the "attendee" ... It works
for
> us.
>
> All our other saves are automated and unattended though.....
>
> Kenneth