Re: Call program(s) on subsystem start -- MIDRANGE-L

When you say the subsystem must be ending when the AG ends, you are overlooking the idea that the job may be ended by ENDJOB while the subsystem remains healthy. To end the SBS just because this job is ending, well, let's just say I would not advise that.

Jobs running in other subsystems would not suffer from the problem that Charles suggested. In those jobs, the notification steps would not run when the monitored subsystem ends (of course). But Charles suggested (rightly) that if the job running RAGE is ended, you WILL be notified, falsely, of SBS end.

But again, I like the concept. I get it.

dieter.bender@xxxxxxxxxxxx wrote:

CEE4RAGE will even run if you would do a pwrdwnsys *immed. didn't try
if it
runs at IPL time, after you pulled the plug to the power supply. I use
it in
all daemon jobs and in nearly all ILE programms for cleanups. I would
not
test the sbs status, if the monitorjob ends (its running within the
susbsystem it has to monitor!!!), the sbs has to be ended. To be shure
I
would do an endsbs as the last action in the monitor. BTW: for monitor
jobs
running outside of the sbs, you would have the same problem as chuck
mentioned, if someone ends the monitor job.

D*B

--------------------------------------------------
From: "Dennis" <iseries@xxxxxxxxxxxx>
Sent: Thursday, February 03, 2011 5:25 AM
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Re: Call program(s) on subsystem start

Further to that, ENDSBS . . . OPTION(*IMMED) may not give RAGE a

chance to

do its work. In most instances, monitors do best in observance -

rather

than reactive - mode. But I do like the concept. Maybe follow up

with a

check of SBS status.

"CRPence" <CRPbottle@xxxxxxxxx> wrote:

So a NEP is running in a user job in the subsystem, such that if
someone issues an ENDJOB and the RAGE transpires, the subsystem has

not

really ended but the NEP falsely concludes and reports the subsystem
has
ended.?

While I would generally accept that implementation for my own use

as

well [i.e. I find it perfectly acceptable, but I would also enable

the

job as self-submitted to a single-threaded job queue, behind itself],

I

do not see how that implementation is any less of a "work around"

than

some other suggestions that have been made, because the termination
processing would not be running in the subsystem monitor job itself;
i.e. the RAGE would need to occur as the effect of the subsystem
ending,
not as the effect of the user NEP job ending, in order to conclude

that

the subsystem is ending.

Regards, Chuck

On 2/2/11 12:28 PM, dieter.bender@xxxxxxxxxxxx wrote:

... the program simple has to be a NEP (never ending program)

CRPence on Wednesday, February 02, 2011 9:08 PM wrote:

On 2/2/11 11:57 AM, dieter.bender@xxxxxxxxxxxx wrote:

.... why using work arounds? as I mentioned before, there is an
API CEE4RAGE to register a procedure, called at end of activation
group. Just call a program in your startup in a named activation
group CONTROL and register CEE4RAGE for this Programm. At
Subsystem end, the activation group CONTROL will end an the exit
handler is called. You will find this technic in many of my open
Source stuff at my german website bender-dv.de, google translate
will assist you to find it there.

A good approach for a user job, but how does a user get such a
program to run in the OS subsystem monitor job? The intercept of
the end of the AG in a user job that runs "in" the subsystem will
detect when that job\activation group ends, not when the subsystem
[monitor job] has ended.

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

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my

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

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.