On 2018-04-16, at 20:48:39, Charles Mills wrote:
> Good grief! How many experienced z assembler programmers does it take to
> convert 12 bits of binary to hex?
>
Errr... One to write the code and twenty to prate about it on ASSEMBLER-LIST?
--gil
Good grief! How many experienced z assembler programmers does it take to
convert 12 bits of binary to hex?
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of glen herrmannsfeldt
Sent: Monday, April 16, 2018 3:06 PM
To: AS
> Maybe I'm missing something, as this is a bit trickier than the usual
> shlop, but wouldn't it be more efficient to OI the last byte of &TARGET
> with x'F0', and skip the MVZ? Using =C'0123...'-C'0' for the TR table of
> course.
Maybe you are planning to do this a few billion times.
Otherwis
Maybe I'm missing something, as this is a bit trickier than the usual
shlop, but wouldn't it be more efficient to OI the last byte of &TARGET
with x'F0', and skip the MVZ? Using =C'0123...'-C'0' for the TR table of
course.
On Mon, Apr 16, 2018 at 11:59 AM, Jonathan Scott <
jonathan_sc...@vnet.ib
Here's a simplified version of a macro which I've been using to convert
data to printable hex for over 30 years. It uses the extra one-byte
move instead of needing a pad byte, so that the user doesn't need to
know about that, and sets the zones to zero so that it only needs a
16-byte table, which
- Original Message -
From: "IBM Mainframe Assembler List"
Sent:Mon, 16 Apr 2018 09:06:37 -0400
On Sat, 14 Apr 2018 17:44:37 +1000, robi...@dodo.com.au wrote:
>>Since the object is to convert four decimal digits (range 0-9)
>>to EBCDIC, OC is sufficient.
> It is? This thread starte
On Sat, 14 Apr 2018 17:44:37 +1000, robi...@dodo.com.au wrote:
>Since the object is to convert four decimal digits (range 0-9)
>to EBCDIC, OC is sufficient.
It is? This thread started out about converting System Completion code to
three characters representing hexadecimal, then diverged into a m
