IBM i (AS/400) System Health Check Checklist
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.
0 of 37 items complete
14 critical items still open - these are the highest-risk gaps.
Storage and capacity
Jobs, subsystems and performance
Messages and logs
Patching and release
Security
Recovery and continuity
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.
Optional automated IBM i health report
If you would like these checks collected and summarized without manual effort, we can discuss a read-only approach.
Optional. The tool and every export work without this. No spam.
How to use the checklist
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
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.
- 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
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.
Frequently Asked Questions
How often should I run an IBM i health check?
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?
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?
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?
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.
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.
Related Tools
AS/400 (IBM i) Backup Verification Checklist
Verify that your IBM i saves actually completed, cover the right objects, are stored safely and can be restored, with critical items flagged.
ERP Migration & SelectionAS/400 Green Screen Modernization Assessment
Find out whether your IBM i green screen applications should be left alone, wrapped with a web or API layer, or replaced, based on 10 practical questions.
Developer ToolsIBM i (DB2 for i) SQL Data Extraction Script Generator
Generate DB2 for i SQL to inspect a file, count rows, and extract records with Julian date filters for JD Edwards World or other IBM i data.
ERP Migration & SelectionJDE World to E1 Migration Readiness Assessment
Ten questions that show how complicated a JD Edwards World to E1 (or other ERP) move will be, based on customization, data, interfaces and people.
More ERP Operations tools
See allNew to IBM i (AS/400) ERPs? Start with the IBM i (AS/400) ERPs guide and toolkit.
Keep exploring
Free tools
- AS/400 (IBM i) Backup Verification ChecklistVerify that your IBM i saves actually completed, cover the right objects, are stored safely and can be restored, with critical items flagged.
- IBM i (AS/400) Disaster Recovery Runbook TemplateFill-in recovery runbook for an IBM i production partition: objectives, restore sequence, contacts, validation steps and drill history.
- JD Edwards CNC Environment Health Check ChecklistA weekly or monthly checklist for JDE CNC admins covering servers, web tier, database, batch processing, security and backups.
ERP fixes and how-tos
- How to Add a Private AI Layer to JD Edwards World on IBM iAdd AI to JD Edwards World without moving data: DB2 for i access, journal-based replication, rebuilt row security, local GPUs and approved batch write-back.
- How to Add a Private AI Layer to JD Edwards EnterpriseOne On-PremAdd a private AI layer to JD Edwards EnterpriseOne: AIS data service, Orchestrator, Security Workbench mapping, a local model and human approval.
- How to Add AI to an IBM i (AS/400) RPG Application Without Moving ItHow to add a private AI assistant to custom RPG applications on IBM i: Db2 for i access, field names, journals, RCAC security, local LLM, sizing and rollout.
Runs with your ERP
- RF-SMART Manufacturing Data Collection for JD Edwards WorldShop floor barcode data collection for JD Edwards World with RF-SMART: what it reports, how it connects, setup steps, pitfalls and a private AI layer on top.
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- RF-SMART and JD Edwards EnterpriseOne: Barcode Scanning and Mobile WMSHow RF-SMART connects barcode scanning to JD Edwards EnterpriseOne and World: integration method, data flows, setup steps, pitfalls and where private AI helps.
AI on your ERP
- AI for JD Edwards World on IBM i, without a EnterpriseOne migrationAdd AI to JD Edwards World on IBM i without replatforming: read the physical files safely, ground an LLM on your data, and keep control on the box you already run.
- AI for JD Edwards EnterpriseOne Manufacturing, Without Leaving the F-Tables ExposedGrounded AI over JD Edwards EnterpriseOne Manufacturing: work orders, routings, and Orchestrator data, answered on-prem without sending F-table data to a public model.
Integrations
- How to add AI agents to JD Edwards World on IBM iHow to add AI agents to JD Edwards World on IBM i: a read-first tool layer over DB2 for i, human approval before any write, and a fully on-prem model option.
- How to use ChatGPT with JD Edwards WorldUsing ChatGPT with JD Edwards World on IBM i: custom GPT actions vs data exports, enterprise data controls, and when a private model is the better fit.