RE: Base64 decode

Scott,

Thanks... it definitely was encoded. I copied the 40K string and placed it into an online decoder.
Decoded, it represents ZPL (Zebra Printer Language) for a label.

Once I changed the CCSID of the field DECODED to 1208 (to match the incoming data), I was able to write it out to an IFS file.
Before doing so (assuming the DECODED field was 37) the IFS file was illegible.

It must be something with RDi and displaying the resulting field... I know RDi gets unstable when trying to view large character variables while in debug. That is what prompted me to write out the result to a stream file. In this case, it may be useful to keep it (to reprint a USPS label w/out having to call the web service again).

Thanks,
Greg

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, July 20, 2020 3:00 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Base64 decode

Hi Greg,

The code looks okay to me (but, of course, I don't know what the
document looks like or what the expected output is meant to be.)

If you look at 'encoded' immediately before running base64_decode, does
it look like valid base64 text?

You say that 'decoded' is "blank".  What do you mean by that?  it
contains EBCDIC blanks (i.e. x'40404040 ....')?  Or do you mean the
length is 0?  What are you expecting it to look like?

It seems unlikely that 'decoded' will be EBCDIC text (unless you know
that it should be?).  Base64 will treat it as binary data, so the output
will have exactly the same binary values as the data that was input to
create the XML document in the first place.   In my experience, that's
almost never EBCDIC text.  It may be binary data, like an image, or it
may be Unicode data (or perhaps less likely, ASCII data).  But, again,
I'm not familiar with the application.   My point is that displaying it
in a debugger is not likely to be very satisfying...

-SK

On 7/20/2020 10:13 AM, Greg Wilburn wrote:

I'm using http_post_xml() and a callback procedure to parse the response:

After running this through debug, the resulting length LEN is 33243, but the value of variable DECODED is blanks.

I'm assuming the response data is UTF8 as indicated in the HTTP Debug header.
The encoded data length of the <base64LabelImage> element ( in http debug text file) is 44325

rc = http_post_xml(
'https://elstestserver2.endicia.com/LabelService/EwsLabelService.asmx'
: %addr(SOAP) + 2
: %len(SOAP)
: *null
: %paddr(EndOfElement)
: %addr(userData)
: HTTP_TIMEOUT
: *omit
: 'text/xml; charset=UTF-8; +
SOAPaction="www.envmgr.com/LabelService/GetPostageLabel"'
);



P EndOfElement B
D EndOfElement PI
D userData * value
D depth 10I 0 value
D name 1024A varying const
D path 24576A varying const
D value 65535A varying const
D attrs * dim(32767)
D const options(*varsize)

dcl-s encoded varchar(65535);
dcl-s decoded char(65535);
dcl-s outSize uns(10);
dcl-s len uns(10);

select;
when name = 'Status';
response.status = value;
when name = 'TrackingNumber';
response.trackNbr = value;
when name = 'Base64LabelImage';
encoded = value;

outSize = %len(decoded);
len = base64_decode( %addr(encoded:*data)
: %len(%trim(encoded))
: %addr(decoded)
: outSize
);
response.label = %subst(decoded:1:len);

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, July 20, 2020 10:53 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Base64 decode

More information, please?


On 7/20/2020 8:52 AM, Greg Wilburn wrote:

It's been a while since I've had to decode something... I'm consuming a web service that is returning a Base64 encoded value... the web service is SOAP XML and returns a corresponding XML response encoding=UTF-8.

I've tried using Scott Klement's Base64 service program... I'm not getting an error, but the resulting value is blank?

Do I need to do something with the data before decoding?

TIA
Greg