This is just for the purpose of interview preparation only, anyhow I'm not goint to do rpg cycle programs.
You are mixing 2 separate things here. Program cycle and development life cycle.
The RPG PROGRAM CYCLE is what I think you're after.
There are a bunch of features to it, but only a few that you'd see frequently.
- Input Primary file : automatically does the read of the next record in your primary file. No explicit I/O operation in the code. Will also do the update if "UP" instead of "IP".
- Level breaks : automatically sets L1, L2, etc. indicators when the value(s) of specified field(s) changes from the prior record. Very handy for things like having a report force a page break if the company number has changed. Also can do special processing (subroutine-like or printer output) that happens after the record read but before that data rolls into the field values.
- Last record processing : a special case of level breaks. You can have certain code or printer output that only runs when the Input Primary read gets an end-of-file.
You might see new programs written that use Primary files (a fine techniques if reading the entire file anyway) but more rare to see other features in a new program.
Any academic style book on RPG will cover the program cycle.
The development life cycle is not unique to RPG. Unlikely you're asking about this.
Last Wiki Answer Submitted: February 26, 2010 5:38 pm by Kar425 pts.