Brian,

Bear in mind that you don't NEED multiple signatures in the binder
source - the following would also work fine:

STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*NO) SIGNATURE('V1.0')
  EXPORT SYMBOL("Proc1")
  EXPORT SYMBOL("Proc2") 
ENDPGMEXP

If I create the *SRVPGM and specify this binder source member, the
*SRVPGM will be created with a signature of 'V1.0'. If I subsequently
want to add more exports, I can do so easily by adding them to the end
of the above list, e.g.:

STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*NO) SIGNATURE('V1.0')
  EXPORT SYMBOL("Proc1")
  EXPORT SYMBOL("Proc2") 
  EXPORT SYMBOL("Data1") 
  EXPORT SYMBOL("Proc3") 
ENDPGMEXP

Because I'm using LVLCHK(*NO) and a hard-coded signature, any programs
which already use the *SRVPGM won't be affected - they don't need to be
recompiled or anything at all. If you ever want to force them to
recompile, just change the hard-coded signature and recreate the *SRVPGM
ans those programs will stop working and will need to be recompiled

Just remember not to change the order of any existing exports within the
binder source. The above system is much simpler (it's actually what IBM
uses for most of their *SRVPGM's). It also allows you to create a
meaningful signature (such as a version or build number) rather than
have the systemn generate a meaningless (to humans) 16-byte hex value.

HTH,

Rory

Frankly, I don't like IBM's whole PGMLVL(*CURRENT|*PRV) option.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.