PATHWORKS V6.0 for_OpenVMS_(Advanced_Server)_________________ Release Notes These Release Notes supplement the product documentation. Always read the Release Notes before you start the product installation. August 1997 Revision/Update Information: This is a new document. Operating System: OpenVMS Alpha, Version 7.1 Software Version: PATHWORKS V6 for OpenVMS (Advanced Server) Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Published, August 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1997. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC, DECnet-Plus, DECprint, DIGITAL, OpenVMS, PATHWORKS, PATHWORKS 32, and the DIGITAL logo. The following are third-party trademarks: AT&T is a registered trademark of American Telephone and Telegraph Corporation. Apple, LaserWriter, AppleShare, Macintosh, and TRUETYPE are registered trademarks of Apple Computer, Inc. Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company. IBM, OS/2, and NetView are registered trademarks of International Business Machines, Inc. Microsoft, MS-DOS, Windows, and Windows 95 are registered trademarks, and Windows NT is a trademark of Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. MultiNet is a registered trademark of TGV, Inc. PostScript is a registered trademarks of Adobe Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 Distribution Kit 2 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.1 Windows NT Domain Services................... 2-2 2.2 Installation and Configuration............... 2-2 2.2.1 Upgrade Utility.......................... 2-2 2.2.2 Initial Server Configuration Procedure... 2-3 2.3 Configuring Server Parameters................ 2-3 2.4 File and Print Services...................... 2-3 2.4.1 Client Support........................... 2-3 2.4.2 Transports Support....................... 2-4 2.4.2.1 PATHWORKS V6 for OpenVMS with DECnet... 2-4 2.4.2.2 PATHWORKS for OpenVMS TCP/IP Support... 2-4 2.4.3 WINS Server Support...................... 2-5 2.5 PostScript Printing Support.................. 2-5 2.6 Management Interfaces........................ 2-5 2.6.1 ADMINISTER Command Line Interface........ 2-5 2.6.2 Windows NT Server Administration Tools... 2-6 2.7 PATHWORKS Advanced Server Licensing.......... 2-6 2.7.1 License Enforcement...................... 2-7 2.7.2 Server-Based Licensing................... 2-7 2.7.3 Client-Based Licensing................... 2-8 2.7.4 Upgrading Client-Based Licenses.......... 2-9 2.8 External Authentication Support.............. 2-9 2.9 Differences Between PATHWORKS V5 and PATHWORKS V6................................. 2-10 iii 2.10 PATHWORKS V5 for OpenVMS (LAN Manager) Features That Are Not Supported.............. 2-11 3 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3.1 Server Configuration......................... 3-1 3.1.1 Configuring Physical Memory Usage for Running Both PATHWORKS Advanced Server and the NetWare Server................... 3-1 3.1.2 ADMIN/CONFIG Insufficient Resources to Support Any Clients...................... 3-1 3.1.3 Data Cache Utilization by the File Server................................... 3-2 3.2 External Authentication Support.............. 3-3 3.2.1 External Authentication Logon Information.............................. 3-3 3.2.2 Avoiding User Name Conflicts............. 3-4 3.2.3 Setting Up External Authentication By a Trusted Domain........................... 3-5 3.2.4 Special Name Mapping..................... 3-6 3.3 Netlogon Service for a Client................ 3-7 3.4 Administrating Shares from a Windows NT Server....................................... 3-7 3.4.1 Adding a Share From a Windows NT Server................................... 3-8 3.4.2 Enumerating Shares or Modifying Shares from a Windows NT Server................. 3-9 3.5 Removing PATHWORKS Advanced Server ACEs From a File....................................... 3-9 3.6 License Server Information................... 3-9 3.6.1 License Server Startup and Shutdown...... 3-10 3.6.1.1 Integrated License Server Startup...... 3-11 3.6.1.2 Integrated License Server Shutdown..... 3-12 3.6.1.3 Joint PATHWORKS Advanced Server and NetWare Startup........................ 3-12 3.6.1.4 Joint PATHWORKS Advanced Server and NetWare Shutdown....................... 3-12 3.6.1.5 Standalone License Server Startup and Shutdown............................... 3-13 3.6.2 License Server Configuration Parameters............................... 3-13 iv 3.6.3 Determining Configuration Parameter Values................................... 3-13 3.6.4 Dynamic Configuration Parameters......... 3-14 3.6.5 Controlling License Registrar Logging.... 3-14 3.6.6 License Registrar Messages............... 3-15 3.6.7 Setting the PWRK$LICENSE_SERVER_INHIBIT Parameter................................ 3-16 3.7 Defining Communications Devices.............. 3-17 3.8 Using TCP/IP Products with PATHWORKS Advanced Server....................................... 3-18 3.9 Time Zone Setup.............................. 3-19 4 Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4.1 Domain Management Problems................... 4-1 4.1.1 A Computer Cannot be Removed From the Domain If It Has Been Promoted to be a PDC in Another Domain.................... 4-1 4.2 User Interface Problems...................... 4-1 4.2.1 SET PASSWORD Command Does Not Always Set the Password Correctly................... 4-1 4.2.2 The /TYPE=NO* Qualifier Is Not Functioning with the ADMINISTER Command SHOW CONNECTIONS......................... 4-2 4.2.3 Unable to Change an Expired Password when using the ADMINISTER Command LOGON....... 4-2 4.2.4 SEND/USER Command Reports an Error....... 4-2 4.2.5 Misleading Error Message with ADMINISTER Commands for Managing User Account Host Mapping.................................. 4-3 4.2.6 REMOVE PRINT QUEUE Command Fails to Remove the Queue If the Print Queue is Not Stopped.............................. 4-3 4.2.7 SHOW FILE Command Fails to List Subdirectories........................... 4-4 4.2.8 Incorrect Count of Active Links Displayed After a Forced Disconnect................ 4-4 4.3 Interoperability Problems.................... 4-4 4.3.1 PATHWORKS Advanced Server Does Not Support the LOCKOUT Feature.............. 4-4 4.3.2 Nonstandard Domain Guest Group on Windows NT Servers Causes Replication to Fail.... 4-5 v 4.4 Host Mapping Problems........................ 4-5 4.4.1 A Host Map Setting from a Trusted Domain Cannot be Removed After the Trust Relationship Has Been Removed............ 4-5 4.5 File Service Problems........................ 4-6 4.5.1 PATHWORKS Advanced Server Fails to Handle Corrupted ACEs Properly.................. 4-6 4.5.2 Moving a Directory May Not Preserve Security Settings........................ 4-6 4.5.3 PATHWORKS Advanced Server Cannot Support More Than 32,767 Shares.................. 4-7 4.5.4 File Permissions Are Not Displayed on Initial Connect.......................... 4-7 4.5.5 File Server May Issue Incorrect BlobCache Warning Messages......................... 4-7 4.6 Event Logging Problems....................... 4-8 4.6.1 SHOW EVENT/FULL Command Fails to Recognize Messages with ID 6033.......... 4-8 4.6.2 Incorrect Audit Type When Password Change Failure Event Occurs..................... 4-8 4.6.3 Incorrect Syntax in SHOW EVENT Backup File Causes the Server to Fail........... 4-8 4.7 Licensing Problems........................... 4-9 4.7.1 License Manager Always Reports Use of PWLMXXXCA06.00 Licenses Allocated to the Server-Based Group as Zero............... 4-9 4.7.2 License Registrar Interval Parameters Do Not Immediately Use New Values When a Change to the Parameter Value is Noticed.................................. 4-9 4.8 Upgrade Problems............................. 4-10 4.8.1 Rollback Fails to Delete All PATHWORKS Advanced Server Data Files............... 4-10 4.8.2 Upgrade May Fail to Start Selected Transports............................... 4-10 vi 5 Restrictions of the PATHWORKS V6 for OpenVMS Product 5.1 Installation and Configuration Restrictions................................. 5-1 5.1.1 Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server................................... 5-1 5.1.2 OpenVMS V7.1 Requires a Patch............ 5-1 5.1.3 PATHWORKS Advanced Server May Fail at Startup Time if SYLOGIN.COM Executes with Errors................................... 5-1 5.1.4 PATHWORKS Advanced Server Fails to Start on Non-English Language Versions of OpenVMS.................................. 5-2 5.1.5 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure........................ 5-2 5.2 User Interface Restrictions.................. 5-2 5.2.1 Mouse Selection Highlights Entire Screen................................... 5-2 5.2.2 Windows NT Print Manager Fails to Display Advanced Server Printers................. 5-2 5.2.3 File Server Unable to Resolve Job Logical Translation as Part of a File Specification............................ 5-3 5.2.4 Autoshares are Not Enumerated............ 5-3 5.3 Event Logging Restrictions................... 5-3 5.3.1 Event Log Files Fail to Wrap When Full... 5-3 5.3.2 Unable to Set the Event Logging Setting.................................. 5-4 5.3.3 Displaying Application Event Log Files... 5-4 5.3.4 OpenVMS SET PASSWORD on an Externally Authenticated User Account is Not Audited.................................. 5-4 5.4 Transports Restrictions...................... 5-4 5.4.1 TCP/IP Services for OpenVMS Versions..... 5-4 5.5 File Server Restrictions..................... 5-5 5.5.1 Ownership of a Directory................. 5-5 5.5.2 DEFZA FDDI Controller Is Not Supported in PATHWORKS for OpenVMS.................... 5-5 5.5.3 Premature Disk Full Conditions........... 5-5 5.5.4 Server Does Not Enforce Disk Quotas by Default.................................. 5-6 5.5.5 DECram Performance Problem............... 5-6 vii 5.5.6 Access Denied to Files Restored From Backup of Another System................. 5-6 5.5.7 Intruder Flag's Relationship to PC Connections and Logons................... 5-6 5.5.8 XCCB Not in use Errors in LMMCP Log File..................................... 5-7 5.6 PATHWORKS for OpenVMS Interaction with Oracle Rdb.......................................... 5-7 Tables 2-1 PATHWORKS Advanced Server Features....... 2-1 3-1 Undefined Device Messages................ 3-17 viii ________________________________________________________________ Preface Purpose These release notes describe the features included in PATHWORKS V6.0 for OpenVMS (Advanced Server) software. This document serves as a complement to the PATHWORKS V6 for OpenVMS product documentation set. Audience These release notes are intended for PATHWORKS for OpenVMS system administrators. It assumes you have: o A basic understanding of a PC LAN network o A basic understanding of OpenVMS system management o Access to the PATHWORKS V6 for OpenVMS (Advanced Server) documentation v Related Documents The following manuals are referenced in these release notes. __________________________________________________________ Reference_______________________Topic_____________________ DIGITAL PATHWORKS for OpenVMS Explains how to install Server Installation and and configure all of the Configuration components of PATHWORKS for OpenVMS software including: o The Advanced Server o The NetWare server o The license server o The Upgrade utility DIGITAL PATHWORKS for OpenVMS Explains how to upgrade (Advanced Server) Server the PATHWORKS for OpenVMS Migration Guide (LAN Manager) software to PATHWORKS V6 for OpenVMS (Advanced Server) software. DIGITAL PATHWORKS for OpenVMS Explains how to manage and (Advanced Server) Server customize the PATHWORKS Administrator's Guide for OpenVMS (Advanced Server) software. DIGITAL PATHWORKS for OpenVMS Provides an overview (Advanced Server) Concepts and and introduction to the Planning Guide PATHWORKS for OpenVMS (Advanced Server) software and associated networking concepts for system administrators and operators. DIGITAL PATHWORKS for OpenVMS Describes the license Guide to Managing DIGITAL server software and how to PATHWORKS Licenses manage PATHWORKS licenses. vi __________________________________________________________ Reference_______________________Topic_____________________ DIGITAL PATHWORKS for OpenVMS Lists the PATHWORKS for (Advanced Server) Commands OpenVMS Advanced Server Reference Manual ADMINISTER commands, describing and showing examples for each. Lists the LAN Manager Net commands and the equivalent ADMINISTER ________________________________commands._________________ vii 1 ________________________________________________________________ Distribution Kit The PATHWORKS for OpenVMS software media includes support for Alpha systems and consists of the following BACKUP savesets: __________________________________________________________ Saveset_Name________OpenVMS_System________________________ PWRK060.A Alpha PWRK060.C Alpha PWRK060.E Alpha PWRK060.G Alpha PWRK060.H___________Alpha_________________________________ Distribution Kit 1-1 2 ________________________________________________________________ Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) The PATHWORKS for OpenVMS Advanced Server (known as the PATHWORKS Advanced Server) is the next generation of LAN Manager Server software. Some of the features provided by PATHWORKS Advanced Server are described in the following sections: Table_2-1_PATHWORKS_Advanced_Server_Features______________ Feature_________________________Section_Number____________ Full participation in domains Section 2.1 with Microsoft Windows NT Servers An installation procedure Section 2.2 that allows you to install the Upgrade utility only A new Configuration Manager Section 2.3 tool for configuring server parameters PATHWORKS Advanced Server file Section 2.4 and print services PATHWORKS Advanced Server Section 2.6 management interfaces License simplification and a Section 2.7 new License Manager tool for managing licenses External authentication Section 2.8 support_for_OpenVMS_users_________________________________ If you are upgrading from PATHWORKS V5 for OpenVMS, refer to Section 2.9 for information about the differences Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-1 between PATHWORKS V5 for OpenVMS (LAN Manager) and PATHWORKS Advanced Server. 2.1 Windows NT Domain Services PATHWORKS Advanced Server allows you to run the server as the primary domain controller or the backup domain controller in a Windows NT-compatible domain. PATHWORKS Advanced Server can participate in the domain as a Master Browser or Backup Browser. The Advanced Server supports the ability to be managed remotely from: o Windows NT Server o PATHWORKS Advanced Server o Clients running Windows NT Server Administration tools. For information about remote server management, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 2.2 Installation and Configuration PATHWORKS V6 for OpenVMS (Advanced Server) provides a single installation procedure that allows you to install any of the following: o Advanced Server software (includes the Upgrade utility and the license server) o NetWare server software (includes the license server) o Upgrade utility only o License server only 2.2.1 Upgrade Utility PATHWORKS Advanced Server provides a separately instal- lable Upgrade utility. You can run the Upgrade utility to upgrade the server's user, group, and share information while the PATHWORKS V5 for OpenVMS (LAN Manager) server continues to run. This allows you to plan and upgrade shares, user accounts, and security in preparation for the Advanced Server. 2-2 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) For more information about how to use the new Upgrade utility, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 2.2.2 Initial Server Configuration Procedure A one-time configuration procedure (PWRK$CONFIG.COM) allows you to perform basic on-disk structure setup and configuration modification, as well as allowing you to start up the PATHWORKS Advanced Server processes. For more information about installing and configuring the PATHWORKS Advanced Server software, refer to the DIGITAL PATHWORKS for OpenVMS Server Installation and Configuration Guide. 2.3 Configuring Server Parameters The PATHWORKS Advanced Server provides a new Configuration Manager tool. Use the Configuration Manager to modify server parameters and to enable and disable transport types. Use the following command to start the Configuration Manager: $ ADMINISTER/CONFIGURATION Refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for more information about using the Configuration Manager. 2.4 File and Print Services PATHWORKS Advanced Server supports the Windows NT- compatible SMB V3.0 file and print protocols. 2.4.1 Client Support PATHWORKS Advanced Server supports connections from the following types of clients: o Windows NT o Windows 95 o Windows for Workgroups o PATHWORKS for DOS and Windows Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-3 o PATHWORKS for Windows 95 o PATHWORKS 32 2.4.2 Transports Support Like PATHWORKS V5 for OpenVMS (LAN Manager), PATHWORKS V6 for OpenVMS (Advanced Server) supports the following types of transports and selects them in the following order: 1. TCP/IP 2. NetBEUI 3. DECnet-Plus This selection order differs from the order used by the PATHWORKS V5 for OpenVMS (LAN Manager) server. 2.4.2.1 PATHWORKS V6 for OpenVMS with DECnet PATHWORKS V6 for OpenVMS supports DECnet and DECnet-Plus as supported by the OpenVMS operating system Version 7.1. ________________________Note ________________________ The PATHWORKS mail server works only if DECnet is running on both of the following: o The PATHWORKS server o The client that wants to use the mail server _____________________________________________________ 2.4.2.2 PATHWORKS for OpenVMS TCP/IP Support PATHWORKS for OpenVMS provides transparent support for the following TCP/IP network transport products: o TCP/IP Services for OpenVMS, Version 4.1 o MultiNet Version 4.0, Rev. B o TCPware for OpenVMS, Version 5.1 For information about using TCP/IP products with PATHWORKS Advanced Server, refer to Section 3.8. 2-4 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.4.3 WINS Server Support The PATHWORKS Advanced Server can act as a client to WINS servers, allowing the PATHWORKS server to use the WINS server to resolve NETBIOS names in a Wide Area Network (WAN) configuration. 2.5 PostScript Printing Support The PATHWORKS for OpenVMS distribution media includes two kits for the DECprint Supervisor for OpenVMS (DCPS) family of layered products, which runs on OpenVMS VAX and Alpha to provide access through the OpenVMS queuing system to selected PostScript printers. To use DCPS, you must install the kit for either VAX or Alpha accordingly. You do not need a separate license to use DCPS with PATHWORKS. 2.6 Management Interfaces The following sections describe the management interfaces provided with the PATHWORKS Advanced Server. 2.6.1 ADMINISTER Command Line Interface PATHWORKS V6 for OpenVMS (Advanced Server) includes the PATHWORKS Advanced Server command line interface (ADMINISTER commands). These commands are designed to replace the LAN Manager server Net commands on OpenVMS. ADMINISTER commands can be used to remotely manage a Windows NT server or a PATHWORKS Advanced Server. For more information about how to use the new command line interface, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Commands Reference Manual, or enter the ADMINISTER command HELP to get online help for each command. For example, to get information about the ADMINISTER command ADD USER, enter the following command: $ ADMINISTER HELP ADD USER Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-5 2.6.2 Windows NT Server Administration Tools Like any other domain controller in a Windows NT domain, the PATHWORKS Advanced Server can be managed from a Windows NT Server, or from a client running Windows NT server administration tools. The PATHWORKS Advanced Server software kit includes the Windows NT server administration tools, which can be installed on the following types of computers: o Windows for Workgroups o Windows 95 o Windows NT Workstation These tools are made available in the \pwutil share after you install and configure the PATHWORKS Advanced Server: The srvtools directory contains a subdirectory for each type of client computer. 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. 2.7 PATHWORKS Advanced Server Licensing The PATHWORKS Advanced Server provides a simplified license management model, and a new License Manager tool for managing PATHWORKS Advanced Server licenses. Both the license server and License Registrar are installed with the PATHWORKS Advanced Server software. PATHWORKS Advanced Server requires all clients to be appropriately licensed, as described in Section 2.7.1, in order to access resources on the server. If you are using server-based licensing, when you use a Windows NT Server to manage PATHWORKS Advanced Server, a license is consumed. For additional information about PATHWORKS licensing, refer to the DIGITAL PATHWORKS for OpenVMS Guide to Managing PATHWORKS Licenses. 2-6 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.7.1 License Enforcement The PATHWORKS V6 for OpenVMS (Advanced Server) requires that clients accessing file and print services be appropriately licensed. To conform to this requirement, one of the following must be true: o The client must have acquired a client-based license before connecting to a PATHWORKS Advanced Server. o The PATHWORKS Advanced Server must have a server-based license available to assign to an unlicensed client attempting to use services of the PATHWORKS Advanced Server. In both cases, the license required to access PATHWORKS Advanced Server services is the PATHWORKS Client-Access license: PWLMXXXCA06.00. As a new feature of PATHWORKS V6 for OpenVMS (Advanced Server), this license can be used as either a client-based license or a server-based license. Clients currently using client-based licenses to access PATHWORKS LAN Manager servers must upgrade their licenses in order to access PATHWORKS Advanced Server resources. 2.7.2 Server-Based Licensing To configure your PATHWORKS V6 for OpenVMS (Advanced Server) system to use only server-based licenses: 1. Acquire a PWLMXXXCA06.00 license PAK. 2. Register and load the PWLMXXXCA06.00 license PAK on the system you plan to install the PATHWORKS Advanced Server software. 3. Install the PATHWORKS Advanced Server software. 4. When you run the initial configuration procedure (PWRK$CONFIG.COM), do not configure PATHWORKS to run the PATHWORKS license server. When the PATHWORKS license server is not configured on your system, the PATHWORKS Advanced Server assumes that any PWLMXXXCA06.00 licenses found on the system are to be used as server-based licenses for licensing client access. Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-7 2.7.3 Client-Based Licensing If you decide to configure the system to run the PATHWORKS V6 license server, the license server initially assumes that any PWLMXXXCA06.00 licenses found on the system are to be used as client-based licenses. You have the option of configuring the license server to share the available PWLMXXXCA06.00 licenses, using some as client- based licenses, and allocating the rest for use as server- based licenses, as follows: 1. Configure your system to run the license server when you run the initial configuration procedure (PWRK$CONFIG.COM). 2. Start the PATHWORKS Advanced Server to start the license server. 3. Invoke the new License Manager user interface using the following command: $ ADMINISTER/LICENSE 4. Go to the "Product allocation for group Server-Based" screen as follows: a. From the Products screen, choose View->Groups. b. Select the pre-defined license group "Server-Based." c. Choose Actions->Modify to go to the "Product allocation for group Server-Based" screen. 5. Allocate the number of PWLMXXXCA06.00 licenses you want to use as server-based licenses to the Server-Based group. This reserves the specified number of licenses for use by the PATHWORKS Advanced Server as server- based licenses. The number you have allocated to the Server-Based license group will not be available as client-based licenses. 2-8 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2.7.4 Upgrading Client-Based Licenses If client-based licensing is being used, you can configure the license server to automatically upgrade and assign PWLMXXXCA06.00 client-based licenses to clients requesting or verifying a license that is valid for accessing PATHWORKS V5 file and print services. To enable this feature, define the following system logical before you start the PATHWORKS server: $ DEFINE/SYSTEM PWRK$LS_V6_ACCESS_UPGRADE 1 ________________________Note ________________________ The PWLMXXXCA06.00 license is recognized by PATHWORKS V5.0F for OpenVMS (LAN Manager) servers and later versions of V5. Clients presenting this license to an earlier version of PATHWORKS for OpenVMS (LAN Manager) will be denied access. _____________________________________________________ For more information, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 2.8 External Authentication Support OpenVMS Version 7.1 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. PATHWORKS for OpenVMS software takes advantage of this feature by providing the ability to use the PATHWORKS Advanced Server or Windows NT-compatible user authentication mechanism to authenticate OpenVMS user logons. This allows users to log in at the OpenVMS login prompt using the PATHWORKS Advanced Server user name and password. In addition, it provides automatic password synchronization for user accounts. Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-9 2.9 Differences Between PATHWORKS V5 and PATHWORKS V6 The PATHWORKS V6 for OpenVMS (Advanced Server) is different from the PATHWORKS V5 for OpenVMS (LAN Manager) server. These differences include: o The LAN Manager ADMIN account privilege level is similar to the Advanced Server Administrator privilege level. The Administrator account is created automatically when you install and configure PATHWORKS Advanced Server. o The LAN Manager server provides a single operator privilege level. The PATHWORKS Advanced Server provides Operator user groups. To designate a user account to be an operator, add the user account to one of the following Operator groups: - Server Operator group (similar to LAN Manager Operator) - Print Operator group (similar to LAN Manager Operator) - Account Operator group (differs from the LAN Manager Operator in that members of this group cannot modify the Administrator user account, or the Administrator or Server Operator group). o PATHWORKS Advanced Servers support domain trust relationships. This allows users to access resources in another domain without having an account there. The trust relationships must be established by administrators in both domains. o PATHWORKS Advanced Server users are members of local groups and global groups. PATHWORKS LAN Manager users were divided into global groups only. Local groups are used in the Advanced Server to allow users from trusted domains to access resources in the local domain. o The PATHWORKS license management software and licensing subsystem have been improved in PATHWORKS V6 for OpenVMS. For more information, refer to Section 3.6. 2-10 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) Of course, there are many more differences between the LAN Manager server software and the Advanced Server software. Refer to the DIGITAL PATHWORKS V6 for OpenVMS (Advanced Server) Server Migration Guide for information about upgrading from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server). 2.10 PATHWORKS V5 for OpenVMS (LAN Manager) Features That Are Not Supported The following features of PATHWORKS V5 for OpenVMS (LAN Manager) are not supported with PATHWORKS V6 for OpenVMS (Advanced Server): o Share-Level Security PATHWORKS Advanced Server does not support share-level security. It manages access to all resources through user-level security. Therefore, share passwords are not required under Advanced Server. User accounts are granted access to resources based on their user account information and group membership. o Member and Standalone Server Domain Roles PATHWORKS Advanced Server does not support the following domain roles: - Member server - Standalone server A PATHWORKS Advanced Server must be either a primary domain controller or a backup domain controller in a Windows NT or Advanced Server domain. o FAT Volumes The FAT (File Access Table) file system is not supported by the PATHWORKS Advanced Server. To continue to provide FAT file access to clients, maintain the PATHWORKS V5 for OpenVMS (LAN Manager) server on a separate system. o Backward Compatibility Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 2-11 The PATHWORKS V6 for OpenVMS (Advanced Server) software does not support Backward Compatibility mode. This mode was used to ease the migration from PATHWORKS V4.x to PATHWORKS V5 for OpenVMS (LAN Manager). o Net Commands The Net commands are not supported by PATHWORKS V6 for OpenVMS (Advanced Server). They are replaced by the ADMINISTER commands. A Net command interpreter accepts and translates most Net commands to the equivalent ADMINISTER command. You can use the ADMINISTER command NET/TRANSLATE to see the ADMINISTER command that is supplied for each translated Net command. For more information about the translation of LAN Manager Net commands to PATHWORKS Advanced Server ADMINISTER commands, refer to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Commands Reference Manual. o Remote Boot Service The PATHWORKS V6 for OpenVMS (Advanced Server) does not support the Remote Boot service. If clients depend on remote booting, you must maintain the PATHWORKS V5 for OpenVMS (LAN Manager) server on a separate system. 2-12 Features of PATHWORKS V6.0 for OpenVMS (Advanced Server) 3 ________________________________________________________________ Guidelines for Using the PATHWORKS for OpenVMS Advanced Server This chapter describes guidelines for using the PATHWORKS Advanced Server that are not documented in the PATHWORKS for OpenVMS product documentation. 3.1 Server Configuration The following sections describe server configuration parameters you should modify to enhance performance in certain circumstances. 3.1.1 Configuring Physical Memory Usage for Running Both PATHWORKS Advanced Server and the NetWare Server When you configure PATHWORKS Advanced Server on systems running both PATHWORKS Advanced Server and the NetWare server, set the percent of physical memory used by PATHWORKS Advanced Server the default of 80 percent. DIGITAL recommends that you set the percent of physical memory used by PATHWORKS Advanced Server to 50 percent or lower. 3.1.2 ADMIN/CONFIG Insufficient Resources to Support Any Clients PATHWORKS Advanced Server requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for non-PATHWORKS use, and these resources have already been consumed when PATHWORKS Advanced Server is started, there may be insufficient resources left for PATHWORKS Advanced Server to support any clients. Before you run the Configuration Manager, make sure that all software that will run concurrently with PATHWORKS Advanced Server is installed and started, especially if you run TCP/IP or PATHWORKS for OpenVMS (NetWare). Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-1 After you successfully configure PATHWORKS Advanced Server, it may not start, reporting that there are insufficient resources to support any clients. In this case, examine the following file to determine the system resource that needs to be increased: PWRK$LOGS:PWRK$CONFIG_ERROR_node.LOG To increase the resource, make the appropriate modifica- tions to the MODPARAMS.DAT file and then run AUTOGEN. 3.1.3 Data Cache Utilization by the File Server PATHWORKS Advanced Server uses its data cache for caching the security databases, in addition to client file data. To ensure a balance of cache usage, the file server continuously monitors its use of the data cache, as follows: o Total security databases utilization The file server monitors the total utilization of the data cache by the security databases. If the file server detects that the utilization of the data cache for these files exceeds thirty-five percent (35%), a warning message is posted to the file server log file indicating that the current cache configuration may not be adequate for the current load imposed on the file server. For example: BlobCache Warning: Sum of Blob file control areas is 950272 bytes (45% of data cache). The condition reported by this warning message will not prevent the file server from being able to properly process requests associated with the security databases. The message indicates that you should increase the size of the data cache. o Individual security database utilization The file server monitors security database utilization of the data cache by individual security database files. When the database expands in size, more cache resources are required in order to continue operating. If the file server detects that an operation will 3-2 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server cause a database file expansion, and that expanding the database file will cause it to utilize more than fifty percent (50%) of the data cache, the following error messages are recorded in the file server log: BlobCache Error: The largest single Blob file control area is 1187840 bytes (57% of data cache). BlobCache Error: The largest single Blob file control area is PWRK$LMROOT:[LANMAN.DOMAINS]DOMAIN1. These messages indicate that the operation will prevent the file server from completing the current and future operations. In this case, you should increase the size of the data cache using the Configuration Manager (ADMIN/CONFIG) so that utilization of the data cache by a single database file remains under 50%. In addition to recording the problem in the file server log, the software generates an operator message and raises a server alert. You can use the ADMIN/ANALYZE command to monitor these warning messages and error messages. 3.2 External Authentication Support The following sections describe ways to set up external authentication. 3.2.1 External Authentication Logon Information OpenVMS accepts the user name in one of the following for- mats, for user accounts set for external authentication: o ASusername (PATHWORKS Advanced Server user name) o Domainname\ASusername o ASusername@Domainname The format of the user name string determines the order in which OpenVMS verifies the logon. o If ASusername is used, this name is first interpreted as an OpenVMS user name. If the user name exists and that user is not set for external authentication, the authentication is done as a standard OpenVMS login. Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-3 PATHWORKS Advanced Server authentication does not take place. o If the domain name is included in the user name, OpenVMS activates external authentication of the user, using the name of the domain supplied. - If the domain name is the same as that of the local server, the local server will proceed to authenticate this request. - If the domain name is different from the one the server belongs to, the software checks the value of the HOSTMAPDOMAINS keyword in the LANMAN.INI file to verify whether the specified domain is in the list of those that the server's domain trusts. If the domain is listed there, the authentication request is forwarded to the specified domain for authentication. 3.2.2 Avoiding User Name Conflicts If you have a name space conflict, where the same user name exists in PATHWORKS Advanced Server and OpenVMS, but they are not the same user, external authentication may not work as you expect. In the following examples, you have PATHWORKS running on OpenVMS node VMS1 in the domain SaleOffice, with PATHWORKS Advanced Server users Smith and J_Smith, and OpenVMS users Smith and V_Smith. 1. You enable external authentication for both of the OpenVMS users, and then specify the user host mapping as follow: $ADMINISTER ADD HOSTMAP SMITH V_SMITH $ADMINISTER ADD HOSTMAP J_SMITH SMITH When OpenVMS user Smith uses his PATHWORKS Advanced Server user name J_Smith and password to logon to VMS1, this logon will be successful, providing the password is correct. However, when OpenVMS user V_Smith uses her PATHWORKS Advanced Server user name Smith and password to logon to VMS1, this logon will fail because of the name space conflict between PATHWORKS Advanced Server and OpenVMS. 3-4 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server To logon, OpenVMS user V_Smith must specify her PATHWORKS Advanced Server user name specifying the domain (for example, either Smith@SaleOffice or SaleOffice\Smith). 2. You only enable external authentication for OpenVMS user V_Smith, specifying the following command: $ ADMINISTER ADD HOSTMAP SMITH V_SMITH When OpenVMS user V_Smith uses her PATHWORKS Advanced Server user name Smith to logon to VMS1, the logon will fail, because Smith will be first be interpreted as an OpenVMS user name. Because the OpenVMS user name exists, and it is not enabled for external authentication, the OpenVMS authentication mechanism is used to verify the password. To log on, the OpenVMS user V_Smith must specify the domain name with her PATHWORKS Advanced Server user name (for example, either Smith@SaleOffice or SaleOffice\Smith). 3.2.3 Setting Up External Authentication By a Trusted Domain You can set up an OpenVMS account to be externally authenticated by a trusted domain in your network. To enable this feature, you must include the trusted domain name as a value to the HOSTMAPDOMAINS keyword in the LANMAN.INI file. For example, if your OpenVMS system is in the SaleOffice domain, and this domain trusts the Marketing domain, set up OpenVMS user Jones to be externally authenticated by the Marketing domain as follows: 1. Edit the LANMAN.INI file to include the following in the VMSSERVER section: [vmserver] HOSTMAPDOMAINS = Marketing 2. Ensure that a PATHWORKS Advanced Server user account with user name Jones exists in the Marketing Domain. 3. Enable external authentication for OpenVMS user account Jones. Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-5 4. To log on, specify the user name in one of the following formats: Jones@Marketing Marketing\Jones 3.2.4 Special Name Mapping External authentication supports both explicit and implicit user host mapping between OpenVMS and PATHWORKS Advanced Server. You can explicitly specify host mapping a PATHWORKS Advanced Server user name to an OpenVMS user name using the ADMINISTER command ADD HOSTMAP. Implicit host mapping is established when: o An OpenVMS user name matches a PATHWORKS Advanced Server user name exactly. o The PATHWORKS Advanced Server user name is one of the following: - Administrator (implicitly mapped to the SYSTEM account) - Guest (implicitly mapped to PWRK$GUEST) - PWRK$DEFAULT (used when no match is found) Host mapping is used to determine the OpenVMS user name when logging onto OpenVMS using external authentication. For external authentication, the PATHWORKS Advanced Server user account Administrator is implicitly mapped to the OpenVMS user account SYSTEM. Therefore, if you enabled the OpenVMS user account SYSTEM for external authentication, you can log in to the SYSTEM account using the PATHWORKS Advanced Server Administrator user name and password, without explicitly defining the hostmap information. If you renamed the Administrator account, the implicit mapping is not preserved. You must explicitly map the newly renamed account name to OpenVMS SYSTEM account using the ADMINISTER command ADD HOSTMAP. The same is true with the PATHWORKS Advanced Server user account Guest. 3-6 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3.3 Netlogon Service for a Client The LANMAN.INI file on a PATHWORKS client contains the WRKNETS keyword in the WORKSTATION section. This keyword specifies the network transports that the client can use and the order in which they are used. On Enhanced Redirector clients, these network transports are represented by local area network adapter (LANA) numbers. The NET LOGON command works over LANA0 only, regardless of how many transports are loaded on the client. This may affect your ability to log on to a domain. For example, if a client runs both NetBEUI and DECnet, and WRKNETS associates NetBEUI with LANA0, NET LOGON fails if NetBEUI is not running on the server. If domain logon fails, you can still connect to servers, but you must provide a password for each session established. To avoid this problem, run all transports on the server. Alternatively, you can change the WRKNETS parameter to load a common server-client transport on LANA0. 3.4 Administrating Shares from a Windows NT Server The Windows NT server administration tool Server Manager attempts to verify the share path locally, before passing the server operation request to the OpenVMS server. Any share path that does not conform to the device:\directory convention, where device: is a single letter drive letter, fails the share path check. Therefore, you cannot manage this type of OpenVMS share from the Windows NT Server. ________________________Note ________________________ If you are using server-based licensing, a license is consumed when you administer PATHWORKS Advanced Server from a Windows NT Server. _____________________________________________________ The following sections describe ways to manage an OpenVMS share from the Windows NT Server. Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-7 3.4.1 Adding a Share From a Windows NT Server To add an OpenVMS share using a Windows NT Server, use one of the following procedures: 1. Define the OpenVMS device using the AUTOSHARE keyword in the VMSSERVER section of the LANMAN.INI file. This keyword allows you to map the OpenVMS device to a single letter DOS device. When a device is defined as an autoshare this way, you can add the share using the Windows NT Server by specifying the share path as device:\directory, where device is the mapped device letter. For example, to share the directory DUA1:[SHARE1] using the device letter d, include the following in the LANMAN.INI file: [VMSSERVER] AUTOSHARE= DUA1=D To add this share using the Windows NT Server Manager, specify the share path as follows: d:\share1 2. Convert the share path input string from the OpenVMS directory path by adding C:\ to the beginning of the path specification, and instead of specifing device:[share], enter a backslash (\). For example, if the OpenVMS directory that you want to share is DUA1:[SHARE1], specify the share path as follows: C:\dua1\share1 ________________________Note ________________________ If you intend to use the default C: device, which is defined as PWRK$LMROOT:[000000], add the share using the following path name: 3-8 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server C:\share1 PATHWORKS Advanced Server is designed to interpret C: correctly. In this case, the actual OpenVMS specification is PWRK$LMROOT:[SHARE1]. _____________________________________________________ 3.4.2 Enumerating Shares or Modifying Shares from a Windows NT Server To enumerate or modify the OpenVMS share from a Windows NT Server, use the following share path: c:\vmsdevicename\directorypath For example, if you added a share using the ADMINISTER command ADD SHARE, and you specified $1$DUA2:[SHARE.LEVEL2] as the share path for share LEVEL2, when enumerating this share from the Windows NT Server Manager, the share path is displayed in the following format: C:\$1$DUA2\SHARE\LEVEL2 3.5 Removing PATHWORKS Advanced Server ACEs From a File PATHWORKS Advanced Server supplies an unsupported utility, PWRK$DELETEACE.EXE, which is used to remove PATHWORKS ACEs (Access Control Entries) from any file on OpenVMS. Please note that removing PATHWORKS ACEs will alter the DOS attributes and security settings of a file. To remove the PATHWORKS ACE from a file, use the following command and respond to the prompts appropriately: $ MCR pwrk$deleteace 3.6 License Server Information The following sections provide license server management information that is not documented in the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses and the other PATHWORKS for OpenVMS documenta- tion. Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-9 3.6.1 License Server Startup and Shutdown PATHWORKS for OpenVMS supports running both the PATHWORKS Advanced Server and the NetWare server. The PATHWORKS license server can provide license verification for both PATHWORKS Advanced Server and NetWare clients. The PATHWORKS Advanced Server clients can connect to the file server using any of the following types of transports: o DECnet o TCP/IP o NetBEUI NetWare clients connect to the file server using the IPX transport. Because the license server supports all of these types of transports, the startup and shutdown procedures have been carefully designed to prevent unexpected interruptions in service. The license server is started up and shut down using the file server command procedures. The integrated PATHWORKS license server runs with the file servers. For information about integrated license server startup and shutdown, refer to Section 3.6.1.1. The standalone license server is installed on a system without the file servers. For information about the standalone license server, refer to Section 3.6.1.5. For more information about the installation and config- uration of file servers and the license server, refer to the DIGITAL PATHWORKS for OpenVMS Installation and Configuration Guide. For more information about the PATHWORKS license server and using the license manager, refer to the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses. 3-10 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3.6.1.1 Integrated License Server Startup The integrated license server runs with one or both of the file servers, if it was included in the configuration with the appropriate configuration procedure. The license server is started by the same command procedures that start the file servers. PWRK$STARTUP.COM Starts up the PATHWORKS Advanced Server file server and license server components PWVN$STARTUP.COM Starts up the NetWare file server and license server components The following table shows how the two startup command procedures differ: __________________________________________________________ If the Command following is Then the following is Procedure________configured_______started_________________ PWRK$STARTUP.COM DECnet DECnet transport NetBEUI NetBEUI transport TCP/IP TCP/IP transport license server IPX tunnel and IPX DECnet DECnet transport for PATHWORKS mail notification license server license server component and license registrar component PWVN$STARTUP.COM IPX IPX transport and IPX tunnel license server DECnet transport and DECnet license server NetBEUI transport and NetBEUI license server TCP/IP transport _________________and_TCP/IP_______________________________ Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-11 3.6.1.2 Integrated License Server Shutdown To shut down the license server, use the same command procedures that shut down the file servers. The shutdown command procedures are: PWRK$SHUTDOWN.COM Shuts down PATHWORKS Advanced Server and license server components PWVN$SHUTDOWN.COM Shuts down the NetWare file server and license server components Both procedures shut down the license server, license registrar and all the PATHWORKS transports, including IPX and the IPX tunnel. 3.6.1.3 Joint PATHWORKS Advanced Server and NetWare Startup When both PATHWORKS Advanced Server and the NetWare server are installed, and the integrated license server is configured, run both PWRK$STARTUP.COM and PWVN$STARTUP.COM. These command procedures cannot run at the same time. One must complete before the other can run. If the license server, license registrar, or any of the PATHWORKS transports are already running, those processes are not started. 3.6.1.4 Joint PATHWORKS Advanced Server and NetWare Shutdown If you use both PWRK$STARTUP.COM and PWVN$STARTUP.COM to start the servers, then use both procedures to shut down the file servers and license server. In this type of configuration, the following components are shut down only when you run both shutdown procedures: o License server o License registrar o All of the PATHWORKS transports When both shutdown procedures are executed, the second procedure to execute shuts down the license server, license registrar, and all PATHWORKS for OpenVMS transports, including IPX and the IPX tunnel. 3-12 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3.6.1.5 Standalone License Server Startup and Shutdown The standalone license server runs on a system without the file servers. However, the transports are configured for supporting license services to the appropriate clients. Therefore, the standalone license server startup and shutdown is similar to that described above for the integrated license server. Either PWRK$STARTUP.COM or PWVN$STARTUP.COM will start the license server and the transports it requires, but you should run both PWRK$STARTUP.COM and PWVN$STARTUP.COM if the license server serves both PATHWORKS Advanced Server and NetWare clients. Similarly, you should run both PWRK$SHUTDOWN.COM and PWVN$SHUTDOWN.COM when shutting down the license server if the license server serves both PATHWORKS Advanced Server and NetWare clients. 3.6.2 License Server Configuration Parameters When PATHWORKS Advanced Server is started, the license server and the License Registrar are started using the following command procedures: o SYS$STARTUP:PWRK$LICENSE_S_START.COM o SYS$STARTUP:PWRK$LICENSE_R_START.COM These command procedures contain complete descriptions of the configuration parameters used by each process when it runs. 3.6.3 Determining Configuration Parameter Values As part of their startup sequence and announcement, the license server and License Registrar place tables of their configuration parameters in their respective license processing-related log file: o PWRK$LOGS:PWRK$LICENSE_SERVER_servername.LOG o PWRK$LOGS:PWRK$LICENSE_REGISTRAR_nodename.LOG For each parameter in the table, the following information is recorded: o parameter name Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-13 o parameter type o whether the parameter is dynamic o the current value being used o whether that value is the default value for the parameter 3.6.4 Dynamic Configuration Parameters Dynamic configuration parameters allow the value of the parameter to be changed using a system logical, without having to restart PATHWORKS Advanced Server. The license component that uses the parameter obtains the changed value while the component is running. When the value of a dynamic configuration parameter is changed by redefining the control logical associated with the configuration parameter, the change may not take effect immediately. The license components periodically check the values of their dynamic configuration parameters to see if the value of any parameter has changed. When the license component detects a change to the value of a dynamic configuration parameter, a message is recorded in the component's log file when the new value is put into use. By default, the components check the parameter values every ten minutes. 3.6.5 Controlling License Registrar Logging The License Registrar provided with this software provides extra control of the messages recorded in its log file. Under PATHWORKS V5 for OpenVMS, the License Registrar provides two options: normal logging and verbose logging. This is controlled by the PWRK$LRLOGVERBOSE parameter. PATHWORKS V6 for OpenVMS provides four additional logging control parameters that control the logging of different types of activity, as follows: o PWRK$LR_LOG_SERVERBASED_ACTIVITY o PWRK$LR_LOG_CLIENTBASED_ACTIVITY o PWRK$LR_LOG_CLIENTBASED_SUCCESSES o PWRK$LR_LOG_CLIENTBASED_FAILURES 3-14 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server These parameters are described in the License Registrar startup command procedure, SYS$STARTUP:PWRK$LICENSE_R_ START.COM. All License Registrar logging control parameters are dynamic configuration parameters, so that you can change the License Registrar's logging behavior without restarting PATHWORKS. 3.6.6 License Registrar Messages The License Registrar provides diagnostic messages in the License Registrar log file when a license presented to the License Registrar by a client is not appropriate for accessing the PATHWORKS Advanced Server. For example, the following message results when the License Registrar is presented with a license that is not valid for accessing the file server: 10-JUL-1997 13:18:36.00 CLIENT_LICENSE_INVALID: Client Id = 08002B29D2CC, Client Addr = "PC1234 ", Transport = NetBEUI, Product = PWXXWINAT07.00, Group = default, Reason = License Invalid for File Server The License Registrar records a message similar to the following for any license which is insufficient for accessing the PATHWORKS Advanced Server: 10-JUL-1997 13:18:36.00 CLIENT_LICENSE_INVALID: Client Id = 08002B29D2CC, Client Addr = "PC1234 ", Transport = NetBEUI, Product = PWLMDOSCC06.00, Group = default, Reason = Insuficient License for File Server After recording this message, the License Registrar checks for the availability of a server-based license for the client. If no server-based licenses are available, a message similar to the following is logged: Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-15 10-JUL-1997 13:18:36.00 CLIENT_NOT_LICENSED: Client Id = 08002B29D2CC, Client Addr = "PC1234 ", Transport = NetBEUI, Reason = No Server-Based Licenses Available These messages are controlled by the License Registrar's logging-related configuration parameters. Read the License Registrar's startup commmand procedure, SYS$STARTUP:PWRK$LICENSE_ R_START.COM, for more information about these parameters. 3.6.7 Setting the PWRK$LICENSE_SERVER_INHIBIT Parameter The way the license server interprets the value associated with the PWRK$LICENSE_SERVER_INHIBIT configuration parameter is different from PATHWORKS V5 for OpenVMS. Under PATHWORKS V5 for OpenVMS, a value of zero for this parameter indicates that the license server will be prevented from running on the local node. With PATHWORKS V6 for OpenVMS, the configuration parameter value is interpreted as follows: o A value of one means TRUE, which prevents the license server from running. o A value of zero means FALSE, which allows the the license server to run. When you upgrade from PATHWORKS V5 for OpenVMS to PATHWORKS V6 for OpenVMS, if you use the PWRK$LICENSE_ SERVER_INHIBIT configuration parameter, change the value of the PWRK$LICENSE_SERVER_INHIBIT parameter, or use the PWRK$LS_LICENSE_NODES license server configuration parameter instead. For more information about configuring the license server, refer to the DIGITAL PATHWORKS for OpenVMS Guide to Managing DIGITAL PATHWORKS Licenses. 3-16 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3.7 Defining Communications Devices This section describes how to add new communications devices that are not automatically recognized by the PATHWORKS Advanced Server, as well as restrictions and limitations on communications devices. The PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes require the communications device to be defined in an internal device table. It is possible for new communications devices to be released before updated PATHWORKS images are available to customers. Therefore, this section describes how to define the communications device you want the PATHWORKS server to use. If the communications device is not recognized by PATHWORKS Advanced Server, each failing process writes an error message to its log file. The following table shows each process, the log file that records the error message from the process, and examples of the text of the error message. In the following examples, the server node name is MYNODE. Table_3-1_Undefined_Device_Messages_____________________________ Process__________Log_File_Name__________________________________ PWRK$KNBDAEMON PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG Message: Tue May 31 13:13:50 1997 get_phys_addr: Failed to get Ethernet device characteristics PWRK$NBDAEMON PWRK$LOGS:PWRK$NBDAEMON_MYNODE.LOG Message: Tue May 31 13:13:50 1997 Failed to open datalink NETBIOS PWRK$LOGS:NETBIOS_MYNODE.LOG (continued on next page) Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-17 Table_3-1_(Cont.)_Undefined_Device_Messages_____________________ Process__________Log_File_Name__________________________________ Message: %NB-W-ERRSIGNAL, exceptional conditional detected at 31-May- 1997 13:13:50.00 -SYSTEM-W-NOSUCHDEV,_no_such_device_available___________________ The device tables in the current release include all known communications devices. However, if you are running the latest release and you find any of the messages listed in Table 3-1, you can explicitly specify the communications device for all three processes, using the following procedure: 1. Define the physical communications device type for the PWRK$KNBDAEMON, NETBIOS, and PWRK$NBDAEMON processes. For example, if the physical communications device type is EWA0, enter: $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0: 2. Restart the server: $ @SYS$STARTUP:PWRK$STARTUP 3.8 Using TCP/IP Products with PATHWORKS Advanced Server PATHWORKS Advanced Server provides transparent support for the following TCP/IP network transport products: o DEC TCP/IP Services for OpenVMS, Version 4.1 o MultiNet Version 4.0, Rev. B o TCPWare for OpenVMS, Version 5.1 To use PATHWORKS with TCP/IP, do the following: 1. Install and, if necessary, configure the TCP/IP product. 3-18 Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 2. Start the TCP/IP transport and the PATHWORKS IP driver. The procedure depends on which TCP/IP product you use: o For MultiNet V4.0 enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$SPECIFIC:[MULTINET]START_MULTINET This starts the MultiNet TCP/IP transport and loads the PATHWORKS IP driver. o For DIGITAL TCP/IP Services for OpenVMS, enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:UCX$STARTUP $ @SYS$STARTUP:UCX$PWIP_STARTUP (For more information, refer to the documentation that comes with your TCP/IP product.) 3. Start the PATHWORKS Advanced Server. Enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:PWRK$STARTUP 3.9 Time Zone Setup PATHWORKS Advanced Server's internal time management uses Greenwich Mean Time (GMT). In order to properly represent the time in your local environment, the time zone information must be set up before the server is started. To set the time zone on your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$TIMEZONE_SETUP.COM To set up the time zone differential factor for your OpenVMS system, execute the following command procedure: @ SYS$MANAGER:UTC$CONFIGURE_TDF.COM If you change any time zone information, such as the daylight savings time setting, you must restart the server for the time to be properly represented. Guidelines for Using the PATHWORKS for OpenVMS Advanced Server 3-19 4 ________________________________________________________________ Known Problems in the PATHWORKS V6.0 for OpenVMS Product The following sections describe known problems in the current release of the PATHWORKS for OpenVMS product and their solutions. 4.1 Domain Management Problems The following section describes problems in managing domains and servers in domains. 4.1.1 A Computer Cannot be Removed From the Domain If It Has Been Promoted to be a PDC in Another Domain Problem: If you reconfigure a BDC from one domain to become a PDC of another domain, you will not be able to remove the computer name from the original domain. Solution: Delete the computer name in the original domain database during scheduled down time of the new PDC. This problem will be fixed in a future release. 4.2 User Interface Problems The following sections describe problems in the ADMINISTER command line interface. 4.2.1 SET PASSWORD Command Does Not Always Set the Password Correctly Problem: If you use the ADMINISTER command SET PASSWORD to set a password to lowercase, and the primary domain controller is a Windows NT Server, the command will complete successfully although the password is not set correctly. Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4-1 Solution: Change the password from a client workstation. This problem will be corrected in a future release. 4.2.2 The /TYPE=NO* Qualifier Is Not Functioning with the ADMINISTER Command SHOW CONNECTIONS Problem: The ADMINISTER command SHOW CONNECTION supports the use of NO as a prefix to value for the /TYPE qualifier. This prefix is not properly implemented. Solution: Specify the type of connection that you want to be displayed, instead of using the /TYPE=NOconnection_type qualifier to filter out connections that you do not want to display. This problem will be corrected in a future release. 4.2.3 Unable to Change an Expired Password when using the ADMINISTER Command LOGON Problem: You will encounter a failure if you use the ADMINISTER command LOGON to logon the network if your account password has expired, and you are being authenticated by a backup domain controller. Solution: Change your password from a client workstation, or retry the command. If the primary domain controller is the authentication server, the command will succeed. This problem will be corrected in a future release. 4.2.4 SEND/USER Command Reports an Error The SEND command generates an error message under the following conditions: o If you use the ADMINISTER command SEND from an OpenVMS cluster to send a message to all connected users, the SEND command will report an error delivering the message to your cluster member. The software fails 4-2 Known Problems in the PATHWORKS V6.0 for OpenVMS Product to recognize the cluster member node as a PATHWORKS Advanced Server, which does not support WinPopup services. o If you use the SEND/SERVER command to send a message to all connected users, the software reports an error delivering the message to the specified server. The software fails to recognize the remote server as a PATHWORKS Advanced Server, which does not support WinPopup services. The following error messages appear: %PWRK-E-ERRSENMSG, error sending message for computer "TINMAN_B5" -LM-E-NERR_NAMENOTFOU, the message alias could not be found on the network You can disregard these error messages. The message is successfully delivered to all workstations currently connected to the server. 4.2.5 Misleading Error Message with ADMINISTER Commands for Managing User Account Host Mapping If you provide a user name that does not exist as a parameter to the ADD HOSTMAP, SHOW HOSTMAP, or REMOVE HOSTMAP command, you will get the following error message: -LM-E-NERR_GROUPNOTFO, the group could not be found This message should say that the user could not be found. This will be fixed in the next release. 4.2.6 REMOVE PRINT QUEUE Command Fails to Remove the Queue If the Print Queue is Not Stopped Problem: If you use the ADMINISTER command REMOVE PRINT QUEUE to remove a queue that is not in Stopped state, the command will fail. Solution: Stop the queue using the OpenVMS command STOP QUEUE before you use the ADMINISTER command REMOVE PRINT QUEUE. Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4-3 4.2.7 SHOW FILE Command Fails to List Subdirectories Problem: When you use the ADMINISTER command SHOW FILE with the /SUBDIRECTORY qualifier, and there is a directory name that is the same as a file without any extension, the command will fail to list the subdirectory. Solution: To list all the files and subdirectories in a share, include a wildcard file specification (*.*) after the directory file specification. For example: $ ADMINISTER SHOW FILE \test\*.* /SUBDIRECTORY 4.2.8 Incorrect Count of Active Links Displayed After a Forced Disconnect Problem: If you force a disconnect on a share using the Windows NT server administration tools, the display will continue to show the old connection information even though the connection has been terminated. Solution: If you select the share, the updated data will be displayed. 4.3 Interoperability Problems The following sections describe problems with running PATHWORKS Advanced Server in a domain with Windows NT Server. 4.3.1 PATHWORKS Advanced Server Does Not Support the LOCKOUT Feature PATHWORKS Advanced Server does not support the account policy LOCKOUT setting. Therefore: o The LOCKOUT account setting is not preserved when PATHWORKS V5 for OpenVMS (LAN Manager) servers are upgraded to PATHWORKS Advanced Server. 4-4 Known Problems in the PATHWORKS V6.0 for OpenVMS Product o The PATHWORKS ADMINISTER command line interface fails to report this as an unsupported feature when you attempt to set the LOCKOUT parameter. o PATHWORKS Advanced Server will not enforce the LOCKOUT setting when participating in a PATHWORKS Advanced Server only or Windows NT Server domain. 4.3.2 Nonstandard Domain Guest Group on Windows NT Servers Causes Replication to Fail In rare situations, the Domain Guest group on a Windows NT Server may have been created in a non-standard manner. If the Windows NT Server is the primary domain controller in a domain, a PATHWORKS Advanced Server backup domain controller will not replicate the security databases from the primary domain controller. The error displayed in the PATHWORKS Advanced Server's event log is: T Date Time Source Category Event User Computer - -------- ----------- --------- --------------- ------ ---------- ------------- E 08/20/97 01:41:02 PM NETLOGON None 5730 N/A MATATA NET5730: Replication of the SAM Global Group "Domain Guests" from primary domain controller \\PCROOM_ALIAS failed with the following error: The user cannot be removed from a group because the group is currently the user's primary group. If this occurs, please contact your DIGITAL support representative for further instructions. 4.4 Host Mapping Problems The following section describes problems in setting up host mapping for PATHWORKS Advanced Server users. 4.4.1 A Host Map Setting from a Trusted Domain Cannot be Removed After the Trust Relationship Has Been Removed Problem: If you have established a host mapping for a local OpenVMS user to a PATHWORKS Advanced Server user name in a trusted domain, and the the trust relationship is removed before you remove the host mapping, the ADMINISTER command REMOVE HOSTMAP/HOST will fail because the mapped PATHWORKS Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4-5 Advanced Server user name is no longer represented in its alphabetical string. Solution: Remove all explicit host mapping to user accounts in the trusted domain before you remove the trust relationship, or use the ADMINISTER command REMOVE HOSTMAP/HOST to remove the host mappings. 4.5 File Service Problems The following sections describe problems with the file server. 4.5.1 PATHWORKS Advanced Server Fails to Handle Corrupted ACEs Properly When the file server fails unexpectedly, it is possible that some security information may be corrupted. When PATHWORKS Advanced Server encounters a corrupted security ACE (access control entry), it will remove the ACE and log a message in the common service event log. As a result, these files may not be protected. Solution: Review the common service event log using the the ADMIN /ANALYZE command to determine whether this situation has occurred. If it has, evaluate the file protection on the file to ensure the security setting is correct. 4.5.2 Moving a Directory May Not Preserve Security Settings Problem: When you move a subdirectory that does not have explicit permissions set on it from one location to another, the subdirectory's security settings are not preserved. For example, directory \open has explicit security set for Everyone to have full access while directory \restricted has explicit security set for only Administrators to have full access. The subdirectory \open\test in share \open, without explicit access permissions, inherits the Everyone:Full security setting. However, if it is moved to \restricted\test, it will not preserve this 4-6 Known Problems in the PATHWORKS V6.0 for OpenVMS Product setting. Instead, it will inherit the security setting of the \restricted share. Solution: After you move a directory, make sure the permission is explicitly set to the desired value. 4.5.3 PATHWORKS Advanced Server Cannot Support More Than 32,767 Shares The server will fail to add the 32768th share entry to the share database. This limitation will be lifted in a future release. 4.5.4 File Permissions Are Not Displayed on Initial Connect Problem: If you use a Window NT 4.0 client to connect to a PATHWORKS V6 server, and you select the property menu to display security information immediately after you connect, you will not see a Security tab in the Permissions dialog box. Solution: If you double-click on the window, this information will become available to you. This problem will be fixed in a future release. 4.5.5 File Server May Issue Incorrect BlobCache Warning Messages Problem: Sometimes the PATHWORKS file server will incorrectly report that the sum of the databases has exceeded the recommended maximum percentage of data cache size, indicating that the cache size should be increased, when, in fact, the cache size may not need to be increased. Solution: The warning messages indicate that the cache size should be increased; however, the warning messages may be ignored if the percentage reported in the warning message does not exceed 100% and does not increase once the file server is running (that is, after server startup). Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4-7 Note that the above only applies to "BlobCache Warning" messages. "BlobCache Error" messages should NOT be ignored. This problem will be fixed in a future release. 4.6 Event Logging Problems The following sections describe problems in the event logging functions of the server. 4.6.1 SHOW EVENT/FULL Command Fails to Recognize Messages with ID 6033 Problem: When you use the ADMINISTER command SHOW EVENTS, if the message number 6033 is in the event file, the software will fail to display the error message text associated with it. Solution: Use the Windows NT server administration tool Event Viewer to display the event log. 4.6.2 Incorrect Audit Type When Password Change Failure Event Occurs The server incorrectly indicates a password change failure event as a success in the event log file. This problem will be corrected in a future release. 4.6.3 Incorrect Syntax in SHOW EVENT Backup File Causes the Server to Fail Problem: If you use the ADMINISTER command SHOW EVENTS to view a saved event file, and you incorrectly specify the file specification in DOS syntax in the form of c$:\filename.evt, the file server will crash. The $ sign after the autoshared device name is not properly handled by the server. You can use c:\filename.evt or specify an autoshared device name that is mapped to an OpenVMS device. All valid file specification formats are handled. 4-8 Known Problems in the PATHWORKS V6.0 for OpenVMS Product Solution: Do not include the dollar sign ($) in the DOS device name. This will be corrected in a future release. 4.7 Licensing Problems The following sections describe problems in the licensing software provided with PATHWORKS V6 for OpenVMS. 4.7.1 License Manager Always Reports Use of PWLMXXXCA06.00 Licenses Allocated to the Server-Based Group as Zero Problem: The License Manager (ADMIN/LICENSE) reports zero usage for PWLMXXXCA06.00 licenses that are used as server- based licenses, even if some server-based PWLMXXXCA06.00 licenses have been assigned to clients. Solution: Use the PWLICENSE command to show the current usage and availability of PATHWORKS server-based licenses on the system. The PWLICENSE command is defined in the SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM command procedure. The License Manager will correctly reflect the usage of PWLMXXXCA06.00 license from the Server-Based group in a future release. 4.7.2 License Registrar Interval Parameters Do Not Immediately Use New Values When a Change to the Parameter Value is Noticed Problem: When you change the value of the License Registrar's PWRK$LR_LICENSE_REPORT_INTERVAL or PWRK$LRLMFSYNCHINTERVAL parameters, the License Registrar will not use the new value of this parameter until the time interval for checking the parameter values has passed. For example, if license reporting is initially set to generate a report every six hours, and you change that parameter value to ten minutes while the License Registrar continues to run, the License Registrar will begin to use the new interval only after the current six-hour interval Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4-9 has passed. When the current interval has passed, the License Registrar begins to use the new interval value. This problem will be corrected in a future release. 4.8 Upgrade Problems The following sections describe problems in upgrading a server from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server). 4.8.1 Rollback Fails to Delete All PATHWORKS Advanced Server Data Files Problem: If you have selected installation of the PATHWORKS Upgrade utility only, install PATHWORKS Advanced Server on your system later, and then execute the Rollback procedure to revert the system back to PATHWORKS LAN Manager, the Rollback utility will fail to delete the ACL. and Sharedb. data files from the PWRK$LMROOT:[LANMAN.DATAFILES] directory. This does not introduce any problem to the running PATHWORKS LAN Manager environment. However if you choose to reinstall PATHWORKS Advanced Server, you may have problems with printing security. Solution: Delete these files before installing PATHWORKS Advanced Server again. 4.8.2 Upgrade May Fail to Start Selected Transports Problem: The following sequence of steps will cause the Upgrade utility to fail to start the selected transports: 1. Install PATHWORKS Advanced Server. 2. Run the Upgrade utility to upgrade your server as a backup domain controller without completing the initial configuration of the server (PWRK$CONFIG). Solution: 4-10 Known Problems in the PATHWORKS V6.0 for OpenVMS Product Define the following OpenVMS logical before you run the Upgrade utility: $ DEFINE/SYSTEM/EXECUTIVE/NOLOG PWRK$VERSION V6.0 Known Problems in the PATHWORKS V6.0 for OpenVMS Product 4-11 5 ________________________________________________________________ Restrictions of the PATHWORKS V6 for OpenVMS Product This chapter describes restrictions in the PATHWORKS Advanced Server software. 5.1 Installation and Configuration Restrictions The following sections describe restrictions in the installation and configuration of the PATHWORKS V6 for OpenVMS (Advanced Server) software. 5.1.1 Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server The PATHWORKS Advanced Server cannot share a domain with a server running PATHWORKS V5.0C for OpenVMS (LAN Manager). The V5.0C server incorrectly generates a name conflict when the Advanced Server claims a group name that is used by both servers. To correct this problem, upgrade the PATHWORKS V5.0C server to PATHWORKS V5.0C ECO1, or a later version of PATHWORKS V5 for OpenVMS (LAN Manager). 5.1.2 OpenVMS V7.1 Requires a Patch If the system is running OpenVMS Version 7.1, the DEC C RTL patch ALPACRT02 or higher must be installed. 5.1.3 PATHWORKS Advanced Server May Fail at Startup Time if SYLOGIN.COM Executes with Errors PATHWORKS Advanced Server process startup depends on successful execution of OpenVMS logins and logouts. If your sites make use of SYLOGIN.COM to achieve cluster- member specific logon setup, when SYLOGIN.COM encounters errors PATHWORKS Advanced Server startup hangs. Restrictions of the PATHWORKS V6 for OpenVMS Product 5-1 When this problem occurs, process startup either fails to generate log file messages, or fails to complete. 5.1.4 PATHWORKS Advanced Server Fails to Start on Non-English Language Versions of OpenVMS The PATHWORKS Advanced Server fails to start on any non- English version of the OpenVMS operating system, because PATHWORKS Advanced Server relies on the English language output of the OpenVMS command SHOW MEMORY. 5.1.5 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure Problem: If the PATHWORKS on-disk structure contains directories more than eight levels deep, the PWRK$CONFIG procedure cannot move the on-disk structure to another disk because of an OpenVMS RMS restriction. Solution: Before running the PWRK$CONFIG procedure to move the PATHWORKS on-disk structure, either delete files and directories that are greater than eight levels deep, or rename them so that the standard OpenVMS BACKUP command is able to move them correctly. 5.2 User Interface Restrictions The following sections describe restrictions in the management interfaces. 5.2.1 Mouse Selection Highlights Entire Screen Under certain circumstances the entire screen is highlighted when you select a button using the mouse input device. When this occurs, press Ctrl/W to clear the screen, then select the button again. 5.2.2 Windows NT Print Manager Fails to Display Advanced Server Printers When you attempt to display the printers on the Advanced Server from the Windows NT server administration Print Manager, using the Server Viewer, you will not see the printers offered by the Advanced Server. 5-2 Restrictions of the PATHWORKS V6 for OpenVMS Product Display the list of printers using the PATHWORKS Advanced Server command ADMINISTER command SHOW PRINTERS. 5.2.3 File Server Unable to Resolve Job Logical Translation as Part of a File Specification If you use a job logical as part of a file specification for any ADMINISTER commands, the operation will fail. The file server does not support using a job logical as part of a file specification. Using a job logical as part of a file specification to an ADMINISTER command results in an error, where the error message may not be explicit about the cause of the problem. For example, the following command will fail with an "insufficient privileges" error message. The source of the problem, however, is not the privilege level of the user; rather, it is the use of the SYS$LOGIN job logical. $ ADMIN SAVE EVENT SYS$LOGIN:EVT_BACKUP.EVT Therefore, you cannot use job logicals in file specifica- tions in the ADMINISTER command line. 5.2.4 Autoshares are Not Enumerated PATHWORKS V5 for OpenVMS (LAN Manager) supports the enumeration of "autoshared" devices as part of the share enumeration displayed by the NET SHARE command. PATHWORKS V6 for OpenVMS (Advanced Server) does not enumerate any autoshared device; however, a user with Administrator privileges can connect to these devices. 5.3 Event Logging Restrictions The following sections describe restrictions in the event logging and auditing functions of the PATHWORKS Advanced Server. 5.3.1 Event Log Files Fail to Wrap When Full The server does not support overwriting event messages when the Event log files become full. However, the server generates an Alert message indicating the log file is full. You must manually clear the event log files using the ADMINISTER command CLEAR. Restrictions of the PATHWORKS V6 for OpenVMS Product 5-3 5.3.2 Unable to Set the Event Logging Setting When you use Windows NT Administration tools to alter the event logging setting, if you choose the option "do not overwrite," the server incorrectly reflects the setting as "overwrite events older than 365 days." 5.3.3 Displaying Application Event Log Files The ADMINISTER command SHOW EVENTS does not display the Application event log file in detailed format. When you supply the /FULL qualifier to display the detailed event information, only the summary information is displayed. 5.3.4 OpenVMS SET PASSWORD on an Externally Authenticated User Account is Not Audited The password change event that results from executing the OpenVMS SET PASSWORD command from an OpenVMS account that is enabled for external authentication is not audited in the PATHWORKS Advanced Server Security event log file. However, the password change activity is audit in the OpenVMS audit file. If this capability is crucial to your environment, advise users to use the ADMINISTER command SET PASSWORD to change the password. 5.4 Transports Restrictions The following sections describe restrictions in the use of specific transports (network protocols) with PATHWORKS Advanced Server. 5.4.1 TCP/IP Services for OpenVMS Versions TCP/IP Services for OpenVMS Versions prior to V4.1, ECO6, exhibit a nonpage pool leak when running with PATHWORKS Advanced Server. To ensure that this problem does not exist on your system, update your system to run TCP/IP Services for OpenVMS Version 4.1, ECO6, or later. 5-4 Restrictions of the PATHWORKS V6 for OpenVMS Product 5.5 File Server Restrictions The following sections describe restrictions in the file server. 5.5.1 Ownership of a Directory Directory ownership is inherited from its parent directory instead of the creator of that directory, unless the creator has explicit host mapping set up on the system. PATHWORKS Advanced Server is different from Windows NT Server in this way. On a Windows NT Server, the ownership of a directory and a file are set to the user who created them. 5.5.2 DEFZA FDDI Controller Is Not Supported in PATHWORKS for OpenVMS The DEFZA FDDI controller is not supported with PATHWORKS for OpenVMS. DIGITAL recommends that you use the newer DEFTA, which is supported and provides better performance. 5.5.3 Premature Disk Full Conditions The file server may receive a disk full message when thousands of free blocks remain on the device, because the file server's open file cache holds newly-created or extended files open for about five seconds after the client closes them. Because files are allocated in extent-size chunks, that space is unavailable for other operations until the files are actually closed. To avoid these messages, make sure that at least 1 MB of free space is available on the device or the container file at all times. If this does not work, add the following to the PWRK$COMMON:PWRK.INI file to lower the default file extent quantity. Create this file if necessary. Note, however, that this will significantly affect the performance of file up-loading. [ODS2] create_quantity = 1 extend_quantity = 1 Restrictions of the PATHWORKS V6 for OpenVMS Product 5-5 5.5.4 Server Does Not Enforce Disk Quotas by Default By default, the file server uses the EXQUOTA privilege, which means that quotas on OpenVMS system disk volumes are not enforced. To disable the EXQUOTA privilege and use disk quotas, include the following line in the [LMSRV] section of the file PWRK$COMMON:PWRK.INI. Create the section, if necessary: [LMSRV] START_WITH_EXQUOTA=NO 5.5.5 DECram Performance Problem The DECram performance is inadequate when the disk is mounted using the /NOCACHE qualifier. Do not use the /NOCACHE qualifier when mounting a RAM disk that PATHWORKS accesses. If you omit the /NOCACHE qualifier from the MOUNT command, the XQP+ cache is enabled for the RAM disk, allowing the PATHWORKS internal caches to operate effectively. 5.5.6 Access Denied to Files Restored From Backup of Another System When a directory is backed up from one system and restored on another, stale group ACEs may still be attached to the files that are restored. These ACEs cause the file server to deny access to users even though they have access to the parent directory. To correct the problem, delete the ACLs on the files after they are restored, using the following DCL command: $ SET ACL/DELETE filename 5.5.7 Intruder Flag's Relationship to PC Connections and Logons When a PC user does not provide a correct password with a logon request, the file server logs an OpenVMS intrusion record, which indicates a possible break-in attempt. The file server also sets the intruder flag. This flag may be safely ignored; it does not affect any PC connections or logons. To delete the intrusion record, use the DELETE/INTRUSION_RECORD command. 5-6 Restrictions of the PATHWORKS V6 for OpenVMS Product 5.5.8 XCCB Not in use Errors in LMMCP Log File When an attempt is made to exceed the maximum number of sessions that the server is configured for, the operation fails (as expected) and the following error message appears in the PWRK$LMMCP_nodename.LOG file: ...specified XCCB not in use! You can ignore this error message. 5.6 PATHWORKS for OpenVMS Interaction with Oracle Rdb PATHWORKS fails to start correctly on systems that are also configured to run Oracle Rdb (Relational Database) software, because of the way that Rdb uses the system- wide login command procedure SYLOGIN.COM and the way that PATHWORKS Advanced Server creates processes. To correct this problem, in the system login procedure SYLOGIN.COM, replace the following line: $ @DECRDB$SETVER.COM with the following lines: $ SET NOON $ @DECRDB$SETVER.COM $ SET ON Restrictions of the PATHWORKS V6 for OpenVMS Product 5-7