×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I don't change the version number unless I do something unusual, like
remove an exported procedure. (IOW, The version number is just the
version of the signature, not the version of the product.)
I was not referring to IBM generating the signature *for*you*, I was
specifically replying to what Vern said.
Vern was noting that IBM does this:
STRPGMEXP SIGNATURE('srvpgmname')
I was suggesting that this is better:
STRPGMEXP SIGNATURE('srvpgmname 01.00')
Because you can (if you want to) CHOOSE to break compatibility when you
want to introduce an incompatible feature.
You, on the other hand, are talking about coding
STRPGMEXP PGMLVL(*CURRENT)
-and-
STRPGMEXP PGMLVL(*PRV)
-and-
STRPGMEXP PGMLVL(*PRV)
-and-
STRPGMEXP PGMLVL(*PRV)
-and-
STRPGMEXP PGMLVL(*PRV)
-and so on for every previous version-
That's a whole different discussion, which we can have (for the
umpteenth time) if you want... but I wanted to be clear that wasn't what
I was referring to in my previous message.
Kurt Anderson wrote:
If you retained the old signatures within the binder source and
didn't make a change that required them to recompile the programs as
well (e.g. a parameter change to an existing procedure), then there's
no need to make them recompile to use the new version number.
midrange.com
