On Mon, Nov 11, 2019 at 8:45 AM Charles Mills <charl...@mcn.org> wrote:
> Sure, there are lots of solutions (assuming the shop is not mortally > afraid of touching 1993 assembler code, has a budget and staff to do so, > and can find the source). > > My thought is why would the shop expect a problem? Why would a routine > that has been working since 1993 be a suspect in an obscure > high-halves-in-compiled-code problem? > I guess we'll just have to say "times change". Or, if we want to be "nasty", we could say "What isn't specifically saved is subject to being changed." Of course, this means a code review when something significant changes, such as from 32 bit registers to 64 bit registers. Your code might not have changed, but IBM's might have. Ergo, all use of an API used in code _should_ be reviewed. Of course, who has time for that? Curiously, at least around her, that would be another bullet in the "z/OS is junk" argument, despite the fact that Windows has historically had even worse problems. > > Charles > > -- People in sleeping bags are the soft tacos of the bear world. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
