RE: Restricted State

Jim, et al,

Except for situations like that described in my original post, I only IPL the system when applying CUME's, Groups, etc. , so setting a timer wouldn't work. But good thought.

I checked the Help text for QSTRUPPGM, and it said that it was invoked when the controlling subsystem was started. I'll run a test on our test system today, but I thought that, when the system was brought to a restricted state, only the controlling subsystem was running. Ergo, I thought that QSTRUP would not be invoked since the controlling subsystem (QCTL for us) was already started in those cases. But, as I said, I'll run a test.

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Monday, December 15, 2008 3:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: Restricted State

How you control this may be determined by how complicated your
system start up is...
Is it all in the qstruppgm?
One option to consider is a test in the qstruppgm, before starting other
subsystems, to determine if it is an odd time to be starting up, and if so,
perhaps hold the job queues? This is something that you would have to
evaluate quickly after system up, but at least the jobs won't suddenly go
active at a bad time.
Jim Franz

----- Original Message -----
From: "Jerry Adams" <Jerry@xxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, December 15, 2008 4:35 PM
Subject: Restricted State

A couple of weeks ago we had a power failure over the weekend that drained
our UPS, which caused the system to die. When I manually IPL-ed, one of
the things that happened was that the job scheduler submitted all of the
jobs that should have run but didn't. That's because the Recovery Action
is set to *SBMRLS. I'm going to change that to *NOSBM, but I thought it
would be just peachy keen if I could print a report, as part of an IPL
(especially after an abend) of the items in the scheduler.

Actually that part is relatively easy; I found the API's that I need and
have laid out the report and program logic. But I noticed that part of
the Help text for the *NOSBM option was for jobs that did not get
submitted because the system was in a restricted state. Not that I put it
into a restricted state too often, but it does happen, such as a Save 21.
Is there any way to tell if a system is *coming out of* a restricted
state? I found the API that would tell me if the system is *in* a
restricted state, but not the former.

Next, if there is a way to determine that a system is coming out of a
restricted state, where would I put such a test? Similar to the QSTRUPPGM
system value, which only kicks off if/when the controlling subsystem is
started (such as at IPL).

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

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