RE: Chagning Job Q definition

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

Oh yeah,

One more piece of advice.

If you're going to have programs that depend on the fact that only one
job from a particular job queue is active at once; then QBATCH2 is a
poor choice of for a name.

Instead, call it SINGLE, BATCHONE or something else that makes it
obvious that you expect only one job to be run at a time from the given
queue.

That way your successor won't get bit when he gets his new i6 or
whatever and say "hey with all this extra power we can run multiple jobs
out of QBATCH2 now to."

Actually, I personally tend to frown on limiting job queues like this.
There's usually a better way to handle the problem.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Candidi
> Sent: Monday, March 27, 2006 1:13 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Chagning Job Q definition
> 
> We created an additional jobq a while back (QBATCH2) where we 
> run various
> jobs throughout the day. How do I permanently change the 
> definition of that
> jobq to only allow one job to run at a time. Currently, we 
> submit a CL prog
> to do that but since we only use this on demand, I'd rather 
> just set it up
> permanently that way. Thanks in advance for any info
> 
>  
> 
> John A Candidi
> 
> Rutgers Insurance Companies
> 
> IT Director - AS/400 Manager
> 
> 856-779-2274
> 
>  
> 
>  
> 
> -- 
> 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.
> 
>