On 5/4/2023 5:19 PM, Peter Relson wrote:
Page alignment is what you'd expect.
That's too bad. I was hoping module fetch had been enhanced at some
point over the last quarter century to take advantage the
StartBdy/ContBdy keywords available on GETMAIN/STORAGE (since 1998).
My example was
Page alignment is what you'd expect.
If you need any section aligned at greater than an 8-byte boundary (and you
do), then the entire module needs to be obtained on greater than an 8-byte
boundary, and the only choices made available for obtaining storage for modules
are 8-byte boundary and
On 5/4/2023 1:19 PM, Peter Relson wrote:
Ed,
What you really want is not to dive so deeply into the weeds.
Bind with COMPAT=ZOSV2R1.
It does not work. Here is a trivial example.
I'm compiling with SECTALGN(256) and specifying no binder input other
than a NAME statement:
//LKED.SYSINÂ DD
Ed,
What you really want is not to dive so deeply into the weeds.
Bind with COMPAT=ZOSV2R1.
>From the doc:
COMPAT=ZOSV2R1 is the minimum level that supports preserving all boundary
alignments specifications coming from ESD records. ALIGNT can be used to
specify boundary alignments for both
