From: Rob Scott <[EMAIL PROTECTED]>
There seems to
be two schools of thought on using REXX address - the first one uses ONE
"ADDRESS ENV" statement followed by a number of quoted buffers that are
directed by REXX to that environment
The other school of thought puts an "ADDRESS ENV" on each statement
You prefer school (1) - I prefer school (2).
I use a different approach. I put the default address at the top of the REXX
exec and I *NEVER* let the default address change throughout the rest of the
exec. One glance at the top of the exec and I know exactly what the default
address is. An example (completely contrived) would look something like
this:
/* REXX */
address ispexec
"CONTROL ERRORS RETURN"
"ADDPOP"
"DISPLAY PANEL(MYPANEL)"
address tso "ALLOC F(MYFILE)"
address tso "PROFILE PREFIX"
"REMPOP"
address tso "FREE F(MYFILE)"
With this approach, no matter how big the procedure gets there is never any
confusion as to what the default address is. In addition, I don't need to
clutter things up by adding 'address ispexec' in front of everything that's
passed to ISPF. Put me down for prefering school (3). :-)
Dave Salt
SimpList(tm) - The easiest, most powerful way to surf a mainframe!
http://www.mackinney.com/products/SIM/simplist.htm
----------------------------------------------------------------------
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
