MC Systems Insight
MC Power Technology Manager
MC RPG Developer
MC Power Developer
MC TNT Tips 'n Techniques
MC AIX Expert
MC Linux Expert
MC Mobile on Power
This Week @ the MC Press Bookstore

December 5, 2012 | Volume 11 Issue 22


TOP STORY: Practical RPG: Looping with BIFs
FEATURED ARTICLE: Simon's Solutions: Monitor for End Job Operations, Part II
NEWS HIGHLIGHT: Coglin Mill and GEMKO Partner with DB2 Web Query and RODIN Offering for Complete BI on IBM i
TRIAL SOFTWARE: Free unlimited trial of the Valence Web Application Framework for IBM i
EVENT: Give Your RPG Applications the UI They Deserve with ASNA Wings
Manage Subscription | Contact Us

Feature Article - Programming
Practical RPG: Looping with BIFs

Learn what the built-in functions %FOUND and %EOF are and how to use them to loop through files.

joe plutaWritten by Joe Pluta

One of the most common business tasks is to loop through a file and process records. While many variations of code can be used for this particular task, over the years the community has tended toward a few basic techniques. This is a common occurrence in programmingso much so, in fact, that the idea has been codified into the concept of a design pattern. The book Design Patterns: Elements of Reusable Object-Oriented Software has sold over a half million copies worldwide. In this article, we'll review the common pattern of processing records in a file sequentially.


Feature Article - Programming
Simon's Solutions: Monitor for End Job Operations, Part II

Learn critical cleanup techniques that target end-of-job due to end job commands.

junlei liWritten by Junlei Li

This article continues the discussion we started in Part I. Let's start by looking at invocation exit programs and procedures.


If an MI process phase is terminated and the process was not in termination phase, then the invocations are terminated. Invocation exit programs/procedures set for the terminated invocations are allowed to run. Invocation entries (aka call stack entries) are terminated in the order of from the bottom to the top of the invocation stack (aka call stack). Invocation exits are a cleanup mechanism targeting the abnormal end-of-invocationfor example, end-of-invocation due to unhandled exceptions or thread termination. For this reason, invocation exits can monitor for end job commands issued to a job and protect resources allocated in each individual invocation.


In the News

Support MC Press - Visit Our Sponsors

Forums Sponsor



Search Sponsor