$ is need to differentiate
Filename. You can disable Unix mode by defining the logical
TCPWARE_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
TCPWARE_FTP_UNIX_STYLE_CASE_INSENSITIVE to accept Unix directory and file specifications but ignore the case of a file.
Restricting access to the FTP server requires using a packet filter. The example below is of a filter file that you can use as a template to help set up one that matches your needs. The comments in it describe what each line does. The filter file should be named
TCPWARE:FILTER-line-ID.DAT, replacing line-ID with the TCPware line-ID in use on your system. For example:
NETCU SHOW NETWORK lists the lines configured on your system.
TCPWARE:STARTNET.COM adds the filter automatically during startup if the filter file has a proper name. You can add the filter manually using the
NETCU ADD FILTER command. For example:
$ NETCU SET FILTER EWA-0 TCPWARE:FILTER-EWA-0.DAT ! begin filter-LINEID.dat ! ! permit only IP address on the 126.96.36.199/24 network to FTP to this system ! ! Action proto saddr smask daddr dmask dport ! permit tcp 188.8.131.52 255.255.255.0 0 0 eq 21 ! ! Permit IP address 184.108.40.206 to FTP to this system ! permit tcp 220.127.116.11 255.255.255.255 0 0 eq 21 ! ! permit outgoing (established) FTP connections ! permit tcp 0 0 0 0 eq 21 established ! ! Deny all other FTP connections ! deny tcp 0 0 0 0 eq 21 ! ! Let all other IP traffic go through ! permit ip 0 0 0 0 ! ! End filter-LINEID
Following is an example of how to use FTP from a command procedure:
$ ! FTP files from this host to the ftp.univ.edu $ ! anonymous ftp server. $ ! $ ftp open ftp.univ.edu anonymous firstname.lastname@example.org cd "/download" put sendfile.txt quit $ exit
The problem was probably caused by the wrong format and attributes being applied to the patch when you unzipped it. Chances are that many, if not most, of the files can produce this error
To determine if this is the problem, verify the format of the saveset file by entering:
$ BACKUP/LIST kitname.A/SAVE
kitname is the name of the patch kit with the
.A extension that you extracted.
All the patch kits for TCPware are VMS backup savesets in ZIP format. This is so you can download a patch to any platform (VMS, Windows, UNIX, etc.) and later transfer it to your VMS system.
The zip files are the same zip format as the PC, and although unzipping them using a PC-based program separates the files correctly, the program applies the wrong format and attributes to the files. Only VMS can apply these correctly to a backup saveset file.
You can use either of two methods to correctly download and unzip patch kit files. The first is the recommended method:
IMAGE, then download
UNZIP.EXE(for VAX/VMS) or
UNZIP_ALPHA.EXE(for Alpha/VMS) to the
Then enter the command: MCR UNZIP patchkit.ZIP on a VAX or MCR UNZIP_ALPHA patchkit.ZIP on an Alpha system.
You could change the VMS attributes by entering the following VMS command:
SET FILE/ATTRIBUTES=(LRL=32256,RAT=NONE,RFM=FIX) kitname.A
TCPware's FTP server uses the OpenVMS default protection when creating a file. When an FTP client sends a valid username and password, the FTP server creates a process running under that username to then services the connection. This happens through the normal OpenVMS login process and executes the system-wide login command procedure (defined by the
SYS$SYLOGIN logical) and the login command procedure for that user (determined by the
LGICMD setting in the system authorization file). You can use the OpenVMS
SET PROTECTION/DEFAULT command in the login command procedures to determine what protections are used for newly created files.
For example, if the following command was added to the login command file for the anonymous account any new files created by the anonymous account would have a file protection that enabled world read and execute access:
$ SET FILE/PROT=W:RE/DEFAULT
TCPware does check for inactive FTP control connections and by default will close them after 10 minutes of inactivity. Use the logical
TCPWARE_FTP_IDLE_TIMEOUT to change this behavior. The logical can be set to a delta time to change how long the server waits before timing-out a connection, or if set to 0, the idle time-out is disabled. See the Managing FTP section of the TCPware Management Guide for more information on the
Put the password in quotes if it is upper or mixed case. TCPware’s FTP client will lowercase all usernames and passwords unless put in double quotes.