Helo Rob,

Am 22.01.2020 um 15:45 schrieb Rob Berendt <rob@xxxxxxxxx>:

There's this thing called "observability". On occasion IBM comes out with new hardware which requires a 'conversion' of the compiled code. Anything compiled prior to V5R1 and had the objects observability removed could not get converted and thus had to be recompiled. Removing observability was a thing people used to do. Back in the day it saved some disk space. It actually was a technique recommended by some back when disk drives were still described in MB (as opposed to GB or TB). Some believe that removing observability makes it tougher to reverse engineer compiled code.

Thanks for explanation! I dimly was aware that there was an issue. But even my ancient systems have space measured in the two digit GBytes. Space saving? Honestly? :-) I think it's more about not letting anyone else see your code so easily.

CISC-to-RISC migrations (V3R2 and earlier to V3R6 and above) was the first time everyone went through this.
The next time was V5R4 and earlier to 6.1 and above.
Stuff compiled to V5R1 and above retains enough information to undergo conversion even if observability is removed.

I understand. So it's not an issue if stuff is compiled to V5R4, as you initially "complained". :-)

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.