On Tue, 26 Feb 2013 07:27:33 -0500, John Gilmore wrote: >If I code SECTALGN(16) for a Binder invocation I get alignment on a >doubleword boundary, at an address A such that A = 0 mod(16). > >If instead I code STARTBDY=16 in a STORAGE GET macro I get alignment >on a 2^16 = 65536-byte boundary, at an address A such that A = 0 >mod(2^16), i.e., A = 0 mod(65536). > >Different groups view the world differently; this disparity is >nevertheless a poster boy for an architectural police force. Options >that were once arcane, the province of coloro che sanno, are coming >into regular use by the mandolinisti too; and more coherence is called >for. > And, of course, the SECTALGN convention is to be preferred despite being more verbose because it allows extension at some time in the unforseeable future when a boundary not a power of 2 might become useful.
Do these facilities generate a 31-bit or a 64-bit control block entry? (Or is only the log base 2 stored in either case?) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
