Re: Binder Source

On 01/10/2009, at 5:33 AM, Vern Hamberg wrote:

I have seen the behavior you describe, but not when binding another
service program. Instead, it comes when you /copy both the prototypes
and the actual code, which may have export on various subprocedures.
I've had to use binder language to restrict what is exported.

No comments needed on WHY am I doing this, please!!

I'll restrain myself** but what you describe is nothing like what Rick described. In your case the procedure exists within the service program and it has EXPORT so it's a candidate for external visibility. If you use EXPORT(*ALL) then it will be exported. That's just business as usual i.e., expected behaviour.

Also, Rick mentioned duplicate export errors which can't always be resolved via binder source. In your case if two or more modules in your bound object include the /COPY code then you will have duplicate exports and binder source cannot help. All it can do is allow you to hide an export candidate.

** I can see instances where copying the code (either via bind-by-copy or /COPY) is necessary e.g., licensing verification etc.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------