|
Another question is why a SAVSYS must be done in restricted state in the first place. We can save Security Data, Configuration Data surely the most changed parts of the system. What's so magical about QSYS &c that a snapshot can't be taken while it's running? --Paul E Musselman PaulMmn@ix.netcom.nospam.com Kenneth wrote (in part):
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
