Re: single threaded job ,queue

If the requirement is that the steps in the job be run in a specific sequence, then I would suggest using a single controlling program to call each steps program in order. Relying on a single threaded job queue is risky at best. There's always the chance that someone might accidentally move a job to a different queue.

Calling each steps program from a controlling program ensures the steps happen in sequence and errors can be handled appropriately.

david

On Jun 27, 2008, at 12:04 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

I am suspicious that I am about to learn something new. :)

A new process has several steps which need to be run in order. I have
always just used a CL program and figured that the steps would run in
order, and the next piece would not start until the previous piece had
completed.

However, this line in the spec makes me think they are telling me
something. "You will probably need to utilize a single threaded job
queue(in conjunction with a new series of steps specific to this
process) to ensure synchronization of steps. " I am not sure what they
are saying.

Any comments, ideas, warnings, or suggestions will be more than welcome.

--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------

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