Re: Troubles with UPDSRVPGM

The procedures are not referred to by name, actually by position - something like that. So if you change the order or remove one, it picks up, say, the 5th one, and it isn't the same one it used to be.

We (a 3rd-party vendor) just add new procedures to the end in the bindery language and keep the same signature all the time - this way, our customers never have to recompile when we add procedures in a service program.

HTH
Vern

On 10/5/2012 8:32 AM, Hiebert, Chris wrote:

On 2012/10/4 2:57 PM, Hiebert, Chris wrote:
Old programs continue to function because they reference a specific
signature from an older (*prv) export group that is still found

within

the Exported signatures.

Chris, that won't work. There's only one ordering for the procedures in

a service program. The older signature doesn't keep its own ordering.

If you must change the order, then you must also ensure that old

programs will _not_ continue to function, but instead get a signature
violation, since they would be calling the wrong procedure.

Here's a little test scenario: http://code.midrange.com/9043c56f42.html

--
Barbara

Based on what Barbara is saying this means you can never reorder the
list of procedures. And every procedure in a *PRV list must always
correspond to a matching procedure in the *CURRENT list.
If you reorder, and you don't want to have issues, you have to recompile
everything.

Will removing the old signature always cause a signature violation for
existing programs?

Chris Hiebert
Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the
author and do not necessarily represent those of the company.