# IBM i (AS/400) System Health Check Checklist > Source: https://netray.co/tools/ibm-i-as400-system-health-check-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A practical weekly and monthly health check for IBM i partitions running ERP such as JD Edwards World, covering storage, jobs, patches, security and recovery. ## Category erp-operations ## Erp IBM i / JD Edwards World ## Audience - IBM i administrator - System operator - IT manager ## Tool **Kind:** checklist **Groups:** #### Storage and capacity **Items:** **Text:** Disk used is below your internal alert level (many shops use 70 to 80 percent) on WRKSYSSTS or WRKDSKSTS **Critical:** true **Text:** Storage low action (QSTGLOWACN) and limit (QSTGLOWLMT) system values are set deliberately **Critical:** true **Text:** No disk units reporting errors or in a degraded state on WRKDSKSTS **Critical:** true Growth trend of the largest libraries reviewed since last month Old save files, spool files and job logs purged under a written retention rule Journal receivers are detached and cleaned up so they do not fill the disk Temporary storage and permanent address usage looks normal #### Jobs, subsystems and performance **Items:** **Text:** Required subsystems (QINTER, QBATCH, QSERVER, ERP subsystems) are active on WRKSBS **Critical:** true No long-running or looping jobs consuming CPU on WRKACTJOB **Text:** Jobs in MSGW status are reviewed and answered or ended **Critical:** true Job queues are not backed up with held or stuck batch jobs on WRKJOBQ CPU and memory pool faulting are within normal range on WRKSYSSTS Performance adjuster (QPFRADJ) is set according to your tuning policy Nightly batch cycle finished within its normal window #### Messages and logs **Items:** **Text:** QSYSOPR message queue reviewed and no unanswered inquiry messages **Critical:** true History log (DSPLOG QHST) checked for hardware, storage and security events **Text:** Problem log (WRKPRB) has no open hardware or LIC problems **Critical:** true Product activity log reviewed for repeated errors Job logs from failed ERP batch jobs are retained for diagnosis #### Patching and release **Items:** **Text:** IBM i release is still within IBM support for your hardware **Critical:** true Current Technology Refresh and PTF group levels are known and recorded Cumulative PTF and database group PTFs reviewed against IBM recommendations Pending IPL PTFs identified and a patching window planned Licensed program and third party product release compatibility confirmed before upgrades Hardware maintenance contract and HMC or console access verified #### Security **Items:** **Text:** Security level (QSECURITY) is 40 or higher and documented **Critical:** true **Text:** Default and shared profiles have passwords expired, or are disabled, as required **Critical:** true **Text:** Users with all-object authority (*ALLOBJ) listed and justified **Critical:** true Profiles inactive for 90 days or more reviewed and disabled Audit journal (QAUDJRN) active and receivers retained as policy requires Exit points and network access (FTP, ODBC, remote command) are restricted to approved users Sign-on attempts and failed logins reviewed #### Recovery and continuity **Items:** **Text:** Last full system save and last daily save both completed without errors **Critical:** true **Text:** Backup media or cloud copy is stored off the production site **Critical:** true **Text:** A restore test has been performed in the last 12 months **Critical:** true High availability or disaster recovery replication is current, if you have it UPS and power events checked, and shutdown procedure documented **Scoring Note:** Run this weekly for operations items and monthly for patching and security. Any unchecked critical item should be treated as an open issue with an owner and a date. ## Content **Intro:** Many IBM i systems run for years with little attention, which is exactly why problems such as a full disk or an unpatched release come as a surprise. This checklist gives an administrator a repeatable health check for the partition under a JD Edwards World or similar ERP. **Sections:** #### How to use the checklist **Body:** Work through the groups in order and tick each item only after you have looked at the real system, not from memory. Items marked critical are those where a miss can cause an outage, data loss or a security finding. Export the completed list to PDF or Excel and keep it with your change records so you can show trend and ownership. Operations items are suitable for a weekly rhythm, while patching and security items fit a monthly or quarterly cycle. #### Commands and screens behind the checks **Body:** Most checks are one command. WRKSYSSTS shows disk percentage used, CPU and memory pools. WRKACTJOB shows active jobs, status and CPU. WRKDSKSTS shows disk unit health. DSPLOG QHST reviews the history log, and WRKPRB shows logged problems. WRKPTFGRP and DSPPTF report patch levels. DSPSYSVAL shows values such as QSECURITY and QAUDLVL. Many shops also use the SQL services in QSYS2 for the same data, which makes the check scriptable. **Bullets:** - WRKSYSSTS: disk, CPU, memory pools - WRKACTJOB and WRKSBS: jobs and subsystems - WRKPTFGRP: PTF group levels - WRKPRB and DSPLOG QHST: problems and history - WRKUSRPRF and DSPSYSVAL: security #### Common mistakes **Body:** The costliest mistakes are letting disk climb unchecked until the system halts, never testing a restore, and leaving default or shared profiles active. Another is patching the operating system without checking the ERP vendor and third party tool compatibility first. For ERP systems, remember the check does not stop at the platform: confirm that the nightly batch cycle, the integrations and the reports that users rely on actually ran. A healthy partition can still host a failed batch process. **Cta:** If you want these checks run automatically and summarized in plain language for your IT or operations team, Netray can discuss a read-only monitoring approach. The checklist works fully by itself. **Faq:** #### How often should I run an IBM i health check? **Answer:** Daily glance checks of messages, jobs and backups, a weekly review of disk and performance, and a monthly or quarterly review of PTFs and security is a common pattern. Adjust frequency to how critical the system is and how much it changes. #### What disk percentage is too high on IBM i? **Answer:** There is no single value, but many administrators set an alert between 70 and 80 percent and act well before 90. Growth rate matters more than the number, as a system that is rising quickly needs attention sooner. #### Does this apply to JD Edwards World specifically? **Answer:** The checks are platform level, so they apply to any IBM i workload. They are especially useful for JD Edwards World because many installations have run for years with one administrator and few written procedures. #### Can I automate these checks? **Answer:** Yes. Most can be scripted with CL, or with SQL services in QSYS2, and sent as a report or alert. Start by automating disk, subsystem and message queue checks, then add patch and security reviews. ## Search terms ibm i health check checklist, as400 system health check, as400 daily checklist, ibm i admin checklist, iseries health check, ibm i disk utilization check, ibm i ptf check, as400 monitoring checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json