Re: Service Programs / Binding Directories / *DUPPROC

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 02/06/2018 04:24:30
PM:

Forgive me for hijacking this thread a little. One thing I have never
quite understood about the CRTSRVPGM command, perhaps someone can
enlighten me?

Suppose I wish to create a *SRVPGM using the Binder Language to define
the procedure exports. Suppose also I wish to use a *BNDDIR to specify
the list of *MODULES to search for these exports.

QUESTION: Why then must the CRTSRVPGM command still have the MODULE
parameter explicitly defined? In other words, why does (at least) one
*MODULE have to be specified explicitly on the command. (The default is
MODULE(*SRVPGM).) The Binder Language will specify the export symbol
table and thus determine other *MODULES that are required from the
*BNDDIR (and hence any other *SRVPGMs/*MODULEs) to complete the bind.

CRTSRVPGM SRVPGM(SRVPGMNAME)
MODULE(???????) <<< Why is this needed??
EXPORT(*SRCFILE) SRCFILE(QSRVSRC)
BNDDIR(DIRNAME)

Put another way, since a *SRVPGM has no Entry Module, why is the MODULE
parameter required at all? (The BNDSRVPGM parameter is optional, so why
not the MODULE parameter under these circumstances?)

Silly Example: Suppose I specified MODULE(NOEXPORTS) above. By
implication NOEXPORTS does nothing at all. It is of no use within the
*SRVPGM yet the parameter must be specified.

I must be missing something obvious.

The MODULE parameter is optional so I'm not quite sure just what
you're asking. In our case, we don't create the module with the same name
as the service program so we need this parameter in order to specify just
which module the service program is supposed to bind.


Sincerely,

Dave Clark