|
-----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Graap, Ken >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, IBM looks to be very compartmentalized. There are problems in RPG like the inefficient returning of varying length strings from a procedure because ILE does not know what an RPG varying string is. And the ILE group does not seem to care to know. My guess is that the IPL group takes its responsibility of making sure all systems are go and getting the system started up. And it does not want any non IPL function to be run during IPL. I would have the save system run at PWRDWNSYS time. Where the savsys is done to a save file. And Restart(*YES) to bring the system back up when the save and power down are completed. Steve Richter
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.