IBM Machine Types and Feature Codes
Anyone asking about machine types and feature codes is past the brochure stage. The question is narrower and harder: does this part, upgrade or maintenance quote actually match the system sitting in the rack.
turn a vague hardware question into a configuration review a reseller can actually verify and stand behind.
What You Need to Sort First
- Machine type, model and serial are the identity layer. Without all three, a reseller is guessing, however confidently they say it.
- Feature codes describe what was actually ordered and installed, down to the drive and the adapter. They are the difference between a quote you can check and a quote you have to trust.
- IBM support guidance points buyers to machine type model and feature code details when checking prerequisites and code levels, so these fields matter before upgrades or fixes.
- A useful reseller should verify the configuration against IBM records, installed inventory, support eligibility, and the specific job you need done.
This Page Helps You With...
- Feature code lookup
- Replacement part sourcing
- Maintenance confirmation
- Used hardware review
- Configuration matching
What You Need to Know Before You Verify IBM Machine Types and Feature Codes
Use these questions when the conversation has moved from general IBM Power interest into exact configuration proof. This is where the wrong digit, inactive feature, unsupported adapter, or missing entitlement can turn a simple quote into a support problem.
Can the reseller verify the machine type and serial number?
Start with the identity of the system
Machine type, model and serial number identify the actual system. Everything else depends on getting those three right.
- Support history
- Entitlement
- Maintenance eligibility
- Installed inventory
- Replacement parts
- Upgrade planning
Do not rely on the nickname
AS400, iSeries, P Series and IBM i are useful business words that identify nothing technically. A reseller needs the exact machine type and model before promising anything about compatibility.
Use visible and system-reported sources
Several sources can confirm what the machine is.
- The physical system label
- Management tools
- Hardware inventory output
- IBM records
- Prior maintenance paperwork
When two of those disagree, stop and resolve it. Ordering parts against the wrong identity is how a planned outage becomes an unplanned one.
Serial status affects next steps
The serial number decides more than it looks like it should.
- Entitlement
- Ownership history
- Maintenance eligibility
- Feature activation status
- Whether IBM or a third party can support it as quoted
Which feature codes are installed, active, and supported?
Feature codes describe the real configuration
Feature codes name the components that were ordered or installed.
- Processors and memory
- Storage and drives
- Adapters
- Tape
- Power and rack hardware
- Expansion features
This is how a reseller verifies what is in the system rather than what someone believes is in it.
Installed and active are different questions
A single feature can be in any of these states, and they are not the same thing.
- Physically present
- Ordered but not delivered
- Installed but inactive
- Unsupported at the current code level
- Available only with extra licensing
Ask the reseller to say which one applies. Present and usable are different words for a reason.
Code levels can decide support
IBM support guidance points to machine type model and feature code details when checking prerequisites and minimum code levels. That means firmware, operating system level, and feature support need to be checked together.
Inventory export beats memory
A full system inventory is stronger than someone remembering the configuration. Ask for an inventory-backed review when the request involves expensive parts, firmware, operating system support, or maintenance.
Are replacement parts compatible with my current IBM Power system?
Compatibility is exact
A replacement part has to match on every one of these, not most of them.
- Machine type and model
- Feature code
- Firmware level
- Operating system
- Sometimes the exact slot or enclosure
That holds for a drive, an adapter, a memory module or a whole expansion unit. There is no forgiving category.
One close part can still be wrong
IBM part families look alike and are not.
- Capacity
- Interface
- Firmware
- Feature code
- Supported generation
- Licensing requirement
Close enough is fine for a lab. It is not fine for production.
Used parts need extra scrutiny
Used and refurbished parts are genuinely useful, with conditions attached. They need testing, known provenance and a compatibility review. Then ask the plain question: will you stand behind this part after it is installed.
Installation risk belongs in the quote
A replacement part quote should say who installs it, whether downtime is required, whether firmware changes are needed, and what happens if the part does not resolve the issue.
Can the reseller confirm maintenance coverage before I buy?
Coverage must match the exact system
Maintenance has to be confirmed against the specific machine, not the product line.
- Machine type, model and serial
- Installed features
- Physical location
- Response time
- Named support provider
- Exclusions
A generic support promise covers whatever the provider decides later.
Feature changes can affect support
Any of these changes what the contract needs to cover.
- Adapters
- Storage
- Memory
- Tape
- Processors
- Expansion units
Make the maintenance plan follow the configuration. An upgrade that leaves coverage behind is a gap nobody notices until a part fails.
Support eligibility can differ by condition
Support options differ by how the equipment arrived: new, refurbished, used, transferred or simply old. Ask one question about the quoted maintenance: is it confirmed, or assumed.
Ask for lifecycle guidance
Sometimes the right answer is not maintenance. It may be parts stock, third-party support, a bridge system, or a refresh plan. The reseller should tell you when support is becoming a temporary patch.