Re: Application Architecture/Design Question

<quote>
I see that the Restrictions section of the manual isn't clear on this, but the limit for printer files for ILE RPG is actually just for global program-described printer files. You can have as many externally-described printer files as you want, and you can have as many program-described printer files as you want in a subprocedure.
</quote>

... shows up, that RPG and Architecture/Design are two very diffrent animals. Having lots of files in one compile unit, is far far away from good design and is an indicator for absence of architecture of an application. One of the principles of a good design is having every functionality only once and keep the components small and simple. One of the principles of architecture of an application is, to seperate your application into layers.

I would make one Module responsable for one file, putting all functionality dealing with this file in this module, and one of the procedures might be the one, you where talking about. As this module is needed by multiple other modules, not needing one of the others, just make a SRVPGM out of this.

If your controllingh file (which procedure is to call) might chnage I wouldn't bind the modules at compiletime, just use a generic Prototype based on a ProcPtr and bind the needed SRVPGM at runtime.

D*B