On Tue, 6 Feb 2018 01:16:46 +0000 Jon Perryman <jperr...@pacbell.net> wrote:
> > Shmuel wrote: > > While PL/I macros can't extract the attributes of variable > names, > > they are in most regards as powerful as HLASM > > > macros and syntactically cleaner. > > Would anyone be interested in my CALC macro. Yes. I would be very interested. Thanks, Manfred > To me, the most > important feature is getting a CB address without all the USING and > load statements. It may take a few days to find and make usable > outside my macro environment. > In the following example, it loads R3 > with the TSO PSCB address: > > #CALC .(R3)=PSATOLD=>TCBJSCB=>JSCBPSCB > USING PSCB,R3 > > HLASM macro language is a hodgepodge and could definitely use a major > face lift. It has many important features but not completely. > Fortunately the macro language is robust enough that there is almost > always other ways to do something even though you may not love it. My > #CALC is a good example of some of the compromises you need to make. > > I don't know PLI macro's so I did a little research. The deal breaker > is that it appears to be a pre-processor language rather than macro > language. Is there a way to call the same macro in different > locations with parms for tailoring? > > Regards, Jon.
