That still uses hex notation for character data, which is what I'm trying to 
avoid.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר

________________________________________
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf 
of Tom Harper <000016c16a7381bc-dmarc-requ...@listserv.uga.edu>
Sent: Friday, March 29, 2024 1:12 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Complex immediate fields

Seymour,

How about this:

   LLILH R15,X’4000’

Tom Harper
Phoenix Software International

Sent from my iPhone

> On Mar 29, 2024, at 12:56 PM, Seymour J Metz <sme...@gmu.edu> wrote:
>
> Back in he Assembler XF era I would code something like
>
>         LA    R0,L'DEST
>         LA    R1,DEST
>         XR    R15,R15
>         ICM   R15,8,=C' '
>         MVCL  R0,R14
>
> On current hardware there is an IILF (LFI) instruction, and I would like to 
> use it instead of the XR/ICM sequence. I consider
>
>         LFI   R15,X'40000000'
>
> to be ugly, and would like to be able to either use an immediate field 
> combing CL1 and XL3 pieces or to refer to an EQU defining that combination. 
> Is there any way to do that in HLASM?
>
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> עַם יִשְׂרָאֵל חַי
> נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

Reply via email to