Everything above the OS line.
- The IBM i operating system (OS/400) itself
- Your RPG and application code
- Your database and your data
- Application changes, patches, and upgrades
Untouched by us, always.
Your team keeps the applications. PowerTrue keeps the platform they run on — Power frames, HMCs, VIOS, and firmware — current, monitored, and patched.
The people who tend Power infrastructure are retiring, and you can't hire their replacements. The frame, the HMC, the hypervisor, the firmware still need tending — to a defined N‑2 currency, on a schedule, with someone watching. That's all we do, and we do it as a structured, repeatable service.
We never touch your RPG, your apps, or your data. We manage the layer beneath your OS. And a qualified engineer runs every change by hand — AI helps us diagnose and prepare, but it never acts on your system.
Untouched by us, always.
The platform layer, tended on a schedule.
A bounded, defined scope — the same structured work on every frame, every cycle.
Kept to a defined currency and FLRT-validated before anything changes.
The management consoles that run your frames, kept current and monitored.
Only where your Power is virtualized. Bare-metal shops skip this layer entirely.
Hardware events, firmware drift, and health, watched — not discovered during an outage.
Currency work happens on a plan you agree to, not "when we get to it."
Run bare-metal IBM i? The frame, HMC, and firmware still apply — VIOS only enters the picture where you virtualize.
Twenty minutes with Tanner to talk through what you are running underneath the 400 — and what a structured, repeatable service would cover. Pick a time straight off the calendar. No form, no drip sequence.