IT Jungle: Cleaning Up Excessive Job Logs on Your IBM i Box

mop and bucket

IT Jungle just published my latest tip on detecting and deleting excessive job logs on an IBM i machine.

To view this article, click here.


This post sponsored by Hertvik Business Services (HBS). HBS provides IT consulting and content production services for the IT industry, including review and consulting on IBM i (AS/400) high availability environments. Feel free to contact Joe Hertvik for a free consultation and estimate for your projects.

Follow Joe Hertvik on Twitter @JoeHertvik. You can also add Joe to your professional network on LinkedIn by clicking here.

About Joe Hertvik

Joe is the owner of Hertvik Business Services, a service company providing written white papers, case studies, and other marketing content to computer industry companies. He is also a contributing editor for IT Jungle and has written the Admin Alert column for the past ten years. Follow Joe Hertvik on Twitter @JoeHertvik. Email Joe for a free quote on white papers, case studies, brochures, or other marketing materials.
This entry was posted in IBM i Tech Info. Bookmark the permalink.

2 Responses to IT Jungle: Cleaning Up Excessive Job Logs on Your IBM i Box

  1. Robert Clay says:


    I do something similar on one of my LPARs where this had become a problem.

    I follow it up with a daily scheduled job to reclaim the spool storage during non-peak hours, as well because it has relatively few resources (and every little bit helps). This may also be helpful for LPARs that aren’t IPL’d regularly.

    Schedule a command like this (adjusted for the environment, of course):

    LOG(4 00 *SECLVL)

    Ironically, it produces a joblog itself, but isn’t necessary. 🙂

    • Joe Hertvik says:

      Thanks, Robert. We don’t usually run RCLSPLSTG because we have it set up i our system values, but this is a great idea too. It’s amazing how much space spooled files can take up, if you let them. On one of my client systems, it was up to 10% of usuable storage.

      Love that PRINTNOT output queue name. Have to put one of those on my system.

Comments are closed.