Typo; should be regardless of RMODE.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Seymour J Metz <[email protected]> Sent: Tuesday, November 24, 2020 10:49 AM To: [email protected] Subject: Re: An old-timer confirming what's changed (since MVS/ESA :-) ) IBM has moved a lot of code above the line, with stubs allowing AMODE24 code to continue using the old interfaces. Has IBM started, or at least announced an intention, to move code above the bar for VSCR with stubs providing continuity for existing QAMODE31 code? AMODE64 is necessary for new code using 64-bit addressing, regardless of AMODE; that has nothing to do with the size of the save area. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Rupert Reynolds <[email protected]> Sent: Tuesday, November 24, 2020 9:38 AM To: [email protected] Subject: An old-timer confirming what's changed (since MVS/ESA :-) ) Reading (a lot of) documentation from IBM it seems that a lot has gone into the *nix side of z/OS and extra instructions and 64-bit addrssability for data, but that the code itself still resides below the bar, so that most AMODE 24 and 31 code from years ago will still compile/assemble and run as is, or with minimal change. Is that fair? But if new code using 64-bit data is still loaded and executed below the bar, and new instructions and extended registers handle the addressing of data with 64-bit addresses, why is there an AMODE 64 at all? Is it simply to indicate that a larger (DS 18D) savearea should be provided, as it may be needed by the called program? Thanks for any clarification you can offer. Roops
