On 06/23/2017 07:54 PM, Frank Swarbrick wrote:
It must be encrypted such that when decrypted on an ASCII platform (or any
platform, really) it will be in ASCII. Not sure on the line separator
requirement, but I will find out.
Your comment about TLS ensuring the data is not altered in transmission is
interesting. As far as I know the only concern there is that in the past we've
sent files from z/OS (or more often sent files to z/OS) and the file ended up
being truncated (for example, the FTP client job was somehow cancelled part way
through). Or at least that is the concern. Not sure that TLS could guard
against that. (Yes, I know, Connect: Direct could, but we don't have C:D for
z/OS.)
It does need to be encrypted at rest, as it will be offsite at a location not
under our control.
Thanks! Frank
<snippage>
This is why I suggested doing the work using a Windows machine at
your location. Unless you are using a server, or have managed to
put an ftp server on a non-server copy of Windows, the ftp will
have to be done from windows.
The problem is, if the "file" to be converted to ASCII is size
huge (1TB or better), your Windows system may not be able to
receive it, so you may need to have it access some server that
can provide that size of a workspace via a network connection
(this is going to take longer with the I/Os involved).
However, if you still have tape, you can write the file from
EBCDIC to tape (where conversion will be done by I/O routines) in
ASCII. Once that is done, you can write to DASD with NO
Conversion, and then compress it and do the MD5 thing.
In this way, you [your company] is in control until it is sent to
the other entity. "You" will know if it is able to be "recovered"
as you need it to be (I assume back to EBCDIC...).
I'd suggest that you Zip the file before encryption. You won't
get very much in the way of compression once it is encrypted.
Have fun with checkpoint/retry using ftp. I've had to send files
several times before they finally made it complete to the
receiving entity.
Regards,
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
