RE: Service Program Signatures and Change Management

David,

Right, but I guess I was questioning Mark's idea that the change
management software was "re-binding" the calling programs to the service
programs during promotion as opposed to compiling them.

So are they compiling, binding, or just re-embedding the signature ? 

(btw, I just got the Implementer plug in for WDSC.  Looks pretty
sweet..)

Greg

|-----Original Message-----
|From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
|bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
|Sent: Thursday, February 16, 2006 2:17 PM
|To: Midrange Systems Technical Discussion
|Subject: Re: Service Program Signatures and Change Management
|
|Fleming, Greg (ED) wrote:
|> I thought service programs were bound to the calling programs at
|> run-time.
|
|They are, but at compile time a signature (similar to a file format
|level identifier) is pulled in from the service program and embedded in
|the program ... if the program tries to bind to the service program at
|runtime and the signature doesn't match, you get an error.
|
|Binder source can be used to control the signatures.
|
|david
|
|--
|This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
|To post a message email: MIDRANGE-L@xxxxxxxxxxxx
|To subscribe, unsubscribe, or change list options,
|visit: http://lists.midrange.com/mailman/listinfo/midrange-l
|or email: MIDRANGE-L-request@xxxxxxxxxxxx
|Before posting, please take a moment to review the archives
|at http://archive.midrange.com/midrange-l.