John K wrote: <snip> I had to turn off FLAG(PAGE0) for SWAREQ and TRKCALC.
</snip> SWAREQ addressed this almost 15 years ago. TRKCALC was changed over 15 years ago. Please avoid using ancient versions of macros. Shmuel wrote: <snip> The obvious example is CVTPTR, which currently is an absolute EQU. Changing that to a DS A would break compatibility. Any ideas on how to resolve the PAGE0 issue while remaing compatible? Does it require an HLASM enhancement? </snip> This was in response to my post that told what to do. So I don't know why the question is being asked. Jonathan's post (and any number of macros) show what to do. Michael S wrote <snip> Does this mean: A. Yeah, it is going to give that warning. You have to consider each case to determine if the warning is valid or not. B. I'm coding it wrong. C. I'm coding it right but there's a better way to code it that won't trigger the error. I like my compiles and assembles to be clean: no warnings. So I'm not a fan of option A. I suppose I could put in a compile option to set FLAG(NOPAGE0) in programs that are getting to the CVT. </snip> I'd have chosen choice D: "You're coding it in a syntactically correct way that you have asked to be flagged in case you have some other case that was not intended". And I'd choose the action that would logically go with your choice C. Now that you have found 2 errors and 2 cases of CVTPTR, you'll fix the errors and I'd think (least work, and most effective) change your uses of CVTPTR to specify a base reg of 0. . Peter
