[hercules-os380] LOC=31 to do LOC=32

[[e-mail] [hercules-os380]]

One of the problems I have is specifying a
LOC=32 parameter to MVS/380 GETMAIN
which will prevent assembly on z/OS.

But what we could do instead is that if a
program is running as AM32 or AM64
and it does a LOC=31 GETMAIN request,
it is instead treated as a LOC=32 request
by MVS380MN.

Note that Hercules/380 has an option to
make AM31 programs automatically run
as AM32, and that is how I run my own
system. It is unfortunate that REVIEW
cannot handle AM32 though, as I have to
switch off this feature whenever I do
REVIEW testing.

Anyway, I need to document somewhere
that "best practice" is for programs to be
written so that they are AMODE anything,
ie they don't use the high bit as a flag,
expecting it to be ignored, but if they do,
then they need to obtain LOC=24
memory rather than LOC=31 memory,
as LOC=31 memory has the potential
to get memory in the 2 GiB to 4 GiB region.

BFN. Paul.

[[e-mail] [hercules-os380]]

And to make the source look better, we
can return to using LOC=ANY for 31/32
and LOC=BELOW for 24, as originally
used, instead of LOC=24/31.

BFN. Paul.

[[e-mail] [hercules-os380]]

Post by ***@yahoo.com.au [hercules-os380]
And to make the source look better, we
can return to using LOC=ANY for 31/32

ie LOC=31 is deprecated.

BFN. Paul.