Hi Roger
I just use a table to control what is started and stopped and when.
My experience is that you often need to end NEPS for a backup or other
process and then re-start them so you need to have a mechanism to do that.
Ending the subsystem and re-starting it seems a crude way of doing this,
plus often not every job in the subsystem should be ended or needs to be
ended.
Since you will probably end up having to explicitly start the process
sometimes, why not always start it that way.
AJE's are also not as visible - I like the visibility of code in a program,
or even better, a table. A table has some added advantages in that I can use
a column to *HOLD jobs and also associate an end process and other data with
the job.
That's just my take; I'm not suggesting that AJE's are bad, they're just not
my particular cup of tea.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Wednesday, 25 March 2009 11:29 a.m.
To: midrange-l@xxxxxxxxxxxx
Subject: RE: User-defined subsystems
Just curious why/why not? If you want something, say a NEP or whatever,
to run (without intervention) every time you start a subsystem what's
the alternative?
spanner@xxxxxxxxxx 03/24/2009 1:06:46 PM >>>
I have to say that I prefer not to use ADDAJE to start jobs - a call to
a
program or better yet a command to start a process always works better
from
my point of view.
Regards
Evan Harris
midrange.com
