Re: Option 21 Save - QSTRUPPGM -- MIDRANGE-L

Good News Everybody!

A new search engine is coming soon.

As a stop gap measure, we are using Google's custom search engine service.

Noah Sandestin wrote:

<<SNIP>> we IPL the
system after the save finishes but our operator is having to
wait for the system to start, then end back to a restricted
state before he can IPL the system. <<SNIP>>

Regarding the responses about controlling the QSTRUPPGM processing... Consider that the system still actually /starts/, irrespective of either limiting or eliminating the work in the startup program. The controlling subsystem, the QSYSWRK [& possibly other mandatory startups], plus any other autostarts [AJE & PJE] effected by any subsystems started will still transpire.

If the manual procedure of ending the system again to restricted state is maintained, then consider that the ENDSBS *ALL request can add the parameter request to ENDOPT(*NOJOBLOG) which will limit the unnecessary work of spooling joblogs; i.e. speed up the ending of the system. Also FWiW the operator need not await full [or partial, given modified QSTRUPPGM processing] completion of the startup before issuing the ENDSBS.

Regards, Chuck

This mailing list archive is Copyright 1997-2026 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.