AS400 Support: Choose the Right Kind of Help
AS400 support is not one service. Identify whether the problem belongs to IBM i, IBM Power hardware, an application, or daily administration before choosing who should fix it.
The right AS400 support starts with one question: what part of the system is actually in trouble? Separate the operating system, hardware, application, and daily administration first. Then you can call the person who can fix it instead of paying one provider to find another.
Match the AS400 Problem to the Right Support Layer
| Support layer | Problems it usually owns | Best starting point |
|---|---|---|
| IBM i operating system | Release level, Program Temporary Fixes (PTFs), security fixes, system messages, and software maintenance | An IBM i support provider or IBM support when coverage applies |
| IBM Power hardware | Machine faults, disks, adapters, Hardware Management Console issues, parts, and warranty or maintenance coverage | IBM or a hardware maintenance provider that supports the exact machine type and model |
| Business application | RPG or COBOL code, an enterprise resource planning package, custom workflows, reports, and vendor software | The application vendor or a developer who understands that code and business process |
| Daily administration | User profiles, backups, jobs, subsystems, printers, 5250 access, and routine monitoring | An internal IBM i administrator or a managed service provider |
Modernization is a separate decision. A support provider may keep the current environment healthy without being the right team to redesign an application or plan a migration.
Use the Page That Matches the AS400 Question
| Your question | Dominant answer |
|---|---|
| What is the AS400 operating system called now? | AS400 OS |
| Which IBM i version is installed and what can it upgrade to? | IBM i Release History |
| Is this IBM i release still covered? | IBM i Support Status |
| Is the original AS400 platform at end of life? | AS400 End of Life |
| Should the application be improved or replaced? | AS400 Modernization |
These pages support one another without answering the same question. Start with the narrow answer, then follow the handoff when the problem moves into another layer.
Gather This Information Before Asking for AS400 Support
A useful support request needs enough information to reach the right person quickly:
- IBM i level: the version, release, and current PTF group levels
- Hardware identity: the machine type, model, serial number, memory, and storage layout
- Application identity: the product name, vendor, language, job, and subsystem involved
- What happened: the exact message ID, time, recent change, and whether the problem can be repeated
For an upgrade discussion, also document the backup method, high availability setup, connected systems, and any application certification limits.
When AS400 Support Becomes an Upgrade Decision
Support turns into upgrade planning when a release leaves normal support, hardware parts become difficult to obtain, backups cannot be tested with confidence, or an application vendor stops certifying the current environment. Keeping the system running is not the same as keeping the business protected.
IBM publishes current dates on its IBM i release life cycle page. IBM also publishes the release and Power server combinations on its platform support details page. Use both before assuming an operating-system update and a hardware refresh are the same project.
Choose an AS400 Support Provider by the Work They Own
Ask a provider to name the layer it supports, the hours it covers, and what happens when the problem belongs somewhere else. A clear agreement should identify response targets, remote-access rules, included PTF work, backup responsibilities, application boundaries, and the escalation process.
The provider does not need to own every layer. It does need to know where its work ends and make the handoff without leaving the system owner to coordinate a guessing game.