Re: Character conversion

[Dennis <iseries@xxxxxxxxxxxx>]

His responses indicate that that won't work.  He's saying that (for example) 78 would be represented as decimal 78 (hex 4E) rather than the hex 78 that your proposition would produce.

I've already given my opinion of that supposition.  :)


++
Dennis
++
 "When you go into court you are putting your fate in the hands of twelve people who weren't smart enough to get out of jury duty."
     -- Norm Crosby 
 

Sent from my Galaxy tablet phone.  Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"John Yeung" <gallium.arsenide@xxxxxxxxx> wrote:

> On Thu, Aug 4, 2011 at 10:51 AM, John McKee <jmmckee@xxxxxxxxxxxxxx>
> wrote:
> > But, those digit pairs are essentially packed unsigned decimal.
> >  All values are decimal.  Issue was how to get those values
> > converted from character string to single byte values.  So,
> > instead of two bytes containing F5F6 (zoned), a single byte
> > with 56 (no zones).
>
> Ah, so what you want to do is convert the integer value to a (hex)
> byte.  Just create a data structure with a 3-digit unsigned integer
> (data type 'U') and an overlaid single character.  Put your numeric
> value into the int and read back the char.
>
> John Y.
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.