yea, but how does a *ENTRY module fit into that. You can do that and I have
seen people doing it.

Back when I ILE first shipped the tech journals were publishing articles
telling people that is how you write service programs. I remember thinking
"what the hell. This is not how you write a service program" and later
articles started appearing with procedures.

On Mon, Nov 13, 2017 at 10:21 AM, Hiebert, Chris <
chris.hiebert@xxxxxxxxxxxxxx> wrote:

From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan
--- Recently we had a programmer write a service program without the
NOMAIN and he used a *INLR so we ended up with a service program using the

A service program would never use the cycle in the same sense that a bound
program does.

The modules of the Service program "should" be created Nomain.

You can still bind "Main" modules into a service program.
But only exported procedures are included in a service program.
If none of the procedures in the "Main" module are exported, then the
module is just a waste of space as it contains non reachable code.

A service program is a collection of exported procedures.
Turning on LR in a service program procedure has no impact on resources of
a service program.

Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.

This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related

Help support by shopping at with our affiliate

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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 [javascript protected email address].