IBM i batch jobs are the ones nobody watches — until one fails. This post covers SBMJOB, WRKJOBSCDE, job queues, completion monitoring, and the production patterns that keep overnight processing reliable.
Every RPG developer eventually writes a program that does something it should not. The calculation is wrong. The loop runs
Most RPG programs are written to handle the happy path. The file exists, the record is found, the calculation succeeds,
IBM i has a reputation for being secure. That reputation is earned — the security model is granular, well-designed, and
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,