Re: QCTL - restricted state

My solution was to build a startup program tied to a CONSOLEMON user
profile. When you signed on, it just sat and waited for messages to arrives
from a data queue. I built a database of commands to execute and put the
commands into the job scheduler. The job scheduler would call a command
that would send the message at the correct time and the process would
start. Everything was created at highest authority so no one but the sec
officer or that user profile could make changes. When it was done running
the command it would wait for the next one or do a shutdown and restart if
requested.

This is how we did all the full system backup without an operator.

I still have the source code if you are interested. What I should do is put
it up on www.think400.dk.




On Mon, Jun 10, 2013 at 2:37 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Paul,

If you are in a restricted state to start with, meaning the only device
on the system that is running is the console in the controlling
subsystem, then the only way to run the save is with submit *NO.

If you bring up the system far enough that the BRMS monitor job ( not
the same as the console monitor ) can be running, then you can run it
in the controlling subsystem.

I suspect your going to get the best luck by bringing the system most
of the way up, and then having the control group take the system back
down into restricted state, but then you will have a system that's
unresponsive (by design) with an SRC code to show the save is running
until the save finishes and BRMS restarts it. I've never really liked
this approach since you can't get to the console in the event of a
problem with the save.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 6/10/2013 3:22 PM, Steinmetz, Paul wrote:

No, save is submitted from AJS, either immediately or scheduled.
STRBKUBRM CTLGRP(SAVSYS05) SBMJOB(*CTLSBS) OMITS(*IGNORE)

-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx [mailto:

midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer

Sent: Monday, June 10, 2013 4:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: QCTL - restricted state

Since you are by definition in an attended state with console in a

restricted state, you run your save interactively, so submit is *NO.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 6/10/2013 3:07 PM, Steinmetz, Paul wrote:

Following an IPL to restricted state, I would like to submit a BRMS

system save to the controlling subsystem, QCTL.

However, even though QCTL is up, its state is restricted, so the

save doesn't run, jobq QCTL not active.

Total Subsystem Active
Opt Subsystem Storage (M) Number Jobs Status
QCTL .00 013885 1 RSTD
I need to STRSBS QCTL, but this will start the process of bringing

up the entire system, QSTUPJD is called.

It has been suggested to have a 2nd QSTRUP, that only starts QCTL

and changes QSTRUP back to normal.

One issue is that QSTRUPJD is not called until you come out of

restricted state.

Instead of restricted state IPL, I tested a QSTRUP pgm that only

starts QCTL.

However, QSYSWRK starts by default, QSYSWRK auto start entries then

start QHTTPSVR, Q1ABRMNET, ZENDSVR.

At this point, sys is not up, but also not restricted.
Has anyone else experimented with QCTL and restricted state?
Total -----------Subsystem

Pools------------

pt Subsystem Storage (M) 1 2 3 4 5 6 7 8 9 10
QCTL .00 2
QHTTPSVR .00 2
QSYSWRK .00 2
Q1ABRMNET .00 2
ZENDSVR .00 2
--

--

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