Oh sorry, the from and to. I assumed it came from:37 and found information
that led me to believe it should be 1208 so I changed the from CCSID to
1208.
In my label request to UPS or FedEx, I do indeed specify what printer
language I need returned. ZPL for my zebra printer is my choice.
When viewing my data during debug, after encoding it does not appear to be
in a state for direct printing, so my thought was to translate to ASCII and
store on IFS to print.
Please correct me if I am mistaken that this is a valid way to approach this
issue.
Thanks!
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
