HP 3000s do lots of duty with data from outside the server. The 3000's FTP services sit ready to handle transfers from the world of Windows, as well as other systems, and PCs far outnumber the non-Windows computers networked to 3000s. Several good, low-cost FTP clients on Windows communicate with the 3000, even though MPE/iX still has some unique "features" in its FTP server.
Our former columnist John Burke once reported that his HP 3000 emitted a second line of text during an FTP session that could confuse the open source FTP client FileZilla:
FileZilla issues the PWD command to get the working directory information. On every other system I've tried, the result is something like 257 "home/openmpe" is the current working directory However, MPE responds with something like 257-"/SYSADMIN/PUB" is the current directory. 257 "MGR.SYSADMIN,PUB" is the current session. The second line appears to be confusing FileZilla because it reports the current directory as /MGR.SYSADMIN,PUB/, which of course does not work.
Back when it was a freeware, Craig Lalley took note of a worthy solution, WS-FTP from IP Switch. The product is now for sale but its client is not costly. And an MPE setting can remove the problems that can choke up FileZilla.
Chris Thompson of The Internet Agency, another 3000-friendly vendor, echoed the praise of WS-FTP. Thompson also sells MPE software, the MPE/iX Enterprise Client. Alas, he noted that the much-praised Whisper Technology, now defunct, also had a laudable FTP product
WS-FTP is a really good product. Also, try FTP Surfer, which is freeware from Whisper Technology Limited. Usually we use this product to FTP to our 937. It's always worked well.
But as might be expected, there's a way to make HP's FTP behave in less unique and more compliant way. Lars Appel, who ported Samba to the HP 3000 before he left HP's support team, delivered the answer that makes FileZilla work with the 3000
Try the "SITE POSIX ON" command in your FTP session already (or the respective POSIX=ON setting in the SETPARMS.ARPA.SYS config file to change the default, in case the FileZilla session cannot issue "site"
Burke once reported that "POSIX = ON in the SETPARMS file did the trick, eliminating the message that confused FileZilla. I've been using FileZilla for all my ad hoc FTP needs for some time now — works great to all manner of Unix, Windows and Linux systems."
HP's James Hofmeister, who's led the effort to keep FTP up to date on the 3000, took issue with claims that the 3000 doesn't play well with Web-based FTP clients.
Lots of work went into an implementation of the FTPSRVR to support web access to the 3000... The "SITE POSIX ON" command can be sent by a FTP client and the 3000 FTPSRVR will emit Posix "standard" FTP output and will react like a Posix host (including file naming conventions).
It also is possible as documented to specify "POSIX=ON" mode in the SETPARMS.arpa.sys file and achieve this functionality system-wide for all non-3000 client to 3000 FTPSRVR connections; again the FTPSRVR will emit Posix "standard" FTP output and will react like a Posix host (including file naming conventions).
Warning: Before you specify "POSIX=ON" mode in the SETPARMS.arpa.sys file, make sure you read the FTPDOC file closely; as you are warned that MPE file syntax will "no longer" work; The 3000 FTPSRVR is acting in Posix mode.