No. In theory, but obviously you were creative enough to find a way.
I have done this too many times to count. How are you trying to do this, and what is it that is stopping you or what have you tried and what is it that makes you think it isn't working?
More details. FTP from the PC or the mainframe? What kind of emulation? FLEX-ES? Hercules?
If you want to use the contact feature to send me mail directly, go ahead. This isn't the most efficient method for a dialog.
==================
Your profile does not allow me to send you email, so you can go to mine and send one directly to me.
==================
Have not gotten anything from you, so I will just shotgun this one.
Unless I am going mainframe to mainframe, I always start the interactive ftp from the PC. You have to use different options and different techniques depending on what it is you are trying to transfer.
There are two issues I find that are problematic. 1. PCs use streams and the mainframe things in terms of records. 2. ASCII to EBCDIC translation issues.
A lot of this depends on exactly what you are trying to do. If you are talking character data in fixed length records, then when you transfer to the PC, the records get delimited with CRLF characters. When you send them back up, it puts them back in, but the file allocation can wind up not matching what you really want. I find it handier to preallocate the file on the mainframe with the proper DCB information, then transfer directly to that file.
FTP will lock an entire PDS when you are trying to load a member into it, so it is best to create a private PDS to load into that you know will not be locked by another process.
If you are trying to transfer binary data, then you have real problems. The EBCDIC to Windows code page translation is not symmetric with the Windows to EBCDIC translation. So binary data gets scrambled. In addition, because PC use stream processing, it may treat the CR or LF characters that may be in the data as record delimiters and do strange things to the data. Transferring in binary, and you lose any record boundaries that existed on the mainframe.
The best way to transfer binary data is to use TRSMAIN. This will compress the data and put it into fixed 1024 length records. You use the binary option on the transfer. When downloading to the PC, nothing special other than the binary option. When uploading to the mainframe, you need to preallocate the dataset as FB with LRECL=1024. Use binary transfer and it will put it back into the same format that you had on the other box. Then you use TRSMAIN to unpack the data into its original format. They have a newer version of TRSMAIN with a different name, but it is alias'ed to TRSMAIN anyway.
If you are transferring a bunch of files, you can use ADRDSSU to back it up, then TRSMAIN to put into FB format for transmission.
That is about all I can think of that might help at all without knowing the nature of why it doesn't work.