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

To me that is what the multiple priorities are for. Those jobs that you
are sure will not cause conflict can be submitted with a priority that
allows multiple jobs. Those with questions or with know issues run at a
"max by priority" of 1. For me this allows submission of small transaction
processing jobs that need to run immediately but I don't want to tie up a
tube to run it interactively.

Jim Horn


message: 4
date: Thu, 06 May 2010 13:46:33 -0700
from: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
subject: Why do people set up their batch submission defaults to run
multiple batch jobs at the same time?

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 email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.