AS400 Support
If you are looking for AS400 support, you are probably trying to protect a system the business still depends on. You may need IBM i help, hardware maintenance, application support, managed services, upgrade planning, or just someone who understands what you mean when you say AS400.
What You Need to Sort First
- AS400, iSeries, IBM i, and IBM Power often point to the same environment, just from different naming eras.
- Hardware maintenance, operating system support, application support, and managed services are different requests. Getting the label right helps you get useful help faster.
- Before you contact a provider, gather the system model, serial number, IBM i version, business application, backup method, and the hours the system must stay available.
- You do not need to know every IBM term before asking for help. You do need a clear picture of what is working, what is failing, and what would hurt the business if it stopped.
Where This Page Helps
- Hardware maintenance
- IBM i operating system support
- Legacy application support
- Managed AS400 services
- Upgrade and migration planning
What You Need to Know Before You Ask for AS400 Support
Use these questions as your map. Each one points to a different kind of support conversation, and getting that distinction right usually saves time on the first call.
Do I need AS400 hardware maintenance, IBM i support, application help, or managed services?
Start with the risk
Start with the part of the system that is causing the risk. If the physical server, disk, tape drive, power supply, HMC, or parts coverage is the concern, you are looking for hardware maintenance. That conversation is about machine type, serial number, support eligibility, replacement parts, response time, and whether you need IBM or third-party maintenance.
IBM i support is system administration
If the operating system is the issue, you need IBM i support. That usually means help with releases, PTFs, licensing, job queues, printers, backup configuration, security settings, performance, or system administration. This is not the same as fixing the application that runs on IBM i.
Application support is business logic
If the business application is the pain point, you need application support. That could involve RPG, COBOL, CL programs, vendor ERP software, custom reports, integrations, data files, or workflows that only one person in the company still understands.
Managed services are ongoing coverage
If you want someone to watch and manage the environment over time, you are asking for managed AS400 services. That usually includes monitoring, backups, patch planning, routine administration, escalation, documentation, and a named support plan.
What machine type, IBM i version, and business application are currently running?
Have the system profile ready
A good AS400 support conversation gets much easier when you can identify the system. The provider will usually ask for the IBM machine type and model, serial number, IBM i release, processor and memory basics, storage layout, tape or backup method, and whether the system is physical, virtualized, hosted, or part of a high availability setup.
Ask for the key IBM i details
If you have an internal IBM i administrator, ask them for a quick system profile. Useful details often come from commands such as DSPSYSVAL QMODEL for the model, DSPSYSVAL QSRLNBR for the serial number, DSPPTF or GO LICPGM for release and installed program context, plus whatever documentation exists for backup, printers, users, jobs, and application dependencies.
Explain what the system does
The business application matters as much as the hardware. Tell the provider whether the system runs ERP, accounting, warehouse, manufacturing, distribution, custom RPG applications, EDI, reporting, or integrations with newer platforms. Support gets much better when the provider understands what the system actually does for the business.
Is the system stable, at risk, out of support, or ready for an upgrade?
Stable systems still need prevention
If the system is stable, the smartest move is prevention: confirm backups, document the environment, review hardware support, check IBM i release status, and make sure there is a real escalation process before something fails.
At-risk systems need triage
If the system is at risk, focus on the risk first. Warning signs include aging disks, failed backups, no recent restore test, unknown passwords, no current maintenance contract, old IBM i releases, one employee who knows the application, or hardware that cannot be replaced quickly.
Out of support can mean several things
If the system is out of support, do not treat that as one problem. It may mean the hardware is no longer covered, the IBM i release is old, the application vendor has moved on, or the person who built the custom code is gone. Each of those needs a different plan.
Upgrade planning is dependency planning
If you are ready for an upgrade, the support conversation should include migration planning, downtime tolerance, application testing, backup and restore testing, printer and device dependencies, third-party software, licensing, and whether the target is newer IBM Power hardware, hosting, or a managed services option.
Can the support provider handle both old AS400 terminology and current IBM Power Systems?
They should translate the naming
Yes, and they should. Many businesses still say AS400 because that is the name everyone remembers. IBM now talks about IBM i running on IBM Power Systems. A useful provider can translate between those names without making you feel like you asked the wrong question.
They should know old and current IBM terms
The provider should understand old and current pieces of the environment: AS400, iSeries, System i, IBM i, AIX, Power Systems, hardware maintenance, PTFs, BRMS, tape, high availability, RPG applications, and modern migration plans. You do not need all of those, but the provider should know how they fit together.
Good providers ask practical questions first
A good sign is a provider who asks practical questions before selling a solution: What does the system run? What version are you on? When was the last restore test? What breaks if this machine is down for a day? Who supports the application? What are you trying to avoid?
Weak providers rush the prescription
A weak sign is a provider who jumps straight to a replacement, hosting contract, or managed services package before understanding the workload. Sometimes you need a refresh. Sometimes you need maintenance. Sometimes you need documentation and backup discipline first.