On 2/26/2013 5:06 AM, John Gilmore wrote:
I have also verified that Edward Jaffe's clarification is entirely
correct. I am now more than a little curious to discover how this
particular bug was discovered.
It is clear that one can specify GOFF and quadword alignment and then,
avoiding with care or having had the blind luck to avoid any GOFF
features that are not supported by the linkage editor (or the binder
pretending to be the linkage editor), obtain a load module.
What is not entirely clear is why anyone would wish to do so. (I can
think of a scenario or two, but none is very plausible.)
This bug in AMASPZAP was discovered by one of our customers. He tried to
ZAP one of his own exits and the ZAP failed.
We use GOFF and SECTALGN(256) for all of our in-house product build
assemblies. We also specify GOFF and SECTALGN(16) for any install-time,
SMP/E-driven assemblies in the field for user exits, etc. that have the
potential to include IBM code or macros that use 'LQ' constants. (It
happened with some JES2 macro a few releases ago. I can't remember the
exact details...)
You don't need blind luck to link-edit such a program. You just link it.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
