On 2015-12-28, at 18:41, Lizette Koehler wrote: > Would it make more sense to change 0CL512 to 0LQ32 ? > > Does the 0CL512 place it on a quad word boundary? > Are you suggesting that AIADSECT is guaranteed to be on a doubleword boundary, but not on a quadword, so the number of possible slack bytes before a LQ is unknowable at assembly time?
But isn't it the job of HLASM, not Loader to generate the slack bytes? But it's a DSECT anyway. It's the programmer's responsibility, via USING or otherwise, to associate it only with a suitably aligned object at execution time. (I've been on the periphery too long; my Assembler knowledge goes little past XA.) >> -----Original Message----- >> From: Ed Jaffe >> >> Check this out... >> >> Try to assemble the following test program. Attempts to use AIALENTH as a >> duplication factor fail with 'ASMA080E Statement is unresolvable' >> while BIALENTH works just fine. Why? >> >> AIADSECT DSECT , >> AIAVRS DS 0CL512 >> DS 32LQ >> AIALENTH EQU *-AIADSECT >> >> BIADSECT DSECT , >> BIAVRS DS 0CL512 >> DS 32XL16 >> BIALENTH EQU *-BIADSECT >> >> TEST CSECT >> DC (AIALENTH)X'00' >> DC (BIALENTH)X'00' >> DC (AIALENTH)X'00' >> DC (BIALENTH)X'00' >> END -- gil
