Re: Call program(s) on subsystem start

[<dieter.bender@xxxxxxxxxxxx>]

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

D*B

--------------------------------------------------
From: "CRPence" <CRPbottle@xxxxxxxxx>
Sent: Wednesday, February 02, 2011 9:08 PM
Newsgroups: midrange.midrange-l
To: <midrange-l@xxxxxxxxxxxx>
Subject: Re: Call program(s) on subsystem start

> 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.
>
> Regards, Chuck
> --
> 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.