Return to the Systems Tips
RUN Away Jobs... CPU Hogs...
Did you try the Hoghunter option? I've use it a couple of times and it work's fine. In both times, i had only one job eating my cpu. In case you don't know, you can use the option 76 in control panel. This function is available since v3r2. I'm not in the office so I'm not sure if it is available in power machines.
A new control panel function (?76) is supported at V3R2, and PTFs MF11581, MF11960, MF11982, SF29221 at V3R1, which will invoke an internal VLIC mechanism to inspect for a high-priority CPU blocking job; if one is found, its priority may be lowered immediately by +20 (i.e., a priority 15 job will become a priority 35 job). This function thus provides a new alternative for the support person to correct system 100% busy symptoms (i.e., Processor Active light on solid) and no terminals are responding to operator requests.
There may be cases when the priority can not be changed, an example would be if the job found was QSYSARB or QLUS.
Hoghunter will not change the priority of any system jobs or VLIC tasks. This function may not be totally successful, as the real cause of the symptoms may be much more complex. After selecting control panel function ?76, one of the following status SRC sequences will be displayed on the control panel:
D600 0652 -> A900 2052 - a job's priority was changed > D600 0653 -> A900 2053 - system job was indicated, priority not changed D600 0654 -> A900 2054 - no CPU blocking job was found >(To clear one of these SRCs, it will be necessary to SIGNON the console). A message will be sent to QHST, and QSYSMSG or QSYSOPR describing the action(s) which were taken; and an internal VLIC LOG entry (1700 0301 or 1700 0302 or 1700 0303) will also be recorded to assist with any possible subsequent problem resolution; this may include another selection of control panel function ?76.
Back to Top
Securing Passwords
Booth,
I can't seem to find the general security manual at the moment. I think thats where the list is. But if you do a retrieve cl source on QSECCFGS you will see a list of user profiles that the CFGSYSSEC command automatically changes to Password *NONE. Here's the list from that:
QSYS/CHGUSRPRF USRPRF(QSYSOPR) PASSWORD(*NONE) QSYS/CHGUSRPRF USRPRF(QPGMR) PASSWORD(*NONE) QSYS/CHGUSRPRF USRPRF(QUSER) PASSWORD(*NONE) QSYS/CHGUSRPRF USRPRF(QSRV) PASSWORD(*NONE) QSYS/CHGUSRPRF USRPRF(QSRVBAS) PASSWORD(*NONE)HTH
Ron Hawkins
[report a broken link by clicking here]