Guru: Putting Failure Handling In Its Place
August 24, 2026 Gregory Simmons
One of the things I enjoy most about procedure-driven RPG is that it encourages us to think about responsibility. Every procedure should have a clear purpose. It should perform one task well and leave unrelated concerns to other parts of the application.
That sounds straightforward enough, yet one responsibility often finds its way into nearly every procedure we write: failure handling.
If you have worked with RPG for any length of time, you have probably encountered applications where nearly every procedure begins with a MONITOR operation. The procedure performs its work, catches any exception that occurs, logs an error, returns …
Read more
