This is what came to my mind, too.
We are talking about this ASSEMBLER or machine instruction:
MVC 0(16,R1),=CL8'EJESPOP PATHNAME' Set cmd name/parm
which, IMO, could be diagnosed as containing a possible run time error
at assembly time.
Others, which sometimes occured to me, and which I had some hard time
to find, are of the following kind:
LH Rx,HALFWORD
...
STH Rx,HALFWORD
and then, some place
ST Rx,HALFWORD
(wrong opcode, simple mistake).
Or, another thread some days ago:
N Rx,=X'0C'
It would be very nice, if there were an ASSEMBLER option to flag such
statements
that have the potential to generate run time errors. Or: a tool that
reads the
ASSEMBLER source text and checks for such errors. BTW: I wrote such a tool
for PL/1, which is much like the first passes of the compiler, without
code generation;
it is possible to add site-specific coding rules to the tool, so that
they can be enforced
during program transport, that is, change management. Please contact me
offline,
if you want to know more on this.
Kind regards
Bernd
Am 01.05.2015 um 18:44 schrieb John Gilmore:
The modified statement is, of course, a blundering one. The modifier's
zeal outran his skills.
Still, it seems to me that situations like this one in which 1) an explicit
length is provided and 2) there is a mismatch between this length and that
of the literal involved should be noted by the assembler.
Such a messaged would at worst be innocuous.
