Tom Marchant <[email protected]> posted: >On Thu, 10 May 2018 08:47:33 -0500, Paul Edwards wrote: >This is a matter of defining "best programming >>practices" and noting that you can't rely on the >>BALR crap byte > est for you perhaps. Using only a limited subset of the instruction set. >And you don't seem to understand the value of the linkage information >saved in R1 by BAL and BALR in AMODE(24). > This is a pointless discussion. > -- >Tom Marchant
The request was for suggested wording for an RFE for AMODE 64 to change data addresses 2GB to 4GB-1 so AMODE 64 could use GETMAIN to get memory there. To insure that only AMODE 64 programs that wanted the memory, the AMODE 64 program would specify something like GETMAIN LOC=32 in the source of the AMODE 64 program. The RFE would double the addressable memory with an address storable in four bytes for data for an AMODE 64 program. That is an incredible enhancement allowed for AMODE 64 programs. If people wish to convert old programs from their existing AMODE to a different AMODE, that is fine. If they want to use the AMODE 64 enhancement that the RFE would request, then their program would need to be AMODE 64 or converted to AMODE 64. Posts about BAL, BALR, crap bytes, AMODE 24, AMODE 31, AMODE 32, S/370-24bit, S/370-31bit, S/360-32bit, MVS 3.8j, PDOS, MVS/XA, ESA/370, and other totally off a tangent responses do not help address the RFE wording question. Please help shorten this thread by helping with the wording needed to request an AMODE 64 enhancement for AMODE 64 programs that would double the 4-byte addressable for data. Moving extended common would be icing on the cake. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
