RE: QSTRUP modification -- MIDRANGE-L

When you go to V4 you can probably use the STRRSTD parm on the CHGIPLA
command prior to shutdown.  I haven't tested to verify this would affect
what is done at startup time if you run the startup program via a STRSBS
for the controlling subsystem when you haven'' done an IPL (like after a
complete save) - but presume it should work.

Change IPL Attributes (CHGIPLA)  
                                                         
Type choices, press Enter.                               
                                                         
Restart type . . . . . . . . . . RESTART        *SYS     
Keylock position . . . . . . . . KEYLCKPOS      *NORMAL  
Hardware diagnostics . . . . . . HDWDIAG        *MIN     
Compress job tables  . . . . . . CPRJOBTBL      *NONE    
Check job tables . . . . . . . . CHKJOBTBL      *ABNORMAL
Rebuild product directory  . . . RBDPRDDIR      *NONE    
Clear job queues . . . . . . . . CLRJOBQ        *NO      
Clear output queues  . . . . . . CLROUTQ        *NO      
Clear incomplete joblogs . . . . CLRINCJOB      *NO      
Start print writers  . . . . . . STRPRTWTR      *YES     
Start to restricted state  . . . STRRSTD        *NO

Change IPL Attributes (CHGIPLA)                  


Type choices, press Enter.



Restart type . . . . . . . . . .   *SYS          *SAME, *SYS, *FULL

Keylock position . . . . . . . .   *NORMAL       *SAME, *NORMAL,
*AUTO...
Hardware diagnostics . . . . . .   *MIN          *SAME, *MIN, *ALL

Compress job tables  . . . . . .   *NONE         *SAME, *NONE,
*NORMAL...
Check job tables . . . . . . . .   *ABNORMAL     *SAME, *ABNORMAL, *ALL

Rebuild product directory  . . .   *NONE         *SAME, *NONE,
*NORMAL...
Clear job queues . . . . . . . .   *NO           *SAME, *YES, *NO

Clear output queues  . . . . . .   *NO           *SAME, *YES, *NO

Clear incomplete joblogs . . . .   *NO           *SAME, *YES, *NO

Start print writers  . . . . . .   *YES          *SAME, *YES, *NO

Start to restricted state  . . .   *NO           *SAME, *YES, *NO


... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com


        -----Original Message-----
        From:   Marc Zylka [SMTP:mzylka@netpath.net]
        Sent:   Thursday, February 12, 1998 11:09 PM
        To:     Midrange List
        Subject:        QSTRUP modification

        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)

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