|
HP OpenVMS Systems Documentation |
|
Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server)Release Notes
December 2002
This document includes information about the PATHWORKS V6.1 for OpenVMS (Advanced Server) distribution kit, software features and usage guidelines, the latest problem fixes, fixes from preceding product versions, and restrictions. These Release Notes supplement the product documentation. Always read the Release Notes before you start the product installation. Revision/Update Information: This document supersedes the PATHWORKS V6.0D for OpenVMS (Advanced Server) Release Notes.
Operating Systems:
OpenVMS Alpha Version 6.2, 7.2-1, 7.2-2, 7.3
Software Version: PATHWORKS V6.1 for OpenVMS (Advanced Server)
© 2001 Hewlett-Packard Development Company, L.P. Compaq, the Compaq logo, Alpha, OpenVMS, Tru64, DECnet, VAX, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.
Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft
Corporation in the U.S. and/or other countries.
Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. The HP PATHWORKS for OpenVMS (Advanced Server) documentation set is available on CD-ROM.
PrefaceThe Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server) Release Notes include information about the distribution kit, software features and usage guidelines, the latest problem fixes, and restrictions. These Release Notes supplement the product documentation. Always read the documentation as well as the product Release Notes. Intended AudienceThese Release Notes are intended for the PATHWORKS for OpenVMS (Advanced Server) system administrator. It assumes you have:
Document StructureThis manual contains the following chapters:
Related DocumentsThe Release Notes supplement the following manuals:
The following table lists related OpenVMS documents.
For additional information about OpenVMS products and services, access the following World Wide Web address:
Reader's CommentsHP welcomes your comments on this manual. Please send comments to either of the following addresses:
How To Order Additional DocumentationFor information about how to order additional documentation, visit the following World Wide Web address:
Chapter 1
|
| Saveset Name | OpenVMS System |
|---|---|
| PWRK061.A | VAX and Alpha |
| PWRK061.B | VAX |
| PWRK061.C | Alpha |
| PWRK061.D | VAX |
| PWRK061.E | Alpha |
PATHWORKS for OpenVMS (Advanced Server) --- known also as the PATHWORKS Advanced Server, and often referred to as the Advanced Server --- is an OpenVMS layered application providing a network operating system that is compatible with the Microsoft networking technology. PATHWORKS for OpenVMS (Advanced Server) implements networking functions that are compatible with a Windows NT Server. PATHWORKS for OpenVMS (Advanced Server) offers easy access to OpenVMS file and printer resources from Windows desktops, using native Microsoft products and utilities such as Windows Explorer. PATHWORKS for OpenVMS (Advanced Server) combines the networking strengths and rich application set of Windows NT with the proven availability, reliability, scalability, and security of OpenVMS. It incorporates much of the code and functionality of Advanced Server for UNIX (Tru64 UNIX), as well as of Advanced Server for OpenVMS. The latest version of this software supports:
This chapter includes the following information:
The main new features provided by PATHWORKS V6.1 for OpenVMS (Advanced Server) include the following:
The Advanced Server provides the following Windows 2000 support:
For more information about Windows 2000 domain support, refer to the
Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
2.1.2 Member Server Support
The PATHWORKS Advanced Server now gives you the option of configuring the server as a member server instead of a primary domain controller (PDC) or backup domain controller (BDC). As a member server, the Advanced Server can participate in a Windows 2000 native-mode environment (a domain in which all domain controllers are Windows 2000 systems). Windows NT member servers can also participate along with Advanced Server member servers in Windows 2000 native-mode environments.
Member servers rely on domain controllers for authenticating credentials of users requesting access. Any domain controller can authenticate domain user requests to member server resources.
The PWRK$CONFIG.COM configuration procedure allows you to define the role of the Advanced Server as a member server. You cannot use the ADMINISTER SET COMPUTER/ROLE command to change an Advanced Server domain controller to a member server role (or vice versa) --- you must use PWRK$CONFIG. (This restriction is similar but less restrictive to that of Windows NT, which requires the software to be reinstalled to change a domain controller to a member server, or vice versa.)
For more information on member server support, refer to the
Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. For information on restrictions relating to the member
server role, see Section 7.8.5, Member Server Role Restrictions.
2.1.3 Support of Alias File Names
To enable compatibility with legacy applications (such as MS-DOS) whose file naming conventions are more restricted than those used by the Advanced Server, the PATHWORKS Advanced Server now creates MS-DOS-compatible alias file names for shared files whose names do not conform to the MS-DOS format. As a result, client applications that must use, or choose to use, the MS-DOS format for file names, can access these shared files on the server by using the file's associated alias file name. Clients can use either the real file name or the alias file name to access the file, depending on the client's file system.
The PATHWORKS Advanced Server returns a file's alias name, instead of the real file
name, to an MS-DOS client only if the real name is not MS-DOS
compatible. Otherwise, the Advanced Server returns the file's real name to
the MS-DOS client. For more information on support of alias file names,
refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
2.1.4 DNS Support for Resolving NetBIOS Names
Previous to this release, the PATHWORKS Advanced Server used WINS, broadcast name query, and LMHOSTS for name resolution, but not DNS. With this release, the PATHWORKS Advanced Server 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 Compaq PATHWORKS for OpenVMS (Advanced Server) 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.1.5 Server-Based License Management for Performance Gains
As documented in the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses, you can set the logical
PWRK$LR_DISABLE_CLIENT_PING systemwide in the PWRK$LICENSE_R_START.COM
to cause the License Registrar to assign a server-based license
immediately to a client attempting to connect to the file server
instead of first checking for client-based licenses. This can improve
performance.
2.2 Overview of Advanced Server Features
Some major features provided by the PATHWORKS Advanced Server are described in the
following sections.
2.2.1 Dynamic Cluster Load Balancing in Wide Area Networks
Previous to PATHWORKS V6.0C for OpenVMS (Advanced Server), 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.
Now, dynamic cluster load balancing is 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 Compaq 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).
You can set up dynamic cluster load balancing using TCP/IP Services for OpenVMS Version 4.2 (supported on OpenVMS Version 6.2 systems); however, Compaq recommends using TCP/IP Services for OpenVMS, Version 5.0A or later, which means you would need to upgrade any OpenVMS Version 6.2 systems. |
For information about enabling dynamic load balancing in WANs, refer to
the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
2.2.2 Support for OpenVMS V6.2 Alpha and VAX Systems to Facilitate Migration of PATHWORKS V5 for OpenVMS (LAN Manager) Server Users
To facilitate the migration of PATHWORKS V5 for OpenVMS (LAN Manager) server users to the PATHWORKS Advanced Server product, the PATHWORKS V6.1 for OpenVMS (Advanced Server) is supported on OpenVMS V6.2 Alpha and VAX systems. Functionality and features of the PATHWORKS Advanced Server can vary slightly according to the OpenVMS operating system it runs on, as noted in Table 2-1.
| Feature | OpenVMS V6.2 | OpenVMS V7.2 and Later |
|---|---|---|
| External Authentication | Not supported. See Section 3.13, Guidelines for External Authentication. | Supported. |
| External Authentication Images only installation | Not supported. | Supported. |
| Images | Uses *_V6.EXE; for example, PWRK$CSSHR_V6.EXE common services shareable image. | Uses *_V7.EXE; for example, PWRK$CSSHR_V7.EXE common services shareable image. |
| Date/Time | A delta-time restriction exists which, for example, affects file creation dates. An ECO is available to remove the restriction: refer to Section 3.18.1, Patch Required for Servers Running on OpenVMS V6.2. | No similar restriction |
| Time Zone Setup | Optional. | Required. See Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide. |
| XQP+ | Must be enabled explicitly by users. Refer to Section 3.19, Enabling XQP+ Support. | Enabled automatically on V7.2 or later. Must be enabled explicitly by users on V7.1. Refer to Section 3.19, Enabling XQP+ Support. |
| TCP Support | Compaq TCP/IP Services for OpenVMS V4.2. For other TCP/IP products, see the Compaq Advanced Server V7.3A-ECO1 for OpenVMS and PATHWORKS V6.1 for OpenVMS (Advanced Server) Software Product Description (SPD 30.50 xx). | Compaq TCP/IP Services for OpenVMS V5.0, 5.0A, and 5.1 or later. For details on versions supported per platform, as well as information on other TCP/IP products, see the Compaq Advanced Server V7.3A-ECO1 for OpenVMS and PATHWORKS V6.1 for OpenVMS (Advanced Server) Software Product Description (SPD 30.50 xx). |
| ODS-5 devices | Not supported. | Supported as ODS-2 devices on OpenVMS Alpha V7.2 and later. |
The PATHWORKS for OpenVMS (Advanced Server) software has been streamlined to improve the
performance for network logons and domain security accounts database
(also referred to as SAM database) replication. Formerly, 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.11, PWRK$LMDMN Process and Startup File Replaced.
2.2.4 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 PATHWORKS V6.0C for OpenVMS (Advanced Server), 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 PATHWORKS V6.0C for OpenVMS (Advanced Server) and higher versions compensate for the OpenVMS inconsistencies and now handles security information more efficiently and in conformance with the behavior of Windows NT.
The PATHWORKS V6.0C for OpenVMS (Advanced Server) and higher versions also provide 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 now supports the new STORE_SECURITY_ACES LANMAN.INI parameter value that you can use to limit the security information 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 enhancements to the file server's handling of
file security information, the PWRK$FIXACE utility, and the
STORE_SECURITY_ACES parameter, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
2.2.5 Enhanced Interoperation Between the PATHWORKS Advanced Server and 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:
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 V6.0C 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.
PATHWORKS V6.0C for OpenVMS (Advanced Server) and higher versions have made adjustments to interoperate better in environments that include Windows NT. The PATHWORKS Advanced Server now:
| Next | Contents |