I had a job schedule entry which may be really old. So old that it causes more harm than good. It was like this:
ADDJOBSCDE JOB(OPBASEPOOL) CMD(CHGSHRPOOL POOL(*BASE) ACTLVL(1880))
FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*MON) SCDTIME(040000)
SAVE(*NO) RCYACN(*SBMRLS) JOBD(*USRPRF) JOBQ(*JOBD)
USER(ROB) MSGQ(*USRPRF)
TEXT('QPFRADJ adjustment at IPL can be too low.')
I'm guessing that at the time I created this entry I was actually raising the base activity level. Every Monday, after a possible weekend IPL (which is really only done quarterly) up QBASEACTLVL. However, in this era, it has the reverse effect of lowering the base activity level.
Dangerously low. Like, no jobs can be started, not even the system console job, low. Like unscheduled IPL low. And having to force IPL, outside of the OS, from the HMC (from home).
DSPLOG PERIOD((*AVAIL *BEGIN)) MSGID(CPF1805 CPF0909)
System value QBASACTLVL changed from 3248 to 1880.
Ineligible condition threshold reached for pool 02.
That was one case with IBM. The second case with IBM was why is the auditing on their system values so weak?
DSPJRN JRN(QAUDJRN) RCVRNG(*CURCHAIN) FROMTIME(093019 0400)
JRNCDE((T)) ENTTYP(SV)
and
DSPLOG PERIOD((*AVAIL *BEGIN)) MSGID(CPF1805 CPF0909)
System value QBASACTLVL changed from 2707 to 1880.
System value QBASACTLVL changed from 3248 to 1880.
Ineligible condition threshold reached for pool 02.
System value QBASACTLVL changed from 2707 to 1227.
Neither of the above solve this riddle: What changed the system value QBASACTLVL to 3248?
Both show entries from QPFRADJ (and elsewhere)
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
midrange.com
