From: "retired mainframer" <[email protected]> Sent: Monday, May 04, 2015 4:35 AM
But the fact that some bits are already set means the result of the OR could have a different value than the LSB of the register, resulting in more bytes being moved than desired.
That's the intention. The result of the OR is, of course, what the programmer intended.
-----Original Message----- From: IBM Mainframe Assembler List [mailto:ASSEMBLER- [email protected]] On Behalf Of robin Sent: Sunday, May 03, 2015 7:36 AM To: [email protected] Subject: Re: Option to Prevent Data Loss Due to Truncation of Nominal Value From: "Mike Shaw" <[email protected]> Sent: Sunday, May 03, 2015 4:28 AM >A good idea, but the HLASM should not warn on zero lengths coded in MVCs > that are EX targets: But such an MVC can have a non-zero length. The EX instruction ORs together the LS 8 bits of the register with the 8 bits in the second byte of the subject instruction.
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
