Performance tuning on IBM i: finding bottlenecks and reading query plans
Performance problems on IBM i tend to fall into a small number of categories. A query that reads every record […]
Performance problems on IBM i tend to fall into a small number of categories. A query that reads every record […]
Every IBM i developer eventually ends up doing some administration. A job gets stuck. The output queue fills up. A
IBM i has been talking to other systems for decades. EDI over AS/400 communications, FTP file drops, MQ message queues
Most IBM i developers spend their entire careers working with physical files and never touch the IFS. That is understandable
Every physical file you have ever defined in DDS, every CHAIN and READ in your RPG programs, every logical file
If you write RPG, you already use CL whether you realise it or not. Every time you submit a job,
You already know how to read files with READ and CHAIN. They work. But the moment your query involves a
Subprocedures let you break logic into reusable blocks inside a single program. Service programs take it further — compile your procedures once and share them across every program on the system.
You already write RPG. Free-format does not replace what you know — it removes the straitjacket. No more counting columns, no more cryptic opcodes. Here is how to make the switch.
A practical enterprise guide to IBM i modernization covering APIs, RPG transformation, AI-assisted modernization, and legacy system evolution.