×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Peter,
Encryption and decryption operate on data as binary bit strings. Translating the data from EBCDIC to ASCII damages the encrypted data bit string, rendering it impossible to decrypt that data successfully.
Download the encrypted data using FTP in BINary mode, then decrypt that bit string data, and finally, translate the decrypted data from EBCDIC to ASCII, if needed.
NOTE: if that physical file encrypted contains binary or packed decimal fields, translation from EBCDIC to ASCII on the PC will also ruin the data in those fields. You may also need to consider doing something like CPYTOIMPF or convert the data in the file to a "comma delimited" stream file, possibly in ASCII, and then do the encryption on that data. This should avoid issues with binary or packed fields.
Hope that helps,
Mark S. Waterbury
On Tuesday, May 5, 2020, 5:47:26 AM EDT, peter jones <kirkhill@xxxxxxxxxx> wrote:
Hello,
A colleague has put together software to encrypt and decrypt a physical file using the standard API QC3ENCDT and QC3DECDT.
This software using AES works fine on the Iseries.
The QDCXLATE API was then used to convert the encrypted file from EBCDIC to ASCII.
He has had no success decrypting the file once it is transferred to a PC.
To copy the file from the Iseries he has used FTP, CA Data Transfer and CPYTOSTMF.
Any help appreciated, this is not the kind of work we normally do so probably need dummies guide level responses.
Thanks all.
Peter
midrange.com
