Your wiki note is incorrect. MVCL doesn't use the high-word for its length registers. And 'O' instructions do not insert, they OR (duh). OILH is useful when a length has already been loaded, and you know the high byte is zero. OILF is overkill, but some say you can never have too much overkill.
sas On Thu, Aug 17, 2017 at 12:08 PM, Richard Kuebbing <[email protected]> wrote: > I have a note in my wiki that says this is possible > > OIHF Rx,X'40000000' inserts X'40' into high order byte for pad character > > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:[email protected]] > On Behalf Of Steve Smith > Sent: Thursday, August 17, 2017 12:04 PM > To: [email protected] > Subject: Re: Source address significance for clearing MVCL > > HLASM doesn't do "obviously I meant" (aka DWIM). > > The source address register is ignored, doesn't have to be cleared, and will > not be changed, when the source length is 0. btw, the cool modern way to set > that with one instruction is LLILH Rx,x'4000' > (e.g.). Fair warning, this clears the high-word, if that matters to your > program or environment. > > sas > > On Thu, Aug 17, 2017 at 11:27 AM, Robin Vowels <[email protected]> wrote: >> From: "Charles Mills" <[email protected]> >> Sent: Friday, August 18, 2017 1:04 AM >> >> >>> I'd need a whole lot more than two SR R2,0's. >> >> >> Obviously I meant SR R2,R2. >> >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus > > > > -- > sas > > > ----------------------------------------- The information contained in this > communication (including any attachments hereto) is confidential and is > intended solely for the personal and confidential use of the individual or > entity to whom it is addressed. The information may also constitute a legally > privileged confidential communication. If the reader of this message is not > the intended recipient or an agent responsible for delivering it to the > intended recipient, you are hereby notified that you have received this > communication in error and that any review, dissemination, copying, or > unauthorized use of this information, or the taking of any action in reliance > on the contents of this information is strictly prohibited. If you have > received this communication in error, please notify us immediately by e-mail, > and delete the original message. Thank you -- sas
