Re: Module source naming schemes

["paul cunnane" <paul@xxxxxxxxxxx>]

> Which brings up a question.  I build this all into my modules.  I link my
> modules into my service program. I link my service programs into my Bound
> Library.  Then I go and change RcvNetF, and the way it interacts with my
> other calls in the same module.  When I recompile my module, do I have to
> relink it to my service program?  And then do I have to relink my service
> programs into my bound library?  And then do I have to recompile all the
> programs that use the bound directory?

Jim, I think you are confusing yourself with terminology.  When you use a
term like `bound library' for binding directory, it implies (wrongly) that
the modules and service programs are bound to the directory.  The directory
is just what it says -- a list of bindable objects.

Take an example of creating a bound program which has a single module, but
which depends on (say) the system() C runtime function.  The module has a
prototype referring to an external procedure called `system', but it has no
information as to where that procedure physically exists.

When the module is created, the `system' procedure is considered an
unresolved external reference.  Then, when you CRTPGM, you specify
BNDDIR(QC2LE).  The binder notes that there is an unresolved `system'
symbol, and looks for it in the binding directory.

The first entry in binding directory is service program QC2SYS.  This
service program exports a procedure called `system', so the binder late
binds your module to service program QC2SYS.  If you look at the finished
program, you will see a reference to QC2SYS, but no reference to the binding
directory.  In other words, there is no difference (in this case) between
specifying BNDDIR(QC2LE) and BNDSRVPGM(QC2SYS).

Finally, if you change a module that is part of a service program, you must
re-bind it into the service program (using UPDSRVPGM or CRTSRVPGM).  If you
are managing the signatures correctly, there is no need to re-bind the
client programs to the service program, as they dynamically bind at runtime.


--
Paul


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---