On Thu, 29 Dec 2011 07:48:42 +0100, Fred van der Windt wrote:
I know what code I want (a single MVI instruction) but need
to find the best (most readable and maintainable) way to
express it in HLASM.
Code a macro if readability is your goal and you do it often.
I previously suggested two ways
I want to use MVI to assign the low byte of value that is larger than 255. This
results in an ASMA031E error message:
** ASMA031E Invalid immediate or mask field
I tried to use ACONTROL to circumvent this issue:
PUSH ACONTROL
ACONTROL TYPECHECK(NOMAGNITUDE)
MVI FQC7001_OP+3
ACONTROL TYPECHECK(NOMAGNITUDE)
As far as I understand this should instruct the assembler not to check
the magnitude of the immediate value
NOMAGNITUDE Specifies that the assembler not perform magnitude validation
of signed immediate-data fields of machine instruction
operands
MVI does
Fred,
But it is a bit disappointing (and strange) that this option would work for
instructions like LHI but not for MVI or CLI
Here is my sore point
MVI CHAR,C'a' move in a lower case a
works.
But
MVI CHAR,CA'a' move in an ASCII lower case a
nor
MVI CHAR,CE'a' we
Martin Truebner noted:
Here is my sore point
MVI CHAR,C'a' move in a lower case a
works.
But
MVI CHAR,CA'a' move in an ASCII lower case a
nor
MVI CHAR,CE'a' we want an EBCDIC lower a regardless of codepage
DO NOT WORK.
I understand the reasoning, but I
It seems that you want an option like AUTOTRUNC rather than a TYPECHECK
sub-option, which is intended to reduce confusion about what one might
expect from different forms of immediate operand in some instructions.
Whatever the name, I want to be able to code for example:
MVI
