Yes. Since the start of RISC, the system made a decision that it could do
a better job of tuning than we could, and it takes over. It is very
complicated.
The bottom line is likely that you have jobs that go way past their end of
time slice, and are consequently punished.
You could change the time slice for the class QINTER for a longer time
slice, and then go execute the SPENDMONEY command (a favorite at IBM), or
reengineer your applications.
My jury is mixed as to weither this was good move by IBM, but they have a
lot more data at hand to make these decisions.
Al
Al Barsa, Jr.
Barsa Consulting Group, LLC
400>390
"i" comes before "p", "x" and "z"
e gads
Our system's had more names than Elizabeth Taylor!
914-251-1234
914-251-9406 fax
http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com
<c.chambers@xxxxx
om>
Sent by: To
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s@xxxxxxxxxxxx cc
Subject
04/25/2007 05:50 Interactive job adopting priority
AM 89 !!
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
We had a situation whereby all interactive jobs seemed to adopt the
priority of 89 (rather than the default 20 they normally run under) and
all sessions seemed to grind to halt - understandably.
Is this an automatic action taken by OS400 when certain conditions are
met - or do we have a rogue operator changing the priorities ?
Ideas??
--
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.
midrange.com
