On Aug 22, 2010, at 06:27, Don Higgins wrote:
> I support John Baker's request to add HLASM option to force odd length
> literals to next even length by adding pad character when referenced by
> relative instructions. The single extra pad byte can be added at the time
> the literal is added to the literal pool reference table without any other
> special flags required.
>
Given that pending literals are kept in the literal pool in their
source text representation and this is unlikely to change, I wonder
how the assembler might transmogrify the operand of
LARL 4,=AL3(*+9000000)
to have even length.
I think it's more reasonable to expect only that the assembler
provide the programmer with a warning of the use of an
indeterminate construct.
Surely similar problems must have arisen with the s360 which
generated a specification exception at execution time for
reference to an unaligned operand, which may have been coded
as a literal.
-- gil
