Well some of us actually do exactly that, and here's the start of a routine
EXECANTL HMSECT ,
HMRDATA DEF
ANTRQTC MF=(L,EXECANTL_ANTRQ) ANTRQST parameter list
EXECANTL_ANTRCD DS F ANTRQST retcode
EXECANTL_ANTRSN DS F ANTRQST reason code
EXECANTL_ANTINF DS F,XL96 ANTRQST retinfo
*
HMRDATA
HMERH ADD,EXIT=EXECANTL_ABND,PRXO=(IDMP,IABM)
The HMRDATA macros declare the dynamic storage local to the code section (plus
SA, recovery data etc). All allocated up in a stack set up at program entry.
Sorry about the capitals though, no one's perfect.
-----Ursprüngliche Nachricht-----
Von: IBM Mainframe Assembler List [mailto:[email protected]] Im
Auftrag von John Gilmore
Gesendet: Donnerstag, 27. Juni 2013 19:28
An: [email protected]
Betreff: Re: wish? for two new instructions.
CC has made my point better than I did.
For reasons that I have never really understood assembly-language
programmers almost always use heap storage for DSAs instead of the
stack storage they should use. (Their failure to use an extension of
such a stack-based DSA for scratch/automatic/local storage is a
little, but only a little, more excusable.)
John Gilmore, Ashland, MA 01721 - USA
