RE: Can an RPG module call another RPG module?

> From: alan shore
>
> Sorry, I sent the last e-mail before I was ready to.
> The point I was trying to make was, if the modules etc are NEVER
> migrated to the production area, there is no way to satisfy an
> audit. (Been there, done that) If you can prove that the modules
> etc were migrated to the production area, and that when they were
> required again, they had been migrated back or accessed from the
> production area, the auditors will be satisfied (been there done that)

Do your auditors require source on the production machine?  A module is no
more relevant to the program object than is the source.  In a completely
secured environment, you would do neither compiles nor binds on the
production machine, so you'd need neither the source nor the modules for
auditing purposes.

Think of it the same way you would a C program.  You create a C program by
linking together a bunch of .obj files.  In a production environment, you'd
never see those .obj files.

My .02