What I suggested is that
1. The combination of legacy mapping macros and
legacy code using those macros causes lots of
PAGE0 warning.
2. Getting rid of the warnings requires a mass update.
3. A mass update is disruptive.
4. There is no easy fix.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf
of Jonathan Scott <jonathan_sc...@vnet.ibm.com>
Sent: Thursday, July 11, 2024 11:52 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting to CVT with FLAG(PAGE0)
What are you suggesting as a "fix"?
If a symbol such as CVTPTR has been defined with an EQU (as it
has since OS/360 in the 1960s) it obviously cannot be redefined
to make it relocatable (for example as a field in a DSECT)
without triggering compatibility problems in existing code.
Shmuel (Seymour J.) Metz writes:
> The problem isn't in the assembler, but in the IBM mapping macros that have
> EQU to absolute addresses. FLAG(, PAGE0) is doing what it is supposed to
> do.
>
> For new code, there's no issue: use, e.g., CVTPTR(,0), FLCCVT.
Jonathan Scott, HLASM
IBM Hursley, UK
