Release Notes
VMS/ULTRIX Connection Version 1.3
The VMS/ULTRIX Connection, Version 1.3 contains functional
enhancements and problem corrections. The major functional
enhancements for this field test include the following:
o Support for the Berkeley Internet Name Domain (BIND) resolver
o Support for dynamic routing
o Support for Digital remote procedure call (DECrpc), Version
1.0
The Release Notes are organized as follows:
o Operating system requirements
o Documentation
o Installation
o New Features and Functions
o Problems Corrected
o Restrictions
NOTE
Version 1.3 of the VMS/ULTRIX Connection is a
maintenance and functional update release. Prior
releases of the Connection include Version 1.0 and
1.2; there is no Version 1.1 of the Connection.
1 OPERATING SYSTEM REQUIREMENTS
You can install and run the VMS/ULTRIX Connection on any system
running VMS Version 5.0 or higher. However, to receive support from
Digital Customer Software Support Center, you must install the
Connection on VMS Version 5.3 or higher.
Also, the programming interface requires VMS Version 5.2 or higher and
DECwindows requires Version 5.3 or higher. All the other components
run on VMS Version 5.0 or higher. DECrpc Version 1.0 (which is
included in the the VMS/ULTRIX Connection kit) requires VMS Version
5.2.
Page 2
2 DOCUMENTATION
The VMS/ULTRIX Connection documentation set has been revised for this
release.
The VMS/ULTRIX Connection User's Guide has been added to the
VMS/ULTRIX Connection documentation set. This guide provides user
information on Telnet, FTP, and NFS. Previously this information was
contained in the VMS/ULTRIX Connection System Manager's Guide.
3 INSTALLATION
The following changes have been made to the installation process for
this field test of the VMS/ULTRIX Connection:
o The amount of free disk space required to install the
Connection has increased to 5400 blocks.
o The number of global pages necessary for the Connection
software to function properly has increased to 1800.
o The number of global sections necessary for the Connection
software to function properly has increased to 27.
o DECrpc Version 1.0 is included on media with the Connection.
As such, you must install the Connection first. See the
VMS/ULTRIX Connection Installation guide for more
information.
o UCX$ROUTE.DAT file format has changed. You must run
UCX$CONFIG to covert the file to the new format.
o The options of enabling the Berkeley Internet Name Domain
(BIND) resolver and dynamic routing have been added to
UCX$CONFIG. Even if you have installed previous versions of
the software, you should run the command procedure to enable
these options.
Before installing the VMS/ULTRIX Connection, read the Restrictions
section to see if any restrictions apply to your installation.
4 NEW FEATURES AND FUNCTIONS
This section includes information on new VMS/ULTRIX Connection
features and functions for the following Connection components:
o BIND
o Dynamic Routing
Page 3
o DECrpc
o Connection Management
o Network File System (NFS)
o Internet
o Telnet Client
o Telnet Server
o File Transfer Protocol (FTP) Client
o FTP Server
o Interprocess communications (IPC)
4.1 BIND
The Berkeley Internet Name Domain (BIND) service is a host name and
address lookup service for the Internet network. The BIND service is
implemented in a client-server model. The client software is referred
to as the resolver. The resolver allows client systems to obtain host
names and addresses from servers rather than from locally hosted
databases. As such, you can use the BIND service to supplement the
host address mapping provided by the local UCX$HOST file.
You can enable the BIND resolver by using the configuration procedure
(UCX$CONFIG.COM) provided with the Connection.
If the BIND resolver is running on your system, the Connection
searches the local host database to resolve a host name or address.
If it is unsuccessful, then the Connection queries the BIND server(s).
If you use the the UCX SHOW HOST * command, both are queried in the
same order.
You can access the BIND resolver by using the socket interface
routines gethostbyname() and gethostbyaddr(), or the UCX QIO
programming interface.
For more information on BIND, see the VMS/ULTRIX Connection
documentation.
4.2 Dynamic Routing
Dynamic routing allows hosts on a network to share routing information
and automatically update the Internet routing tables. The Connection
provides dynamic routing capabilities through its implementation of
the Routing Information Protocol (RIP). The Connection uses this
Page 4
protocol to maintain up to date information in the Internet routing
table entries.
You can manage the Connection's dynamic routing processes with the
following UCX commands. These commands are documented in the
VMS/ULTRIX Connection System Manager's Guide.
o SET ROUTE -- Enables you to create entries in the
SYS$SYSTEM:UCX$ROUTE.DAT
o SHOW ROUTE -- Displays routing information
o START ROUTING -- Starts the dynamic routing server
o STOP ROUTING --Stops the dynamic routing server
When stopped, the dynamic routing server flushes the Internet tables
of the dynamically created routes, leaving only those routes that
belong to the host's Internet active interfaces.
When you start or stop the dynamic routing server, informational
messages are written to the Network Operator console and log file.
For more information on the dynamic routing server, see the
Restrictions section and the VMS/ULTRIX Connection documentation.
4.3 DECrpc
DECrpc is the remote procedure call mechanism supported by the VMS
operating system. DECrpc is based on and is compatible with the RPC
components of Apollo's Network Computing System (NCS) Version 1.5,
which is a set of tools for heterogeneous distributed computing.
Using remote procedure calls, software applications can be distributed
across heterogeneous collections of computers, networks, and
programming environments. Distributed applications can take advantage
of computing resources throughout a network or Internet, with
different parts of each program executing on the computers best suited
for the tasks.
For more information on DECrpc, see the DECrpc release notes and
documentation.
4.4 Connection Management
The following UCX commands have been added. For more information on
these commands, see the VMS/ULTRIX Connection System Manager's Guide.
o The SET NAME_SERVICE command has been added. This command
modifies the system and process image parameters for the BIND
Page 5
resolver.
o SHOW NAME_SERVICE command has been added. This command
displays all information pertaining to the name service.
o The START ROUTING command has been added. This command
starts dynamic routing.
o The STOP ROUTING command has been added. This command stops
dynamic routing.
The following commands have been modified:
o The SET COMMUNICATION command has been modified to include
the /[NO]BROADCAST qualifier. This qualifier enables or
disables nonprivileged users to send broadcast messages from
the local host. You may want to change this parameter if
your users are running DECrpc applications.
/BROADCAST enable nonprivileged users to send broadcast
messages.
/NOBROADCAST specifies that privileges are required to send
broadcast messages.
The default is /NOBROADCAST.
o The SET ROUTE command has been modified as follows:
- You can now specify SET NOROUTE.
- The /DEFAULT qualifier has been added.
You use the /DEFAULT qualifier to define a default route.
To define the default route, you must also specify the
/GATEWAY gateway qualifier to define the gateway for the
default route.
The default route defines the route on which a packet is
sent if initial attempts to route the packet fail.
- The /PERMANENT qualifier has been added. This qualifier
specifies that the changes are to be applied only to the
UCX$ROUTE database.
The default depends on whether the Internet is running.
If the Internet is running, you must use the /PERMANENT
qualifier for the changes to be applied to the UCX$ROUTE
database. If the Internet is running and you do not use
this qualifier, the changes affect only the routing
information stored in memory.
If the Internet is not running, the changes are made to
the UCX$ROUTE database by default.
Page 6
o The SHOW COMMUNICATION command has been modified to include
the /ROUTE qualifier. This qualifier displays routing
statistics. The default is to give a brief listing of the
information.
o The SHOW EXPORT, SHOW HOST, SHOW NETWORK, SHOW PROXY, and
SHOW ROUTE commands have been modified to include the /OUTPUT
qualifier. This qualifier specifies that the output of the
command is output to the specified file. By default the
output is displayed on the screen.
o The SHOW HOST command has also been modified to include the
/DOMAIN, /[NO]LOCAL, and /SERVER qualifiers.
The /DOMAIN qualifier specifies the domain to be used by the
local host. However, the definition of the domain name is
only valid during the execution of the current SHOW HOST
command. The BIND request is sent to the specified domain.
The /[NO]LOCAL qualifier specifies whether the SHOW HOST
command displays information from the local or the BIND
database. If you do not specify this qualifier, information
from both databases is displayed.
The /SERVER qualifier specifies the name of the BIND server
that will provide host information to the local host.
However, the definition of the server name list is only valid
during the execution of the current SHOW HOST command. The
BIND request is sent to the specified server. (Note that you
cannot use wildcard characters to search a BIND database.)
The server name list is ordered by request preference.
o The SHOW ROUTE command has also been modified to include the
/PERMANENT qualifier. This qualifier specifies that only the
permanent UCX$ROUTE database information will be displayed.
o The ADD PROXY and SHOW PROXY commands have been modified to
include the /PERMANENT qualifier.
If you use the /PERMANENT qualifier with the ADD PROXY and
NFS is active, only the permanent database is updated. If
NFS is not active, the permanent proxy database is updated by
default. Note that the UCP can timeout while updating the
volatile database. If this occurs, it is possible that the
volatile database will not be updated.
If you use the /PERMANENT qualifier with the SHOW PROXY
database command, records found in the volatile database are
identified by an asterisk (*) in the rightmost position.
o To support the dynamic routing changes, the UCX$ROUTE
database is now located in SYS$COMMON:[SYSEXE] rather than
SYS$SPECIFIC:[SYSEXE].
Page 7
o The file format for UCX$ROUTE.DAT has changed. If you
installed a previous version of the Connection, you must run
UCX$CONFIG to convert your database to the new format.
4.5 Network File System (NFS)
o A new logical (UCX$CFS_SHOW_VERSION) has been added to the
UCX$NFS_STARTUP.COM. This logical enables you to specify
whether version numbers are displayed with the file names,
when there is only one version of the file. Normally, the
VMS NFS server removes the version number if there is only
one version of the file. To have the VMS NFS server always
display a version number, regardless of the number of files,
set the logical to 1. The default (0), specifies that the
NFS server will not display a version number if there is only
one version of the file.
o NFS now supports use of multiple buffers when interfacing
with the Connection file system and the Inet driver. This
feature eliminates data copying during file transfers and
therefore should improve performance. To enable this
feature, modify tthe following system logical name in the
UCX$NFSSTARTUP.COM as follows:
$DEFINE/SYSTEM UCX$NFS_MULTIBUFFER 1
o Support for Automount has been added. Automount enables you
to implicitly mount file systems without specifying the mount
command. This feature is transparent to the NFS server. It
is documented in the ULTRIX Version 4.0 documentation.
o Support for VMS network access control has been added.
You can restrict user's access to the NFS server through the
UAF file associated with the user's account. The Authorize
Utility enables you to restrict a user's network access with
the /NETWORK and /ACCESS qualifiers.
When you add a proxy record to the volatile proxy database,
the NFS server reads the network access information from the
SYSUAF file. The NFS server does not automatically receive
any changes made to the SYSUAF. Therefore, you must make
sure that the information in the NFS virtual database
reflects the information in the respective SYSUAF file.
If access is denied, the following message is written to the
error log file:
UCX$-W-NFS_ACCNOA, Access to the VMS account XXXX is denied
The NFS client receives an AUTH_BADCRED error in the reply
Page 8
message, which is translated into a permission denied message
during the mount operation.
Verification of the security setup for each NFS message
reduces performance of the Connection because it requires at
least 3 system calls and some additional calculations for
each NFS message. If the account has no restrictions on the
network mode of operations, no verification is done. If the
verification is disabled, no additional processing occurs.
You enable and disable this feature with bit 4 in the
security logical name UCX$NFS00000000_SECURITY table in the
UCX$NFS_STARTUP command file. To enable the feature, set bit
4 to 0. To disable the feature, set bit 4 to 1.
When you start NFS with the UCX$NFS_STARTUP.COM command
procedure, the security verification feature is enabled by
default.
o Proxy database synchronization.
When you start the NFS server, it reads the proxy database
file and creates a volatile database that is used to map the
ULTRIX-to-VMS identity for each NFS client.
Prior to Version 1.3, if you modified the proxy database with
UCX commands ADD PROXY and REMOVE PROXY, the volatile
database was not updated. Therefore, for NFS to recognize
the changes made to the proxy database, you had to restart
the NFS server.
In Version 1.3, updating the proxy database causes
corresponding changes in the volatile database. As such, you
do not have to restart NFS to recognize the changes.
Additionally, when you use the UCX command SHOW PROXY,
changes to the volatile database will be indicated.
Any record that appears in the volatile database will also
appear in the proxy database. However, there may still be a
situation when a record in the proxy database, is not in the
volatile database, for example, records for disabled
accounts. If a proxy has been setup to use a disabled VMS
account, this proxy record is not loaded into the volatile
database.
New messages have been provided to reflect the updates to the
volatile database. Each message will be followed by a
UCX$-I-NFS_CLIENT message and will contain the UID, GID, host
name, and user name for each record.
When adding new records to the volatile database, the
following messages may appear:
UCX$-I-NFS_READDS, Added account XXXX to volatile database
Page 9
UCX$-I-NFS_READDF, Failed to add account XXXX to volatile database
Reasons for not being able to add a new record to the
volatile data base and the appropriate user actions are as
follows:
- The dynamic memory allocation failed.
User Action: Change the NFS startup file page file
quotas or use SYSGEN to increase the virtual page count.
- The Connection failed to get the information for the
account from the UAF file. Either the account was not in
the UAF file or the account was disabled.
User Action: Modify the UAF file appropriately. If the
account is not in the UAF, add the account. If the
account is disabled, enable the account.
- The record already exists in the volatile database.
User Action: None.
- The host names limit has been reached.
User Action: Increase the value for the host names
parameter in the UCX$_NFS_STARTUP.COM and restart NFS.
- Incorrect record data was used. For example, the UID
exceeds the maximum.
User Action: Correct one of the parameters in the UCX
command.
When deleting a record from the volatile database, the
following messages may appear:
UCX$-I-NFS_ACCDES Deleted account XXXX from volatile database
UCX$-I-NFS_ACCDEF Failed to delete account XXXX from volatile database
The only reason this operation fails is if the record is not
in the volatile database.
The volatile database stores only the host name that was
specified in the proxy file (which is the actual name of the
host). If an NFS client uses a different name (an alias)
instead of the actual name of the host, NFS updates the
volatile database and logs the following message to the log
file:
UCX$-I-NFS_SUBNAM, Substitute hostname XXXX for hostname
This message is augmented by a UCX-S-CLIENT message that
Page 10
shows the alias name used by the host.
o The name of the error log file (UCX$NFS_ERRLOG.DAT) has been
changed. The new name is UCX$NFS_ERRLOG.LOG.
o Logging the setting of NFS parameters.
The following messages are logged to the error log file when
the corresponding NFS parameter is set by the UCX command SET
NFS:
_____________________________________________________________________________
| Message | SET NFS Command/Qualifier |
|_____________________________________________________________________________|
|UCX$-I-NFS_DISERR Disable writing into NFS | SET NFS/DISABLE |
| error log file | |
|_____________________________________________________________________________|
|UCX$-I-NFS_ENAERR Enable writing into NFS | SET NFS/ENABLE |
| error log file | |
|_____________________________________________________________________________|
|UCX$-I-NFS_SETGID Setting default GID to XXX | SET NFS/GID=XXX |
|_____________________________________________________________________________|
|UCX$-I-NFS_SETUID Setting default UID to XXX | SET NFS/UID=XXX |
|_____________________________________________________________________________|
|UCX$-I-NFS_SETITM Setting inactivity timer to | SET NFS/INACTIVITY=hh.mm |
| hh.mm | |
|_____________________________________________________________________________|
o A new option has been added to the ANALYZE CONTAINER command.
In previous versions, if you run ANALYZE CONTAINER with the
/REPAIR and /CONFIRM qualifiers, prompted for a confirmation
for every problem detected.
In Version 1.3, your answer to the prompt can be Y for yes, N
for no, or G for go. If you choose the new option G, ANALYZE
completes the rest of the repairs without prompting you for
confirmation.
4.6 Internet
o Support for dynamic routing has been added through the
Connection's implementation of the Routing Information
Protocol (RIP). For more information, see the section on
dynamic routing.
o Support for extending subnet routing has been added. For
more information, see the section on extended subnet routing.
o In previous versions there was a restriction of using the
Internet cluster alias only on a host that has the IP
forwarding disabled. This restriction has been removed.
Page 11
In Version 1.3, you can use the Internet Cluster Alias while
your host acts as a gateway.
o Prior to Version 1.3, an application program needed SYSPRV,
OPER, or BYPASS privileges to send Internet broadcast
packets.
In Version 1.3, the /[NO]BROADCAST qualifier has been added
to the UCX SET COMMUNICATION command. This qualifier allows
the system manager to enable or disable the checking of the
privileges required to send Internet broadcast packets.
The following command disables the checking of privileges
when sending Internet broadcast packets. Therefore, no
special privileges are required.
UCX> SET COMMUNICATION/BROADCAST
The following command enables the checking of privileges when
sending Internet broadcast packets. Therefore, SYSPRV, OPER,
or BYPASS privileges are required.
UCX> SET COMMUNICATION/NOBROADCAST
The default is /NOBROADCAST.
4.7 Telnet Client
The following features have been added to the Telnet client. For more
information, see the VMS/ULTRIX Connection User's Guide.
o The SET DEVICE/TERMINAL command has been added. This command
enables you to specify the terminal type to the remote host.
The syntax for the command is:
SET DEVICE/TERMINAL_TYPE=terminal_type
Where terminal_type can be any standard Digital terminal
type.
This command is useful for situations when the remote host
does not recognize your terminal type. As such, it enables
you to set your terminal type to VT100 (a standard terminal
type) that is widely accepted by Telnet servers.
4.8 Telnet Server
o To have login and logout messages displayed on the operator's
console, you must define the equivalence string as TRUE in
the logical name UCX$TELNET_LOG_MESSAGE or
UCX$RLOGIN_LOG_MESSAGE.
Page 12
You can insert the definition of the logical name in the
SYS$MANAGER:UCX$REMOTE_TTY_STARTUP.COM file. By default the
logical name is set to FALSE.
o Security audit has been added.
The security audit record that a TELNET or RLOGIN login
failure creates contains the remote host name (truncated to 6
characters) and the remote host Internet address (as a
decimal value in host representation). The record also
includes the following information (truncated to 16
characters), if it is available:
- Telnet -- the "TELNET_user" character string
- rlogin -- the remote user name
Note that to delete the NETWORK intrusion records created by
Telnet or rlogin, you have to specify the host name and the
user name in the appropriate case. For example, if the SHOW
INTRUSION command showed the following:
$ SHOW INTRUSION
Intrusion Type Count Expiration Source
NETWORK INTRUDER 6 12:27:26.06 boston::TELNET_user
You would have to enter the following command to delete the
record:
$ DELETE/INTRUSION "boston"::"TELNET_user"
o The Connection Telnet client allows you to switch between
character mode and line mode with the Telnet SET MODE
command. In some cases it may be useful to have the
switching done by the remote Telnet server. The Connection
porvides this capability through the use of the DCL SET
TERMINAL/[NO]ECHO command. Note that this feature is only
available when both the Telnet client and server are
Connection implementations.
Normally, the SET TERMINAL/[NO]ECHO command specifies whether
or not characters are echoed (displayed) to the display
screen. To allow Connection Telnet clients to use the SET
TERMINAL/[NO]ECHO command to toggle between character mode
and line mode, you must set the equivalence string of the
logical name UCX$TELNET_LINE_MODE to TRUE before starting the
Telnet server.
You can insert the definition of the logical name in the
SYS$MANAGER:UCX$REMOTE_TTY_STARTUP.COM file. By default the
logical name is set to FALSE.
If you set the equivalence string to TRUE, a SET
Page 13
TERMINAL/NOECHO command issued during a Connection Telnet
client session the Telnet session from character mode to line
mode. To return to character mode, enter the client issues a
SET TERMINAL/ECHO command.
Enabling this feature has no effect on the SET
TERMINAL/[NO]ECHO command for terminals connected directly to
the your system or those connected through a LAT. This
feature is restricted to terminals connected through the
Connection Telnet server.
4.9 File Transfer Protocol (FTP) Client
o The GET command has been modified to allow the use of
wildcards in the remote file name.
o The ENABLE PARSE and DISABLE PARSE commands have been added.
(The equivalent ULTRIX command is glob.)
These commands enable or disable filename expansion during
wildcard operations with the GET and PUT commands for
wildcard operations.
If parsing is enabled (the default), the file specifications
are expanded. If parsing is disabled, the file
specifications are taken literally and are not expanded. It
is useful to disable parsing in situations when the actual
file specification includes a VMS wildcard character (for
example an *).
For the PUT command the file specification expansion is done
on the local host (client). For the GET command each remote
file specification is expanded separately on the remote host.
Expansion of a directory specification (with a wild card) is
likely to be different from expansion of the name of an
ordinary file. The result depends on the remote host's
operating system and the remote FTP server.
To transfer the entire contents of a directory, you should
set default to the directory from which or to which the files
are to be copied and use a wildcard in the file specification
only.
o The /CONFIRM qualifier has been added to the GET and PUT
commands. This qualifier enables you to confirm GET and PUT
copy operations. If you use the /CONFIRM qualifier during
wildcard GET and PUT copies, FTP prompts you for a
confirmation before each individual file is copied. Valid
responses are as follows:
Page 14
- YES -- copy the displayed file
- NO -- do not copy the displayed file
- GO -- copy the displayed file and all other files that
fit the criteria
- QUIT -- do not copy the file and quit the copy process
o The QUOTE command has been added to the FTP client
docuemntation. The QUOTE command enables you to send
arguments verbatim to the remote FTP server. For more
information, see the VMS/ULTRIX Connection User's Guide.
4.10 FTP Server
o In Version 1.3, the FTP server implementation has been
changed to include the following FTP protocol commands:
- SITE -- Used to indicate the client's system type to the
FTP server. As a result, the server formats the display
of commands such as ls in the format of the specified
system. The SITE command accepts the following three
parameters: VMS, UNIX, and ULTRIX.
- STAT -- Causes a status response to be sent over the
control connection in the form of a reply.
- SYST -- Used to find out the type of operating system the
server is running on.
These commands are sent to the FTP server by the client users
through the QUOTE command; for example:
ftp>quote SYST
o In Version 1.3, the FTP server implementation has been
changed to execute LOGINOUT.EXE during child process
creation. The FTPC child process is created as a detached
network process.
User authorization is done by the LOGINOUT.EXE following the
VMS network access rules. Login is authorized only if
network access is authorized. Login is authorized during the
time intervals specified for network access in the UAF file.
Login failures are sent to the operator's console, and if the
security audit feature is enabled, security audit messages
are issued. The FTPC child process runs in an environment
which is built by LOGINOUT.EXE including logical names,
privileges, and quotas.
Page 15
A UCX$FTPSERVER.LOG file is created in user's default
directory to record the login and logout information and any
errors that occur.
Implementing this feature has the following restrictions:
- If your account has a secondary password, you cannot
establish a login session; LOGINOUT rejects it.
- After successive login failures from a remote FTP client,
an intrusion record is recorded for the remote node from
which the login request came. The record has the
following format:
Intrusion Type Count Expiration Source
NETWORK INTRUDER 6 15:10:28:08 NODE::FTP_user
Once the record is entered, any FTP login requests from
the originating node are rejected. You must delete this
record to enable further FTP logins from that node.
4.11 Interprocess Communications
The following new INET_ACP call codes were added to the IO$_ACPCONTROL
I/O function:
o INETACPC$_C_HOSTENT -- INET_ACP returns full host information
in a HOSTENT structure.
o INETACPC$_C_NETENT -- INET_ACP returns full network
information in a NETENT structure.
The INET_ACP call codes are defined by the macro or module
$INETACPSYMDEF.
The HOSTENT and NETENT structures are defined by the $HOSTENTDEF and
$NETENTDEF macros or modules.
5 PROBLEMS CORRECTED
This section provides information on problems that have been corrected
since the last release of the VMS/ULTRIX Connection. Information on
the following Connection components is included in this section:
o Network File System (NFS)
Page 16
o Internet
o File Transfer Protocol (FTP) Client
o FTP Server
o Interprocess Communications
5.1 Network File System (NFS)
o The mechanism to synchronize the UNIX times with VMS revision
times has been changed. UNIX ctime is not propagated back to
VMS.
o In earlier versions, there was a problem with the container
file extension that prevented it from extending beyond 8199
blocks.
This has been fixed.
o In earlier versions, there was a problem with locking the
loop on exec stack caused by failure of the blocking ast to
flush the file attributes.
This has been fixed.
o In earlier versions, there was a problem with creating a
directory in the VMS file system if the directory already
existed.
This has been fixed.
o In earlier versions, there was a problem with the way the VMS
file system handled the file backlink on RENAME operations.
This has been fixed.
o ANALYZE CONTAINER has been modified to handle the following
correctly:
- UNIX times
- Directory entries with inode sequence 0
- inode checking backout strategy
o The problem with send message through $SNDOPR while in kernel
mode has been corrected.
Page 17
o The file system two write attribute subfunction failure
problem has been corrected.
o In Version 1.2, the GID of a file created in ULTRIX CFS was
set to the GID of the client.
This has been changed to make the behavior consistent with
native ULTRIX NFS. As such, the GID of a file created in
ULTRIX CFS is set from the parent's directory GID.
o In Version 1.2, NFS had a problem processing host names that
contained blanks.
This has been fixed.
o In Version 1.2, NFS incorrectly calculated file sizes and
displayed the information incorrectly on an ls -s command.
This has been fixed.
o In Version 1.2 sometimes a problem would occur when sending a
message to an unreachable node that caused NFS to abort with
a host is unreachable message.
This problem has been fixed. If any error is returned by the
Internet driver, NFS logs an error message into the error log
file and continues to work. For each error, NFS tries to
translate the remote host address into a host name. If it is
possible, the following message is written to the error log:
UCX$_NFS_INETWR error writing to host XXXX on socket YYY
If NFS cannot translate the remote host name into an address,
then the following message is written to the error log:
UCX$_NFS_INETWH error writing on host XXXX (no name) on socket YYY.
In addition, a VMS error message is added to the error log
file as well.
5.2 Internet
o In previous versions, you could define multiple interfaces
with the same Internet address.
This has been corrected. Each Internet interface must have a
unique Internet address.
Page 18
5.3 FTP Client
o In previous versions, the FTP client did not work correctly
with resource identifiers if the disk quotas were enabled.
This has been fixed.
o In previous versions, the FTP client would display an error
message if you used the TT: symbol to type a file to the
screen.
This has been fixed; the error message is no longer
displayed.
o In previous versions, FTP would not place a user in their
default directory when they logged in to a VMS running
Version 1.2 of the VMS/ULTRIX Connection through FTP and
their default directory is made of a device name longer than
15 characters. This would happen because FTP would truncate
the device name to 15 characters.
This has been fixed.
o The FTP client is an installed image without any privileges;
therefore, the TCP buffer size cannot be changed. The
default TCP send and receive buffer size is 4K.
For window optimization, you should give the FTP client
process SYSPRV.
o In Version 1.2, the FTP client would hang in certain cases
after a data transfer completed.
This problem has been fixed.
o In Version 1.2, the FTP client would exit with an ACCVIO if
you did not specify any arguments with the ULTRIX command
'lcd'.
This problem has been fixed.
5.4 FTP Server
o In previous versions, an FTP session could hang when the FTPD
parent and FTPC child processes could not communicate.
This problem has been fixed.
Page 19
o In Version 1.2, when the FTP server retrieved data from a
remote host, it would first create a temporary file, then
enter the file name in the directory after the data transfer.
If the user did not have system privileges, the temporary
file would be created; however the entry would not be entered
in the directory. Since this failure was not checked by the
FTP server, it resulted in lost files that would take up the
disk quota. Also, if the the data transfer was aborted, the
FTP server did not delete the files.
This has been fixed.
5.5 Telnet Client
o The Telnet client is an installed image without any
privileges; therefore, the TCP buffer size cannot be changed.
The default TCP send and receive buffer size is 4K.
For window optimization, you should give the Telnet client
process SYSPRV.
o In Version 1.2, if you specified an Internet address instead
of a host name, and that host name was not defined in the
host database, Telnet would fail to establish a connection
with that host.
This has been fixed.
5.6 Telnet Server
o In previous versions, the system would crash sometimes if
many sessions were being established and closed
simultaneously. In these cases the system would crash with
an access violation on a 'remque' or 'insque' instruction.
This has been fixed.
o In previous versions, the system would crash when the
'rlogin' local user name has a zero length and the user
issued a login command, such as the following, from an
'ULTRIX' system:
% rlogin hostname -l ""
This has been fixed.
Page 20
o In previous versions, the system may crash when a TELNET or
RLOGIN terminal device changes terminal characteristics and
the TELNET or RLOGIN connection is no longer active.
This has been fixed.
5.7 Interprocess Communications (IPC)
o The description of the inet_network routine in Appendix C of
the VMS/ULTRIX Connection Programming Manual is wrong. The
description should read as follows:
The inet_routine returns an Internet address as a
machine format integer value when given as its argument
an ASCII string representing the address in the Internet
standard "." notation.
o The description of the optlen argument for the setsockopt
routine in Appendix C of the VMS/ULTRIX Connection
Programming Manual is wrong. The description should read as
follows:
optlen is an integer value specifying the size of the
buffer pointed to by optval.
6 RESTRICTIONS
This section explains the current restrictions for the following
Connection components:
o Installation
o NFS
o FTP server
o Dynamic routing server
6.1 Installation
If you are running a Field Test version or Pre-SSB version of the
VMS/ULTRIX Connection Version 1.3 in a cluster environment (on more
than one node in a cluster), you must shut down the Connection on all
the cluster members running the Connection before you install Version
1.3. If you install the Connection without shutting it down on all
Page 21
the nodes and you choose to purge the old Connection files, the
installation procedure may not be able to purge the old
UCX$ACCESSSHR.EXE file, because it is locked by other members of the
cluster still running the Connection. Therefore, you will get a
warning message from the installation procedure.
6.2 NFS
o chgrp command
The Connection's NFS server does not maintain a local
/etc/group file. Therefore, chgrp operations are
different for CFS VMS, CFS ULTRIX, and native ULTRIX
NFS.
When a chgrp command is performed on a file that is
mounted on a remote Connection NFS server, the command
may act in two possible ways, depending on what file
system is mounted.
If the file system is a CFS ULTRIX file system the
Connection's ULTRIX server stores the file's owner as
UID and GID in the container file. However, there is no
/etc/group file to be consulted. Therefore, the chgrp
operation is allowed only if the owner of the file
changes the file to their own GID. For example, if a
user with UID=10 and GID=15 owns a file with a UID=10
and a GID=17, the following chgrp will succeed:
chgrp 15 FILE
However, if the owner attempts to change the group to
any other GID, the operation will fail because the NFS
server does not support the /etc/group file and
therefore cannot identify that the user belongs to the
specified group.
If the file system is a CFS VMS file system, the VMS
file system does not save the file's UID and GID.
Therefore this operation is a "null" operation. No
errors are reported, and the GID is not changed. This
occurs because the GID that the client observes with the
"ls -g" command is a result of a back translation of the
VMS UIC into a UID GID pair through the proxy database.
o All users that can access the Connections's file systems must
be registered in the proxy database.
If a user that is not registered in the proxy database
issues a command, an error message appears. For
example, if a nonregistered user issued a 'df' command,
the following message appears:
Page 22
server xxxx: RPC: Authentication error
df: /xxxx: Not owner
o The ULTRIX last access time and change time are not
maintained by the VMS operating system. The revision date is
used instead for both the access time and the change time.
o Files on the VMS server may appear to be different size than
the same files on an ULTRIX system. This occurs because on
an ULTRIX system, the file size includes both the indirect
blocks and the data blocks. On a VMS system, the file size
includes only the data blocks.
6.3 FTP Server
o If the FTP server is shut down while a control connection
exists between the server and a remote FTP client, the
connection may stay open until the remote FTP client closes
the connection. If this situation occurs, you will not be
able to restart the FTP server until the remote FTP client
closes the connection.
Therefore, prior to shutting down the FTP server, you must
make sure that all client connections are closed.
You can avoid this situation by shutting down the Internet,
which automatically shuts down the FTP server.
6.4 Dynamic Routing Server
The Internet routing tables may not correspond to those used by the
dynamic routing server for short periods of time while processes
utilizing existing routes exit.