|
Marc Zylka wrote: > > I'm curious, how do most people set up QSTRUP so that > most of the subsystems such as QINTER, QSPL, etc. > don't start up? I'd like to prevent the starting of these > subsystems when doing system saves, PTF installs, etc. > so that no one signs as QSTRUP is run. Once I > check everything out, then I'd like to start them up. > > I've thought of setting up a data area, say STARTALL, > and set the one and only character to 'Y' for normal > operations and 'N' for the above explanation. Or, is > there an even easier way? > > TIA, > Marc Zylka (mzylka@netpath.net) Marc, THat is the way I do it at many sites, and it works great. After checking everything out, we just change the dataarea, and call the program again. -- Pete Massiello OS Solutions International Phone: (203)-744-7854 Ext 11. http://www.os-solutions.com mailto:pmassiello@os-solutions.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.