If you don't know that your caller provided a 144-byte save area, you have to assume that they only provided 72 bytes. That's what F5SA is for. The low halves are stored as they are in a standard save area, and you can save the forward pointer at offset 8. You store the high halves in your 216-byte save area.
ATTACH(X) always provides a 144-byte save area to the attached task. ESTAE(X) exits are also provided a 144-byte save area. -- Tom Marchant On Mon, 24 Jan 2022 14:14:33 -0500, Dave Clark <[email protected]> wrote: >I'm given to understand that none of that information is helpful when a >called program receives control from a 2nd- or 3rd-party caller (i.e., any >caller not written on-site) in terms of being able to tell how much >storage the caller allocated for the savearea whose address is passed to >the called program. Now, if I've got that wrong, then please enlighten >me. Thanks.
