RE: Chagning Job Q definition

Thanks for the nice summary Charles! I will file that info away.It just
happens that none of those situations really apply to us. I pretty much use
it for my own purpose. I run a lot of single threaded jobs where job b is
based on what job a does and right on down the line..

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Monday, March 27, 2006 2:37 PM
To: Midrange Systems Technical Discussion
Subject: RE: Chagning Job Q definition

John,

One reason for a job to be submitted to a "single-threaded" job queue is
that only one copy of it can be run at once.  That way a fat figured
user who accidentally submits it twice won't harm anything.

The ways around that problem without limiting the job queue are:
1) Modify the programs involved to allow multiple copies to be run at
the same time
2) Modify the program to check to see if another copy is running.

Option 2 is usually the easier method.

The reason I don't like limiting the job queue is that while program A &
program B can't be run at the same time nor can program C & program D;
there is no reason why program A & program C can't be run at the same
time.  However, limiting the job queue will prevent program A & program
C from running together.

Unless you want a bunch of single purpose job queues.

Now, from you post, it doesn't sound like that's the reason you're
looking at doing this.  Instead, you're using QBATCH2 to separate your
work from the rest of the users and you want to minimize the effect you
have on other users by limiting the number of your jobs running.

That's a perfectly reasonable use of limiting the job queue.  

But you might consider that a max active of 1 is really limited.  In
addition, there may be a better solution.  Consider, if the system isn't
running at 100%, why shouldn't your work take those spare cycles?  You
might want to consider submitting your jobs at a different priority than
the users jobs are submitted at.  Look at the JOBPTY parm of the SBMJOB
command and the related MAXPTYx parms of the CHGJOBQE.  In addition,
consider the RUNPTY parm of the job description used when submitting the
job.

If you haven't look at it, you probably want to take a look at the work
management section of the infocenter.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzaks/rzaks1
.htm


HTH,

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:49 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Chagning Job Q definition
> 
> I'm interested in finding out how you would handle that 
> differently.We're a
> small shop and the only jobs that run in that sbs are the 
> jobs I submit. I
> just like to keep them separate for QBATCH so as not to 
> interfere with user
> requests,etc. 
>