On Dazel 3.3 job databases tend to grow very large, sometimes up to 200 or 300 MB per JQM. Stopping or starting the JQM won't solve this problem; you'll have to recreate the JQM:
Stop the JQM:
# stop_server jqmDelete the JQM:
# config_server -d jqmDon't worry about the delivery pathways, the CM will still hold their configurations.
Recreate the JQM:
# config_server -t JQM jqmIf you have a special start order for the JQM, set it now:
# config_server -u -x"server-start-order 700" jqmThis will bring back the job database to approximately 400 KB.
If you found this useful, here's more on the same topic(s) in our blog:
- Growing System Dump Device usage with HPOS on AIX
- HPOS sizing rules
- HP Output Server introduction
- Number of jobs per logical destination
- HPOS maintenance
UNIX Health Check delivers software to scan Linux and AIX systems for potential issues. Run our software on your system, and receive a report in just a few minutes. UNIX Health Check is an automated check list. It will report on perfomance, capacity, stability and security issues. It will alert on configurations that can be improved per best practices, or items that should be improved per audit guidelines. A report will be generated in the format you wish, and the report includes the issues discovered and information on how to solve the issues as well.
Interested in learning more?
Interested in learning more?




