Charles In the case you outline the overhead is probably non-trivial - but unavoidable.
This is one of the reasons for making the "delete dataspace on pull" optional in STEMPULL - so that a "init" style rexx exec could load up all the required variables and then other execs can pull them down multiple times if required. Obviously not all users of STEMPULL/PUSH will fall under this design umbrella and will have to keep going through the IRXEXCOM loop. Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] http://www.rs.com/portfolio/mxi_g2 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Charles Mills Sent: 16 January 2007 19:32 To: [email protected] Subject: Re: PULL? PUSH? STEM? (was: REXX EXECIO changing LOWERCASE TO UPPERCASE) Thanks. Nice looking code! I kind of wonder about the overhead of looping through all of the Rexx variables with IRXEXCOM. A lot of work if the program has lots of variables, but the stem in question has only a few tails. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rob Scott Sent: Tuesday, January 16, 2007 4:12 PM To: [email protected] Subject: Re: PULL? PUSH? STEM? (was: REXX EXECIO changing LOWERCASE TO UPPERCASE) Charles Checkout the STEMPUSH and STEMPULL rexx functions on www.mximvs.com - I wrote these some time ago to allow rexx stems to be passed between rexx execs in the same address space. The rexx variables are pushed onto a dataspace stack and the STOKEN for the stack is passed to the other rexx exec where it is used to pull the stem variables down. ---------------------------------------------------------------------- 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
