Each subsystem can have a list of jobs to start when the subsystem is
started. By putting your startup jobs in there, they will be restarted
if you ever have to restart the subsystem. Perhaps that is what they
are referring to.
Personally I like the documentation of having all your startup jobs in
one CL program, but I also like to be able to get all the correct jobs
to run when the subsystem starts. I guess it is really a matter of
preference.
I can see venders having their own subsystem that starts all the correct
jobs and giving instruction to add their subsystem to your startup
program.
What I do not like is a mixture of both for in-house stuff. Arg! It is
a pain to keep up with.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Friday, May 09, 2008 1:26 PM
To: Midrange Systems Technical Discussion
Subject: Anybody ever heard of "HUNT" or the phrase "startup job name"?
Somebody is asking us for a "startup job name" for launching the server
for one of our products, which he would like to add to a "HUNT startup
process."
I've never heard of such things. Around here, we just stick stuff in
QSTRUP.
Can anybody shed some light on what he's talking about?
--
James H. H. Lampert
Touchtone Corporation
--
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.
midrange.com
