Re: Character conversion

["John McKee" <jmmckee@xxxxxxxxxxxxxx>]

In the event that the two digits were 7 and 8, in a character string, the hex values (zoned) would be F7F8.  Goal is to convert zoned to unsigned packed, so F7F8 converts to 78 not 4E.

I believe I messed up earlier in terminology.  

John McKee

-----Original message-----
From: Dennis iseries@xxxxxxxxxxxx
Date: Thu, 04 Aug 2011 10:52:56 -0500
To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
Subject: Re: Character conversion

> 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.