Re: Service Programs / Binding Directories / *DUPPROC

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

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.

OK, I think I get what you're asking -- why isn't there a default
for the MODULE parameter that actually serves a purpose? ...a purpose in
line with what omitting the MODULE parameter really accomplishes? If
you're not using a binder source member to drive the module selection,
then either *SRVPGM or specifying a module name would be sufficient to
drive that process. Conversely, if you are letting the binder source
member drive the module selection, then it would make more sense to have a
*SRCFILE default for the MODULE parameter -- which is in line with the
default for the EXPORT parameter. Sound about right?

CRTSRVPGM SRVPGM(DLCTEST) MODULE(*SRCFILE) SRCMBR(*SRVPGM)
BNDDIR(WSBNDDDIR) ACTGRP(*CALLER)


Sincerely,

Dave Clark