|
Hi Rob, What you are getting is a form of Level Check for the Service program. You need to get to grips with Binder Source - all is explained in the ILE Concepts manual. Generally speaking, if you simply update a module in a Service program (using UPDSRVPGM and assuming parameters have not changed) then no re-compilation of programs is required. If you re-create the Service Program (CRTSRVPGM), you will have to re-compile the programs UNLESS you are using Binder Source to specify the exports from the Service Program. Have a look at the EXPORT Keyword (I think that is the keyword - not near machine or manual at the moment) on the CRTSRVPGM command. HTH Paul Tuohy. Rob Berendt wrote: > I think we recently peered down this path. I think > I am ready for the trip. > > I have a service program. It is used by many programs. > I have a compiler directive in these programs that looks like: > H Bnddir('ROUTINES/SRVPGM':'QC2LE') > > And the binding directory ROUTINES/SRVPGM has one entry: > --------Creation------- > Object Type Library Date Time > > SRVPGM *SRVPGM ROUTINES 02/02/00 16:00:10 > > When I change the service program, then other programs > that use this service program err out with: > MCH4431-Program signature violation. > Cause . . . . . : The source program PCGETSTS specifies > a signature > X'000C5D4D0B5DAD1E2685A5A737085332' which is not > supported by service > program SRVPGM. > Recovery . . . : The service program interface has > changed. Re-bind source > program PCGETSTS. > > How do I avoid this situation? > > I am thinking that there are 1 of three solutions. > 1) Employ some method of changing the service program > that doesn't change the signature. > 2) Employ some binding trick that doesn't care what the > signature is. > 3) Recompile or rebind every program that uses the > service program - yuck! > > Rob Berendt > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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 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.