While it may not be relevant, what is in the PDS. From your description, it appears that you are talking about a load library that contains executable code. [Contrast this to a PDS with source code.]
We do this on a regular basis. And, we have had problems in the past, or some of our customers have had problems. In some cases, it is a problem with the particular file transfer tool being used.
While it is not as convenient, you may want to try the most basic approach: Instead of using whatever 3270 emulator you have, when you LOGON to TSO, stay at the READY prompt. Then, open a command prompt window on your PC. Use the SEND/RECEIVE command to transfer the file rather than any tool built into the emulator.
e.g., RECEIVE LoadLib.Bin a:'hlq.applic.Unload'
This format assumes:
1) Your 3270 session is 'Session-A'
2) You have IND$FILE installed on TSO.
3) The default options for the RECEIVE are NOT
ASCII and/or CRLF. Either of these options turned on
will mess up the transfer.
4) The file 'hlq.applic.UnLoad' is the sequential file
created by unloading the PDS.
You should be able to reverse this process substituting SEND for the RECEIVE.
A couple of additional pointers:
1) Before you do the SEND to upload the file, you MUST
preallocate the target file on TSO. I have found that
it is rare that the allocation attributes provided by
the SEND and IND$FILE are acceptable. And, the attributes
must be identical to the original file.
2) Instead of specifically using IEBCOPY, try using the TSO
TRANSMIT and RECEIVE commands. *Theoretically* there should
be no difference. TRANSMIT and RECEIVE use IEBCOPY. But,
again from painful experience, there are times when TRANSMIT
and RECEIVE work after multiple failures from just using
I hope this gets you started. As I said, we do this on a regular basis with no problems. But, I do avoid 3270 emulator file transfer tools. There appear to be some [unknown] problems because of special characters in EBCDIC that drive ASCII PCs nuts. One other tip: If you are going to transfer the downloaded file to another PC, over the Network or just by doing a copy, I recommend ZIPping the file first. Again, there are strange gremlins at work here.