RE: Binding Source/Signatures

Eric,

In practice, I use this technique:
  STRPGMEXP  PGMLVL(*CURRENT) SIGNATURE('MYSRVPGM')
     EXPORT....
   /* Add new exports here */
  ENDPGMEXP


In my opinion, this is the only good/easy/simply way to do it. I know there are
several different approaches, but if you code enough you realize there's a
difference between book learning and doing it.

Having said this, if you already have a *CURRENT with *GEN set up, you only have
two choices:
1) Change the SIGNATURE to a hard coded one (recommend using the service program
name as the signature) and recompile the world, then use the new technique
(above) where you add new exports ONLY to the end of the EXPORT list. 
2) Create a one-time *PRV signature with *GEN that is a copy of the existing
*CURRENT signature. Then change the existing *CURRENT (not the *PRV copy) to a
hard coded signature. 

With option 1, you have to recompile the world once, but after that you just add
new exports (i.e., subprocedure names) to the end of the export list. You should
never have to recompile anything unless you want to use one of the new
subprocedures.

With option 2 you don't have to recompile the world, but you add the new
hard-coded signature to the mix. Then anything new you create or any existing
code that's recompiled will use the new hard code signature and will not need
recompiling except as described in option 1. The existing stuff will continue to
work without recompile and link to the new *PRV / *GEN signature.

But as I said, moving forward, I would avoid *CURRENT/*PRV with *GEN at all
costs.


-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Eric Wolf
Sent: Monday, April 03, 2006 5:53 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Binding Source/Signatures

   To the list,
   I know that I can have many *PRV versions of a service program using
   signatures.  My question is - if I am only adding a new module to my
   service program, do I have to create another *PRV version or can I add the
   new module to the bottom of the list of modules leaving the signature the
   same and then re-create the service program?
    
   Thanks...
   Eric