RE: job queues

Let me add a little detail that may suggest some alternatives.

When you use the SBMJOB command, the default JOBQ is QBATCH. You can change the requested JOBQ in SBMJOB.

QBATCH is configured out of the box as a one-job-at-a-time *jobq in subsystem QBATCH.

QINTER is configured as a *nomax outq in subsystem QINTER.

There are several other jobq's set up by default in various subsystems to optimize various kinds of work. One I find useful for the type of work you're doing is QUSRNOMAX in QUSRWRK.

Many admins have set up other subsystems and jobq's for their own specialty work and changed the defaults. IBM includes subsystem QPGMR, but doesn't start it by default. Before you make any assumptions, check the subsystem and jobq definitions.

There are other ways besides SBMJOB to put jobs on jobq's. 5250 sessions, for instance, are started through QINTER jobq.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Hoteltravelfundotcom
Sent: Monday, July 15, 2013 10:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: job queues

Yes I can't make this change on my own. There must be a reason for the
single thread. Let's say I run my jobs in QSPL or even QINTER ( Qinter was
suggested to me by a consultant. For over the weelkend it would be fine).
I think they are still sharing the same que. So you have a situation where
testing is impossible.


On Mon, Jul 15, 2013 at 11:29 AM, Jerry Draper
<midrangel@xxxxxxxxxxxxx>wrote:

Use nomax jobq qsysnomax if you want a job to run immediately without
hanging up users who are submitting to a single threaded jobq.

J


On 7/15/2013 8:24 AM, Hoteltravelfundotcom wrote:

What do you think of a shop which has only 1 jobs que? SHouldn't there

be a

test system
for a programmer? This has happened twice now. I have a long running
RPG program, working over the weekend, it didn't sink in the first time.
so then its still running and causes some jobs to not run. Consequently
subsystems
did not come up. I don't recall in many years either a system that shuts
down every night and comes back up.
It is frustrating. Am I wrong in thinking that they should have more

than 1

jobq, that is, that other jobs can run at the same time that there should
be a test system? Is it possible for a newcomer to not make these

mistakes?

I suppose I am to blame that it happened again. BUt I really
have trouble acclimating to this type of environment, and not sure what

can

be done.

--
Jerome Draper, Trilobyte Software Systems, since 1976
iSeries, Network, and Connectivity Specialists -- iSeries, LAN/WAN/VPN
Representing WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431; www.trilosoft.com

--
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.

--
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.