@Scott,
Just wanted to thank you for your open source tools. They are invaluable and
I appreciate them tremendously. Hope you are doing well and continue to
improve back to normal quickly.
Thanks again,
Lynn
Lynn McManus
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Scott Klement
Sent: Wednesday, September 25, 2013 5:32 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Retrieving shipping label strings from webservices
Lynn,
There are always two CCSIDs involved in translation. The "from" and "to"
CCSIDs. So that the system knows what to translate from/to.
When you say "I assumed 37", what are you assuming is 37? And "I changed it
to 1208"... changed what to 1208?
I would think that UPS or FEDEX would send a label that's already in ASCII
or Unicode. It would seem rather odd that it'd be in EBCDIC. So most
likely, you'll want to translate FROM 1208 TO 37 in order to get something
that's in EBCDIC that you can then split into lines and print.
Or, you could use a *USERASCII print file and just send it directly to the
printer as-is. Assuming, of course, that it's in a printer language to
begin with. (Which is what you said, right? Though, that seems weird to
me, too... how could they know which printer language to encode the label
in?)
-SK
On 9/25/2013 5:22 PM, Lynn McManus wrote:
I am just decoding the label string received from UPS/FEDEX SOAP request.
I
assumed 37, and I could get a return from my translation to ascii, but it
is
unrecognizable. I changed it to 1208, what was recommended and my
translation is now blank, no errors just no translated data.
midrange.com
