Subsystems are how IBM i organizes work. They decide which jobs run in which place, what resources they use, and which priorities they receive while the system is busy.
Why this matters
If you have ever wondered why one workload runs in a batch window while another stays interactive, subsystems are part of the answer.
Core concepts
Subsystems
A subsystem is a controlled runtime environment that accepts jobs and runs them under the rules defined for that workload.
Job descriptions
A job description sets defaults such as routing, output priorities, libraries, and the initial environment a job starts with.
Classes
Job classes help group work with similar response-time expectations.
Operational separation
Splitting interactive and batch work keeps critical users from competing with overnight processing.
Practical example
A retailer can keep customer-facing order entry in one subsystem and nightly inventory updates in another. That separation makes performance easier to predict and troubleshoot.
Common mistakes
- Letting everything run in the same place because it seems simpler.
- Changing a job description without understanding downstream defaults.
- Ignoring how batch windows affect end-user response time.
Where this fits in the series
If you want the platform foundation first, read the pillar article, What Is AS400 (IBM i)? A Complete Beginner’s Guide.