×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Use binding source and export only the procedure from the service program you want callers of the service program to have access to.
Duane Christen
--
Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx
Visit PAETEC.COM
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Andy Hautamaki
Sent: Wednesday, July 22, 2009 11:58 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: Export keyword on a procedure - can it be limited to which modules can use it?
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 the program.
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 of the service program modules as well.
Is it possible to have the services utility module only available/limited to other modules in the service program but not available to programs that have the service program bound to them?
Thanks
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,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
