To return a bit to reality it is important to be able to allocate storage at runtime on a 16 byte (quadword) boundary if one is using instructions such as CDSG or LPQ which require 16 byte alignment of the storage operand. That ability is fortunately and conveniently provided by the STORAGE/GETMAIN STARTBDY=4 parameter, rather than the "inescapable runtime modulo arithmetic" being proposed yesterday, for example. The CDSG or LPQ instruction itself sits quite happily on the usual halfword boundary. All the SECTALGN(16) and GOFF business is a bit of a red herring. One can get by perfectly well without these options, assuming one is sensibly only using dynamically allocated storage for data areas, anyway. One needs to take a little care in laying out data structures, that's all.
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
