|
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.
Personally I've always let IBM name my signatures (always felt my naming was completely arbitrary), however applying versioning sounds like as good an idea as any to me.
And IBM and version numbers - well the new OS is 6.1 vs V6R1 (thank god). Also, the IDE environments use the version numbers. Just throwing that out there. ;)
-Kurt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Friday, October 09, 2009 3:22 PM
To: RPG programming on the IBM i / System i
Subject: Re: Service programs and QSRVSRC
Point well-taken. However, I'm working in a vendor situation - as much as possible, we want to avoid making the customer have to recompile anything that uses a *SRVPGM we distribute. Therefore, I don't use a version number. If I needed to force recompilation, I'd use some rename of the signature - perhaps a version number that's not there now.
Nonetheless, IBM do not typically use version numbers. Not that they are the be-all-and-end-all!!
Vern
-snip-
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.