RE: BRMS and bare bones System Save

[rob@xxxxxxxxx]

You can start numerous other things before starting your controlling 
subsystem.

Situation:
We ran a downtime.  Associate got the system in a restricted state.  Ran 
the RCLSTG, saves, etc.  Then ran our VARYON program.  (As a rule, we 
don't like to modify QSTRUP.)  Noticed some things weren't quite right, 
even though most things were working.  Then, with WRKACTJOB, I noticed 
that the controlling subsystem was in END state.  As a general rule we IPL 
after the RCLSTG, saves, etc.  When you only get once every 8 weeks to IPL 
to apply ptf's, etc, you take advantage of it.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





rick.baird@xxxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/16/2004 08:33 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, 
midrange-l-bounces@xxxxxxxxxxxx
Subject
RE: BRMS and bare bones System Save







Rob, Mike,

Thanks, that's good to know.  (20 years in the 'bidness' and I've never
manually restricted a system - pathetic ;)

Again, pardon my ignorance, can I start QSYSWRK and QSERVER before QCTL?
or must QCTL be running to start any other subsystems.

Are there any other ramifications of starting QCTL after the other two 
have
started?

Thanks again,

Rick




  
                      rob@xxxxxxxxx   
                      Sent by:                    To:       Midrange 
Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 
                      midrange-l-bounces@m        cc:    
                      idrange.com                 Subject:  RE: BRMS and 
bare bones System Save 
  
  
                      07/15/2004 06:05 PM   
                      Please respond to   
                      Midrange Systems   
                      Technical Discussion   
  




No, if your controlling subsystem shows up as a status of END in
WRKACTJOB, it will then be started.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





rick.baird@xxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/15/2004 05:04 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: BRMS and bare bones System Save







thanks, Tom and Micheal.

Forgive my ignorance, but isn't the controlling subsystem still running in
order to operate the console and run the backup?

If so, is there any reason I can't just call the QSTRUP?

Or does STRSBS SBSD(QCTL) do something other than run QSTRUP?

If so, will it do any of these things if QCTL is still already running, or
bomb with a 'already in requested state' type of message?

as you see from my list, I want to bring up JUST the QSERVER and QSYSWRK
and restart my IXA servers before continuing with the backup,  and THEN
get
everything else up and running.

Thanks a ton!

Rick

-------original message--------
>From restricted state you start your controlling subsystem.  This should
>run your QSTRUP (as specified in SysVal).

--------------
1.  end the IXA servers, in order using VRYCFG (this is important, because
2 of them are failovers to the others and have to be shut down in order).
2.  wait for these servers to shut down.
3  ENDSBS *ALL *IMMED
4.  save *SAVSYS
5.  save *ALLIBM
6. save '/QFPNWSSTG/*' (the IXA server data blob)
7.  STRSBS QSERVER and QSYSWRK
8.  STRTCP
9.  bring up the IXA servers.
10.  save 3 domino servers, and several other things
11.  bring the system back up to it's original state.




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.