-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Edward Jaffe Sent: Friday, March 23, 2007 10:26 AM To: [email protected] Subject: Re: Macro List/Execute Forms (Was: Need help with Assembler ...)
<snip> > > One GREAT example is the IBM macros' use of branch rather than jump > instructions. Yes, they work as documented, but they conflict with the > exploitation of the (wonderful!) new base-register-constraint-relief jump > instructions. > <snip> How about the declarative macros ignoring SPLEVEL? This actually bit IBM internally when a developer did an assembly at SP3 but had specified SET=2. The STCB C/B generate in that case had all the code and length for access registers, but the module in question was specifically for XA. Can anyone say storage corruption? (STL, AI software development, IBM Prolog for 370, 1991). Similar things have continued to happen where macros for execution generate the correct code, but the declarative macros do not (based on SPLEVEL). The problem that one may have is, the lower level macro libraries may not be available during an assembly because IBM never implemented ASYSLIB (so one can point to a different concatenation to ensure the correct expansions). As a result, one must capture older macros and update them in private libraries to ensure that correct expansions are done. Regards, Steve Thompson ---------------------------------------------------------------------- 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
