× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. October 2009

Re: Survey: STRTCP(*YES) or STRTCP(*NO) in IPL attributes

Tommy.Holden wrote:
FWIW I use the QSTRUP method...why? That way I can change the
QSTRUPPGM sys value to a temp program that does not start TCP for
performing system admin tasks that require multiple IPLs (i.e.
hardware replacement/maintenance, etc) without having to worry
about users and external applications trying to "tap into" the
system. When I have completed the tasks then I can change the
sys value back to the real start up program and do a quick IPL
and we're back up and running. I just feel that this is a
"cleaner" method but that's JMO


Of course the "start to restricted state" [STRRSTD] IPL attribute handles that, so it seems just as easy if not easier to simply use the CHGIPLA vs CHGSYSVAL before the PWRDWNSYS RESTART(*IPLA); no need for two programs\sources anyway, only one /change/ vs two so only the STRSBS of the controlling subsystem after the final IPL.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.