1. Home
  2. Support
  3. MultiNet
  4. FAQ
  5. FTP

MultiNet FAQ: FTP

 

When a UNIX client uses FTP to put files to my system the file names get changed, some have $’s added to them, why?

The $ is need to differentiate filename from Filename. You can disable UNIX mode by defining the logical MULTINET_FTP_UNIX_STYLE_CASE_INSENSITIVE to be true. You can do this in a user’s login command procedure to disable it for that one user or you can define the logical /SYSTEM to change the behavior for all users. You can also define the logical MULTINET_FTP_UNIX_STYLE_CASE_INSENSITIVE to accept UNIX directory and file specifications but ignore the case of a file.

Why does FTPing savesets from VMS to Windows cause the record length to change?

When FTPing files from VMS to a PC, the record length changes to 512; MultiNet savesets should be 2048, TCPware savesets should be 32256. In VMS V6.1 and above you can use the SET FILE/ATTRIBUTE to change the record length, but in VMS v5.x that command does not exist. What can be done on VMS v5.x system to change the file attributes?

Use the following sequence of commands to change the record length of the saveset: 

$ ANALY/RMS/FDL saveset.a

Edit the .FDL file and change the record length to 2048 for MultiNet or 32256 for TCPware. 

$ EXCHANGE/NET/FDL=saveset.FDL oldsaveset.a newsaveset.a

The newsaveset.a should be in the correct format with the correct record length.

This should work in all versions of VMS.

Can I configure different FTP access for different users?

Yes, by defining a system level logical name MULTINET_ FTP_username_CONTROL you can disable the following FTP rights for a user:

NOLIST
NOREAD
NOSPAWN
NOWRITE
NODELETE

For example, if you wanted to restrict the user JONES from using the LS, DIR, and PUT commands, you would define the logical as follows: 

$ DEFINE/SYSTEM/EXEC MULTINET_FTP_JONES_CONTROL "NOLIST,NOREAD"

Why do I get Invalid Block Side errors after installing a patch?

First check the saveset file to verify the format: $BACKUP/LIST kitname.A/SAVE where kitname is the file with the .A extension that you extracted. Chances are that many, if not most, of the files will give this error. All the patch kits provided for MultiNet are VMS backup savesets and are stored on our server on a ZIP format. This allows one to obtain the patch from our FTP servers to any platform (VMS, UNIX, Windows, etc.) to later be transferred to the VMS system.

Although the zip files are the same zip format as the PC, unzipping them using a PC based "un-zipper" program will separate the files fine, but since only VMS knows the attributes of a backup saveset, the PC will apply the wrong format to the saveset file.

There are two ways that you can fix this:

  1. The recommended way is to FTP the VMS unzip utility from our website at ftp://ftp.multinet.process.com/patches/. Depending in your architecture, you will need UNZIP.EXE (for VAX) or UNZIP_ALPHA.EXE (for Alpha). Before you download the files, make sure your FTP client is set to BINARY or IMAGE. Put the unzip file in the SYS$COMMON:[SYSEXE] directory. Then execute the command: $MCR UNZIP patchkit.ZIP on VAX; $MCR UNZIP_ALPHA patchkit.ZIP on Alpha
  2. Another way is to change the VMS attributes of the with the following VMS command: 
    $ SET FILE/ATTRIBUTES=(LRL=32256,RAT=NONE,RFM=FIX) kitname.A
    Then check the file validity by: 
    $ BACKUP/LIST kitname.A/SAVE

How can I run Multiple FTP servers on different ports?

The following steps will help you do this with MultiNet: 

$ copy multinet:ftp_server.com multinet_common_root:[multinet]ftp_2121_server.com

Then edit multinet:ftp_2121_server.com to establish a default directory, etc: 

$ multinet configure/server
 SERVER-CONFIG> copy ftp ftp_2121
 SERVER-CONFIG> select ftp_2121 
 SERVER-CONFIG> set socket-port 2121
 SERVER-CONFIG> set program multinet:ftp_2121_server.com enable ftp_2121 
 SERVER-CONFIG> write restart