Re: Subsystem

Yes, however, may I suggest you set the subsystem number of jobs at *nomax, and limit the job queue to a more appropriate number based on how much memory you have set aside for batch? I'll pick 10 max jobs for that queue as a starting point. If you find the memory is trashing (lots of faults and non-database paging) then drop that number down until you can still get work done, but the memory is not getting beat up. You could of course add memory to that pool if you have sufficient memory.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/15/2013 2:01 PM, John Mathew wrote:

We have two departments Billing and Finance, batch jobs of both departments are going to same job queue QBATCH.
jobs submitted by one department should not conflict with those of other.
I have a job queue KIS which is attached to subsystem QBATCH.
the number of maximum jobs in subsystem allowed is one and Job queue is also one.
If I increase maximum jobs in subsystem to *NOMAX and KIS job queue to *NOMAX will it solve my problem.
means can I run multiple jobs in same jobq.

Can you please advise.
subsystem description: QBATCH Status: ACTIVE Subsystem description . . . . . . . . : QBATCH Library . . . . . . . . . . . . . . : QSYS Maximum jobs in subsystem . . . . . . : 1 Sign-on display file . . . . . . . . . : QDSIGNON Library . . . . . . . . . . . . . . : QSYS System library list entry . . . . . . : *NONE Seq Job Max ---------Max by Priority---------- Nbr Queue Library Active 1 2 3 4 5 6 7 8 9 10 QBATCH QGPL 10 * * * * * * * * * 20 QS36EVOQQ QGPL *NOMAX * * * * * * * * * 40 KIS QGPL 1 0 0 1 1 1 * * * * 50 QTXTSRAH QGPL *NOMAX * * * * * * * * * John
--