I'm in the process of breaking down a huge RPG program into ILE RPG. I need to break the whole program into modules so we can make changes to one module only and then promote the changed module to production. What areas do I need to concentrate on in terms of making the program modules independent of each other? Can I have a specification wise (F,D,C,O) listing as to what needs to be changed in the main program?
If you're breaking the program down and using procedures, only "D" and "C" specs can be used in the procedures. I would suggest you take business logic calculations and put them in independent modules or bound programs. With Bound programs, you can have common file usage in the bound programs and modules to process the business logic in each area.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: tips, tutorials and more.
Ask your programming questions--or help out your peers by answering them--in our live discussion forums.
Ask the Experts yourself: Our application development gurus are waiting to answer your programming questions.
Dig Deeper on RPG iSeries programming
Related Q&A from John Brandt
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.