Re: QSTRUP modification

["Roger Vicker" <rvicker@xxxxxxxx>]

What I've done for my clients is have QSTRUP send an inquiry message to QSYSOPR.
RCVMSG using a wait of ten minutes.
If the RCVMSG times out or if an operator is available and answers "G" it starts
the sub-systems etc.
If the operator answers "C" I short cut the startup because I want to do some
"system" things without giving the users their sub-system.

This way I still can have an un-attended IPL and when I am doing installs or
upgrades it's easy to prevent the extra startups.

Roger Vicker, CCP

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)

--
*** Vicker Programming and Service *** Have bits will byte ***
P.T. Barnum would DEFINITELY approve!




+---
| 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
+---