Re: Why do people set up their batch submission defaults to run multiple batch jobs at the same time?

I believe that the real problem is that people tend to change the *JOBQs
default instead of creating new jobqs tailored to specific requirements. I
don't know if it is due to laziness or ignorance :-(

Regards,


Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Thu, May 6, 2010 at 4:16 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

I admit that it can be nice not to have to wait for another user to
notice his or her locked-up compilation job, but what if you've got two
batch-by-design jobs that could get into a fight with each other if
allowed to run concurrently?

For probably the fourth or fifth time, I had to clean up a mess that was
partly caused by two batch jobs (running the same program!) getting into
exactly that sort of fight, for exactly that reason.

Isn't "running jobs sequentially, one at a time" the essence of batch
processing?

Why it took me until now to fix it so that they'd be explicitly run
through a "normal" batch queue instead of the default "abby-normal" one,
I dunno.

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