× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



oh ok got it, so you mean to say multiple jobs can run in single subsystems and all are active.
 


________________________________
From: "rob@xxxxxxxxx" <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, 3 April 2013 1:44 PM
Subject: Re: subsystem.

Ok, you're talking about TWO different things:
One, QBATCH the subsystem.
Two, QBATCH the job queue.
If you do a DSPSBSD QBATCH, and then take 6. Job queue entries, you may
see a list like
Seq  Job                      Max
Nbr  Queue      Library    Active
10  QBATCH      QGPL            7
11  CHECKJOBQ  QGPL            1
12  CLAIMEVOKE  QGPL            1
13  CLAIMJOBQ  QGPL            1
14  QBATCH1    QGPL            1
15  EISJOBQ    QGPL            1
16  BANKXMIT    QGPL            1
17  QBATCH2    QGPL            1
18  QBATCH3    QGPL            1
19  QBATCH4    QGPL            1
20  QS36EVOKE  QGPL        *NOMAX
21  BACKUPLOG  QGPL            1
22  QBATCH5    QGPL            1
...
if you still can't figure this out, you're in over your head and contract
someone to solve this problem for you.
Because if you can't get this we're going to have a hell of a time trying
to explain to you setting up your routing entries so that you line up your
subsystem pools with your system pools.  I really mean no disrespect.  I
just think you'll be much better suited to multiple job queues in this
single subsystem.

Here's another example.  I have a system with NO qbatch subsystem running.
However, if I do DSPSBSD QBASE I will see:
Seq  Job                      Max
Nbr  Queue      Library    Active
  10  QBATCH      QGPL            1
  50  QINTER      QGPL        *NOMAX
100  QCTL        QSYS        *NOMAX
150  QS36MRT    QGPL        *NOMAX
200  QS36EVOKE  QGPL        *NOMAX
250  QBASE      QGPL        *NOMAX
1000  DSKSUM      ROUTINES        1
9898  ONEATATIME  ROB              1
9998  RTVDSKINF  ROUTINES        1

So if I run
SBMJOB CMD(...) JOBQ(QBATCH) JOB(A)
and
SBMJOB CMD(...) JOBQ(QBASE) JOB(B)
or even
SBMJOB CMD(...) JOBQ(ROUTINES/DSKSUM) JOB(C)
they all run in the QBASE subsystem.  If I do WRKACTJOB SBS(QBASE) I will
see job A, B, C all active.

The only other possible conflict (trying to get in your mind) is DSPSBSD
QBATCH, option 1.  What do you have for
Maximum jobs in subsystem  . . . . . . :  *NOMAX
Normally this is set to *NOMAX.



Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.