Thank you Gents for the best practice and the explanations. Much appreciated,
Mike
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Don Poitras
Sent: Saturday, March 7, 2020 11:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
On Fri, 6 Mar 2020 16:01:41 -0600 Michael Hochee wrote:
:>Ideally, I would like to create all future data spaces with a size of 2GB,
rather than 2GB OR 2GB-4K (when the returned ORIGIN value is NZ). I looked at
assembler service reference manuals as far back as 1999, and they all state
that
ZAD is to deal with base registers (register 0 can never be a base register)
loaded with 0 being incorrectly used to read data in the first 4k by
instructions
with a base/12-bit displacement. While long-displacement instructions could
incorrectly read data in the first 512K of a dataspace, I
With 64 bit machines, each processor now has 8K unique to it. Do they
need to avoid the first 8K?
On Sat, Mar 7, 2020 at 7:25 AM Peter Relson wrote:
>
> Answer: Not totally
>
> It is true that all current machines support page 0 in a data space, and
> for them the "normal" origin returned would
>did you have an ENTRY BAR statement in the assembly?
I did not. I used the form you and Gil showed of "BAR" on the "END" with
no entry statement (either in the assembly or the bind).
Grrr... But I've even complained of seeing a "I" suffix on messages
reporting JCL errors fatal from the
Answer: Not totally
It is true that all current machines support page 0 in a data space, and
for them the "normal" origin returned would be 0.
That is not a guarantee that all future machines would have such support,
but I find it hard to believe any would not.
However, we have found it highly