Unpacking x'0123' gives you x'F0F132'; the OI then gives you x'F0F1F2'; what 
you want is x'F0F1F2F3'. Or with an UNNPK length of 4 you get x'F0F0F1F2'; 
still not what you want.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on behalf 
of Keven <k...@k3n.us>
Sent: Thursday, April 12, 2018 7:40 PM
To: ASSEMBLER-LIST@listserv.uga.edu
Subject: Re: SDWA - SDWACMPC conversion





                “Keep in mind that UNPK swaps bits 0-3 of the right byte with 
bits 4-7.”
That’s why the Or Immediate is there; it enforces a zone nibble of 0xF for the 
last hex digit and ensures correct execution of the TRanslate.









On Thu, Apr 12, 2018 at 3:00 PM -0500, "Seymour J Metz" <sme...@gmu.edu> wrote:










Keep in mind that UNPK swaps bits 0-3 of the right byte with bits 4-7.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List  on behalf of Keven
Sent: Wednesday, April 11, 2018 4:15 PM
To: ASSEMBLER-LIST@listserv.uga.edu
Subject: Re: SDWA - SDWACMPC conversion





                Good point; I should have stuck with HEXTBL-240 but I decided 
last minute that hexadecimal notation would make for a better aesthetic and for 
some reason X’C0’ stepped forward instead of the apposite value.
Using the UNPK/OI does mean no reading past the last byte of the value to be 
converted which may be desirable for a generalized implementation.
Keven









On Fri, Apr 6, 2018 at 9:22 AM -0500, "J R"  wrote:










As you're concerned with robustness, it might be better to address the 
translate table thus:

 TR    ZONED,HEXTBL-X'F0'        X'C1C2C3'

> On Apr 5, 2018, at 18:29, Keven  wrote:
>
> TR    ZONED,HEXTBL-X'C0'        X'C1C2C3'

Reply via email to