RE: system save

["McGivern, Tom" <Tom.McGivern@xxxxxxx>]

I'm sure it's possible, it's just a question of ROI...  How many
customers would really want it...

To your other points, I've been told that if the process runs under the
controlling subsystem (as defined by the sysval: QCTLSBSD) Then it can
bring the system down to restricted state, do  it's work, and then bring
everythign back up again..

It can't communicate with anything (network is down), and I don't know
what the effect of QSPL being down, but if it writes it output to a
file, it could be printed later..

I think LXI's product and robot/save does this.

-----Original Message-----
From: Graap, Ken [mailto:keg@nwnatural.com]
Sent: Wednesday, October 23, 2002 1:30 PM
To: 'midrange-l@midrange.com'
Subject: RE: system save


I still don't know why IBM can't incorporate a SAVSYS process in an IPL
...

IPL to a certain point, and then while still in a restrictive state call
the BU program specified in some new system value. The BU process would
run SAVSYS and whatever else the user wanted to do in an unattended
restrictive state, then when the process ends, continue with starting up
the system using the QSTRUPPGM system value.

I seems so simple to me... Does anyone care to speculate on why this
presents such a technological challenge to IBM?

Kenneth

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


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

_______________________________________________
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.



This communication is confidential and may be legally privileged.  If you are 
not the intended recipient, (i) please do not read or disclose to others, (ii) 
please notify the sender by reply mail, and (iii) please delete this 
communication from your system.  Failure to follow this process may be 
unlawful.  Thank you for your cooperation.