>"... 216-byte save area (if using F5SA) or 288-byte save area >(if using F8SA)..." > >but your layout of F5SA (p. 11) is 52 words (208 bytes) and >your layout of F8SA (p. 12) is 70 words (280 bytes)
We think of the save area as 216 bytes or 288 bytes. It was perhaps laziness on my part that led to not showing the undefined bytes. The defined bytes are all properly shown. The undefined ones are not. The mappings in IHASAVER show those undefined bytes. As to your point about allocating using space based on a format shown in a book, that is not using best programming practices when a symbol is provided in a macro. Still, even if you do allocate 208 bytes, since no one will be using the 209th to 216th bytes, there won't be a problem. Regardless, thanks for letting me know, as I would intend to get it corrected. >On pages 21, 23, and 241 you refer to a F6SA; but you never define >that; how is it different from a F4SA? It has no similarity at all. The string F6SA (as with any of the FxSA strings) identifies how the caller's registers were saved. As shown, both F1SA and F6SA indicate that registers were saved on the linkage stack. The fact that you have allocated 144 bytes of save area in addition to saving registers on the linkage stack does not state how a callee may use those 144 bytes. The publication is correct. >I'm afraid this section is full of carelessness like that. Most >uncharacteristic of Peter. Please be specific. The section you show was not careless in any way. It was fully intentional. The fact that F6SA says that the area is 144 bytes (or larger) does not characterize its format. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
