Re: making changes in service programs visible to caller without rebinding

Joel,

Basically, what you can do with the binder language is add new procedures to
a service program, while keeping the old signature.  You specify the new
procedures in the *CURRENT list (STRPGMEXP PGMLVL(*CURRENT)), and keep the
old list as *PRV.  The binder gives the service program a signature (either
calculated or specified in the SIGNATURE parameter) for every list (there
can only be one *CURRENT, but there may be several *PRV).  This way, when a
program is executed that uses the service program and was created before you
added the new procedures, it finds the old signature and there is no level
check.

Joep Beckeringh

----- Oorspronkelijk bericht -----
Van: Joel Fritz <JFritz@sharperimage.com>
Aan: <RPG400-L@midrange.com>
Verzonden: donderdag 2 september 1999 21:50
Onderwerp: making changes in service programs visible to caller without
rebinding


> I've been laboring under the misconception that you could change a service
> program and not have to rebind it to the programs that call it to see the
> results of any changes you made as long as you don't change the interface.
> It galls me to say it, but I'm wrong.
>
> What do you need to do with binder language to make this happen?
>
> Joel Fritz x1568


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