Data is getting corrupted in FTP

We have just now started FTPing a file to vendor in lieu of sending Mainframe tapes. We have a packed field for dollor amount.

The vendor has complained that during the process of encrypting the file and then transferring it through FTP, the packed fields are getting corrupted, so they are not readable on their end.
In reply to the corrupt field location and record no, they replied us: --

When viewed in hexadecimal format, every packed field needs to end in either a "C" or a "D". But the value ends in an "A", which cannot be converted to a real number.

Although ‘C’ and ‘D’ may be normal sign digits for certain data types used by certain languages, an ‘A’, ‘B’, ‘E’ and ‘F’ are also valid signs for packed decimal fields. ‘B’ and ‘D’ are considered negative signs while the other values indicate positive.

This is not the only issue ,Vendor has also complained about the other issues with data - like scrambled values - mixture of letters and numbers within a packed field.

Is this a issue with how the data is being transmitted ? If yes, how can we sort this out. Or do we need to change dollar amounts in normal character format instead of packed format?

Appreciate your help.

Make sure they are downloading in Binary.

What if they download it in ASCII, EBCDIC? does that make any difference , is this causing the issue?

I apologize for basic questions but my lack of hands on experiance just make it out of my reach.

ASCII was being used for getting the file from Mainframe to our FTP server from our FTP server to vendor its always been binary.

I have asked our FTP guys to use binary instead of ASCII, lets see how it goes, will get back on results.

Good news! The file worked in this format. Apparently the trick is downloading the file in binary mode as well as FTP'ing it using binary mode. Vendor was able to successfully read our packed fields and process the data.

Thanks Juniperr for your help.