Re: Submitting Jobs to QBATCH -- MIDRANGE-L

I try to set up clients to have job queues based upon department within
location. That way, the users have only themselves to whine at.

For example, I've got a client who has 11 different locations. There are 2
to 3 departments within each location, i.e., Accounts Payable in Denver. If
somebody in A/P in Denver submits their month-end close, the sales
department there is not affected since the applications are mutually
exclusive.

The company does, however, have a common general ledger file. Any job that
updates the G/L gets routed through a job queue named, oddly enough,
GLUPDATE. Since we set them up this way, they've never had a problem with
jobq queue contention or record locks in the G/L.

Paul Nelson
Braxton-Reed, Inc.
630-327-8665 Cell
708-923-7354 Home
pnelson@braxton-reed.com
----- Original Message -----
From: "Jeff Crosby" <jlcrosby@DILGARDFOODS.COM>
To: <midrange-l@midrange.com>
Sent: Tuesday, September 17, 2002 9:30 AM
Subject: Re: Submitting Jobs to QBATCH


> Justin Houchin wrote:
>
> > I need some help. We have are QBATCH subsystem setup to only
> > run one job at a time. This is so that when running sales reports, only
> > one will run at a time
>
> I don't think it's a good idea to run batch jobs in QINTER either.
>
> Did you know:
>
> 1) A subsystem can have multiple job queues.  Our QBATCH subsystem has 4
> job queues:
>
> QBATCH:  does production work.
> DQUERIES:  handles Query/400 submissions.
> PGMJOBQ:  is for me only so my compiles don't hold anything else up(and
> vice versa <g>)
> NIGHT:  Gets released at night only for various housekeeping, file
> reorgs, and whatnot.
>
> 2) A single job queue can be like 9 job queues in 1 with the use of
> JOBPTY parm when submitting.  With the CHGJOBQE command, you can allow X
> number of jobs from a job queue to be active at once, yet only a single
> job at a time for a job queue priority.  The following is how we have
> QBATCH set up.  Even though 4 jobs can be active from QBATCH job queue,
> they are single threaded within priority.  You could submit sales jobs
> with a JOBPTY(7) for example, and they would not interfere with JOBPTY
> 1-6 and 8-9.  HTH.
>
>                          Change Job Queue Entry (CHGJOBQE)
>
>   Type choices, press Enter.
>
>   Subsystem description  . . . . . > QBATCH        Name
>     Library  . . . . . . . . . . .     *LIBL       Name, *LIBL, *CURLIB
>   Job queue  . . . . . . . . . . . > QBATCH        Name
>     Library  . . . . . . . . . . .     *LIBL       Name, *LIBL, *CURLIB
>   Maximum active jobs  . . . . . .   4             0-1000, *SAME, *NOMAX
>   Sequence number  . . . . . . . .   *SAME         1-9999, *SAME
>   Max active priority 1  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 2  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 3  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 4  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 5  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 6  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 7  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 8  . . . . .   1             0-99, *SAME, *NOMAX
>   Max active priority 9  . . . . .   1             0-99, *SAME, *NOMAX
>
> --
> Jeff Crosby
> Dilgard Frozen Foods, Inc.
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
>
> The opinions expressed are my own and not necessarily
> the opinion of my company.  Unless I say so.
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>