The same would be true if you used macro parameters.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [[email protected]] on behalf of Tony Thigpen [[email protected]] Sent: Monday, May 3, 2021 5:24 PM To: [email protected] Subject: Re: [PossibleSpam] Re: AREAD question Because the AREAD enables building the built-in error trapping logic. If the reg is too large or negative, it's trapped automatically. And, I don't have to remember to change the limit edits every time I add something to the branch table. Tony Thigpen Steve Smith wrote on 5/3/21 5:13 PM: > Why not just have a macro to generate each entry, and not mess with AREAD > at all? > > Like: > INITAPI PERF_ENT 00 > ACCEPT PERF_ENT 01 > ... > > Seems like you'd save a bunch of code, besides avoiding AREAD complications. > > sas > > > On Mon, May 3, 2021 at 5:03 PM Tony Thigpen <[email protected]> wrote: > >> I use LOCTR heavily in my programs. Separate areas for base code, >> basr'ed to code, lits, acons, just to name a few. It will not help me >> with this issue. >> >> The following is the code that uses the AREAD macro that I am working >> with. The macro is attached. (I have trimmed down the source call a bit >> as the real one has a lot more entries in the table. >> >> PERFORM_ON (R3),BAD_VALUE=ERRNO_20000 >> INITAPI 00 >> ACCEPT 01 >> BIND 02 >> CLOSE 03 >> CONNECT 04 >> FCNTL 05 >> ----- >> >> In reality, I think this is a very appropriate use of AREAD and I am >> just stuck with only using the macro in real program code and not in >> another macro. >> >> Tony Thigpen >> >>
