IBM connected in remotely. It was believed to be related to:
Machine ineligible condition threshold reached.
Ineligible condition threshold reached for pool 02.
Caused by some serious choking done by automatic performance adjusting by
our quarterly IPL. It was recommended that I put a job schedule entry for
Sunday night or Monday morning to do a
CHGSHRPOOL POOL(*BASE) ACTLVL(....)
to correct any shortages caused by the IPL. Then again, nothing stopping
me from adding that to my version of the program stored in WRKSYSVAL
QSTRUPPGM. Being a Mimix shop, I could also add it to the program called
by the switch process. Our IPL could happen on a Saturday early afternoon
(if IBM ever gets our @#$% tape drive to actually get through a whole save
without being replaced - #$% HUGE customer dissat issue). We always do
our Mimix switch backs on Sunday night at a set time (allows scheduling of
outage). It's up to you.
It was also recommended that I WRKSYSVAL QPFRADJ and change it from 2 to
3. This will turn off the automatic adjustment at IPL and just use
automatic adjustment based on system performance. The only advantage,
IMHO, of an IPL adjustment is if you just added a bunch of new memory. I
think I can take care of that on the few occasions that happens.
Apparently the IPL adjustment ignores any minimums and maximums you set in
WRKSHRPOOL.
http://www-912.ibm.com/s_dir/SLKBase.nsf/1ac66549a21402188625680b0002037e/f1ade588854219988625738a0061150b?OpenDocument
Rob Berendt
midrange.com
