Thanks Rory.

----- Original Message ----- From: "Rory Hewitt" <roryhewitt@xxxxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, July 22, 2009 1:05 PM
Subject: Re: Export keyword on a procedure - can it be limited to which modules can use it?

Yes - don't specify it as an export in the binder listing (QSRVSRC member)
for the service program. Then it's available to all modules *in* the *SRVPGM
but is not available to anything outside the *SRVPGM.

On Wed, Jul 22, 2009 at 9:58 AM, Andy Hautamaki

I look at the manual and it looks pretty cut and dry. If you define the
export on the procedure then the procedure is available to any module in

I have a service program made up of many modules. I have a utility module
that my service modules are sharing. Now programs that I have the service
program bound to, this utility module is available to its modules outside
the service program modules as well.

Is it possible to have the services utility module only available/limited
other modules in the service program but not available to programs that
the service program bound to them?

Andy Hautamaki
This is the RPG programming on the IBM i / System i (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

This thread ...

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

This mailing list archive is Copyright 1997-2019 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].