|
Because I'm using LVLCHK(*NO) and a hard-coded signature, any programs which already use the *SRVPGM won't be affected - they don't need to be recompiled or anything at all.
There's no point in supplying a signature if you're going to specify LVLCHK(*NO). LVLCHK(*NO) basically means "I don't want to use signatures".
If you ever want to force them to recompile, just change the hard-coded signature and recreate the *SRVPGM ans those programs will stop working and will need to be recompiled
That's not true. Because you specified LVLCHK(*NO) it'll never force anyone to recompile.
Just remember not to change the order of any existing exports within the binder source. The above system is much simpler (it's actually what IBM uses for most of their *SRVPGM's). It also allows you to create a meaningful signature (such as a version or build number) rather than have the systemn generate a meaningless (to humans) 16-byte hex value.
[SNIP]
Frankly, I don't like IBM's whole PGMLVL(*CURRENT|*PRV) option.
I agree with you completely. Using *CURRENT/*PRV provides absolutely no benefits that I can find.
However, I strongly suggest using LVLCHK(*YES) so that you CAN deliberately break backward compatibility if you want to. With LVLCHK(*NO), you've turned signature checking off completely, and thrown away that useful capability.
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.
midrange.com
