RE: Create Service Program

Acutally IMO *ALL should not be used, and should never have been an option.


In our systems we have no modules in any binding directory. Modules are used
in one service program or one program. Only in a very rare exception would I
allow a module to be used in more than one program/service-program. I have
yet to find that exception in 6-7 years of ILE coding.

Binding source may be oddball, but other languages have oddball ways of
creating/recreating their objects. Could there be a better interface
definition process, probably, but binding source with built in version
control and exceptional, if not complete, control of the service programs'
exposure to the outside world is brilliant.

Besides *ALL means *ALL.

Duane
 

 

-----Original Message-----
From: Paul Morgan [mailto:pmorgan@xxxxxxxxxxxxxx]
Sent: Tuesday, August 30, 2005 12:32 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Create Service Program


Duane,

You think it's brilliant that EXPORT(*ALL) not only exports procedures in
any module I've got in my MODULE list but also any subprocedure you might
have linked into your service program from the binding directory?  You think
it's brilliant that I have to use some oddball configuration format (binding
source) to get around this problem?  That's an odd definition of brilliant.

Binding source is great if you only want to export some procedures but not
others.  There's also other uses for binding source like maintaining a
procedure's entry point in the service program between versions.  All well
and good but EXPORT(*ALL) shouldn't apply to modules in the binding
directory.  If I want to export something from a module make it more
explicit.  Should have made me place it in the MODULE list before I can
export it from the service program.

Paul