This document contains the release notes for Version 1.1 of DIGITAL OpenVMS Disk Services for Windows NT:

• What's New in This Release?

• Known Problems

1 What's New in This Release?

Version 1.1 of DIGITAL OpenVMS Disk Services for Windows NT:

• Runs on OpenVMS Alpha Version 6.2 as well as on OpenVMS Alpha Version 7.1

• Increases the number of concurrent connections that are supported.

  You can now have up to 50 concurrent connections to the disk services on a single OpenVMS Cluster. For example:

  • One Windows NT system can connect to 50 disk services on the OpenVMS Cluster, or

  • 25 Windows NT systems can each connect to two disk services on the OpenVMS Cluster.

  Although you can set up more than 50 concurrent connections, DIGITAL only supports configurations that have 50 or fewer concurrent connections to the disk services on each OpenVMS Cluster.

2 Known Problems

• Case Sensitivity of Cluster Names

• Limit on the Container File Size with Spiralog Volumes

• I/Os on User Workstations Time Out During Service Failover

For information on fixes for these problems, and on other problems that were discovered after these Release Notes were written, visit our web site at:

http://www.openvms.digital.com/openvms/products/ntds/

2.1 Case Sensitivity of Cluster Names

Although the cluster name that you define using the NTDS START SERVER command is currently case sensitive, you should not set up two OpenVMS Clusters that have the same cluster name but use different combinations of upper and lower case. For example, don't set up two clusters with the names Media and MEDIA.

In a future version of DIGITAL OpenVMS Disk Services for Windows NT, cluster names may not be case sensitive.

2.2 Limit on the Container File Size with Spiralog Volumes

You must not create a container file larger than 4 GB on a Spiralog volume. This is because of a problem with the Spiralog file system that causes it to corrupt data in any file that is larger than 4 GB. This applies to all current versions of Spiralog.

DIGITAL OpenVMS Disk Services for Windows NT issues no warning messages about the size of a container file, because it has no knowledge of the underlying file system.

Note

If you are not using Spiralog volumes there is no limit on the size of container file for DIGITAL OpenVMS Disk Services for Windows NT.

2.3 I/Os on User Workstations Time Out During Service Failover

If you lose cluster quorum when the OpenVMS Alpha node providing a disk service fails, you may find that I/O requests issued by users connected to shares on the virtual disk may time out before the disk service fails over to a standby node in your OpenVMS Cluster.

If you encounter this problem, reconfigure your OpenVMS Cluster so that it does not lose quorum when the node providing the disk service fails.

Alternatively, if you are unable to reconfigure your OpenVMS Cluster, you can increase the parameter that controls the SMB timeout period on the user workstation. For example, if you find that I/Os are timing out on a Windows NT workstation, increase the value of the SessTimeout parameter in the NT registry:

SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\SessTimeout

This value specifies the timeout in seconds. By default, it is 45.

To estimate the required value, use the Windows NT Event Viewer to find out the average length of time between the connection being lost and the connection being regained during OpenVMS Cluster failover.

Legal