Another option is to getmain your storage once, and anchor it somewhere for later use. TCBUSER or a name/token pair are two obvious choices. You can also create a variable inside your rexx exec, from the assembler program, with your anchor and grab it each time your function gets called, assuming your function will be called over and over.
Todd > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Gerhard Postpischil > Sent: Sunday, January 13, 2008 8:57 AM > To: [email protected] > Subject: Re: Rexx external assembler functions and reentrancy > > > Yes. Generally, storage must be obtained and released if you > want your functions to be reentrant/refreshable (along with > other considerations). Static storage (generally) makes your > program reusable, at best. In a typical REXX function > environment, reentrancy is not required, but reusability is. > Dynamic storage comes with overhead, and should be avoided in > heavily used functions. Also if the amount of storage you use is > small, you might be able to use a word or two in the save area, > and not alter the corresponding registers. > > Gerhard Postpischil > Bradford, VT No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.2/1222 - Release Date: 1/13/2008 12:23 PM ---------------------------------------------------------------------- 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
