RE: system save

["Graap, Ken" <keg@xxxxxxxxxxxxx>]

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
--
********************************
Kenneth  E.  Graap
IBM Certified Specialist
AS/400 Professional
System Administrator
NW Natural - Information Services
System Services
Phone 503 226 4211 X5537
FAX   603 849 0591
keg@nwnatural.com
********************************


-----Original Message-----
From: Andy Nolen-Parkhouse [mailto:aparkhouse@attbi.com]
Sent: Wednesday, October 23, 2002 10:52 AM
To: midrange-l@midrange.com
Subject: RE: system save


Todd,

Could you provide a brief description of how BRMS handles this?  I know
that I have written code to wait at the console, dedicate the system,
save the system, and then bring the system back up.  Is this what BRMS
does, or is it different in methodology?  (I'm sure it's more
sophisticated, but is it different in kind?)

Regards,
Andy Nolen-Parkhouse

> On Behalf Of Todd kidwell
> Subject: RE: system save
>
> Tom,
>
> We use BRMS to run scheduled, unattended full system saves in a
restricted
> state.  Works very nice.
>
> Robot/SAVE allows the same thing.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.