>Is it guaranteed by LE that the services potentilly invoked by CEEENTRY will not >violate those conventions? I.E., initial stack frame allocation, extend stack >frame, etc.? Otherwise saving/restoring outside of the prolog/epilog would vio
I'm sure that whatever LE calls does not violate LE's own requirements. That is the overriding requirement. >P.S. -- Given how long that z/OS itself has been 64-bit, it is somewhat suprising >to me that CEEENTRY and CEETERM do not have an option to save and restore all 64-bit >register contents by using an F4SA-format save area, at least, if not F5SA-format. >That would make a lot of sense for calling to assembler routines which use "G"rande >instructions, and we are talking about an assembler macro here... I have no idea if 31-bit LE provides a 144-byte savearea for target routines to save into. Maybe your state of surprise should be replaced by your (or your user group) submitting a requirement to make absolutely sure that your case is understood. Even for something perhaps fairly obvious, it always helps to have a user requirement on the books to justify whatever resources need to be expended. 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
