In my humble opinion you should create a command to start and stop NEPS.
(Server jobs or services as windows calls them.)
Then you can use an Auto Start Job Entry in the subsystem to start the
job. This enables you to end and restart the job without taking down
the whole subsystem. Yet if you do end the subsystem, the jobs will
start when the subsystem is restarted. But a twist is to have one ASJE
that then starts all the jobs for the subsystem. I do not like to start
jobs in my startup program for the entire system but just start the
Subsystems I need running.
You should have documentation of each server job and how to start them.
I like to program into the startup of the program a check to make sure
the job is 1. Batch, 2. Correct name, 3. Correct subsystem and 4.
Correct user. I generally use CLLE to do this and submit if not
correct.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Tuesday, March 24, 2009 3:29 PM
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.
midrange.com
