On 2014-08-19 11:29, Peter Hunkeler wrote: > > Under no circumstance must the macro generate code that would write into > storage it has not been given and I don't want the error to be caught and > displayed only at run time. > Peter Relson discussed "macro time" versus "run time":
On 2014-08-19 06:11, Peter Relson wrote: > > What is surprising to me in this discussion is that I have seen no one > mention that unless you have full control over the invocations, in all > likelihood there will be cases that cannot be evaluated at macro time no > matter what technique you choose; they have to be evaluated at run time. I believe three phases need to be distinguished: o The generative phase (SET*, MACRO, COPY, AIF, ...) o The translation phase (CSECT, EQU, DC, BALR, ... ) Classically, at least. Assembler H and more so HLASM blur the distinction between the first two. o Run time (EXEC PGM=) You'd probably be satisfied with detecting and reporting the error in either of the first two. -- gil
