Re: Base64 decode

Greg,

If you need to use a CCSID(1208) field to write to the IFS, then you are using the IFS APIs incorrectly.

Since you know your data is in CCSID 1208, tell the open API that the data is CCSID 1208 and that it should not perform translation for you.  This will cause the file to be created successfully.  It does not matter what the CCSID of your RPG field is in that case.

-SK

On 7/20/2020 4:00 PM, Greg Wilburn wrote:

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).