HP OpenVMS Systems

HP Advanced Server V7.3B for OpenVMS
Release Notes

Previous to V7.3 of the Advanced Server for OpenVMS, WAN clients used WINS or LMHOSTS to resolve the cluster alias name, based on a static source of address information. From request to request, the cluster alias name was resolved to the same server node in the cluster, regardless of the load.

With V7.3 and subsequent releases of the Advanced Server, dynamic cluster load balancing is now available for service requests from WAN clients that are outside the server cluster's LAN. This dynamic cluster load balancing mechanism for WAN environments is provided by HP TCP/IP Services for OpenVMS V5.0A (or later), and uses a Domain Name System (DNS) server to resolve the cluster alias name, instead of WINS or LMHOSTS. This DNS name server must support dynamic updates (Berkeley Internet Name Domain (BIND) server, Version 8.1.1 or later).

For information about enabling dynamic load balancing in WANs, see Section 3.17, Setting Up Dynamic Cluster Load Balancing in WANs.

2.6.9 DNS Support for Resolving NetBIOS Names

Previous to V7.3 of the Advanced Server for OpenVMS, the Advanced Server used WINS, broadcast name query, and LMHOSTS for name resolution, but not DNS. With V7.3 and subsequent releases, the Advanced Server for OpenVMS can use DNS for name resolution as well. To enable DNS name resolution, use Configuration Manager and select the Transport Configuration Parameters screen, as documented in the HP Advanced Server for OpenVMS Server Administrator's Guide.

If you select the DNS option, the Advanced Server will use the currently configured DNS server as a last resort (that is, if all other methods fail to resolve a NetBIOS name). WINS should still be the primary resource for resolving names.

2.6.10 Support for Use of the POLYCENTER Software Installation Utility

As of V7.3 of the Advanced Server for OpenVMS, you use the POLYCENTER Software Installation (PCSI) utility to install the Advanced Server for OpenVMS.

The PCSI utility allows you to install several software products (including the Advanced Server for OpenVMS) with a single command. It also allows you to remove products from the OpenVMS system.

Furthermore, with the implementation of PCSI, the Advanced Server installation procedure has been enhanced in several ways:

• If a reboot is necessary, PCSI gives you the option of delaying it indefinitely, such as when you need to configure or change more settings before rebooting.
• Installations on multiple system disks have better support.
• Scripts and messages have been improved and include better support for installations on clusters.

Advanced Server for OpenVMS allows you to run the server as the primary domain controller (PDC), a backup domain controller (BDC), or a member server in a Windows NT-compatible domain.

Advanced Server for OpenVMS can participate in the domain as a Master Browser or Backup Browser.

The Advanced Server for OpenVMS supports the ability to be managed remotely from:

• Windows NT Server
• Advanced Server for OpenVMS
• PATHWORKS for OpenVMS (Advanced Server)
• Clients running Windows NT and Windows 2000 server administration tools.

For information about remote server management, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide.

2.6.12 File and Print Services

Advanced Server for OpenVMS supports the Windows NT-compatible Server Message Block (SMB) file and print protocols.

2.6.13 Client Support

Advanced Server for OpenVMS supports connections from the following types of clients:

• Windows NT
• Windows 2000, Windows 2003, and Windows XP Professional
• PATHWORKS 32

OpenVMS supports Extended File Specifications, providing the following capabilities to OpenVMS Alpha systems, and helping ensure Advanced Server compatibility with a wide variety of clients and legacy applications attempting to share server resources. The benefit to the Advanced Server client computers depends on the type of client, as noted below.

• Deep directories, similar to Microsoft Windows NT. Previous versions of OpenVMS support a maximum of eight directory levels.
  Deep directories allow network clients to use hierarchical storage of directories and files on the OpenVMS disk similar to the client-based disk. They are also of benefit to applications developers who are porting applications from other environments that have support for deep directories.
• Extended file names (using ODS-5). Support of extended file names is an optional feature originally provided with the OpenVMS V7.2 operating system that extends OpenVMS file name capabilities to more closely match those of contemporary Windows computers. With this functionality, OpenVMS Alpha systems support long file names (up to 243 characters including the version number), and add ISO Latin-1 characters to the supported character set.

For more information, refer to the OpenVMS documentation set.

2.6.15 Transport Support

Advanced Server for OpenVMS supports the three transports listed below, in the order listed:

1. TCP/IP
2. NetBEUI
3. DECnet-Plus (or DECnet Phase IV)

Advanced Server for OpenVMS provides transparent support for the following TCP/IP network transport products:

• HP TCP/IP Services for OpenVMS. The latest supported version is recommended. For the latest supported version, refer to the Advanced Server for OpenVMS Software Product Description (SPD 30.50xx.
• MultiNet for OpenVMS, from Process Software LLC
• TCPware for OpenVMS, from Process Software LLC

For information about using TCP/IP products with Advanced Server for OpenVMS, see Section 3.12, Using TCP/IP Products with the Advanced Server.

2.6.15.1.1 WINS Support for Resolving NetBIOS Names in a WAN

The Advanced Server can act as a Windows Internet Name Service (WINS) client, allowing the Advanced Server to use WINS services to resolve NetBIOS names in a Wide Area Network (WAN) configuration. For information about setting up WINS services for the Advanced Server, refer to the HP Advanced Server for OpenVMS Server Installation and Configuration Guide and the HP Advanced Server for OpenVMS Server Administrator's Guide.

2.6.15.1.2 DNS Support for Resolving NetBIOS Names in a WAN

The Advanced Server can use DNS services to resolve NetBIOS names in a Wide Area Network (WAN) configuration. For information about setting up DNS services for the Advanced Server, refer to the HP Advanced Server for OpenVMS Server Installation and Configuration Guide and the HP Advanced Server for OpenVMS Server Administrator's Guide.

2.6.15.2 NetBEUI Support

The Advanced Server for OpenVMS provides the NetBEUI transport. NetBEUI is recommended only for use in small LAN-only environments (approximately 50 nodes or less).

2.6.15.3 DECnet Support

Advanced Server for OpenVMS supports DECnet and DECnet-Plus as supported by the OpenVMS operating system Version 7.2-2 and higher.

The Advanced Server for OpenVMS supports all PostScript printers supported by OpenVMS. Selected PostScript printers may optionally need the DECprint Supervisor for OpenVMS (DCPS) software to provide access through the OpenVMS queuing system over DECnet or TCP/IP. For information about installing the DCPS software, refer to the appropriate documentation.

2.6.17 Management Interfaces

The following sections describe the management interfaces provided with the Advanced Server for OpenVMS.

2.6.17.1 ADMINISTER Command-Line Interface

Advanced Server for OpenVMS includes the Advanced Server for OpenVMS command-line interface (ADMINISTER commands).

ADMINISTER commands can be used to remotely manage Windows NT Server, PATHWORKS for OpenVMS (Advanced Server), and Advanced Server for OpenVMS servers. For more information about how to use the command-line interface, refer to the HP Advanced Server for OpenVMS Commands Reference Manual, or invoke the ADMINISTER online Help.

For example, to get information useful for new users, enter the following command:

$ ADMINISTER HELP NEW_USER

The following command displays an overview about using the ADMINISTER user interface:

$ ADMINISTER HELP NEW_USER

NEW_USER

     Welcome to the ADMINISTER command-line user interface. The
     ADMINISTER command-line interface is a comprehensive utility for
     managing domains and servers in a network of compatible servers.

     You can invoke the interface in one of two ways:

     o  Enter the command ADMINISTER, then press Return. This invokes
        the interface in subsystem mode. This is shown by the prompt
        DOMAIN\\SERVER>, where DOMAIN and SERVER are the default
        names of the domain and server you will be administering.
        Initially, DOMAIN is the name of the domain to which your
        local computer belongs, and SERVER is the name of your local
        computer. Once in subsystem mode, you can execute commands by
        entering subcommands, keywords, parameters, and qualifiers. To
        return to DCL, type EXIT or press Ctrl/Z.

     o  Enter commands one at a time from DCL level. You enter the
        ADMINISTER command followed on the same line by keywords,
        parameters, and qualifiers, then press Return. After the
        command is completed, control returns to DCL.


  Additional information available:

  Case_Sensitivity      UNC

As any other domain controller in a Windows NT domain, the Advanced Server for OpenVMS can be managed from a Windows NT Server or from a client running Windows NT server administration tools.

The Advanced Server for OpenVMS software kit includes the Windows NT server administration tools, which can be installed on computers running any of the following operating systems:

• Windows for Workgroups
• Windows 95 and Windows 98
• Windows NT Workstation

The Windows NT server administration tools are available in the PWUTIL share after you install, configure, and start the Advanced Server for OpenVMS.

The SRVTOOLS directory contains a subdirectory for each type of client computer (Windows 95 tools are usable with Windows 98 clients). Refer to the README.TXT file in the subdirectory for instructions on installing the software on the client computer.

Refer to the Windows NT Server documentation or use online Help for more information about how to use Windows NT server administration tools. See also Section 3.16, Installing Optional Server Administration Tools.

2.6.17.3 Windows 2000 File and Print Server Tools

The Advanced Server can be managed from a Windows 2000 Server using tools related to file and print servers. These tools are available as part of the Windows 2000 Server.

2.6.18 Advanced Server for OpenVMS Licensing

The Advanced Server for OpenVMS follows the PATHWORKS V6 for OpenVMS simplified license management model. Both the License Server and License Registrar are provided with the Advanced Server for OpenVMS software, and a License Manager utility is also provided for managing Advanced Server licenses.

The License Server included with the Advanced Server for OpenVMS will not issue or manage PATHWORKS for OpenVMS (NetWare) licenses. If you have clients using NetWare networking software, maintain the existing version of the License Server on a different system from the one that is running Advanced Server for OpenVMS.

Advanced Server for OpenVMS requires all clients to be appropriately licensed to access resources on the server. The minimum license required to access Advanced Server for OpenVMS services is the Client Access license PWLMXXXCA07.03, or an equivalent client virtual license. See Section 3.19.1, License Enforcement, for more information about setting up licensing.

For additional information about licensing, refer to the HP Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.

2.6.19 External Authentication Support

The OpenVMS operating system includes support for external authentication. This feature allows the OpenVMS system manager to set up a user account for which login authentication is based on a security mechanism other than OpenVMS security.

Advanced Server for OpenVMS software participates with the operating system to provide the ability to use the Advanced Server user authentication mechanism to authenticate OpenVMS user logons. This allows users to log in at the OpenVMS login prompt using the Advanced Server for OpenVMS user name and password. In addition, it provides automatic password synchronization for user accounts.

For more information about implementing external authentication, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide. For information on installing the external authentication images, refer to the HP Advanced Server for OpenVMS Server Installation and Configuration Guide.

2.6.20 Performance and Interoperability Enhancements

This section describes several enhancements to server performance and its interoperability with Windows NT.

2.6.20.1 Domain Database Replication and Network Logon Performance Improvement

The Advanced Server for OpenVMS software has been streamlined to improve the performance for network logons and domain security accounts database (also referred to as SAM database) replication. Previous to V7.3 of the Advanced Server for OpenVMS, these operations were performed by the PWRK$LMDMN process. The server now uses the PWRK$LMSRV process to perform them. The PWRK$LMSRV process is responsible for communicating with the data cache that contains the SAM database. Moving the responsiblity for network logon validation and SAM database replication from the PWRK$LMDMN process to the PWRK$LMSRV process streamlines the operations by eliminating the interprocess communication that was required between the PWRK$LMDMN process and the PWRK$LMSRV process. The PWRK$LMDMN process no longer exists, as noted in Section 3.21, PWRK$LMDMN Process and Startup File Replaced.

2.6.20.2 Improved Performance for Access of Sequential and VFC Files

Previous to V7.3 of the Advanced Server for OpenVMS, when a file on an ODS-2 or ODS-5 volume was opened for the first time, the server had to read the entire file to determine the correct file size. On ODS-5 volumes, the Advanced Server now uses file-size calculations maintained by RMS for RMS sequential and VFC (variable length with fixed-length control) files. This reduces the number of I/Os and the file-open time when the Advanced Server opens a file for the first time.

This benefits especially those sites where OpenVMS RMS application files (sequential or VFC) are provided for Advanced Server users at regular intervals, such as overnight to make the files accessible to PCs the next day. HP recommends that such sites store the RMS files on ODS-5 volumes and disable high-water marking to optimize I/O throughput. (High-water marking is a security feature set by default when a volume is initialized to guarantee that users cannot read data they have not written.)

2.6.20.3 Improved Handling of File and Directory Permissions

The file server is designed to handle access permissions in conformance with the behavior of Windows NT. Previous to V7.3 of the Advanced Server for OpenVMS, certain OpenVMS behaviors caused discrepancies. For example, when files were created in a shared directory, they inherited inappropriate or wrong access permissions from the parent directory. The Advanced Server for OpenVMS now compensates for the OpenVMS inconsistencies and handles security information more efficiently and in conformance with the behavior of Windows NT.

The Advanced Server for OpenVMS also provides a new utility, PWRK$FIXACE, that can help resolve security problems that arise because of inappropriate permissions on files. The utility removes inappropriate security information and compresses the valid security information to optimize disk storage.

In addition, the Advanced Server for OpenVMS introduces a new OpenVMS Registry parameter value, STORE_SECURITY_ACES, to limit the security information that is propagated to files created in directories. This can help optimize the usage of disk space (at the expense of runtime performance). For more information on the file server's handling of file security information, the PWRK$FIXACE utility, and the STORE_SECURITY_ACES parameter, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide. For information about the relevant ACE problems fixed in Advanced Server V7.3 for OpenVMS, see Section 4.2.1, Files Inherit Wrong or Inappropriate ACEs, and Section 4.2.2, Cannot Create File on Disk Because of Insufficient Space for Index Header Blocks.

2.6.20.4 Enhanced Interoperation with Windows NT

In some instances, Microsoft Windows NT does not strictly conform to Request for Comments (RFCs) 1001 and 1002. Most notably, the lack of conformance occurs when clients fail to resolve names by either WINS or broadcast, and use DNS for resolving NetBIOS names as a last resort. When Windows NT resolves a NetBIOS name by using DNS, the subsequent sequence of actions differs from the actions taken following the normal methods of name resolution (by either WINS or broadcast).

When Windows NT has resolved a NetBIOS name to an IP address by using a DNS server, it does the following:

1. Windows NT attempts to PING the resolved IP address to determine whether the node is up.
2. If the PING is successful, Windows NT sends a node status request for the NetBIOS name "*....<15>". This is a wildcard name; however, it is an invalid NetBIOS name according to RFCs 1001 and 1002.
   If Windows NT does not get a node status response, it assumes the server is down and stops attempting to establish a session. This will happen with an Advanced Server for OpenVMS prior to V7.3, because such a server rejects the node status request as an invalid NetBIOS name.
3. If Windows NT receives a valid node status response, the response includes a list of NetBIOS names owned by the node. Windows NT assumes that the first name ending in "0x20" (the server service) in the list is always the file server name. Windows NT uses this name in its attempt to establish a session with the server.
   However, with the Advanced Server for OpenVMS prior to V7.3, the first name returned in a node status response that ends in "0x20" is either "PWRK$Lxxxxxx" (License Server) or "xxxxxxCMTSERVER" (CMT server), but never the file server name.

Another way in which Windows NT does not strictly adhere to RFCs 1001 and 1002 is in how it responds to a node status request. When an Advanced Server user enters the following command, where nt-host is the NetBIOS name of a Windows NT host, the Advanced Server sends a node status request to the specified Windows NT host:

$ NBSHOW KNBSTATUS nt-host

The Windows NT host replies to this command with a node status response. However, an Advanced Server prior to V7.3 discards the returned node status response because the packet size of the response does not conform to RFC 1001/1002 expectations --- the response includes 18 extra, undefined bytes.

Advanced Server for OpenVMS now interoperates better in environments that include Windows NT. The Advanced Server now:

• Responds to Windows NT node status requests for name "*....<15>" as Windows NT expects, even though the name specified in the query is an invalid NetBIOS name according to RFC 1001 and 1002.
• Always returns the file server name as the first name in the NetBIOS name list that is returned as part of the node status response.
• No longer discards a node status response from Windows NT, even if it has 18 extra bytes of undefined information. The Advanced Server will accept the node status response, ignoring the 18 extra bytes.

Table 2-1 summarizes the differences between the Advanced Server V7.3B and PATHWORKS V6.1 for OpenVMS (Advanced Server) products.