|
Richard B Baird wrote: > > Barbara, > > could you elaborate a little on what you are trying to say? > > do you mean that by hard coding your signature, you still don't need to > re-bind the srvpgm to it's previous callers after you add a procedure? > > If so, I agree, i'm not enamored with the *current/*prv scheme either. > > and, if so, what is the purpose of that scheme? > Rick, that's indeed what I mean. By "hard-coded signature", I mean using a binder source with a STRPGMEXP line like this: STRPGMEXP PGMLVL( *CURRENT ) SIGNATURE("WHATEVER") As long as you never change the signature value ("WHATEVER"), programs using the service program never need to be recreated. See my long-winded answer to Joe's request for a simple example. I don't know what's the purpose of the *current/*prv scheme.
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.