Lesson 12 of 288
IBM i Platform FundamentalsWhere to Go Next
A closing look at what you've learned across the IBM i Fundamentals path, and practical directions for continuing to learn.
Learning Objective
By the end of this lesson, you will have a clear picture of what you have covered across the IBM i Fundamentals path, understand that you now have a mental map rather than full mastery, and know some practical directions for continuing to learn.
Simple Explanation
Across this path, you have built up a picture of IBM i as an integrated platform, why it continues to matter to real businesses, and the major pieces that make it up: libraries and objects, the 5250 interface, physical and logical files, RPGLE, CLLE, Db2 for i, job logs and spool files, and a general sense of how development work flows from source code to a released program.
It is worth being honest about what this means and does not mean. You now have a mental map of IBM i: a set of concepts and how they relate to each other. You do not yet have full mastery of any one of these topics. That is expected, and it is a completely normal place to be after an introductory path. Real comfort with IBM i comes from continued, gradual exposure: reading existing programs, asking questions, and connecting new details back to the concepts you have already built here.
IBM i Fundamentals is the foundation of a larger IBM i curriculum iRPGenie is building out over time -- deeper coverage of RPGLE and CLLE, Db2 for i and SQL, interactive screens and subfiles, and troubleshooting in production settings, among other topics. None of that deeper content exists yet; this path is where it starts.
Why It Matters
Setting realistic expectations matters. If you expected to be an expert after one introductory path, you might feel discouraged when you encounter something unfamiliar. Recognizing that this path gave you a foundation, not the finish line, makes it easier to keep learning steadily rather than feeling like you have fallen behind.
Practical Example
Imagine a new developer joining a team that maintains IBM i business applications. In their first weeks, they spend time reading existing programs to see how earlier lessons' concepts show up in practice, watch how more experienced colleagues check job logs when troubleshooting an issue, and gradually take on small pieces of RPGLE or CLLE work under guidance.
Over time, and without trying to learn everything at once, they become comfortable navigating the platform. This is a simplified, illustrative example rather than a real system, but it reflects a common, realistic pattern for how comfort with IBM i tends to develop.
Common Confusions
"Do I understand everything about IBM i now that I have finished this path?" No. This path gave you a foundational mental map, not full mastery. Real comfort with any of these topics comes from continued exposure and practice over time.
"Is there one correct order to learn everything next?" No. Several directions are reasonable depending on your goals, such as practicing 5250 navigation, learning more RPGLE or CLLE basics, gradually understanding Db2 for i and SQL, getting comfortable reading job logs and spool files during troubleshooting, or learning from existing programs and business processes. As iRPGenie adds more structured content over time, you will be able to pick a specific direction -- such as RPGLE, CLLE, or troubleshooting -- rather than guessing where to look next.
"Are deeper topics like advanced RPGLE, troubleshooting, or integrations already available right now?" No, not yet. Topics like these are planned as part of a larger curriculum iRPGenie is actively building, not features that are already built or promised on a specific timeline. Treat them as areas worth exploring once they are published, not something you are missing today.
Quick Recap
- This path covered IBM i as an integrated platform, libraries and objects, the 5250 interface, physical and logical files, RPGLE, CLLE, Db2 for i, job logs and spool files, and a general development workflow.
- You now have a mental map of these concepts, not full mastery of any single one of them; that is a normal and expected place to be.
- Continued learning happens in small steps: repeated exposure, reading existing code carefully, asking questions, and connecting new details back to what you already know.
- Reasonable next directions include practicing 5250 navigation, learning more RPGLE or CLLE basics, gradually learning Db2 for i and SQL, reading job logs and spool files during real troubleshooting, exploring real development workflows, and learning from existing programs and business processes.
- Deeper topics such as advanced RPGLE, CLLE, Db2 for i, troubleshooting, modernization, and integrations are natural future learning directions, not promises of features available today.
- IBM i Fundamentals is the foundation of a larger IBM i curriculum iRPGenie is building out over time; deeper tracks are planned but not yet available.
Try Asking the AI Tutor
Use the AI Tutor to ask follow-up questions about this path. For example, try asking:
- "What should I focus on learning next after finishing IBM i Fundamentals?"