Ray Mullins wrote:
Steve, welcome to MF=L/E land.
Note - the following is really simple, and merely a starting point.
[snip]
It's good practice to generate an MF=L list in your constant area so you can
define the MF=E area properly. It's not so important for OPEN, but for
things like ATTACH that have a lot of bits set, it's a lifesaver.
There are actually two different macro list/execute techniques.
1. The older macros use what is known as the "conventional" list form.
The MF=L expansion of these macros actually generates data which must be
copied from your constants to your dynamic area at run time prior to
invoking the modify form (if available) and/or execute form of the
macro. The OPEN macro uses a "conventional" list form. See
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a270/1.9.1
2. The newer macros generally use what is known as the "alternative"
list form. These macros merely reserve space for the parameter list in
your dynamic working storage area. You do not put the MF=L invocation in
your constants area; you do not copy the parameter list at run time.
Instead, you simply place the MF=L invocation in your working storage
DSECT. At run time, the execute form of the macro clears the entire
parameter list to zeros and then fills in every needed parameter. There
is no modify form. The IXGBRWSE macro is an example of a macro that uses
the "alternative" list form. See
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a270/1.9.2
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
