Well, we were talking about the IEANTRT service, right? [Look at the subject]
I've seen a rather clever EXIT code where IEANTRT was actually used to locate the DSA. And this was accomplished using just the EXIT caller's savearea, i.e. without any OBTAINs at all [of course, the EXIT caller's registers were also saved on and restored from the stack]. Personally, I liked this idea and now epmloy it whenever I am coding an EXIT [as in the original question]. Those, who are fortunate enough to always have a LIFO stack available to their disposal, may freely disregard the hint. -Victor- On Mon, 4 Dec 2006 23:31:05 +0000, john gilmore <[EMAIL PROTECTED]> wrote: >Chris Craddock wrote: > >>Well if they already -have- a save area of their own, then they >>presumably have already done a STORAGE OBTAIN (or whatever technique >>floats their boats) and they can probably spare a few extra bytes for >>parameter lists and return areas for IEANTRT. Those would be the >>sensible ones. > >and I understand why, but I need not be so polite. > >The use of STORAGE OBTAIN to acquire heap storage for a DSA is no longer >really acceptable. DSA's are classical examples of LIFO storage and they >should be obtained by a push operation on a stack, one's own or one supplied >and managed by an IBM [sub]system. > >A single DSA so obtained can, as Chris of course pointed out, be sized to >provide both a register-save area and any other LIFO storage that may be >required. > >John Gilmore ---------------------------------------------------------------------- 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
