I was placing a file into queue for upload (drag and drop). Then, I select properties and change destination to new name as required and click on ok button. However, destination field now is empty, subsequent upload fails.
How to change destination file name for upload without rename of original file?
client: CoreFTP Version 2.2 build 1888 in Windows 7 professional (NTFS)
server: IBM z/OS Communications Server V2R2 (MVS Data Set)
Thank you, kind regards
Michael
Rename file during upload
Upload to PO data set is working (though with wrong syntax). But now we fail upload to PS data set with rename. For example:
source name C:\WindowsFileName.txt (too long for MVS)
destination name: 'USER.PS.DATA.SET.NAME'
It seems, the upload dialog expects a "/" symbol (slash) somewhere within the destination name. As long as we do not give it, the dialog simply rejects our input and clears the destination name field.
In connection definition, we explicitly chose host type of MVS. So what might be the trick to enter MVS host file names?
Upload without rename works as expected. However, this typically will not work due to very different naming conventions in Windows compared to MVS.
Thank you, Kind regards
Michael
source name C:\WindowsFileName.txt (too long for MVS)
destination name: 'USER.PS.DATA.SET.NAME'
It seems, the upload dialog expects a "/" symbol (slash) somewhere within the destination name. As long as we do not give it, the dialog simply rejects our input and clears the destination name field.
In connection definition, we explicitly chose host type of MVS. So what might be the trick to enter MVS host file names?
Upload without rename works as expected. However, this typically will not work due to very different naming conventions in Windows compared to MVS.
Thank you, Kind regards
Michael
Make sure you have the correct server selected under Advanced -> General -> Server Type.
You shouldn't see any "/" characters being used with the "MVS" server (MVS HFS might be a Unix based version of MVS so it uses them).
I'll add a note to see if the filename length can be truncated in a future build.
You shouldn't see any "/" characters being used with the "MVS" server (MVS HFS might be a Unix based version of MVS so it uses them).
I'll add a note to see if the filename length can be truncated in a future build.