Re: Binding question...

Forgive me if I cause confusion.  I would suggest a more accurate
terminology:

DYNAMIC BINDING:  Also known as a Late Bind, where the final resolution to
the target of the 'call' operation is done at execution time - i.e. when
the 'call' is performed.  In iSeries terms, this would be a Program Call,
(the target is a *PGM object) achieved through CALL or CALLP (with EXTPGM
keyword) operations in RPG IV.  The traditional approach to application
design - very, very flexible and easy to maintain.

STATIC BIND: Where the resolution to the target code is done as part of the
bind process.  The bind may be completed at creation time (Bind By Copy) or
partly at creation time, and partly at activation (load) time (Bind By
Reference).  In iSeries terms the target of the 'call' is a Procedure,
achieved through the CALLB or CALLP (usually with the EXTPROC keyword)
operations.  (It is also possible to call a procedure within an
expression.)

Bind By Copy infers that all procedure call can be resolved at creation
time, which usually means multiple modules have been 'bound' together into
a single program.  A simpler creation process, slightly faster activation
times, but a no-no as far as application maintenance is concerned.  The
exception rather than the rule.

Bind By Reference infers that some of the required procedures are located
in a separate service program.  Binding cannot be completed until
activation (program load) time.  A more complicated process but much more
flexible - this should be the normal approach for application design under
ILE.

To my mind, a Dynamic Bind is not the same as a Bind by Reference - but
wiser folk than I may have a different view.

Brian Parkins