Dave Cole, please raise a support case for this. APAR PH40885 exposed a bug when the duplication factor on a DXD involves a forward reference, for example:
DXD1 DXD (A)X A EQU 3 The problem is that if a DXD definition has to be deferred because it cannot be resolved immediately, the field which would normally point to the owning section (itself) is used instead to point to some information about the deferred definition, to be resolved after the end of the first pass. In the second pass, when the alignment is supposed to be checked against the alignment of the owning section, it ends up being checked against the deferred definition instead, in which the field corresponding to the alignment is unused, equal to zero, causing the warning. The good news is that this doesn't affect the object code output. Jonathan Scott, HLASM IBM Hursley, UK
