Posix file movements, using FTP and more
August 31, 2015
I'm attempting to move files in and out of Posix namespace on my HP 3000. The file I've copied becomes bytestream, and has a REC of 1. But I want to transfer that file from Posix down to my PC, I need to maintain it's structure — but what appears to be happening is it's one long record, with no separators. Is there a way (automated) that I can move files in and out of Posix, maybe FCOPY, and be able to keep the structure?
Donna Hofmeister replies
Simply copying/renaming a 'regular' MPE namespace file into HFS-namespace will not change its structural attributes.
If the MPE file was ';rec=-80,,f,ascii' to begin with, it will still be that afterwards. And it will retain those attributes (cr/lf in particular) following an FTP transfer from your 3000 to [something else less enlightened].
To have a foreign/non-MPE filed take-on MPE fixed-record length attributes during an FTP transfer, simply add something like the following on your transfer line:
[put|get] non_mpe_file_name MPEFILE;rec=-NN,,f,ascii (making all the proper substitutions)
How do I get my HP 3000 to play well with Web-based FTP clients?
HP's James Hofmeister, who led the effort to keep FTP up to date on the 3000, replies
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).
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.