While there are limits to this, in a COBOL program, you can declare your
codeset as <special-name> in the SELECT statement, and in the SPECIAL NAMES
section, give a name to EBCDIC, even as simple as EBCDIC IS EBCDIC. However.
None of the data can be binary or packed decimal if you do this. OTOH, PCs
are little endian (reverse byte order, or least significant byte first), and
the EBCDIC systems I have dealt with are big endian, so you have more hoops
to jump through if you need binary data in your EBCDIC file anyway.

Now, if you are going to ftp to an EBCDIC system, MVS TCP FTP (and probably
others) offers filters that can convert ASCII to EBCDIC during an "ASCII"
transfer, although I keep waiting for the day that an admin deconfigures
these filters and no one tells us their data isn't quite right for a few
days.