|
On Fri, 4 Nov 2005, Scott Klement wrote:
Yes, but programs and service programs (which are executable) are built from modules. The RPG cycle (the part that *INLR affects) is a per-module thing, not a per-program thing. You can make a program out of 500 different modules if you want to, and therefore your program would have 500 different *INLR indicators, and 500 different main procedures.The point is that the LR indicator operates at the per-module level. Whether you take these modules and make programs from them or whatever you use them to make service programs doesn't matter.
This is totally different than how I've always worked. I always have one module that does *not* specify NOMAIN and all the rest of the modules used in a given program do specify NOMAIN. By specifying NOMAIN for a module the RPG cycle code is not generated AFAIK. At the very least specifying NOMAIN means that a PEP cannot be created for that module. I cannot for the life of me imagine a situation where a program would be created from multiple modules that do *not* specify NOMAIN, thereby allowing multiple PEP candidates (and multiple RPG cycles). AFAIK the RPG *does* "operate at the program level". Can you give an example of a program that uses multiple non-NOMAIN modules?
midrange.com
James Rich
It's not the software that's free; it's you.
- billyskank on Groklaw
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
