Always use "/" to transfer files from a UNIX host to a Windows host, or from a Windows host to a UNIX host. This is because the operating system interprets "\" and lsrcp opens the wrong files.
For example, to transfer a file from UNIX to a Windows host:
lsrcp file1 hostA:c:/temp/file2
To transfer a file from Windows to a UNIX host:
c:\share>lsrcp file1 hostD:/home/usr2/test/file2
file_name
Name of source file. File name expansion is not supported.
Examples
lsrcp myfile @hostC:/home/usr/dir1/otherfile
Copies file myfile from the local host to file otherfile on hostC.
lsrcp user1@hostA:/home/myfile user1@hostB:otherfile
Copies the file myfile from hostA to file otherfile on hostB.
lsrcp
Appends the file myfile on hostD to the file otherfile on the local host.
lsrcp /tmp/myfile user1@hostF:~/otherfile
Copies the file myfile from the local host to file otherfile on hostF in user1’s home directory.
Diagnostics
lsrcp attempts to copy source_file to target_file using RES. If RES is down or fails to copy the source_file, lsrcp uses either rsh or the shell command specified by LSF_RSH in lsf.conf when the
lsrcp uses rcp.
Limitations
File transfer using lsrcp is not supported in the following contexts:
◆If LSF account mapping is used; lsrcp fails when running under a different user account
◆On LSF client hosts. LSF client hosts do not run RES, so lsrcp cannot contact RES on the submission host
◆Third party copies. lsrcp does not support third party copies, when neither source nor target file are on the local host. In such a case, rcp or rsh (or the shell command specified by LSF_RSH in lsf.conf) is used. If the target_file exists, lsrcp preserves the modes; otherwise, lsrcp uses the source_file modes modified with the umask (see umask(2)) of the source host.
You can do the following:
Platform LSF Command Reference 271