Re: Creating a service program

["Mike Silvers" <msilvers@xxxxxxxxxxx>]

You must specify the current signature and the old signature in the binder
language.  The binder language is saved in a source file and is of the type
MOD.  When the service program is compiled, you must then specify the
location of the binder language.  The binder language would state the
following to include the old signature:

STRPGMEXP PGMLVL(*CURRENT)
EXPORT  SYMBOL(Proc1)
EXPORT  SYMBOL(Proc2)
EXPORT  SYMBOL(Proc3)
EXPORT  SYMBOL(Proc4)
ENDPGMEXP

STRPGMEXP  PGMLVL(*PRV)
EXPORT  SYMBOL(Proc1)
EXPORT  SYMBOL(Proc2)
EXPORT  SYMBOL(Proc3)
ENDPGMEXP


What this is saying is that the current signature includes all 4 procedures.
It saves an old signature with the first three procedures.  The older
programs will use the older signature with 3 procedures.  Any newer programs
that are compiled will use the new signature with 4 procedures.  Any program
using the older signature can not reference the new 4th procedure unless it
is compiled again and has a prototype defining the new procedure.  If a
program is compiled again, it will always use the current signature, not any
of the old signatures.

Mike



----- Original Message -----
From: <Gwecnal@aol.com>
To: <rpg400-l@midrange.com>
Sent: Wednesday, August 23, 2000 12:56 PM
Subject: Re: Creating a service program


> OK - From the thread on this topic I understand that when you add
procedures
> to a service program and export(*all) the signature changes and calling
> programs will do the equivalent of a level check.  If you list the
procedures
> separately in a bind source and use this on the create service program,
this
> problem goes away. This is the part I don't understand.  Say I have a
service
> program with three procedures (Proc1, Proc2, and Proc3) and I create a
> service program (SrvProg) listing all three in my bind source.  Then I use
> this service program in 50 other programs.  Then I decide that Proc4 would
be
> useful so I add it to my service program source, add it to my bind source
> list and re-create SrvProg with the new bind source.  Doesn't SrvProg now
> have a new signature?  Won't my other 50 programs blow up?  If not, why
not?
> TIA, Lance
> +---
> | 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
> +---

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