Dennis-

Thanks for the example. And to your point, I was looking at the returned
data in hex mode when I realized what had been returned and wrote the
email, so I guess that is why I had hex on the brain. I realized after I
sent it that I wasn't technically accurate, but I figured everyone would
get what I meant. Almost sent a follow up but decided against it.

Since everyone seemed to follow, I suppose my less than perfect wording was
adequate but not accurate. :-)

Thanks again for the example.


On Mon, Apr 23, 2012 at 3:31 PM, Dennis Lovelady <iseries@xxxxxxxxxxxx>wrote:

Just remember, the character data here does not contain '20.345'. If
it did, it would be easy. The data here is in hex and I need to get
it to packed.

To quote Tom Hanks: I don't even want to think about what they're not
teaching you in school! Hex, in this context, is a human's view of the
data. Packed has to do with the way the data is stored. Their usage is
not
interchangeable, and neither is in/compatible with the other.

What you've said is equivalent to "I wanted to send data to by friend but
all he received was ones and zeroes."

At any rate, the code found here will, I believe, do exactly what you want.
http://code.midrange.com/83a6933d01.html

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Too bad all the people who know how to run the country are busy driving
taxis and cutting hair."
-- George Burns

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].