RE: Service Program issue

["Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx>]

You have to become familiar with binder language.  When a service program is
created, it creates a signature based on the procedures contained in the
program and, I think, the parameters for each procedure.  You can use binder
language contained in a source member to manually generate those signatures.


For example, you might use the following in a source member:

/* Current version of procedures to be exported. */      
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE('1')   
    EXPORT SYMBOL(Procedure1)                            
    EXPORT SYMBOL(Procedure2)
ENDPGMEXP                            

Then when you add a new procedure, your source member might look like this:

/* Current version of procedures to be exported. */      
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE('2')   
    EXPORT SYMBOL(Procedure1)                            
    EXPORT SYMBOL(Procedure2)
    EXPORT SYMBOL(Procedure3)
ENDPGMEXP                            

/* Previous version of procedures to be exported. */      
STRPGMEXP PGMLVL(*PRV) LVLCHK(*YES) SIGNATURE('1')   
    EXPORT SYMBOL(Procedure1)                            
    EXPORT SYMBOL(Procedure2)
ENDPGMEXP                            

When you create the service program, specifiy EXPORT(*SRCFILE)
SRCFILE(<library>/<source file>) SRCMBR(<source member>)

Unfortunately, if you didn't use this technique from the start, you probably
have to recreate the service program and rebind all the programs that use
it.  I am, however, far from an expert. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
I added a new routine today to a service program and it stopped the only
program we have using it with the following error.  How do you change a
service program without having to rebind all objects that are using it.
<clip>