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

I'm a little late to the discussion, but I use ALCOBJ OBJ((LIBRARY/PROGRAM *PGM *EXCL)) WAIT(1), at the beginning of the program and keep the lock until it is complete. If I can't get a lock I know that it is already running.

Duane Christen


--


Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx

Visit PAETEC.COM


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, May 10, 2010 10:31 AM
To: Midrange Systems Technical Discussion
Subject: Re: Why do people set up their batch submission defaults to run multiple batch jobs at the same time?

Vern Hamberg wrote:

Of course, only when I know that
it'll have no effect on other activity.

Smart. I've been known to move compilation jobs over to the QINTER queue when the QBATCH queue was clogged and the system was relatively quiet; while it's certainly possible for two compilation jobs to get in a fight, it's not especially likely.

And over the weekend, I thought of a simple, but elegant way to keep programs from fighting with each other, even if their job queue does get changed to dispatch multiple jobs concurrently.

For the moment, though, since there's only one of me, and I have a brushfire to put out elsewhere, just having them in a job queue that keeps them from fighting should do.

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