|
HP OpenVMS Systemsask the wizard |
|
The Question is: We currently use the following sytax to manage FTP file transfers to/from remote servers on our Alpha 2100 (6.2) cluster: $ftp <ip address>/username=<"username">/password=<"password">/input=<file of ftp commands> And typically a file of ftp commands will contain something like: lcd disk$disc11:[jefftest.migtest_app_code_tree_root.STUDENTS.PROGS] get DKC5:[STUDENTS.PROGS]STP010.PCO (I.e. after connecting, get the file stp010.pco into the directory specified by the lcd command) OK When we try this method we get the following error: %SYSTEM-W-BADFILENAME, bad file name syntax Example: EDISON:>ftp 10.2.16.2/username="xxxxxxxx"/password="yyyyyyy"/input=DISK$DISC11:[JEFFTEST ..MIGTEST_KIT_WORK]FTP_COMS.FTP %SYSTEM-W-BADFILENAME, bad file name syntax OK If I move the file DISK$DISC11:[JEFFTEST.MIGTEST_KIT_WORK]FTP_COMS.FTP to my default directory it works OK : EDISON:>copy DISK$DISC11:[JEFFTEST.MIGTEST_KIT_WORK]FTP_COMS.FTP [jefftest]*.*;0/log %COPY-S-COPIED, DISK$DISC11:[JEFFTEST.MIGTEST_KIT_WORK]FTP_COMS.FTP;7 copied to DISK$DISC11:[jefftest]FTP_COMS.FTP;7 (1 block) EDISON:>ftp 10.2.16.2/username="xxx"/password="yyyy"/input=FTP_COMS.FTP 220- 220 puma FTP Server (Version V4.1-12) Ready. Connected to 10.2.16.2. 331 Username SYSDEVFTP requires a Password. 230 User logged in. Local directory now DISK$DISC11:[JEFFTEST.MIGTEST_APP_CODE_TREE_ROOT.STUDENTS.PROGS] 200 TYPE set to IMAGE. 200 PORT command successful. 150 Opening data connection for DKC5:[STUDENTS.PROGS]STP010.PCO (10.2.16.110,50738) 226 Transfer complete. local: DISK$DISC11:[JEFFTEST.MIGTEST_APP_CODE_TREE_ROOT.STUDENTS.PROGS]STP010.PCO;6 remote: DKC5:[STUDENTS.PROGS]STP010.PCO 82187 bytes received in 00:00:00.07 seconds (1070.14 Kbytes/s) 221 Goodbye. EDISON:> OK This method also works fine on our ds20e server (OVMS 7.3) The Answer is : The OpenVMS Wizard would encourage the use of COPY/FTP, as this allows for DCL symbol substitution and other useful command-level features. Your specified FTP server (on OpenVMS Alpha V6.2) is down-revision, and in need of an upgrade to V4.2 with the current ECO. The OpenVMS Wizard would encourage testing with spawned subprocesses, and to check the protections and file access paths involved. The "SYSTEM-W-BADFILENAME, bad file name syntax" error implies there is a file specification error somewhere within the processing. The use of logical names would be an obvious check; ensure that the subprocess has the specified logical name(s) available. Resolution of this will very likely involve investigation within the context of the current running enviroment, as indicated above. Please contact the support center directly. (Expect to be asked to install current ECO kits for TCP/IP Services on all platforms involved, and expect to be asked to upgrade from now-unsupported releases to more current versions.)
|