RE: making changes in service programs visible to caller without rebi nding

[Jon.Paris@xxxxxxxxxx]

 >> depending on how you create your programs the service programs are either
bound by copy or by reference.

Hate to contradict you, but your comment is a contradiction in terms (pun
intended).

By definition a Service Program is bound by reference.

A source member compiles to a *module which can contain one or more procedures.

The *Module can be bound into a program (CRTPGM) - this is Bind by Copy.

A *Module can alternatively be bound into a Service program (CRTSRVPGM).  When
the service program is subsequently referenced by a CRTPGM (or a CRTBNDRPG if it
is listed in a Binding Directory) this is a Bind by Reference.

What you may have missed on the CRTBNDRPG approach when using Service programs
is that they must be listed in the binding directory as a service program _not_
as the module object.

Typically service programs comprise multiple modules.


+---
| 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
+---