Thank you Scott
I was actually noticing that I kept consistently getting blank output when
using varying fields so this should help.
The EBCDIC also might explain why I get something that looks like
gibberish on the display when I do get output.
I do have another question. Base64 decode is decoding the value back to
its binary form correct?
Technically should my output variable be of type B(binary) instead of a
character string?
Ultimately, I'll be applying this code to send a device token
Russell Wesh, PMP | Data Integration Specialist
Sumitomo Drive Technologies
Sumitomo Machinery Corp. of America
Tel: +1-757-485-3355 ext. 8633
Cell: +1-757-822-4446
Fax: +1-757-485-7190
www.sumitomodrive.com | How are we doing?
From: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)"
<rpg400-l@xxxxxxxxxxxx>
Date: 04/06/2015 05:24 PM
Subject: Re: Base64 Decode Help
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
One more wrinkle to this... to get the length right on the otuput
field, you'll need to start by expanding it to it's full size, then
shrinking it back to only the size you're using.
So you'd do this on recent releases:
%len(W#TKN2) = %len(W#TKN2:*MAX);
len = base64_decode( %addr(W#TKN:*DATA)
: %len(%trimr(W#TKN))
: %addr(W#TKN2:*DATA)
: %len(W#TKN2:*MAX) );
%len(W#TKN2) = len;
Or, on older releases you'd do this:
%len(W#TKN2) = %size(W#TKN2) - 2;
len = base64_decode( %addr(W#TKN) + 2
: %len(%trimr(W#TKN))
: %addr(W#TKN2) + 2
: %size(W#TKN2) - 2 );
%len(W#TKN2) = len;
I don't know whether the %trimr() on the 2nd line is really needed, that
depends on whether there are trailing blanks in W#TKN, but it shouldn't
hurt anything.
Also keep in mind that base64 preserves the binary value of the string.
So if your data was originally text data that was encoded in ASCII,
UTF-8, or something like that, the output will still be in ASCII or
UTF-8, or whatever. So if it is indeed text that you want to have in
EBCDIC, you'll need to convert it after you decode it.
-SK
On 4/6/2015 2:59 PM, Scott Mildenberger wrote:
Since they are varying you can't just use %addr of the field, you need
%addr(W#TKN : *data) so it points to the actual data part of the field
bypassing the length portion at the beginning. If you are not at a new
enough release use %addr(W#TKN : 2) instead. Do that for both fields in
the call.
Scott Mildenberger
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
RWesh@xxxxxxxxxxx
Sent: Monday, April 06, 2015 1:54 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: Base64 Decode Help
Apologies
D rc S 10U 0
D W#TKN S 50a varying
D W#TKN2 S 50a varying
midrange.com
