I think the fix for APAR PH08424 is the one that corrects this issue.
The fix for APAR PH06572 addressed an issue with truncation of constants and
introduced the padding issue being discussed here.
Keven
On Mon, Apr 20, 2020 at 8:45 PM -0500, "Paul Gilmartin"
<[email protected]> wrote:
On 2020-04-20, at 18:31:19, [email protected] wrote:
>
> On 2020-04-21 02:29, Ed Jaffe wrote:
>> On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
>>> DC CL8'&RQS'
>> For such a case, I will always code:
>> DC CL8'&RQS. '
>
> Why not just apply the bug fix?
>
Possible need to support customers to whom the macro is
distributed as source but who can not be relied on to
apply the fix?
Hmmm. HLASM prints the PTF level on the SYSPRINT title
page. Is that available for a feature test at assembly
time? But that shows only the most recent PTF, not if
a particular earlier PTF has been applied.
No, don't multi-path in the source. Just fail and admonish
the user if downlevel.
-- gil
