× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Curiosity question on this.  Okay, now you have 2 signatures in your binder 
langauge, one
*PRV for the old calls, one *CURRENT for the new calls.  What do you do when 
you add
a few more procedures to your directory?  You can't have 2 *PRV can you?

Regards,

Jim Langston

Mike Silvers wrote:

> 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

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.