On 20/11/2025 11:28 am, Paul Gilmartin wrote:
But some customers insist, "Fix no problem other than the one I reported!" Fear of collateral damage results in regenerative maintenance phobia.
For the same reason that it's difficult to define a maintenance level in SMP/E, a single fix is a bit of a SMP/E myth. A single fix is likely to pull in prereqs etc. so you get a whole lot of other changes whether you like it or not.
With a non-SMP/E full replacement delivery, I can identify and check out and test the exact code you're running. I can compare it with the current released version. If it's important to change nothing other than fixing the problem, I can make a single change to the code (or merge a change from the current release if it's already fixed) and build a custom release. I can test the version that will be running in your system.
As a bonus, if code doesn't have to be delivered as separate modules the compiler can work it's magic and give much better performance through inlining, removing dead code etc.
-- Andrew Rowley Black Hill Software ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
