Yes I did see "test" and it makes it worse since you really don't know the outcome. I'd be careful sending jobs that are not clearly defined into the realm where it could freeze up the system. It happens, and I get several calls a year because something like this happens.
There are nearly 60 different routing entries in QUSRWRK using a multitude of classes that start with execution priorities of 7 (yes less than the console) and run up to 50. If you're lucky you get the default which runs at priority 50, then again depending on the job description you use that could be almost any one of them.
QSYSWRK was set up by IBM for specific reasons. So was QUSRWRK. Let's let them have those reasons and think about putting our jobs where they belong. Additionally it does not eliminate thread blocking it simply forces the threads to all run in *BASE which of course has limits just like all the other pools do. So the desired outcome is still not achieved.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Thursday, May 25, 2017 3:07 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Running a program interactively or in batch
You did see the word test right ? 😊
That would eliminate any thread blocking issues from the test mix.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
----------------------------------------------------------------------
message: 1
date: Thu, 25 May 2017 14:21:04 -0500
from: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
subject: RE: Running a program interactively or in batch
Yikes! Stay away from QSYSNOMAX! That will run in QSYSWRK and that's just a real bad place to run application software, unless of course you like making IBM i and it's components work harder........ (that slows everything
down....)
If you must, use QUSRNOMAX to achieve the same result in QUSRWRK, (still hurting overall performance if you're not careful).
Rather use a job queue attached to your QBATCH subsystem. As a default you'll find QTXTSRCH that has *NOMAX on the number of jobs. Now I understand that will not have as free of a hand with activations and memory as QUSRWRK/QSYSWRK but you won't sacrifice the system in the meantime.
Ordinarily the automatic performance adjustment will deal with threads/memory if it's turned on.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Thursday, May 25, 2017 2:12 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Running a program interactively or in batch
Is it in a memory or thread constrained subsystem ?
Try testing by running in QSYSNOMAX.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
