It sounds incredible to me that this kind of mistake could be made so many times and go undetected. While the typo of CLC/MVC for CLI/MVI isn't uncommon, it usually isn't propagated into a huge number of programs. I'd be pretty nervous about my future if I were in any way responsible for this.
I guess the easiest (not necessarily easy) thing would be to roll back to 2.4 until the fixes can be identified and made. SLIP ZAD may be a useful tool for finding the bugs, but it is a debug tool, not a way to circumvent the errors. The other suggestions sound like brainstorming, but none seem at all practical. As two very authoritative IBMers have just said. My product actually had this bug (just one!) where AH Rx,2 was inadvertently coded when AHI was meant. It worked for years, because whatever happened to be there was close enough, until 2.5, when it became zero. Zero led to a failure way, way down the line, and it took a while to figure that out. sas On Tue, Mar 28, 2023 at 6:01 AM Jonathan Scott <[email protected]> wrote: > Preventing access is not practical. The standard approach here > would be to use the IEAVTSZR method documented on that ZAD web > page to collect ZAD events and then to use the resulting report > to identify which programs need to be fixed. > > Jonathan Scott, HLASM > IBM Hursley, UK >
