PATHWORKS_V6.0B_for_OpenVMS_(Advanced_Server)_ Release Notes January 1999 The PATHWORKS V6.0B for OpenVMS (Advanced Server) Release Notes include information about the 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 replaces the PATHWORKS V6.0A for OpenVMS (Advanced Server) Release Notes. Operating Systems: OpenVMS Alpha Version 7.2 OpenVMS VAX Version 7.2 OpenVMS Alpha Version 7.1 OpenVMS VAX Version 7.1 Software Version: PATHWORKS V6.0B for OpenVMS (Advanced Server) Compaq Computer Corporation Houston, Texas __________________________________________________________ First Published, 1997 Revised, January 1999 Compaq Computer 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 Compaq or an authorized sublicensor. Compaq conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Compaq Computer Corporation 1997, 1999. All rights reserved. The following are trademarks of Compaq Computer Corporation: Alpha, Compaq, DECdirect, DECnet-Plus, DECprint, DIGITAL, OpenVMS, PATHWORKS, VAX, VAX DOCUMENT, VAXcluster, VMS, and the Compaq logo. The following are third-party trademarks: AT&T is a registered trademark of American Telephone and Telegraph Company. Apple, AppleShare, LaserWriter, Macintosh, and TRUETYPE are registered trademarks of Apple Computer, Inc. DEC Rdb is a trademark of Oracle Corporation. Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company. IBM and OS/2 are registered trademarks of International Business Machines Corporation. Microsoft, MS-DOS, and Windows are registered trademarks, and Windows 95, Windows 98, and Windows NT are trademarks of Microsoft Corporation. MultiNet and TCPWARE are registered trademarks of Process Software Corporation. Novell and NetWare are registered trademarks of Novell, Inc. PostScript is a registered trademark of Adobe Systems Incorporated. All other trademarks and registered trademarks are the property of their respective holders. The PATHWORKS for OpenVMS (Advanced Server) documentation set is available on CD-ROM. ________________________________________________________________ Contents Preface.................................................. xiii 1 Distribution Kit 2 Features of PATHWORKS for OpenVMS (Advanced Server) 2.1 New Features of PATHWORKS V6.0B for OpenVMS (Advanced Server)............................... 2-2 2.1.1 Optional Support for Eight-Bit Characters in File Names.................................... 2-2 2.2 Overview of PATHWORKS V6.0B for OpenVMS (Advanced Server) Features...................... 2-3 2.2.1 Windows NT Domain Services ................... 2-4 2.2.2 Installation and Configuration ............... 2-4 2.2.2.1 Upgrade Utility............................ 2-5 2.2.2.2 Initial Server Configuration Procedure..... 2-5 2.2.2.3 Configuring Server Parameters.............. 2-5 2.2.3 File and Print Services ...................... 2-6 2.2.4 Client Support ............................... 2-6 2.2.5 Transport Support ............................ 2-6 2.2.5.1 DECnet Support............................. 2-6 2.2.5.2 TCP/IP Support............................. 2-7 2.2.5.3 WINS Support............................... 2-7 2.2.6 PostScript Printing Support .................. 2-7 2.2.7 Management Interfaces ........................ 2-8 2.2.7.1 ADMINISTER Command Line Interface.......... 2-8 2.2.7.2 Windows NT Server Administration Tools..... 2-9 2.2.8 Account Lockout .............................. 2-10 2.2.9 PATHWORKS Advanced Server Licensing .......... 2-10 2.2.9.1 License Enforcement........................ 2-11 2.2.10 External Authentication Support .............. 2-12 iii 2.3 Differences Between PATHWORKS V5 for OpenVMS (LAN Manager) and PATHWORKS V6 for OpenVMS (Advanced Server)............................... 2-12 2.4 Unsupported PATHWORKS V5 for OpenVMS (LAN Manager) Features............................... 2-14 3 Guidelines for Using PATHWORKS Advanced Server Software 3.1 Disk Space Requirements......................... 3-1 3.2 Server Configuration............................ 3-1 3.2.1 Monitoring Data Cache Use by the File Server........................................ 3-1 3.3 If You Reconfigure the Advanced Server.......... 3-3 3.4 Upgrading Client-Based Licenses................. 3-3 3.4.1 Upgrading PATHWORKS V5 License Requests ...... 3-4 3.4.2 Upgrading PATHWORKS V6 License Requests ...... 3-4 3.5 License Server Configuration Parameters......... 3-5 3.5.1 Determining Configuration Parameter Values ... 3-5 3.5.2 Dynamic Configuration Parameters ............. 3-5 3.5.3 Setting the PWRK$LICENSE_SERVER_INHIBIT Parameter..................................... 3-6 3.6 Setting Up Account Lockout...................... 3-7 3.6.1 Setting Up or Disabling User Account Lockout....................................... 3-7 3.6.2 Displaying Account Lockout Parameters ........ 3-8 3.6.3 Unlocking a Locked User Account .............. 3-9 3.7 External Authentication Logon Information....... 3-10 3.7.1 Avoiding User Name Conflicts ................. 3-10 3.7.2 Setting Up External Authentication by a Trusted Domain................................ 3-12 3.7.3 Implicit Host Mapping ........................ 3-12 3.8 PATHWORKS Client Can Log On Using Only One Transport....................................... 3-13 3.9 Administering OpenVMS Shares from a Windows NT Server.......................................... 3-14 3.9.1 Adding a Share from a Windows NT Server ...... 3-14 3.9.2 Enumerating or Modifying Shares from a Windows NT Server..................................... 3-15 3.10 Removing PATHWORKS Advanced Server ACEs from a File............................................ 3-15 3.11 Displaying PATHWORKS Advanced Server ACEs....... 3-16 iv 3.12 Using TCP/IP Products with PATHWORKS Advanced Server.......................................... 3-16 3.13 Time Zone Setup................................. 3-17 3.14 Entering Passwords on the ADMINISTER Command Line............................................ 3-17 3.15 External Authentication Requirement............. 3-17 4 Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4.1 MS ACCESS Unable to Open a File Read/Write...... 4-1 4.2 Unable to Complete PWRK$CONFIG After Upgrade.... 4-1 4.3 Windows 95 Cannot Enumerate All Shares on the Server.......................................... 4-2 4.4 Fatal Exception Results on Windows 95 Explorer.. 4-2 4.5 Unable to Log On to Any Domain on a Different Subnet.......................................... 4-2 4.6 ADMINISTER Command Hangs........................ 4-3 4.7 TCP/IP Stops Responding to Requests............. 4-3 4.8 XCOPY from MS-DOS Command Fails to Create Subdirectory.................................... 4-3 4.9 File Server Crashes When Enumerating Open Files........................................... 4-4 4.10 Server Incorrectly Returns Access Denied Message to Create Directory Request..................... 4-4 4.11 Server Cannot Validate Connection Requests in a Trust........................................... 4-4 4.12 File Server Becomes 100% CPU-Bound When Validating Connection Requests.................. 4-4 4.13 Windows 95 and Windows NT Clients Time Out When Creating Large Files on the Advanced Server..... 4-5 4.14 Nonpaged Pool Leak When Running with TCP/IP Services for OpenVMS V4.1, ECO6................. 4-5 4.15 File Modification Date Is Not Preserved When the File Is Copied from a Workstation............... 4-6 4.16 License Server Crashes at Restart............... 4-6 4.17 Loss of Server-Based License Units.............. 4-6 4.18 Memory Leak in Print Function................... 4-7 4.19 Unable to Print to OpenVMS V6.2 Print Queue..... 4-7 4.20 Memory Leak in PWRK$LMDMN Process............... 4-8 4.21 Session Limit Is Incorrectly Set to 99.......... 4-8 4.22 Unable to Access File Name That Has a Period at Position 40..................................... 4-8 v 5 Problems Corrected in PATHWORKS V6.0A 5.1 Installation and Configuration Problems......... 5-2 5.1.1 Installation with Upgrade Only Option Does Not Install PWRK$DELETEACE........................ 5-2 5.1.2 PATHWORKS Advanced Server Crash in PWRK$LMMCP.................................... 5-2 5.2 Licensing Problems.............................. 5-2 5.2.1 Incorrect Error Message Logged When Client Access Denied................................. 5-3 5.2.2 License Server Logs Incorrect Message When Request for License Is Rejected............... 5-3 5.2.3 Server-Based Licenses Are Not Counted in OpenVMS Cluster Environments.................. 5-3 5.2.4 Change in Client-Based Licensing Causes License Server to Crash....................... 5-4 5.2.5 Failure to Handle Client License Requests .... 5-4 5.2.6 License Server Does Not Handle PWNWXXXFP05.00 Licenses...................................... 5-5 5.2.7 License Manager Always Reports Zero Usage of PWLMXXXCA06.00 Licenses Allocated to the Server-Based Group............................ 5-5 5.2.8 License Registrar Interval Parameters Do Not Use New Values................................ 5-6 5.2.9 License Required of Backup and Primary Domain Controllers for Replication................... 5-7 5.2.10 PATHWORKS License Registrar Logs Incorrect Data in an OpenVMS Cluster.................... 5-7 5.3 Upgrade Utility Problems........................ 5-9 5.3.1 Upgrade Utility Does Not Report Locked-Out or Disabled Accounts............................. 5-9 5.4 Server Problems................................. 5-10 5.4.1 Server Fails to Start: PWRK$SECTION Not Defined....................................... 5-10 5.4.2 Server Crashes When Windows NT V3.51 Is Used to Delete Directories......................... 5-10 5.4.3 Advanced Server Crashes at PCM_BUFFER Routine....................................... 5-11 5.4.4 Server Crashes when Interacting with Windows for Workgroups V3.11 Computers with Browsing Capabilities ................................. 5-11 5.4.5 Server Crashes with INVEXCEPTN Bugcheck at PWRK$STREAMSOS_V6+00064FFC.................... 5-11 vi 5.5 ADMINISTER Command Problems..................... 5-12 5.5.1 SET PASSWORD Command Does Not Always Set the Password Correctly in Windows NT Domains...... 5-12 5.5.2 ADMINISTER SHOW GROUPS Command Results in Access Violation (ACCVIO)..................... 5-12 5.5.3 Autoshares Are Not Enumerated by the Advanced Server........................................ 5-12 5.5.4 CLOSE OPEN_FILE Command Does Not Work Properly with Wildcard................................. 5-13 5.5.5 HOSTMAP Commands Do Not Accept Domain-Qualified User Names................... 5-13 5.5.6 Specifying User Names Without Domain Names ... 5-13 5.5.7 /NOPASSWORD Qualifier with ADMINISTER Commands Defaults to Pre-expired....................... 5-14 5.5.8 PATHWORKS ADMINISTER Command Line Interface Does Not Allow Computer Names with Leading Backslashes................................... 5-15 5.5.9 ADD TRUST Command Does Not Require Confirmation.................................. 5-15 5.5.10 MODIFY SHARE Command Does Not Issue Confirmation Message.......................... 5-16 5.5.11 SET COMPUTER Command Does Not Allow You to Override Confirmation......................... 5-16 5.6 File Access/Printing Problems................... 5-16 5.6.1 Enumeration Slow on Shares with Many Subdirectories................................ 5-17 5.6.2 Implicit Hostmapping Does Not Work for a Windows 95 Domain Logon ...................... 5-17 5.6.3 Print Jobs Submitted to PATHWORKS Advanced Server Printers Fail With a SPOOL32 Error..... 5-17 5.6.4 Cannot Open More Than Five Shares from Windows NT Browser List .............................. 5-18 5.6.5 Unable to Access Some File Names That Have Greater Than 40 Characters.................... 5-18 5.6.6 PATHWORKS Advanced Server Crashes When Disk Quota Is Set Too Low.......................... 5-18 5.6.7 When Using the DOS Enhanced Redirector to Copy Files, the Modify Time Is Set Incorrectly..... 5-19 5.6.8 PATHWORKS Advanced Server Crashes with ACCVIO During Forced-Logoff Processing............... 5-19 5.6.9 Moving Job in Print Queue Causes PATHWORKS Advanced Server to Crash...................... 5-19 vii 5.6.10 External Authentication Fails after 444 Uses.......................................... 5-20 5.6.11 External Authentication Does Not Work When PWRK$ACME_DEFAULT_DOMAIN Is Defined........... 5-20 5.6.12 External Authentication Does Not Work When the Primary Domain Controller Is Not Running ..... 5-20 5.6.13 Printing Fails When Copying a Large File from a Windows NT DOS Window to LPT1............... 5-21 5.6.14 Failures Printing from Clients ............... 5-21 5.7 Problems with PATHWORKS Advanced Servers in OpenVMS Clusters................................ 5-21 5.7.1 NetLogon Fails to Start on Cluster Members ... 5-22 5.8 Problems with PATHWORKS Advanced Servers Running PATHWORKS for OpenVMS (NetWare)................. 5-22 5.8.1 System Crash in PWRK$STREAMSHR ............... 5-22 5.9 Transport Problems.............................. 5-22 5.9.1 PATHWORKS Advanced Server Fails to Detect and Discard Duplicate Name Responses.............. 5-23 5.9.2 KNB Resource Exhaustion Results in "Dead" Listener and ADMIN Commands Hang.............. 5-23 5.10 Browser Problems................................ 5-24 5.10.1 Browser Deadlock Hangs NetLogon Processing ... 5-24 5.10.2 STOP SERVICE BROWSER Does Not Release Master Browser....................................... 5-24 5.11 Windows NT Remove Management Problems........... 5-24 5.11.1 Groups Display May Be Incomplete in Windows NT User Manager.................................. 5-24 6 Problems Corrected in PATHWORKS V6.0B 6.1 Installation and Configuration Problems......... 6-1 6.1.1 PWRK$CONFIG.COM Procedure May Fail When Upgrading Accounts Database Files............. 6-1 6.2 Server Problems................................. 6-2 6.2.1 PWRK$LMMCP Process Hangs with "Not a Valid Pipe End" Errors.............................. 6-2 6.2.2 NetLogon Fails to Start If Domain Contains Many Computers................................ 6-2 6.2.3 Full Synchronization of Backup Domain Controller Occurs at NetLogon Startup......... 6-2 6.2.4 PWRK$LMSRV Crashes Intermittently with ACCVIO........................................ 6-3 viii 6.2.5 PWRK$LMSRV Crashes with ACCVIO After Printer Error......................................... 6-3 6.2.6 PWRK$LMSRV Crashes with ACCVIO After "Illegal SMBCount" Message............................. 6-3 6.2.7 PWRK$ACME_STARTUP.COM Unconditionally Sets SYS$SINGLE_SIGNON............................. 6-4 6.2.8 PWRK$LMSRV Crashes with ACCVIO When Processing Large SMB Messages............................ 6-4 6.3 ADMINISTER Command Problems..................... 6-4 6.3.1 SHOW PRINT QUEUES Command Fails to Fully Enumerate Print Queues........................ 6-4 6.4 File Access/Printing Problems................... 6-5 6.4.1 PWRK$LMSRV Crashes ........................... 6-5 6.4.2 File Server Allows Clients to Truncate Directory Files............................... 6-5 6.4.3 Printer Spool Files Are Not Deleted .......... 6-5 6.5 Event Logging Problems.......................... 6-6 6.5.1 Global Lock Warnings in Log File ............. 6-6 6.5.2 OpenVMS SET PASSWORD on an Externally Authenticated User Account Is Not Audited..... 6-6 6.6 Browser Problems................................ 6-7 6.6.1 Cannot Browse Across a Wide Area network to a PATHWORKS Server.............................. 6-7 7 Restrictions in PATHWORKS V6.0B 7.1 Installation and Configuration Restrictions..... 7-1 7.1.1 Configurator Allows Invalid Values for Maximum Concurrent Signons............................ 7-1 7.1.2 PWRK$CONFIG and PWRK$SETINI Command Procedures Fail After Domain Name Change Failure......... 7-1 7.1.3 PATHWORKS Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server........................................ 7-2 7.1.4 OpenVMS V7.1 Requires a Patch ................ 7-3 7.1.5 Advanced Server Fails to Start If Any Processes Are Running the ADMININSTER Command Line Interface................................ 7-3 7.1.6 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure............................. 7-3 7.2 File Server Restrictions........................ 7-4 7.2.1 File Server May Issue Incorrect BlobCache Warning Messages.............................. 7-4 ix 7.2.2 Advanced Server Cannot Support More Than 32,767 Shares................................. 7-4 7.2.3 OpenVMS File Names with a Dot at Position 40 Are Not Displayed Properly from the Client.... 7-4 7.2.4 Ownership of a Directory ..................... 7-5 7.2.5 Premature Disk Full Conditions ............... 7-5 7.2.6 File Server Does Not Enforce Disk Quotas by Default....................................... 7-6 7.2.7 DECram Performance Problem ................... 7-6 7.2.8 Access Denied to Files Restored from Backup of Another System................................ 7-6 7.2.9 Intruder Flag's Relationship to Computer Connections and Logons........................ 7-7 7.2.10 XCCB Not in Use Errors in LMMCP Log File ..... 7-7 7.3 User Interface Restrictions..................... 7-7 7.3.1 SHOW FILES Command Fails to List Subdirectories................................ 7-8 7.3.2 Server Description (SrvComment) Restriction .. 7-8 7.3.3 Alias Name Not in Browse List When Using DECnet Transport Only......................... 7-8 7.3.4 Server Acting as a BDC Will Not Allow Changes to Share Permissions Until Synchronized with PDC........................................... 7-9 7.3.5 Directory File (Folder) Name Length Restrictions.................................. 7-9 7.3.6 Mouse Selection Highlights Entire Screen ..... 7-10 7.3.7 When a User Account Is Created Without a Password, an Encrypted Password is Supplied... 7-10 7.3.8 File Server Unable to Resolve Job Logical Translation as Part of a File Specification... 7-10 7.4 Printing/Print Management Restrictions.......... 7-11 7.4.1 Client Cannot Purge Print Queues ............. 7-11 7.4.2 Windows NT Print Manager Fails to Display PATHWORKS Advanced Server Printers............ 7-11 7.4.3 Cannot See Print Job Name from Client ........ 7-11 7.4.4 Cannot Move Print Job Postion In Queue from Client........................................ 7-12 7.4.5 ADMINISTER REMOVE PRINT QUEUE Fails to Delete a Routing Print Queue......................... 7-12 7.5 Event Logging Restrictions...................... 7-12 7.5.1 Event in Browser Function not Reported Properly...................................... 7-13 x 7.5.2 Certain Event Code Descriptions Do Not Appear in ADMINISTER SHOW EVENTS Display............. 7-13 7.5.3 Event Log Files Fail to Overwrite When Full .. 7-13 7.5.4 Unable to Set the Event Logging Setting ...... 7-14 7.5.5 Displaying Application Event Log Files Fails to Display Event Data......................... 7-14 7.6 Domain Management Problems...................... 7-14 7.6.1 Changes to Trust Relationship on One Cluster Node Are Unknown to the Other Cluster Nodes Until NetLogon Restart........................ 7-15 7.6.2 Error When Displaying Advanced Server Domains from a Windows NT Server Manager.............. 7-15 7.6.3 A BDC Cannot Be Removed from the Domain If It Has Been Promoted to Be a PDC in Another Domain........................................ 7-15 7.7 Browser Restrictions............................ 7-16 7.7.1 Browser State Is Not Distributed on an OpenVMS Cluster....................................... 7-16 7.8 Transport Restrictions.......................... 7-16 7.8.1 System Error Is Reported If NetBEUI Is Not Configured.................................... 7-16 7.8.2 DEFZA FDDI Controller Is Not Supported with PATHWORKS Advanced Server..................... 7-17 7.8.3 NetBIOS Fails to Start, Dumps Invalid Media Address....................................... 7-17 7.8.4 Communication Device Names Must Not Begin with an Underscore................................. 7-18 7.9 PATHWORKS Advanced Server in an OpenVMS Cluster Restrictions.................................... 7-18 7.9.1 SRVHIDDEN Parameter Causes Browser to Fail to Announce Itself............................... 7-18 7.9.2 PATHWORKS Advanced Server May Fail at Startup Time If SYLOGIN.COM Executes with Errors...... 7-19 7.9.3 PATHWORKS Alias Cannot Be Used Across Subnets....................................... 7-19 7.10 PATHWORKS Advanced Server Interaction with DEC Rdb (Oracle) Restrictions....................... 7-19 7.10.1 PATHWORKS Advanced Server Fails to Start Correctly on Systems Running DEC Rdb.......... 7-19 xi ________________________________________________________________ Preface The PATHWORKS V6.0B 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 Audience These Release Notes are intended for the PATHWORKS for OpenVMS (Advanced Server) system administrator. 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 for OpenVMS (Advanced Server) documentation xiii Document Structure This manual contains the following chapters: o Chapter 1 contains information about the PATHWORKS for OpenVMS (Advanced Server) software kit. o Chapter 2 describes the main features of the PATHWORKS for OpenVMS (Advanced Server) software. o Chapter 3 provides guidelines for using the PATHWORKS for OpenVMS (Advanced Server) software. o Chapter 4 lists the software changes that were made in PATHWORKS V6 for OpenVMS ECO2. These changes also apply to PATHWORKS V6.0B for OpenVMS (Advanced Server). o Chapter 5 lists the software changes that were made in PATHWORKS V6.0A for OpenVMS (Advanced Server). These changes also apply to PATHWORKS V6.0B for OpenVMS (Advanced Server). o Chapter 6 lists the problems corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). o Chapter 7 describes restrictions in the PATHWORKS for OpenVMS (Advanced Server) software. xiv Related Documents The Release Notes supplement the following manuals: __________________________________________________________ Document___________________Description____________________ PATHWORKS for OpenVMS Explains how to upgrade a (Advanced Server) Server PATHWORKS V5 for OpenVMS (LAN Migration Guide Manager) server to PATHWORKS V6 for OpenVMS (Advanced Server). PATHWORKS for OpenVMS Explains how to install and Server Installation and configure PATHWORKS Advanced Configuration Guide Server software. Advanced Server for Provides an overview of and OpenVMS Concepts and introduction to the PATHWORKS Planning Guide for OpenVMS (Advanced Server) software and associated networking concepts for system administrators and operators. PATHWORKS for OpenVMS Explains how to manage and (Advanced Server) Server customize the PATHWORKS for Administrator's Guide OpenVMS (Advanced Server) software. Advanced Server for Provides command syntax OpenVMS Commands descriptions for all ADMINISTER Reference Manual commands and NET command equivalents. Advanced Server for Describes the license server OpenVMS Guide to Managing software and how to manage Advanced Server Licenses PATHWORKS for OpenVMS (Advanced ___________________________Server)_licenses.______________ xv The following table lists related OpenVMS documents. __________________________________________________________ OpenVMS_Document___________Description____________________ OpenVMS Alpha V7.1 Describes how to install the Upgrade and Installation OpenVMS Alpha V7.1 system Manual software. OpenVMS Alpha V7.2 Describes how to install the Upgrade and Installation OpenVMS Alpha V7.2 system Manual software. OpenVMS VAX V7.1 Upgrade Describes how to install and Installation Manual the OpenVMS VAX V7.1 system software. OpenVMS VAX V7.2 Upgrade Describes how to install and Installation Manual the OpenVMS VAX V7.2 system software. OpenVMS System Manager's A task-oriented guide to Manual managing an OpenVMS system. OpenVMS System Management A reference guide to the Utilities Reference utilities and tools used in Manual managing an OpenVMS system. OpenVMS License Explains how to load and manage Management Utility Manual license Product Authorization ___________________________Keys_(PAKs)____________________ xvi Reader's Comments Compaq welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_ COMMENTS.TXT and send us your comments by: Internet openvmsdoc@zko.mts.dec.com Fax 603-884-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the following World Wide Web address to order additional documentation: http://www.openvms.digital.com:81/ If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). xvii 1 ________________________________________________________________ Distribution Kit The PATHWORKS for OpenVMS software kit includes support for both OpenVMS VAX and OpenVMS Alpha systems and consists of the following BACKUP savesets. __________________________________________________________ Saveset_Name________OpenVMS_System________________________ PWRKV60B060.A VAX and Alpha PWRKV60B060.B VAX PWRKV60B060.C Alpha PWRKV60B060.D VAX PWRKV60B060.E_______Alpha_________________________________ Distribution Kit 1-1 2 ________________________________________________________________ Features of PATHWORKS for OpenVMS (Advanced Server) The PATHWORKS for OpenVMS Advanced Server (known as the PATHWORKS Advanced Server) is the next generation of the PATHWORKS LAN Manager server software. It supports: o LAN Manager V3.0 technology o OpenVMS Alpha and VAX V7.2 as well as V7.1 o Trusted domains o Wide Area Domain, Windows Internet Naming Services (WINS) integration over TCP/IP o Full browser functionality o Windows NT management APIs o The PATHWORKS comprehensive ADMINISTER command line interface o Password synchronization between OpenVMS and Advanced Server systems o User account lockout This chapter includes the following information: Features of PATHWORKS for OpenVMS (Advanced Server) 2-1 __________________________________________________________ Section Topic_______________________________________________Number New Features of PATHWORKS V6.0B for OpenVMS 2.1 (Advanced Server) Overview of PATHWORKS V6.0B for OpenVMS (Advanced 2.2 Server) Features Differences Between PATHWORKS V5 for OpenVMS (LAN 2.3 Manager) and PATHWORKS V6 for OpenVMS (Advanced Server) Unsupported PATHWORKS V5 for OpenVMS (LAN Manager) 2.4 Features__________________________________________________ 2.1 New Features of PATHWORKS V6.0B for OpenVMS (Advanced Server) The new features provided by PATHWORKS V6.0B for OpenVMS (Advanced Server) include the following: o Support for OpenVMS V7.2 VAX and Alpha systems, as well as for OpenVMS V7.1 VAX and Alpha systems o Support for V5.0 of TCP/IP Services for OpenVMS o Support for the PWLMXXXCA07.02 Client-Access licenses, as well as PWLMXXXCA06.00 licenses, allowing client access to both PATHWORKS for OpenVMS (Advanced Server) and Advanced Server for OpenVMS services o With OpenVMS V7.2, support for ODS-5 devices as ODS-2 devices o Optional support for eight-bit characters in file names (see Section 2.1.1) o Support for clients running Windows 98 2.1.1 Optional Support for Eight-Bit Characters in File Names PATHWORKS V6.0B for OpenVMS (Advanced Server) provides an optional feature that allows file names to contain the lowercase international characters, such as: 2-2 Features of PATHWORKS for OpenVMS (Advanced Server) é ï ö ô Characters must be encoded using the ISO Latin-1 character set (ISO-8859-1). When this feature is enabled, users on Windows 95, Windows 98, and Windows NT client computers can create and browse file names that contain these types of characters. File names are stored in the directory share using these characters, so the files can be accessed by these file names using the PATHWORKS Advanced Server. Restrictions Because Windows for Workgroups and MS-DOS computers do not recognize these types of characters, files with file names containing these characters will not be accessible by these client computers. This feature does not provide support of eight-bit characters in the names of shares and user accounts. Enabling this Feature This feature is disabled by default. To enable it, define a system-wide logical using the following command: $ DEFINE/SYSTEM PWRK$TEMP_VMSSERVER_CODE_PAGE "88591" For the feature to take effect, you must restart the server after entering this command. You can add this command to the following file, to ensure this feature is always enabled: SYS$STARTUP:SYLOGICALS.COM 2.2 Overview of PATHWORKS V6.0B for OpenVMS (Advanced Server) Features PATHWORKS V6.0B for OpenVMS (Advanced Server) supports the Alpha and VAX systems supported by OpenVMS V7.1 and V7.2. Some of the main features provided by PATHWORKS V6.0B for OpenVMS (Advanced Server) are described in the following sections. Features of PATHWORKS for OpenVMS (Advanced Server) 2-3 2.2.1 Windows NT Domain Services PATHWORKS Advanced Server allows you to run the server as the primary domain controller (PDC) or the backup domain controller (BDC) in a Windows NT-compatible domain. PATHWORKS Advanced Server can participate in the domain as a Master Browser or Backup Browser. The PATHWORKS Advanced Server supports the ability to be managed remotely from: o Windows NT Server o PATHWORKS Advanced Server o Advanced Server for OpenVMS o Clients running Windows NT Server administration tools For information about remote server management, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide. 2.2.2 Installation and Configuration PATHWORKS Advanced Server provides a single installation procedure that allows you to install any of the following: o PATHWORKS Advanced Server software (includes the Upgrade utility and the license server) ________________________Note ________________________ The NetWare server software is not provided with PATHWORKS V6.0B for OpenVMS (Advanced Server). If the NetWare software is present on your system, you must deinstal it before installing PATHWORKS V6.0B for OpenVMS (Advanced Server). To use the PATHWORKS V6.0B for OpenVMS (Advanced Server), users of the NetWare server software must migrate clients to a TCP/IP or NetBEUI networking solution. _____________________________________________________ o Upgrade utility only o License server only o External Authentication images only 2-4 Features of PATHWORKS for OpenVMS (Advanced Server) 2.2.2.1 Upgrade Utility PATHWORKS Advanced Server provides a separately instal- lable Upgrade utility. Use this Upgrade utility to upgrade the server's user, group, and share information from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server) while the server continues to run. This allows you to plan and upgrade shares, user accounts, and security in preparation for the PATHWORKS Advanced Server installation, without interrupting file and print services. ________________________Note ________________________ The separately installable Upgrade utility is offered only if the PATHWORKS V6 for OpenVMS (Advanced Server) installation procedure detects the presense of PATHWORKS V5 for OpenVMS (LAN Manager) _____________________________________________________ For more information about how to use the Upgrade utility, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. 2.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 the PATHWORKS Advanced Server processes. For more information about installing and configuring the PATHWORKS Advanced Server software, refer to the PATHWORKS for OpenVMS Server Installation and Configuration Guide. 2.2.2.3 Configuring Server Parameters The PATHWORKS Advanced Server provides a Configuration Manager tool. Use the Configuration Manager to modify server parameters and to enable and disable transport types after the server has been started. Use the following command to start the Configuration Manager: $ ADMINISTER/CONFIGURATION Features of PATHWORKS for OpenVMS (Advanced Server) 2-5 Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide for more information about using the Configuration Manager. 2.2.3 File and Print Services PATHWORKS Advanced Server supports the Windows NT- compatible Server Message Block (SMB) V3.0 file and print protocols. 2.2.4 Client Support PATHWORKS Advanced Server supports connections from the following types of clients: o Windows NT o Windows 95 and Windows 98 o Windows for Workgroups o PATHWORKS for DOS and Windows o PATHWORKS for Windows 95 o PATHWORKS 32 2.2.5 Transport Support PATHWORKS Advanced Server supports the same types of transports as does PATHWORKS V5 for OpenVMS (LAN Manager), but selects them in the following order, which differs from the order used by the PATHWORKS V5 for OpenVMS (LAN Manager) server: 1. TCP/IP 2. NetBEUI 3. DECnet-Plus (or DECnet Phase IV) 2.2.5.1 DECnet Support PATHWORKS V6.0B for OpenVMS (Advanced Server) supports DECnet and DECnet-Plus as supported by the OpenVMS operating system, Versions 7.1 and V7.2. 2-6 Features of PATHWORKS for OpenVMS (Advanced Server) ________________________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.2.5.2 TCP/IP Support PATHWORKS V6.0B for OpenVMS (Advanced Server) provides transparent support for the following TCP/IP network transport products: o On OpenVMS Version 7.1 systems, TCP/IP Services for OpenVMS, V4.1, V4.2, and V5.0. On OpenVMS Version 7.2 systems, TCP/IP Services for OpenVMS V5.0. o Process Software Corporation's MultiNet[1] o Process Software Corporation's TCPWARE for OpenVMS[1] For information about using TCP/IP products with PATHWORKS Advanced Server, refer to Section 3.12. 2.2.5.3 WINS Support The PATHWORKS Advanced Server can act as a client to Windows Internet Name Servers (WINS), allowing the PATHWORKS Advanced Server to use WINS services to resolve NetBIOS names in a Wide Area Network (WAN) configuration. For information about setting up WINS services for PATHWORKS Advanced Server, refer to the PATHWORKS for OpenVMS Server Installation and Configuration Guide. 2.2.6 PostScript Printing Support The PATHWORKS Advanced Server supports the DECprint Supervisor for OpenVMS (DCPS) family of layered products, which runs on OpenVMS VAX and Alpha systems to provide access through the OpenVMS queuing system to selected PostScript printers. ___________________ [1]For the supported software version, see the PATHWORKS V6.0B for OpenVMS (Advanced Server) Software Product Specification. Features of PATHWORKS for OpenVMS (Advanced Server) 2-7 2.2.7 Management Interfaces The following sections describe the management interfaces provided with the PATHWORKS Advanced Server. 2.2.7.1 ADMINISTER Command Line Interface PATHWORKS 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 Advanced Server for OpenVMS 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 after you start PATHWORKS Advanced Server: $ ADMINISTER HELP ADD USER The following command displays an overview about using the ADMINISTER user interface: 2-8 Features of PATHWORKS for OpenVMS (Advanced Server) $ ADMINISTER HELP NEW_USER NEW_USER Welcome to the ADMINISTER command line user interface. The ADMINISTER command line interface is a comprehensive utility for managing domains and servers in a network of compatible servers. You can invoke the interface in one of two ways: o Enter the command ADMINISTER, then press Return. This invokes the interface in subsystem mode. This is shown by the prompt DOMAIN\\SERVER>, where DOMAIN and SERVER are the default names of the domain and server you will be administering. Initially, DOMAIN is the name of the domain to which your local computer belongs, and SERVER is the name of your local computer. Once in subsystem mode, you can execute commands by entering subcommands, keywords, parameters, and qualifiers. To return to DCL, type EXIT or press Ctrl/Z. o Enter commands one at a time from DCL level. You enter the ADMINISTER command followed on the same line by keywords, parameters, and qualifiers, then press Return. After the command is completed, control returns to DCL. Additional information available: Case_Sensitivity UNC 2.2.7.2 Windows NT Server Administration Tools As 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 computers running any of the following operating systems: o Windows for Workgroups o Windows 95 and Windows 98 o Windows NT Workstation Features of PATHWORKS for OpenVMS (Advanced Server) 2-9 The Windows NT server administration tools are available in the PWUTIL share after you install, configure, and start 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 product documentation or use online Help for more information about how to use Windows NT Server administration tools. 2.2.8 Account Lockout The Windows NT account lockout feature supported by PATHWORKS V6.0B for OpenVMS (Advanced Server) allows administrators to have user accounts locked automatically after a specified number of failed attempts to log in (that is, after the user has entered the specified number of invalid passwords). Three ADMINISTER commands have been enhanced to accommodate the account lockout functionality: o SET ACCOUNT POLICY to enable or disable lockout capabilities o SHOW ACCOUNT POLICY to display lockout settings o MODIFY USER to unlock a locked out user account For more information on setting up the lockout policy for user accounts, see Section 3.6. If you are upgrading a PATHWORKS V6 for OpenVMS (Advanced Server) product, when you configure the PATHWORKS Advanced Server, the PWRK$CONFIG.COM procedure upgrades the V6.0 Security Account Manager (SAM) user account databases to a format that supports the account lockout feature. 2.2.9 PATHWORKS Advanced Server Licensing The PATHWORKS Advanced Server provides a simplified license management model. Both the license server and License Registrar are installed with the PATHWORKS Advanced Server software, and a License Manager utility is also provided for managing PATHWORKS Advanced Server licenses. If you use client-based licensing, you must run the license server. 2-10 Features of PATHWORKS for OpenVMS (Advanced Server) PATHWORKS Advanced Server requires all clients to be appropriately licensed to access resources on the server. See Section 2.2.9.1 for more information about setting up client-based licensing. For additional information about PATHWORKS licensing, refer to the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. 2.2.9.1 License Enforcement PATHWORKS Advanced Server requires that clients accessing server resources 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 minimum license required to access PATHWORKS V6 for OpenVMS (Advanced Server) services is the PATHWORKS Client-Access license: PWLMXXXCA06.00. The higher level PWLMXXXCA07.02 license, required by the Advanced Server V7.2 for OpenVMS, is also sufficient for licensing client access to PATHWORKS Advanced Servers. The license can be used as either a client-based license or a server-based license. For more information, refer to Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. Clients using client-based licenses to access PATHWORKS V5 for OpenVMS (LAN Manager) servers must upgrade their licenses to access PATHWORKS V6 for OpenVMS (Advanced Server) resources. Features of PATHWORKS for OpenVMS (Advanced Server) 2-11 2.2.10 External Authentication Support OpenVMS 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 Advanced Server software participates with the operating system to provide the ability to use the PATHWORKS Advanced Server 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. See Section 3.7 in these Release Notes for additional de- tails about external authentication. For more information about implementing external authentication, refer to the OpenVMS V7.2 Guide to System Security or OpenVMS V7.1 New Features Manual. 2.3 Differences Between PATHWORKS V5 for OpenVMS (LAN Manager) and PATHWORKS V6 for OpenVMS (Advanced Server) This section lists some of the general differences between the PATHWORKS Advanced Server product and the PATHWORKS LAN Manager product. o The PATHWORKS Advanced Server Administrator user account is similar to the PATHWORKS LAN Manager ADMIN user account. The Administrator user account is created automatically when you install and configure PATHWORKS Advanced Server. o The PATHWORKS LAN Manager server provides a single operator privilege level. The PATHWORKS Advanced Server provides several Operator groups. To designate a user account to be an operator, add the user account to one of the following PATHWORKS Advanced Server Operator groups: - Server Operator group (similar to LAN Manager Operator) - Print Operator group (similar to LAN Manager Operator) 2-12 Features of PATHWORKS for OpenVMS (Advanced Server) - Account Operator group (differs from the LAN Manager Operator in that members of this group cannot modify the Administrator user account, the Administrator group, or the Server Operator group). o PATHWORKS Advanced Server supports 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 are members of global groups only. Local groups are used by the PATHWORKS 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 the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. o PATHWORKS Advanced Server supports the same transports as does the PATHWORKS LAN Manager server, but selects them in a different order. (Refer to Section 2.2.5.) o The PATHWORKS Advanced Server software includes the Browser service, which allows the PATHWORKS Advanced Server system to function as a master browser in the domain. The Browser service is not included in PATHWORKS V5 for OpenVMS (LAN Manager). Of course, there are many more differences between the PATHWORKS LAN Manager server software and the PATHWORKS Advanced Server software. Refer to the PATHWORKS 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). Features of PATHWORKS for OpenVMS (Advanced Server) 2-13 2.4 Unsupported PATHWORKS V5 for OpenVMS (LAN Manager) Features The following features of PATHWORKS V5 for OpenVMS (LAN Manager) are not supported with PATHWORKS 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 PATHWORKS 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 PATHWORKS 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 Mode The PATHWORKS Advanced Server software does not support Backward Compatibility mode. This mode was used to ease the migration from PATHWORKS V4.x for VMS to PATHWORKS V5 for OpenVMS (LAN Manager). o Net Commands The Net commands are not supported by PATHWORKS 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. 2-14 Features of PATHWORKS for OpenVMS (Advanced Server) For more information about the translation of LAN Manager Net commands to PATHWORKS Advanced Server ADMINISTER commands, refer to the Advanced Server for OpenVMS Commands Reference Manual. o Remote Boot Service The PATHWORKS 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. o NetWare Server The NetWare server is no longer supported by PATHWORKS Advanced Server products. Features of PATHWORKS for OpenVMS (Advanced Server) 2-15 3 ________________________________________________________________ Guidelines for Using PATHWORKS Advanced Server Software Always read the product documentation prior to using the software. This chapter describes additional guidelines for using the PATHWORKS Advanced Server software. 3.1 Disk Space Requirements The installation software calculates the system disk space required for installation. The installation software needs room on the system disk to unpack the savesets containing the software options requested by the installer. The installation procedure calculates the needed space based on the sizes of the savesets to be unpacked, adding an additional 4500 blocks needed for the unpacking process. (The actual space occupied by the PATHWORKS Advanced Server software after installation and configuration may be less, but additional room is needed on the installation device to run the configuration procedure (PWRK$CONFIG).) For the amount of disk space required for installation and configuration, see the PATHWORKS for OpenVMS Server Installation and Configuration Guide. 3.2 Server Configuration The following sections describe server configuration parameters you should modify to enhance performance in certain circumstances. 3.2.1 Monitoring Data Cache Use by the File Server The 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 periodically monitors its use of the data cache, as follows: o Total security databases utilization Guidelines for Using PATHWORKS Advanced Server Software 3-1 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 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 (see below). o Individual security database utilization The file server monitors utilization of the data cache by individual security database files. When the database expands in size, more cache resources are required to continue operating. If the file server detects that an operation will cause a database file expansion, and that expanding the database file will cause it to utilize more than 50% of the data cache, error messages are recorded in the file server log, as in the following example: 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. In addition to recording the problem in the file server log, the software generates an operator message and raises a server alert. These messages indicate that the operation will prevent the file server from completing the current and future operations. In this case, you should use the Configuration Manager (ADMIN/CONFIG) to increase the size of the data cache so that utilization of the data cache by a single database file remains under 50%. The 3-2 Guidelines for Using PATHWORKS Advanced Server Software change to the data cache size takes effect the next time you start the server. You can use the ADMIN/ANALYZE command to monitor these warning messages and error messages. 3.3 If You Reconfigure the Advanced Server If you configure a previously configured server, the PWRK$CONFIG command procedure creates subdirectories in the PWRK$LMDOMAINS and PWRK$LMDATAFILES directories, and stores the original accounts database files there. The names of the subdirectories are based on the data and time, such as 16NOV199814314818.DIR, indicating that the directory was created on 16-NOV-1998, at approximately 2:31 p.m. If an error occurs during configuration, the server configuration will be returned to its original state. After a successful reconfiguration, you can manually delete these subdirectories and their contents. 3.4 Upgrading Client-Based Licenses A new control logical (PWRK$LS_V7_ACCESS_UPGRADE) has been added to the license server startup file (SYS$STARTUP:PWRK$LICENSE_S_START.COM) that allows you to upgrade a PATHWORKS for OpenVMS (LAN Manager) client license request or a PATHWORKS V6 Advanced Server license request to an Advanced Server V7.2 for OpenVMS (PWLMXXXCA07.02) license. If the logical is enabled (assigned a nonzero integer value), and a PWLMXXXCA07.02 license is available, a client that requests to assign or verify a client license will be assigned an Advanced Server V7.2 for OpenVMS license. If the logical is disabled (undefined or assigned a zero value), client license requests are not upgraded to PWLMXXXCA07.02. Guidelines for Using PATHWORKS Advanced Server Software 3-3 The first time the license server is started after an upgrade, the license server state file will be modified to remove all PWLMXXXCA06.00 licenses from the Server-Based license group. (The state file keeps track of licenses that are loaded, groups that are created, and license units assigned to each group.) The PATHWORKS Advanced Server license server still assigns and verifies client- based PWLMXXXCA06.00 licenses. 3.4.1 Upgrading PATHWORKS V5 License Requests To enable the license server to automatically upgrade and assign PWLMXXXCA07.02 client-based licenses to clients requesting or verifying a license valid for accessing PATHWORKS V5 file and print services, do the following before you start the Advanced Server: edit the license server startup file (SYS$STARTUP:PWRK$LICENSE_S_START.COM) and uncomment the following line (by removing the exclamation mark (!) at the beginning of the line): $! DEFINE PWRK$LS_V7_Access_Upgrade 1 !Enable V7.02 upgrade ________________________Note ________________________ The PWLMXXXCA07.02 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. _____________________________________________________ 3.4.2 Upgrading PATHWORKS V6 License Requests If you currently have the PATHWORKS V6 Advanced Server logical PWRK$LS_V6_ACCESS_UPGRADE defined, read the documentation in the license server startup file about the interaction between this logical and the PWRK$LS_V7_ACCESS_UPGRADE logical. If you only define the V6 logical, PWLMXXXCA06.00 licenses are assigned before assigning PWLMXXXCA07.02 licenses. If you want to remove all PWLMXXXCA06.00 licenses so that you only have PWLMXXXCA07.02 licenses, or if all units of a PWLMXXXCA06.00 license are consumed, the license server will assign a PWLMXXXCA07.02 license, if one is available. 3-4 Guidelines for Using PATHWORKS Advanced Server Software 3.5 License Server Configuration Parameters When PATHWORKS Advanced Server is started, the license server and the License Registrar are started using the following command procedures, respectively: o SYS$STARTUP:PWRK$LICENSE_S_START.COM o SYS$STARTUP:PWRK$LICENSE_R_START.COM These command procedure files contain complete descrip- tions of the configuration parameters used by each process when it runs. 3.5.1 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 log files related to license processing: 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 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.5.2 Dynamic Configuration Parameters Dynamic configuration parameters allow the value of a parameter to be changed using a system logical, without having to restart the server. The license component that uses the parameter obtains the changed value while the component is running. Guidelines for Using PATHWORKS Advanced Server Software 3-5 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 for changes to dynamic parameter values every 10 minutes. 3.5.3 Setting the PWRK$LICENSE_SERVER_INHIBIT Parameter The way the PATHWORKS license server interprets the value associated with the PWRK$LICENSE_SERVER_INHIBIT configuration parameter is different from the way PATHWORKS V5 for OpenVMS interprets it. 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 Advanced Server, 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 license server to run When you upgrade from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server), and 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 Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. 3-6 Guidelines for Using PATHWORKS Advanced Server Software 3.6 Setting Up Account Lockout User account lockout allows you to control the way the PATHWORKS Advanced Server handles potential security violations. For example, by enabling account lockout, you can ensure that logons from user accounts are disabled after a specified number of invalid password attempts are made. The following PATHWORKS Advanced Server ADMINISTER commands allow you to control account lockouts: __________________________________________________________ Command_______________Description___________Section_Number SET ACCOUNT POLICY Sets up or disables Section 3.6.1 the account lockout policy, using the /LOCKOUT or /NOLOCKOUT qualifier SHOW ACCOUNT POLICY Displays account Section 3.6.2 lockout parameters MODIFY USER Unlocks a locked Section 3.6.3 user account, using the /UNLOCK ______________________qualifier___________________________ 3.6.1 Setting Up or Disabling User Account Lockout You can enable account lockout by using the /LOCKOUT qualifier with the ADMINISTER command SET ACCOUNT POLICY. You can disable the lockout feature with the /NOLOCKOUT qualifier. (By default, account lockout is disabled.) With the /LOCKOUT qualifier, specify one or more of the following parameters: Guidelines for Using PATHWORKS Advanced Server Software 3-7 __________________________________________________________ Option___________Meaning__________________________________ ATTEMPTS=n Specifies the maximum failed logon count. The account is locked out after the specified number of failed attempts. The value of n can be from 1 to 999. The default is 5. WINDOW=n Specifies the number of minutes from the most recent failed login attempt before the failed login count is reset to zero. For example, if the WINDOW is set to 30 minutes, then thirty minutes after the most recent failed login attempt, the failed logon count is reset to zero. The value of n can be from 1 to 99999. The default is 30. DURATION=n Specifies the number of minutes before a locked-out account is automatically unlocked. The value of n can be FOREVER _________________or_from_1_to_99999._The_default_is_30.___ The following command example sets all three options. This example limits users to three failed logon attempts, resets the failed logon count 20 minutes after the last failed login attempt, and unlocks the locked-out account after 25 minutes. LANDOFOZ\\TINMAN> SET ACCOUNT POLICY - _LANDOFOZ\\TINMAN> /LOCKOUT=(ATTEMPTS=3,WINDOW=20,DURATION=25) %PWRK-S-ACCPOLSET, account policy set for domain "LANDOFOZ" 3.6.2 Displaying Account Lockout Parameters When the account lockout policy is set, the SHOW ACCOUNT POLICY command displays the following information: o Number of failed attempts allowed before a user account is locked. o Number of minutes accounts remain locked o Number of minutes before lockout count is reset 3-8 Guidelines for Using PATHWORKS Advanced Server Software This is how the display would look if you set the account policy as in Section 3.6.1: LANDOFOZ\\TINMAN> SHOW ACCOUNT POLICY Account Policy for domain "LANDOFOZ": Minimum password age (days) : 0 Maximum password age (days) : 42 Minimum password length : 0 Length of password history maintained : None Force user logoff after logon hours expire : NO Lock out account after how many bad password attempts : 3 Number of minutes account remains locked : 20 Number of minutes to wait before resetting lockout count : 25 Role of server TINMAN : Primary Domain Controller The following example shows how to disable account lockout and shows the resulting SHOW ACCOUNT POLICY display: LANDOFOZ\\TINMAN> SET ACCOUNT POLICY/NOLOCKOUT LANDOFOZ\\TINMAN> SHOW ACCOUNT POLICY Account Policy for domain "LANDOFOZ": Minimum password age (days) : 0 Maximum password age (days) : 42 Minimum password length : 0 Length of password history maintained : None Force user logoff after logon hours expire : NO Lock out account after how many bad password attempts : Never Role of server TINMAN : Primary Domain Controller 3.6.3 Unlocking a Locked User Account The administrator can immediately unlock a user's account by using the /UNLOCK qualifier with the MODIFY USER command. The administrator might want to unlock a user's account when the user has forgotten his or her password and exceeded the number of failed password attempts. In the following example, the account for user SCARECROW is unlocked: LANDOFOZ\\TINMAN> MODIFY USER/UNLOCK SCARECROW %PWRK-S-USERMOD, user "SCARECROW" modified on domain "LANDOFOZ" Guidelines for Using PATHWORKS Advanced Server Software 3-9 3.7 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 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. 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 proceeds to authenticate this request. - If the domain name is different from that of the local server, 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.7.1 Avoiding User Name Conflicts If the software encounters a conflict in user names, 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. 3-10 Guidelines for Using PATHWORKS Advanced Server Software In the following examples, the PATHWORKS Advanced Server is 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. Example 1: You enable external authentication for both of the OpenVMS users and then specify the user host mapping as follows: $ 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 log in to VMS1, this login 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 log in to VMS1, this login attempt fails because of the user name conflict between PATHWORKS Advanced Server and OpenVMS. To log in, OpenVMS user V_Smith must specify her PATHWORKS Advanced Server user name, specifying the domain name (either Smith@SaleOffice or SaleOffice\Smith). Example 2: You enable external authentication only 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 log in to VMS1, the login attempt fails because Smith is interpreted as an OpenVMS user name. Because the OpenVMS user name is not enabled for external authentication, the OpenVMS authentication mechanism is used to verify the password. To log in, the OpenVMS user V_Smith must specify the domain name with her PATHWORKS Advanced Server user name (either Smith@SaleOffice or SaleOffice\Smith). Guidelines for Using PATHWORKS Advanced Server Software 3-11 3.7.2 Setting Up External Authentication by a Trusted Domain You can set up an OpenVMS account to be externally authenticated by a trusted domain. 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 the 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. 4. To log in, specify the user name in one of the following formats: Jones@Marketing Marketing\Jones 3.7.3 Implicit Host Mapping Host mapping is used to determine the OpenVMS user name when logging in to OpenVMS using external authentication. External authentication supports both explicit and implicit user host mapping between OpenVMS and PATHWORKS Advanced Server. You can explicitly map 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. 3-12 Guidelines for Using PATHWORKS Advanced Server Software 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) For external authentication, the PATHWORKS Advanced Server user account Administrator is implicitly mapped to the OpenVMS user account SYSTEM. Therefore, if you enable 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 rename the Administrator account, the implicit mapping is not preserved. You must explicitly map the newly renamed account name to the OpenVMS SYSTEM account using the ADMINISTER command ADD HOSTMAP. The same is true with the PATHWORKS Advanced Server user account Guest. 3.8 PATHWORKS Client Can Log On Using Only One Transport 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 the client's 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 the domain logon fails, the client can still connect to servers but must provide a password for each session established. To avoid this problem, do one of the following: o Enable all of the transports that are common to both the server and client Guidelines for Using PATHWORKS Advanced Server Software 3-13 o Change the WRKNETS parameter to load a common server-client transport on LANA0 (for more information, see the client product documentation) 3.9 Administering OpenVMS Shares from a Windows NT Server The Windows NT server administration tool Server Manager attempts to verify share paths locally, before passing server operation requests 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 verification. Therefore, you cannot manage this type of OpenVMS share from the Windows NT Server Manager. The following sections describe ways to manage an OpenVMS share from the Windows NT Server. 3.9.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: Procedure 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 3-14 Guidelines for Using PATHWORKS Advanced Server Software Procedure 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 specifying device:[share], enter device\share. 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: c:\share1 PATHWORKS Advanced Server is designed to interpret C: correctly. In this case, the actual OpenVMS specification is PWRK$LMROOT:[SHARE1]. _____________________________________________________ 3.9.2 Enumerating 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.10 Removing PATHWORKS Advanced Server ACEs from a File PATHWORKS Advanced Server supplies the utility SYS$SYSTEM:PWRK$DELETEACE.EXE, which is used to remove PATHWORKS ACEs (Access Control Entries) from any file on OpenVMS. Note that removing file server ACEs will alter the DOS attributes and security settings of a file. Guidelines for Using PATHWORKS Advanced Server Software 3-15 To remove a PATHWORKS ACE from a file, use the following command and respond to the prompts appropriately: $ MCR PWRK$DELETEACE 3.11 Displaying PATHWORKS Advanced Server ACEs In OpenVMS V7.1 and later, if you execute the DCL command DIRECTORY/SECURITY or DIRECTORY/FULL for files that contain PATHWORKS access control entries (ACEs), the hexadecimal representation for each PATHWORKS ACE is no longer displayed. Instead, the commands summarize the total number of PATHWORKS ACEs encountered for each file in this message: "Suppressed n PATHWORKS ACE." To display the suppressed ACEs, use the DUMP/HEADER command. 3.12 Using TCP/IP Products with PATHWORKS Advanced Server PATHWORKS Advanced Server provides transparent support for the following TCP/IP network transport products: o On OpenVMS V7.1, TCP/IP Services for OpenVMS V4.1, V4.2, and V5.0 o On OpenVMS V7.2, TCP/IP Services for OpenVMS V5.0 o MultiNet[2] o TCPWARE for OpenVMS[2] To use PATHWORKS Advanced Server with TCP/IP, do the following: 1. Install and, if necessary, configure the TCP/IP product. 2. Start the TCP/IP transport and the PATHWORKS IP driver. The procedure depends on which TCP/IP product you use. For more information, refer to the documentation that comes with your TCP/IP product. ___________________ [2]For the supported software, see the PATHWORKS V6.0B for OpenVMS (Advanced Server) Software Product Specification. 3-16 Guidelines for Using PATHWORKS Advanced Server Software 3. Start the PATHWORKS Advanced Server. Enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:PWRK$STARTUP 3.13 Time Zone Setup PATHWORKS Advanced Server's internal time management uses Greenwich Mean Time (GMT). 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. 3.14 Entering Passwords on the ADMINISTER Command Line In most cases, passwords are case sensitive. When entering a password on an ADMINISTER command line, be sure to enclose it in quotation marks if it contains lowercase letters, blanks (spaces), or nonalphanumeric characters. When entering a password in response to a password prompt, the password need not be enclosed in quotation marks. For more information about using passwords, see the Advanced Server for OpenVMS Commands Reference Manual, or use the following ADMINISTER command: $ ADMINISTER HELP Using_Passwords 3.15 External Authentication Requirement To allow users to be externally authenticated over DECnet-Plus for OpenVMS, set the system parameter NET_ CALLOUTS to 255. This enables Advanced Server user ID mapping and authentication for network logins. Guidelines for Using PATHWORKS Advanced Server Software 3-17 4 ________________________________________________________________ Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 This section lists software changes made in the PATHWORKS V6 for OpenVMS ECO2 software to correct problems found in PATHWORKS for OpenVMS. These software changes are also included in PATHWORKS V6.0B for OpenVMS (Advanced Server). 4.1 MS ACCESS Unable to Open a File Read/Write Problem: Using MS ACCESS 97 on Windows 95, if the user opens a database file on an Advanced Server share, the user gets the following message: The database "name" is read-only. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.2 Unable to Complete PWRK$CONFIG After Upgrade Problem: When the Upgrade utility creates the SAM database, the resulting database file is not accessable by the configuration utility. As a result, PWRK$CONFIG fails. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4-1 4.3 Windows 95 Cannot Enumerate All Shares on the Server Problem: If a Windows 95 PC browses the Advanced Server using the Explorer or the NET VIEW command, it may get an incomplete listing of the shares. The same problem is exhibited using an MS-DOS PC with PATHWORKS for MS-DOS V6.0 and the enhanced Redirector. This problem occurs because the return buffer is not of sufficient size to contain all the information to be returned to the client. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. When this situation is encountered, the server removes the descriptive information for these shares from the return buffer in order to accommodate the total share name information. 4.4 Fatal Exception Results on Windows 95 Explorer Problem: Using Windows 95 Explorer, when selecting a folder with a long file name, the following error occurs: A fatal exception 0E has occurred at 0028:C0231810 in VXD VMM (0D) + 00001810. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.5 Unable to Log On to Any Domain on a Different Subnet Problem: When issuing a logon request to another domain where the other domain controller is located on a different TCP/IP subnet, the Advanced Server fails to locate the primary domain controller. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4-2 Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4.6 ADMINISTER Command Hangs Problem: To execute the ADMINISTER command without first logging on to the network, the OpenVMS process must have SYSPRV, OPER, and SYSLCK privileges enabled. If the process has only the SYSPRV and OPER privileges enabled, the ADMINISTER command hangs. When you enter Ctrl/Y, the software returns the command prompt. This causes the following additional problems: o The NetLogon service hangs, failing to authenticate user logons. o The ADMINISTER command line interface hangs. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.7 TCP/IP Stops Responding to Requests Problem: A timing problem in the TCP/IP communication path causes the file server to become unable to communicate with clients using the TCP/IP transport. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.8 XCOPY from MS-DOS Command Fails to Create Subdirectory Problem: When a client running Windows NT V4.0 executes the XCOPY command with the /s option in the MS-DOS command window, and the destination is an Advanced Server, the command fails to create the associated subdirectory. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4-3 4.9 File Server Crashes When Enumerating Open Files Problem: Under some conditions, the file server will crash when responding to a request to display (enumerate) all open files in the server. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.10 Server Incorrectly Returns Access Denied Message to Create Directory Request Problem: The file server returns an error code of "access denied" when responding to a directory create command, if the directory already exists. This is not the correct error code. The correct error code is "file already exists." If auditing is enabled, this error condition causes an unnecessary and incorrect audit trail of NET3004 errors. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.11 Server Cannot Validate Connection Requests in a Trust Problem: When running in an OpenVMS cluster, the file server fails to authenticate a trust connect. This occurs because an inactive NetLogon server in the cluster fails to process the request. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.12 File Server Becomes 100% CPU-Bound When Validating Connection Requests Problem: There is a timing problem in the file server while authenticating a trust connect. When this problem occurs, the server process consumes 100% of the CPU resources and fails to respond to other activities. 4-4 Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.13 Windows 95 and Windows NT Clients Time Out When Creating Large Files on the Advanced Server Problem: When a Windows 95 or Windows NT client attempts to create a large file on the Advanced Server by copying it from the client to the server, the client times out the operation before the file server's create operation is complete. The client reports a failure status of "network resource no longer available." This problem occurs because the file server is waiting for the disk device to complete creation of the large target file. After a timeout occurs, the client may be able to see the target file on the file server; however if the client attempts to access the target file while the file server is still creating the file, the client is denied access. DOS and Windows clients do not experience this session timeout problem when copying and creating large files. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.14 Nonpaged Pool Leak When Running with TCP/IP Services for OpenVMS V4.1, ECO6 Problem: TCP/IP Services for OpenVMS versions prior to V4.1, ECO6, exhibit a nonpaged pool leak when running with Advanced Server. Solution: A previous version of the release notes indicated that this problem is resolved in TCP/IP Services for OpenVMS V4.1, ECO6. This is incorrect. The resolution to this memory leak problem has not been released in any available ECOs for the TCP/IP Services for OpenVMS product. Contact Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4-5 your support representative to obtain the patch for this problem. 4.15 File Modification Date Is Not Preserved When the File Is Copied from a Workstation Problem: The file server fails to preserve the modification date of a file during the copy operation; instead, it uses the current date and time as the modification date. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.16 License Server Crashes at Restart Problem: If the license PAK for the Client Access license (PWLMXXXCA06.00) is removed using the License Management Facility (LMF) while the license server is shutting down, the license server will crash when restarted. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.17 Loss of Server-Based License Units Problem: If the license PAK for the Client Access license (PWLMXXXCA06.00) is removed while some of its license units are in use by the Server-Based license group, those units will not be recovered. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4-6 Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4.18 Memory Leak in Print Function Problem: When there is no information to be retrieved on a print queue, the server fails to return allocated memory resources, causing a memory leak in the file server process. The file server eventually crashes with an %EXQUOTA error. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.19 Unable to Print to OpenVMS V6.2 Print Queue Problem: If you are running Advanced Server in an OpenVMS cluster with members running different versions of OpenVMS, you will be unable to print to a print queue on a member running OpenVMS V6.2. The Advanced Server uses print switches that are not supported by the OpenVMS V6.2 print queue manager. As a result, the submission of the print job fails. When this problem is encountered, the PC receives no error, but the print job is not submitted. The ADMIN /ANALYZE Event log file contains the following error message: ================= EVENT #32758 ================== Event Time: 17-DEC-1997 23:55:49.56 Node: DSSHW1 Process Id: 28C00185 Event: Unexpected System Error Encountered Event Source: Print Services (PPS) Event Class: Error Status: %JBC-F-INVITMCOD, invalid item code or option code Text: submit (2) Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 4-7 4.20 Memory Leak in PWRK$LMDMN Process Problem: A small memory leak occurs in the PWRK$LMDMN process when it is processing account information. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4.21 Session Limit Is Incorrectly Set to 99 Problem: The file server incorrectly uses an obsolete LANMAN.INI parameter (maxvcperproc) and sets the total sessions limit to the default of 99. This limitation prevents connections from the 100th client regardless of the number of clients that the server is configured to support. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. As a result of this correction, the maxvcperproc parameter will no longer have any effect on the file server. 4.22 Unable to Access File Name That Has a Period at Position 40 Problem: The server fails to locate an encoded file name with a period in position 40. The client will not be able to see these files on an ODS-2 disk. Solution: This problem is resolved in PATHWORKS V6 for OpenVMS ECO2. 4-8 Problems Corrected in PATHWORKS V6 for OpenVMS ECO2 5 ________________________________________________________________ Problems Corrected in PATHWORKS V6.0A The problems described in this chapter are corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and in PATHWORKS V6.0B for OpenVMS (Advanced Server). The problems are described in the sections listed in the following table: __________________________________________________________ Problem_Type____________________Section_Number____________ Installation and Configuration 5.1 Problems Licensing Problems 5.2 Upgrade Utility Problems 5.3 Server Problems 5.4 ADMINISTER Command Problems 5.5 File Access/Printing Problems 5.6 Problems with PATHWORKS 5.7 Advanced Servers in OpenVMS Clusters Problems with PATHWORKS 5.8 Advanced Servers Running PATHWORKS for OpenVMS (NetWare) Transport Problems 5.9 Browser Problems 5.10 Windows NT Remove Management 5.11 Problems__________________________________________________ Problems Corrected in PATHWORKS V6.0A 5-1 5.1 Installation and Configuration Problems This section describes installation problems corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5.1.1 Installation with Upgrade Only Option Does Not Install PWRK$DELETEACE Problem: If you select installation of only the PATHWORKS Upgrade utility, the PWRK$DELETEACE.EXE utility is not installed. This utility can be very useful after a failed upgrade attempt. Use the utility to remove PATHWORKS Access Control Entries (ACEs), such as from earlier versions of PATHWORKS. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). PWRK$DELETEACE.EXE is now installed when you choose to install the Upgrade utility only. 5.1.2 PATHWORKS Advanced Server Crash in PWRK$LMMCP Problem: If a server configuration parameter is set to a null value while the PATHWORKS Advanced Server is running (for example, if all user names are removed from the AlertNames list, or if the server description string is removed), the Master Control Process (PWKR$LMMCP) crashes. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2 Licensing Problems This section describes licensing problems corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5-2 Problems Corrected in PATHWORKS V6.0A 5.2.1 Incorrect Error Message Logged When Client Access Denied Problem: If client license software is running, and the client does not have any client licenses loaded, incor- rect error messages are logged. Specifically, if the client tries to access the server, the error message CLIENT_LICENSE_INVALID is logged in the License Registrar log file PWRK$LOGS:PWRK$LICENSE_REGISTRAR_node-name.LOG with the message "TSR not running on client." The log files should contain the message "No client licenses returned." Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2.2 License Server Logs Incorrect Message When Request for License Is Rejected Problem: The license server either fails to log, or logs incor- rectly, the error message indicating the client requested an invalid license. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2.3 Server-Based Licenses Are Not Counted in OpenVMS Cluster Environments Problem: In a cluster environment where the Advanced Server is using server-based licensing, some of the server-based licenses may not be counted. As a result, clients are unable to access the server because of insufficient licenses available. The number of available server based licenses reported by the PWLICENSE utility is less than it should be, based on the number of license units placed into the server-based license group and the number of clients using server-based licensing. Solution: Problems Corrected in PATHWORKS V6.0A 5-3 The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2.4 Change in Client-Based Licensing Causes License Server to Crash Problem: The license server may fail if the number of units of the PWLMXXXCA06.00 license is lowered to a level below the number currently in use. This causes the license server to abort, with messages in the PWRK$LOGS:PWRK$LICENSE_SERVER_ nodename.LOG file similar to the following: 19-MAR-1998 10:16:47.00 MESSAGE: product index 6 19-MAR-1998 10:16:47.00 MESSAGE: excess: initial, later, final: -33, -33, -33 19-MAR-1998 10:16:47.00 MESSAGE: excessCt: = -33, total allocated count = 203, number of licenses = 170 19-MAR-1998 10:16:47.00 FATAL_ERROR: Bad Code Path in LMF resynchronization Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2.5 Failure to Handle Client License Requests Problem: The server fails to handle some client license requests (t_accept/t_look). The log file PWRK$LOGS:PWRK$LICENSE_ SERVER_nodename.LOG will contain a series of messages similar to the following: 18-MAR-1998 01:08:58.00 MESSAGE: t_accept failure t_errno is 9 18-MAR-1998 01:08:58.00 MESSAGE: listener state is 4 accepter state is 2 18-MAR-1998 01:08:58.00 MESSAGE: t_look error on the listener fd is 16 t_look error is on accepter fd is 0 5-4 Problems Corrected in PATHWORKS V6.0A Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2.6 License Server Does Not Handle PWNWXXXFP05.00 Licenses Problem: The license server does not properly handle client requests for a PWNWXXXFP05.00 license. Requests for this license are rejected. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.2.7 License Manager Always Reports Zero Usage of PWLMXXXCA06.00 Licenses Allocated to the Server-Based Group Problem: The License Manager (ADMIN/LICENSE) reports zero usage for Client Access Licenses (PWLMXXXCA06.00) that are used as server-based licenses. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The License Manager reports the correct usage counts. It accumulates the usage data across the OpenVMS cluster. The usage data counts correspond to the counts reported by the PWLICENSE command. (The PWLICENSE command is defined in the PATHWORKS command definition file, SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM, and invokes the SYS$SYSTEM:PWRK$LR_SHOW_USAGE.EXE utility, which displays the number of licenses being used.) Problems Corrected in PATHWORKS V6.0A 5-5 5.2.8 License Registrar Interval Parameters Do Not Use New Values Problem: The PATHWORKS License Registrar defines several parameters used as environment variables to control registrar processing. Two of these parameters define time intervals: o PWRK$LR_LICENSE_REPORT_INTERVAL - Specifies the time interval (in seconds) for generating reports of server-based license usage in the registrar log file (PWRK$LOGS:PWRK$LICENSE_REGISTRAR_nodename.LOG). o PWRK$LRLMFSYNCHINTERVAL - Specifies the time interval (in minutes) for the synchronization of the License Manager and the License Management Facility (LMF) to update server-based license usage information. If the PWRK$LR_LICENSE_REPORT_INTERVAL parameter is either undefined or defined as zero, then server-based license reporting is disabled and cannot be enabled by redefining the parameter. It can only be enabled by the following: 1. Stop the Advanced Server 2. Set the parameter to a non-zero value 3. Restart the Advanced Server If either of these parameters is defined to specify a long interval, and you reduce it to a short interval, the change does not take effect until the current (long) interval ends. For example, if license reporting is currently on a one-day interval, and you need to reduce it to 10 minutes, the change will not be effective until the current one-day interval ends. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). Changes to these parameters are detected within 10 minutes and take effect immediately thereafter. Thus, if you change the license reporting interval from one day to one minute, you will see your first report within 10 minutes and every minute thereafter. 5-6 Problems Corrected in PATHWORKS V6.0A 5.2.9 License Required of Backup and Primary Domain Controllers for Replication Problem: A Client Access license is required for every system making a connection to the server, including primary and backup domain controllers attempting to establish a connection for the purpose of replication. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). Only clients connecting to a PATHWORKS server to access a file share or a print share require a license. Primary and backup domain controllers connecting for purposes of replication no longer require a license. 5.2.10 PATHWORKS License Registrar Logs Incorrect Data in an OpenVMS Cluster Problem: In an OpenVMS cluster environment, with PATHWORKS Advanced Server running on more than one cluster member, the License Registrar's optional License Reporting mechanism logs incorrect data. This report is generated periodically in the License Registrar's log file, if the PWRK$LR_LICENSE_REPORT_INTERVAL parameter is defined. (For information about setting license logging parameters, see the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses. The report includes the Client Access license (PWLMXXXCA06.00) and others. The data displayed includes the total number of license units, the number used, and the number available. For the Client Access license, the total number of license units is cluster-wide. o The number of license units used is the number used on each particular cluster node. o The number of license units available is currently calculated as the difference between the total number of license units and the number used. Problems Corrected in PATHWORKS V6.0A 5-7 Thus, for the Client Access licenses in an OpenVMS cluster, the number of units available is calculated as the total number of units cluster-wide minus the number in use on a given node. This number is meaningless and misleading. For example: 22-JUN-1998 16:02:04.00 MESSAGE: ----------------------------------------------------- License Registrar Server Based License Report at 22-JUN-1998 16:02:04.00 License: PWLMXXXCA06.00 Total: 250 Assigned: 25 Available: 225 ----------------------------------------------------- License: PWNWVMSCU01.00 Total: 250 Assigned: 0 Available: 250 ----------------------------------------------------- This example shows the display for one node in the OpenVMS cluster. Other nodes may also be using Client Access license units. Each displays the available licenses as the cluster-wide total, minus the number in use on the individual node. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). This report is corrected to provide meaningful information. The report looks like this: 23-JUN-1998 09:37:14.00 MESSAGE: ----------------------------------------------------- License Registrar Server Based License Report at 23-JUN-1998 09:37:14.00 5-8 Problems Corrected in PATHWORKS V6.0A License: PWLMXXXCA06.00 Clusterwide Total: 250 Used This Node: 25 Used Clusterwide: 50 Available: 200 ----------------------------------------------------- License: PWNWVMSCU01.00 Total: 250 Used This Node: 0 Available: 250 ----------------------------------------------------- One field has been added to the report of the Client Access license, and the field labels have been modified to be more explicit. All the data in the new report is correct. The available count is correctly reported as the cluster wide total minus the number in use cluster wide. Further, if License Reporting is enabled, previous to PATHWORKS V6.0A for OpenVMS (Advanced Server), the License Registrar was reporting both the Client Access license and the PWNWVMSCU license, even if one or the other was not present. With PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server), if one or the other is not present, it is not listed. 5.3 Upgrade Utility Problems This section describes problems with the Upgrade utility corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5.3.1 Upgrade Utility Does Not Report Locked-Out or Disabled Accounts Problem: The Upgrade utility, which is used to upgrade server information from PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKS V6 for OpenVMS (Advanced Server), does not upgrade user accounts that are disabled or locked out. The User Upgrade report does not indicate these accounts were not upgraded. Solution: Problems Corrected in PATHWORKS V6.0A 5-9 The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The User Upgrade report includes a comment next to user accounts indicating that they are disabled or locked out. Compaq recommends that you ensure that no user accounts are locked out when you start the user upgrade portion of the Upgrade procedure. Refer to the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide for more information about upgrading user accounts. 5.4 Server Problems This section describes the file server problems corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5.4.1 Server Fails to Start: PWRK$SECTION Not Defined Problem: On some systems, server startup fails with messages similar to the following in one of the log files: %ERR, RMS file access failure -ERR, filename = PWRK$SECTION:PWRK$SECTION_2000_server-name.SECTION -ERR, "%RMS-F-DEV, error in device name or inappropriate device type for operation" -ERR, "%SYSTEM-W-NOSUCHDEV, no such device available" Solution: This problem is corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.4.2 Server Crashes When Windows NT V3.51 Is Used to Delete Directories Problem: When a Windows NT V3.51 client is used to delete directories, the file server can lose track of I/O channels and then run out of free I/O channels, causing it to crash. Solution: 5-10 Problems Corrected in PATHWORKS V6.0A The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.4.3 Advanced Server Crashes at PCM_BUFFER Routine Problem: The Advanced Server crashes on startup in module PCM_ BUFFER routine loc_alloc_bdsc. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.4.4 Server Crashes when Interacting with Windows for Workgroups V3.11 Computers with Browsing Capabilities Problem: The Advanced Server crashes when a Windows for Workgroups V3.11 computer that has browsing enabled attempts to connect to it. The crash happens if the Windows for Workgroups name query message does not include a TCP/IP address. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.4.5 Server Crashes with INVEXCEPTN Bugcheck at PWRK$STREAMSOS_V6+00064FFC Problem: On Symmetric MultiProcessing (SMP) systems, the PATHWORKS Advanced Server system crashes with an INVEXCEPTN error at PWRK$STREAMSOS_V6+00064FFC. This is caused by a timing error. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0A 5-11 5.5 ADMINISTER Command Problems This section describes ADMINISTER command problems corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5.5.1 SET PASSWORD Command Does Not Always Set the Password Correctly in Windows NT Domains Problem: If you use the ADMINISTER SET PASSWORD command 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. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.5.2 ADMINISTER SHOW GROUPS Command Results in Access Violation (ACCVIO) Problem: When using the SHOW GROUPS command to display members of a group, if any of those members has invalid security IDs (SIDS), the ADMINISTER interface encounters an access violation (ACCVIO). Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.5.3 Autoshares Are Not Enumerated by the Advanced Server Problem: The ADMINISTER SHOW SHARES command does not enumerate autoshares. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The Advanced Server supports the enumeration of autoshared devices as part of the share enumeration displayed by the SHOW SHARES command. 5-12 Problems Corrected in PATHWORKS V6.0A 5.5.4 CLOSE OPEN_FILE Command Does Not Work Properly with Wildcard Problem: When using the CLOSE OPEN_FILE command with a wildcard (*) to close multiple files, only one file at most is closed. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.5.5 HOSTMAP Commands Do Not Accept Domain-Qualified User Names Problem: The ADD, REMOVE, and SHOW HOSTMAP commands do not accept domain-qualified names. The SHOW HOSTMAP command does not display domain-qualified names, unless the domain is the one the user's computer is in. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.5.6 Specifying User Names Without Domain Names Problem: When certain commands accept user names without the associated domain name, they assume the users are from a trusted domain. The results could be contrary to what you might expect. For example, assume the following: o User KORN is in domain GRAINS o Domain GARDEN trusts domain GRAINS o The server is SERVER24 in domain GARDEN The administrator might enter the following command expecting it to assign full permission to user KORN in domain GARDEN. However, this command would actually assign full permission to KORN in domain GRAINS (GRAINS\KORN). GARDEN\\SERVER24> MODIFY SHARE share-name /PERMISSIONS=(KORN=FULL) Problems Corrected in PATHWORKS V6.0A 5-13 The commands that can exhibit this behavior are: ADD GROUP/MEMBER COPY GROUP/ADD_MEMBERS COPY GROUP/REMOVE_MEMBERS MODIFY GROUP/ADD_MEMBERS MODIFY GROUP/REMOVE_MEMBERS MODIFY SHARE/[NO]PERMISSIONS Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The GROUP commands assume that a user name without a domain name is in the domain currently being administered. The MODIFY SHARE command assumes that a user name without a domain name is in the domain of the server currently being managed. 5.5.7 /NOPASSWORD Qualifier with ADMINISTER Commands Defaults to Pre-expired Problem: When you specify the /NOPASSWORD qualifier with the ADD USER, COPY USER, or MODIFY USER command, the password is marked by default as initially expired. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). If you specify the /NOPASSWORD qualifier, the password is marked to never expire. (This is equivalent to specifying /FLAGS=DISPWDEXPIRATION.) However, you can override this default for /NOPASSWORD by specifying the /FLAGS=PWDEXPIRED qualifier. Note that specifying a password with the /PASSWORD qualifier marks the password as initially expired by default. 5-14 Problems Corrected in PATHWORKS V6.0A 5.5.8 PATHWORKS ADMINISTER Command Line Interface Does Not Allow Computer Names with Leading Backslashes Problem: The following commands should accept computer names with leading backslashes, but they do not: ADD COMPUTER REMOVE COMPUTER SHOW COMPUTER CLOSE SESSION SHOW SESSIONS SHOW CONNECTIONS SEND SHOW EVENTS/COMPUTER Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The software accepts leading back- slashes on computer names. 5.5.9 ADD TRUST Command Does Not Require Confirmation Problem: If a user enters Ctrl/Y to abort adding a trust after having entered the ADD TRUST command, complications can occur. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). A confirmation message is displayed when the user enters an ADD TRUST command. The message informs the user that the operation may take a long time and asks whether the user wants to continue. The /CONFIRM and /NOCONFIRM qualifiers have been added to the ADD TRUST command, allowing you to control the confirmation messages. Problems Corrected in PATHWORKS V6.0A 5-15 5.5.10 MODIFY SHARE Command Does Not Issue Confirmation Message Problem: In keeping with the way the Windows NT Server Manager works, a confirmation message should be issued when modifying a share to remove all permissions (that is, MODIFY SHARE/NOPERMISSIONS). Additionally, the user should be able to override the confirmation with a /NOCONFIRM qualifier. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). When all permissions are being removed (using the /NOPERMISSIONS qualifier without specifying keywords), the PATHWORKS Advanced Server issues a confirmation message to the user. The user can override the confirmation message using the /NOCONFIRM qualifier. 5.5.11 SET COMPUTER Command Does Not Allow You to Override Confirmation Problem: When issuing certain variants of the SET COMPUTER command, the user can be prompted for confirmation. However, the SET COMPUTER command lacks a /NOCONFIRM qualifier to give the user the option of overriding the confirmation message. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The command has been modified so that it checks for the /NOCONFIRM qualifier and issues confirmation requests appropriately. /CONFIRM is the default action. 5.6 File Access/Printing Problems This section describes file access and printing problems corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5-16 Problems Corrected in PATHWORKS V6.0A 5.6.1 Enumeration Slow on Shares with Many Subdirectories Problem: Directory share enumeration from Windows 95 and Windows NT Explorer is very slow on a share that has many subdirectories. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.2 Implicit Hostmapping Does Not Work for a Windows 95 Domain Logon Problem: On a computer with Windows 95 and configured for domain logon, if the domain logon account matches an OpenVMS account, file ownership is incorrect for files created in the Advanced Server share. The owner of the files becomes PWRK$DEFAULT. The owner should be the user. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.3 Print Jobs Submitted to PATHWORKS Advanced Server Printers Fail With a SPOOL32 Error Problem: Attempts to print to a PATHWORKS Advanced Server print share fail with a SPOOL32 error. The client receives the following error message: "There was an error writing to path, incorrect function." In this message, path is the UNC path for the printer. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0A 5-17 5.6.4 Cannot Open More Than Five Shares from Windows NT Browser List Problem: An attempt to open more than five share folders from a Windows NT browser list results in an error messsage received from the client: "Network name not found." Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.5 Unable to Access Some File Names That Have Greater Than 40 Characters Problem: The client is unable to access some file names that have greater than 40 characters. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.6 PATHWORKS Advanced Server Crashes When Disk Quota Is Set Too Low Problem: The PATHWORKS Advanced Server crashes if insufficient space exists for the server data files (Security Accounts Management database). If you attempt an operation that causes server data files to increase in size (for example, adding shares to the share database or users to the user database), beyond the amount of space available on the disk, the server crashes. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). If you perform an operation that causes the data files to grow beyond the amount of available disk space, the server logs an error ("Could not increase BLOB file size") and continues to operate. However, the operation that caused the data files to grow will fail. 5-18 Problems Corrected in PATHWORKS V6.0A 5.6.7 When Using the DOS Enhanced Redirector to Copy Files, the Modify Time Is Set Incorrectly Problem: If you are using the DOS enhanced redirector, and you copy a file from the PATHWORKS Advanced Server share, the "modify time" on the file may be set incorrectly. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.8 PATHWORKS Advanced Server Crashes with ACCVIO During Forced-Logoff Processing Problem: When performing forced-logoff processing, the PATHWORKS Advanced Server crashes. Forced logoff might occur when a user's account has access limited to certain hours during the day and the user is still logged on when the allowed time is about to expire. In this case, the server begins sending warning messages to the user's computer. When a user is in the process of being logged out, and the server attempts to send a warning message to the user's computer, certain fields identifying the user and computer may have already been cleared. When the server tries to authenticate these fields, an access violation error (ACCVIO) occurs. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.9 Moving Job in Print Queue Causes PATHWORKS Advanced Server to Crash Problem: Using a client computer to move a print job in a print queue causes PATHWORKS Advanced Server to crash with an access violation error (ACCVIO). Solution: Problems Corrected in PATHWORKS V6.0A 5-19 The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.10 External Authentication Fails after 444 Uses Problem: External authentication stops working after the authenti- cation mechanism has been used 444 times. Some time after the server startup, an attempt to log on to an account marked for external authentication results with a "user authorization failure" message. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.11 External Authentication Does Not Work When PWRK$ACME_DEFAULT_DOMAIN Is Defined Problem: If the logical PWRK$ACME_DEFAULT_DOMAIN has been defined to change the default domain, the logical does not work properly when a user specifies a user name without a domain name to log into an account that has external authentication enabled. The default domain (defined by the logical) should be used for authentication. However, the local domain is used instead. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.6.12 External Authentication Does Not Work When the Primary Domain Controller Is Not Running Problem: When trying to log into an OpenVMS account with external authentication, if the primary domain controler (PDC) is not running, authentication fails. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5-20 Problems Corrected in PATHWORKS V6.0A 5.6.13 Printing Fails When Copying a Large File from a Windows NT DOS Window to LPT1 Problem: From a DOS window on a Windows NT system, if you copy a file of more than 6500 bytes to LPT1, and LPT1 has been redirected to a PATHWORKS print share, as with the following command, the file will not print. NET USE LPT1: \\server-id\printshare-id An error message is issued, indicating that the process cannot access the file because another process has locked a portion of the file. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). The file is printed, and the erroneous error message is not generated. 5.6.14 Failures Printing from Clients Problem: Print jobs entered with parameters from client computers do not print. This generates an error message in the server event log but does not report an error directly to the client. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.7 Problems with PATHWORKS Advanced Servers in OpenVMS Clusters This section describes problems on servers that are OpenVMS cluster members, corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0A 5-21 5.7.1 NetLogon Fails to Start on Cluster Members Problem: If the PATHWORKS Advanced Server in an OpenVMS cluster has been configured to use WINS, and the WINS server database includes a static multi-homed entry for the PATHWORKS alias name, NetLogon times out and fails to start on the cluster. As a result, login validation and replication operations fail. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.8 Problems with PATHWORKS Advanced Servers Running PATHWORKS for OpenVMS (NetWare) This section describes problems that involve a PATHWORKS Advanced Server that is running PATHWORKS for OpenVMS (NetWare), corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.8.1 System Crash in PWRK$STREAMSHR Problem: When the PATHWORKS for OpenVMS (Advanced Server) and the PATHWORKS for OpenVMS (Netware) server are running at the same time, the system can crash in PWRK$STREAMSHR, which is caused by a timing error. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.9 Transport Problems This section describes problems that involve use of transport protocols, corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5-22 Problems Corrected in PATHWORKS V6.0A 5.9.1 PATHWORKS Advanced Server Fails to Detect and Discard Duplicate Name Responses Problem: The PATHWORKS Advanced Server sends a name query for a unique NetBIOS name, and if it gets two identical responses, it fails to detect (and discard) the second response as a duplicate. Instead, it erroneously sends a name-in-conflict message to the owner of that NetBIOS name. If the owner of the name is a Windows NT Server, that server then logs an event 4319 ("A duplicate name has been detected on the TCP/IP network"). Included in the event message is the TCP/IP address of the PATHWORKS server, the node that sent the Windows NT Server the name- in-conflict message. If the name involved is that of the primary domain controller (PDC), then the PDC becomes unreachable and replication to all backup domain controllers fails. To clear this condition, you must restart the PDC. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.9.2 KNB Resource Exhaustion Results in "Dead" Listener and ADMIN Commands Hang Problem: When PATHWORKS Advanced Server is configured to use the TCP/IP transport, and clients attempt to establish more sessions than the server is configured to allow, server resources are exhausted. The PATHWORKS Advanced Server stops accepting new session requests and local ADMINISTER commands fail. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0A 5-23 5.10 Browser Problems This section describes Browser service problems corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5.10.1 Browser Deadlock Hangs NetLogon Processing Problem: A deadlock in the Browser component stops the server from NetLogon processing. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.10.2 STOP SERVICE BROWSER Does Not Release Master Browser Problem: When you use the ADMINISTER command STOP SERVICE to stop the Browser service, the PATHWORKS Advanced Server ceases to be the Master Browser. However, the role of Master Browser does not move to another system. Solution: The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). 5.11 Windows NT Remove Management Problems This section describes problems managing the PATHWORKS Advanced Server from a Windows NT server, corrected in PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V6.0B for OpenVMS (Advanced Server). 5.11.1 Groups Display May Be Incomplete in Windows NT User Manager Problem: When using Windows NT User Manager for Domains on a Windows 95 client to add a new user account, if you click on the GROUPS button, the displayed list of groups for membership may be incomplete. Solution: 5-24 Problems Corrected in PATHWORKS V6.0A The problem is resolved in PATHWORKS V6.0A for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0A 5-25 6 ________________________________________________________________ Problems Corrected in PATHWORKS V6.0B The problems described in this chapter are corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). The problems are described in the sections listed in the following table: __________________________________________________________ Problem_Type____________________Section_Number____________ Installation and Configuration 6.1 Problems Server Problems 6.2 ADMINISTER Command Problems 6.3 File Access/Printing Problems 6.4 Event Logging Problems 6.5 Browser_Problems________________6.6_______________________ 6.1 Installation and Configuration Problems This section describes installation problems corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.1.1 PWRK$CONFIG.COM Procedure May Fail When Upgrading Accounts Database Files Problem: When running PWRK$CONFIG.COM, the procedure may fail when upgrading accounts (SAM) database files from a V6.0 server to a later version. This happens when the database includes group names exceeding 20 characters. Solution: Problems Corrected in PATHWORKS V6.0B 6-1 This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). The SAM database files are upgraded the first time you run PWRK$CONFIG.COM after installing the server. 6.2 Server Problems This section describes the file server problems corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.2.1 PWRK$LMMCP Process Hangs with "Not a Valid Pipe End" Errors Problem: The file server may stop responding, recording the following messages in the PWRK$LMMCP log file: IPCerr\MCPwork 1\Send.2313 167 is not a valid pipe end IPCerr\MCPwork 1\SendFd.1579 167 is not a valid pipe end Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.2.2 NetLogon Fails to Start If Domain Contains Many Computers Problem: The NetLogon process fails to start on the file server if the file server is in a domain that has more than 250 computer accounts (machine accounts) defined. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.2.3 Full Synchronization of Backup Domain Controller Occurs at NetLogon Startup Problem: In previous versions of the file server, when the file server was configured as a backup domain controller and the NetLogon service started, a full synchronization of the accounts database was performed. Solution: 6-2 Problems Corrected in PATHWORKS V6.0B This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). When the NetLogon service starts, a partial synchronization of the accounts database occurs if there have been changes to the accounts database while the backup domain controller was unavailable for synchronization. 6.2.4 PWRK$LMSRV Crashes Intermittently with ACCVIO Problem: PWRK$LMSRV crashes intermittently because of corruption of an open file cache or pointer map. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.2.5 PWRK$LMSRV Crashes with ACCVIO After Printer Error Problem: PWRK$LMSRV crashes intermittently after a printer error. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.2.6 PWRK$LMSRV Crashes with ACCVIO After "Illegal SMBCount" Message Problem: PWRK$LMSRV crashes intermittently after an "Illegal SMBCount" error message is logged. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0B 6-3 6.2.7 PWRK$ACME_STARTUP.COM Unconditionally Sets SYS$SINGLE_SIGNON Problem: Starting the file server unconditionally sets the value of the logical SYS$SINGLE_SIGNON to 1, even if the logical is already defined. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). If the SYS$SINGLE_SIGNON logical is already defined when the file server is started, the PWRK$ACME_STARTUP.COM command procedure will not redefine the logical. 6.2.8 PWRK$LMSRV Crashes with ACCVIO When Processing Large SMB Messages Problem: PWRK$LMSRV may fail with an ACCVIO when processing large Server Message Block (SMB) messages. The message logged is "GC-insane, SYSTEM-F-ABORT." Solution: This problem is resolved in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.3 ADMINISTER Command Problems This section describes ADMINISTER command problems corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.3.1 SHOW PRINT QUEUES Command Fails to Fully Enumerate Print Queues Problem: With the ADMINISTER SHOW PRINT QUEUES command, if one or more queues cannot be enumerated, an error message is displayed, but the command fails to enumerate (list) the other queues on the server. Solution: 6-4 Problems Corrected in PATHWORKS V6.0B This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.4 File Access/Printing Problems This section describes file access and printing problems corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.4.1 PWRK$LMSRV Crashes Problem: Prior versions of the PATHWORKS Advanced Server allowed a null pointer to be used when releasing the directory context from the directory cache. A null pointer causes the PATHWORKS Advanced Server to crash. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.4.2 File Server Allows Clients to Truncate Directory Files Problem: A client application can send an invalid request to the file server that results in a corrupted, zero-length directory file. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.4.3 Printer Spool Files Are Not Deleted Problem: Under certain conditions, such as when a print job does not complete successfully or when the print queue is purged, the printer spool files (PWRK$SPOOL_nnnn.DAT) should be deleted. However, they are not being deleted. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). However, the problem may continue in mixed version OpenVMS cluster environments where the queue manager is running on an OpenVMS system earlier than V7.2. Problems Corrected in PATHWORKS V6.0B 6-5 6.5 Event Logging Problems This section describes a problem related to event logging corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.5.1 Global Lock Warnings in Log File Problem: With servers in OpenVMS cluster environments, under conditions when access requests to cluster files are high in number, a large number of global lock warning messages may be logged in the PWRK$LMSRV_nodename.LOG file. Solution: This problem is corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). Logging of global lock warning messages, which are inconsequential, has been suppressed. 6.5.2 OpenVMS SET PASSWORD on an Externally Authenticated User Account Is Not Audited Problem: When you issue the OpenVMS SET PASSWORD command from an OpenVMS account that is enabled for external authen- tication, the Advanced Server processes the request. However, the password change event is not audited in the Advanced Server Security event log file as it should be when ACCOUNT_MANAGEMENT is enabled for auditing on the server. The event is not audited if the server from which you issue the SET PASSWORD command is also the primary domain controller for the domain that you specified when you originally logged in. The event is audited in all other cases, such as when the server from which you issue the SET PASSWORD command is a backup domain controller, or it is in a different (trusting) domain than the domain that you specified when you originally logged in. The password change activity is audited in the OpenVMS audit file if auditing for login events has been enabled. Solution: This problem is resolved in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6-6 Problems Corrected in PATHWORKS V6.0B 6.6 Browser Problems This section describes problems with the Browser service corrected in PATHWORKS V6.0B for OpenVMS (Advanced Server). 6.6.1 Cannot Browse Across a Wide Area network to a PATHWORKS Server Problem: Attempts to browse a wide area network to another domain fail when the primary domain controller of that domain is a PATHWORKS server. The PATHWORKS server does not respond to the requesting client. The client times out waiting for the response. Solution: This problem is resolved in PATHWORKS V6.0B for OpenVMS (Advanced Server). Problems Corrected in PATHWORKS V6.0B 6-7 7 ________________________________________________________________ Restrictions in PATHWORKS V6.0B This chapter describes restrictions in the PATHWORKS Advanced Server software. 7.1 Installation and Configuration Restrictions This section describes restrictions in the installation and configuration of the PATHWORKS Advanced Server software. 7.1.1 Configurator Allows Invalid Values for Maximum Concurrent Signons Problem: When you use the ADMIN/CONFIG command to specify a value for Maximum Concurrent Signons, you cannot set the value higher than 100, although the documented maximum is 999. If you specify a value greater than 100, the program logs an event message and resets the value to the default, which is 5. Solution: Do not specify a value greater than 100. 7.1.2 PWRK$CONFIG and PWRK$SETINI Command Procedures Fail After Domain Name Change Failure Problem: The command procedures PWRK$CONFIG.COM and PWRK$SETINI.COM may fail if there has been a previous failure in trying to change the domain name, and your server is going to be a backup domain controller (BDC) in the new domain. Restrictions in PATHWORKS V6.0B 7-1 To change your domain name, you must run either the PWRK$SETINI.COM or PWRK$CONFIG.COM command procedure. If the command procedure fails to communicate with the primary domain controller (PDC), then the next time you run either of the command procedures, it will fail. The command procedures fail while trying to verify the user accounts (SAM) database files. They fail because the name of the domain in PWRK$LANMAN.INI does not match the name of the SAM account database file. The name in LANMAN.INI will have the new domain name, and the name of the SAM accounts file will have the original name. Solution: If the PWRK$CONFIG.COM command procedure fails to communicate with the PDC, then after running either of the command procedures, delete all versions of the file pwrk$lmdatafiles:pwrk$upg_domains.dat. Next, make sure the domain name in PWRK$LANMAN.INI is the original name (the name that existed before you tried to change it). If it is not the original name, then edit the file, delete the new name, and replace it with the old name. Make sure you type it in uppercase. 7.1.3 PATHWORKS Advanced Server Cannot Coexist with PATHWORKS V5.0C for OpenVMS (LAN Manager) Server Problem: 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 PATHWORKS Advanced Server claims a group name that is used by both servers. Solution: 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). 7-2 Restrictions in PATHWORKS V6.0B 7.1.4 OpenVMS V7.1 Requires a Patch If the system is running OpenVMS V7.1, DEC C RTL patch ALPACRT02 (Alpha) or VAXCRTO2 (VAX), or higher versions of these patches, must be installed. Compaq also recommends that F11BXQP patch ALPF11X03 (Alpha) or VAXF11X02 (VAX), or higher versions of these patches, be installed. 7.1.5 Advanced Server Fails to Start If Any Processes Are Running the ADMININSTER Command Line Interface Problem: If you attempt to start the Advanced Server while a process is running the ADMINISTER command line interface, the startup may fail and a message similar to the following is displayed: %PWRK-F-INSGBLSECTS, system has only 53 free global sections -PWRK-I-REQGBLSECTS, PATHWORKS requires a minimum of 75 The system does not have enough free global sections to use PATHWORKS. Please see the Installation Guide on how to increase the number of global sections by modifying the SYSGEN parameter GBLSECTIONS. Solution: Have any process that is running the ADMINISTER command line interface exit from the program. To determine which processes are running the ADMINISTER command line interface, use the following commands: $ SHOW DEVICE/FILES SYS$SYSTEM: /OUT=TMP.TMP $ SEARCH TMP.TMP PWRK$MANAGER.EXE 7.1.6 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure Problem: On OpenVMS V7.1 systems, 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. This restriction does not apply to OpenVMS V7.2 systems. Solution: Restrictions in PATHWORKS V6.0B 7-3 Before running the PWRK$CONFIG procedure to move the PATHWORKS on-disk structure, either delete directories that are greater than eight levels deep, or rename them so that the standard OpenVMS BACKUP command invoked by PWRK$CONFIG can move them correctly. 7.2 File Server Restrictions This section describes restrictions in the file server. 7.2.1 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 the cache size may not need to be increased. Solution: The warning messages may be ignored if the percentage reported in the warning message does not exceed 100% and does not increase after the file server is running (that is, after server startup). Note that the solution applies only to "BlobCache Warning" messages. Do not ignore "BlobCache Error" messages. 7.2.2 Advanced Server Cannot Support More Than 32,767 Shares Problem: The server does not allow the 32,768th entry to be added. The maximum number of share definitions supported by the Advanced Server is 32,767. 7.2.3 OpenVMS File Names with a Dot at Position 40 Are Not Displayed Properly from the Client Problem: If a file created natively on an OpenVMS system has a dot at position 40 of its file name, the dot does not appear in the file name when viewed from a client. Solution: 7-4 Restrictions in PATHWORKS V6.0B If you want a file that is created on an OpenVMS system to be viewed correctly from the client, give the file a name that does not have a dot at position 40. When performing an operation from the client on an OpenVMS file that has a dot at position 40 of its name, treat the file as if it has no dot. When you view a file created on the client, a dot at position 40 in the file's name is displayed, and you can perform any other operations on that file as you normally would, including the dot in the file name. For a related problem that has been fixed, see Section 5.6.5. 7.2.4 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. 7.2.5 Premature Disk Full Conditions Problem: 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. Solution: To avoid these messages, make sure that at least 1 MB of free space is available on the device 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 the file server. Restrictions in PATHWORKS V6.0B 7-5 [ODS2] create_quantity = 1 extend_quantity = 1 7.2.6 File Server Does Not Enforce Disk Quotas by Default Problem: By default, the file server uses the EXQUOTA privilege, which means that quotas on OpenVMS system disk volumes are not enforced. Solution: 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 7.2.7 DECram Performance Problem Problem: DECram performance is inadequate when the disk is mounted using the /NOCACHE qualifier. Solution: Do not use the /NOCACHE qualifier when mounting a RAM disk that PATHWORKS Advanced Server will access. 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. 7.2.8 Access Denied to Files Restored from Backup of Another System Problem: 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 may cause the file server to deny access to users even though they have access to the parent directory. Solution: 7-6 Restrictions in PATHWORKS V6.0B To correct the problem, delete the ACLs on the files after they are restored, using the following DCL command: $ SET ACL/DELETE filename 7.2.9 Intruder Flag's Relationship to Computer Connections and Logons Problem: When a client 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. Solution: The file server also sets the intruder flag. This flag may be safely ignored; it does not affect any computer connections or logons. To delete the intrusion record, use the DELETE/INTRUSION_RECORD command. 7.2.10 XCCB Not in Use Errors in LMMCP Log File Problem: 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! Solution: You can ignore this error message. 7.3 User Interface Restrictions This section describes restrictions in the management interfaces. Restrictions in PATHWORKS V6.0B 7-7 7.3.1 SHOW FILES Command Fails to List Subdirectories Problem: When you use the ADMINISTER command SHOW FILES with the /SUBDIRECTORY qualifier, and there is a subdirectory name that is the same as a file name 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 subdirectory file specification. For example: $ ADMINISTER SHOW FILES \test\*.* /SUBDIRECTORIES 7.3.2 Server Description (SrvComment) Restriction Problem: The maximum length for the server description string is 256 characters. (You can define this string using the SET COMPUTER/DESCRIPTION command, or with the SrvComment keyword in the LANMAN.INI file.) If the server comment is set to a string of greater than 48 characters, the new server comment will not be fully displayed. The comment displayed will contain only the first 48 characters of the comment string. The remainder of the command string is truncated and is not displayed. 7.3.3 Alias Name Not in Browse List When Using DECnet Transport Only Problem: In an OpenVMS Cluster, the Advanced Server alias name is not seen by the browser if DECnet is the only transport configured. The ADMINISTER SHOW COMPUTER display shows the alias, but it marks it as unavailable. Although the alias is marked as unavailable, you can still connect to shares using the alias name. Solution: 7-8 Restrictions in PATHWORKS V6.0B Use the Configuration Manager (ADMINISTER/CONFIGURE command) to configure the Advanced Server to use either TCP/IP or NetBEUI in addition to DECnet. 7.3.4 Server Acting as a BDC Will Not Allow Changes to Share Permissions Until Synchronized with PDC Problem: If a new user or group is added to the domain, an attempt to set permissions on a share on the backup domain controller (BDC) or the primary domain controller (PDC) for the newly added user or group may result with an error message, such as: %PWRK-E-ERRMODSHAREPERM, error modifying permissions for share "QUIP" -LM-E-NOTALLMAPPED, one or more user or group names were not found Solution: Synchronize the BDC with the PDC before adding permissions for the new user or group. 7.3.5 Directory File (Folder) Name Length Restrictions Problem: The length of a directory file (or folder) name is limited to 39 characters. The length is further restricted if the name includes dots, spaces, or other characters that cannot be represented in OpenVMS file names. In general, each instance of these characters reduces the maximum length by four characters. Regular file names (nonfolder names) can have up to 77 characters in the client file name, unless the name includes dots, spaces, or other non-OpenVMS characters. Solution: Limit the length of directory and file names accordingly, or upgrade the file server to Advanced Server for OpenVMS and use the extended file naming capabilities of ODS-5 devices. Restrictions in PATHWORKS V6.0B 7-9 7.3.6 Mouse Selection Highlights Entire Screen Problem: Under certain circumstances, when you use a character-cell user interface, such as ADMIN/LICENSE, the entire screen is highlighted when you select a button using the mouse input device. Solution: When this occurs, press the Ctrl/W key sequence to clear the screen, then select the button again. 7.3.7 When a User Account Is Created Without a Password, an Encrypted Password is Supplied Problem: If you use the ADMINISTER command COPY USER to create a new user account, and you omit the /PASSWORD qualifier, the new user account is created with an encrypted password. Solution: Use the MODIFY USER command to set the password for the new user account. 7.3.8 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 command, 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 line will fail with an "insufficient privileges" error message. $ ADMIN SAVE EVENT SYS$LOGIN:EVT_BACKUP.EVT The source of the problem is not the privilege level of the user; rather, it is the use of the SYS$LOGIN job logical. You cannot use job logicals in file specifications in the ADMINISTER command line. 7-10 Restrictions in PATHWORKS V6.0B 7.4 Printing/Print Management Restrictions This section describes restrictions in printing or managing print queues. 7.4.1 Client Cannot Purge Print Queues Problem: Client platforms, such as Windows NT and Windows 95, include a function to purge the print queue of print jobs in their print manager. This function fails to purge the print jobs in the queue on an Advanced Server file server. If a client user logged on with sufficient privileges to purge the print queue (full or manage documents privilege) attempts to purge the print queue, an error message is returned indicating insufficient privileges to perform the operation. Solution: The client user can remove the jobs from the queue by selecting with the mouse all of the jobs in the queue and then using the delete key. 7.4.2 Windows NT Print Manager Fails to Display PATHWORKS Advanced Server Printers Problem: When you attempt to display the printers on the PATHWORKS Advanced Server from the Windows NT server administration Print Manager, using the Server Viewer, you will not see the printers offered by the PATHWORKS Advanced Server. Solution: Display the list of printers using the PATHWORKS ADMINISTER command SHOW PRINT QUEUE. 7.4.3 Cannot See Print Job Name from Client Problem: Client computers do not display print job names. Print jobs submitted from client computers are not displayed from the Print Manager with the print job name. Solution: Restrictions in PATHWORKS V6.0B 7-11 This is a restriction of PATHWORKS Advanced Server. 7.4.4 Cannot Move Print Job Postion In Queue from Client Problem: If the user of a client computer attempts to use the Print Manager to move a print job to a different position in the print queue, the operation fails. Solution: Use the ADMINISTER command SET PRINT JOB to move the print job within the print queue. 7.4.5 ADMINISTER REMOVE PRINT QUEUE Fails to Delete a Routing Print Queue Problem: If you attempt to delete a PATHWORKS Advanced Server print queue using the ADMINISTER command REMOVE PRINT QUEUE, the command fails with the following error message: %PWRK-E-QUEGENERR, error removing print queue "queue-name" at server "\server-vname" %PWRK-I-QUENOTPW, This queue may not have been created by PATHWORKS The second message is misleading: the print queue may have been created using the PATHWORKS Advanced Server. The routing queue is not deleted if it has been defined to print to a printer queue that is set up to print to a virtual port (such as an LTA device). Solution: Use the OpenVMS DCL command DELETE/QUEUE to delete the print queue. 7.5 Event Logging Restrictions This section describes restrictions in the event logging and auditing functions of the PATHWORKS Advanced Server. 7-12 Restrictions in PATHWORKS V6.0B 7.5.1 Event in Browser Function not Reported Properly Problem: When the Browser stops, the ADMINISTER SHOW EVENTS command does not display the event. The Windows NT Event Viewer reports the event but does not identify the Browser but instead the node name. For example: 6108 The BAGELS service has stopped. BAGELS is the node name. Instead, the event source (Browser) should be identified. Solution: The event source improperly identified by the 6108 event message should be the Browser. 7.5.2 Certain Event Code Descriptions Do Not Appear in ADMINISTER SHOW EVENTS Display Problem: After the server parameter MORELOG in the [BROWSER] section of the LANMAN.INI file is set to YES, descriptions are not provided for several event types in the ADMINISTER SHOW EVENTS display. Instead, the following message is displayed: I xxxx - The description for Event ID (xxxx) in Source (BROWSER) could not be found The message displays the Event ID number for the event (xxxx). Solution: Use the Windows NT Event Viewer to display the event log. 7.5.3 Event Log Files Fail to Overwrite When Full Problem: 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. Solution: Restrictions in PATHWORKS V6.0B 7-13 You must manually clear the event log file by using the ADMINISTER CLEAR EVENTS command. 7.5.4 Unable to Set the Event Logging Setting Problem: When you use Windows NT server administration tools to alter the event logging setting, and you choose the option "Do Not Overwrite Events (Clear Log Manually)," the server incorrectly reflects the setting as "overwrite events older than 365 days." 7.5.5 Displaying Application Event Log Files Fails to Display Event Data Problem: The ADMINISTER command SHOW EVENTS/FULL displays details about events. Both the ADMINISTER command and the NT Event Viewer give you the description of the event (the text associated with an event ID). There is also optional data included with some events that helps with troubleshooting problems. This information is not available from the ADMINISTER command. Solution: If you require this missing information, use the NT Event Viewer to display it. If this tool is not available, use the following ELFREAD command when the server is not running. (The ELFREAD utility is for reading the event log file when the Advanced Server is not running.) $ ELFREAD -D logtype where logtype is either SYSTEM, SECURITY, or APPLICATION. 7.6 Domain Management Problems This section describes restrictions in managing domains and servers in domains. 7-14 Restrictions in PATHWORKS V6.0B 7.6.1 Changes to Trust Relationship on One Cluster Node Are Unknown to the Other Cluster Nodes Until NetLogon Restart Problem: If a trust relationship is added or deleted on a cluster node, it will not be known to the other cluster nodes until after they restart NetLogon. Solution: After adding or removing a trust relationship to a cluster node, restart the NetLogon service clusterwide by issuing the following commands on any one cluster member running PATHWORKS: $ ADMINISTER STOP SERVICE NETLOGON $ ADMINISTER START SERVICE NETLOGON 7.6.2 Error When Displaying Advanced Server Domains from a Windows NT Server Manager Problem: When using the Windows NT Server Manager to display information about an Advanced Server, the following error message may be displayed: The data is invalid Solution: This error message indicates that an Advanced Server does not support replication. 7.6.3 A BDC Cannot Be Removed from the Domain If It Has Been Promoted to Be a PDC in Another Domain Problem: If you reconfigure a backup domain controller (BDC) from one domain to become a primary domain controller (PDC) of another domain, you cannot remove the computer name from the original domain. Solution: Delete the computer name in the original domain database during scheduled downtime of the new PDC. Restrictions in PATHWORKS V6.0B 7-15 7.7 Browser Restrictions This section describes restrictions related to the Browser service. 7.7.1 Browser State Is Not Distributed on an OpenVMS Cluster Problem: Performing an ADMIN STOP SERVICE BROWSER command on one node in an OpenVMS cluster should stop browsers on all nodes of a cluster. However, it only stops the browser service on the node where the command was issued. Solution: To stop the browser service on a cluster, issue the STOP SERVICE BROWSER command on each node on a cluster. 7.8 Transport Restrictions This section describes restrictions related to the use of transports with the PATHWORKS Advanced Server. 7.8.1 System Error Is Reported If NetBEUI Is Not Configured Problem: When you configure the Advanced Server without the NetBEUI transport, an error is logged in the PWRK$MONITOR log file, such as the following: 4-AUG-1998 14:50:11.67 00000169:00249CF0 Message Text: t_errno from t_bind for : system error 4-AUG-1998 14:50:11.67 00000169:00249CF0 Status Code: 8 4-AUG-1998 14:50:11.67 00000169:00249CF0 In module , in function 4-AUG-1998 14:50:11.67 00000169:00249CF0 Message Text: No clients will be connected over 4-AUG-1998 14:50:11.67 00000169:00249CF0 Status Code: 1 Solution: These messages do not indicate a real error and can be ignored. 7-16 Restrictions in PATHWORKS V6.0B 7.8.2 DEFZA FDDI Controller Is Not Supported with PATHWORKS Advanced Server Problem: The DEFZA FDDI controller is not supported with PATHWORKS Advanced Server. Solution: Use the newer DEFTA controller, which is supported and provides better performance. 7.8.3 NetBIOS Fails to Start, Dumps Invalid Media Address Problem: If an Advanced Server on a DECnet-Plus system does not have a Phase IV address set up for the circuit to be used by the NetBIOS process, the NetBIOS process fails to start. The NetBIOS log file will include the following error message: %NB-F-SIGFAIL, Startup - error initializing ethernet controller -SYSTEM-F-IVADDR, invalid media address Solution: When the Advanced Server is running on a system that is running DECnet-Plus, a DECnet Phase IV address must be set, and it must be enabled on the routing circuit of the device that the NetBIOS process will use. For example, if the Advanced Server is running on a system with DECnet-Plus and is going to use the FDDI device FWA0: (define a system logical name NETBIOS$DEVICE), then in the NCL script SYS$STARTUP:NET$ROUTING_STARTUP.NCL, include the following: SET NODE 0 ROUTING PHASEIV ADDRESS = 13.1012 SET NODE 0 ROUTING PHASEIV PREFIX = 49:: SET NODE 0 ROUTING CIRCUIT FDDI-0 ENABLE PHASEIV ADDRESS = TRUE SET NODE 0 ROUTING CIRCUIT CSMACD-0 ENABLE PHASEIV ADDRESS = FALSE Restrictions in PATHWORKS V6.0B 7-17 7.8.4 Communication Device Names Must Not Begin with an Underscore Problem: The names of devices defined by use of the logical names PWRK$NBDAEMON_DEVICE, PWRK$KNBDAEMON_DEVICE, and NETBIOS_ DEVICE must not start with an underscore (_); otherwise, the PWRK$KNBDAEMON will not start, and other processes will start, but they will not operate properly. For more information about defining communications devices, see the PATHWORKS for OpenVMS Server Installation and Configuration Guide. Solution: When you use any of these logical names to define a network device, do not begin the device name with an underscore. 7.9 PATHWORKS Advanced Server in an OpenVMS Cluster Restrictions This section describes restrictions involving PATHWORKS Advanced Server participating in OpenVMS cluster environments. 7.9.1 SRVHIDDEN Parameter Causes Browser to Fail to Announce Itself Problem: OpenVMS cluster configurations that are upgraded from PATHWORKS V5 for OpenVMS (LAN Manager) may exhibit the following behavior. Under PATHWORKS V5 for OpenVMS (LAN Manager), it is possible to set server configuration parameters in a way that presents the PATHWORKS cluster alias to the clients, but not the names of the individual nodes in the cluster. The configuration settings can be included in the LANMAN.INI file: o In the [SERVER] section: srvhidden=yes o In the [VMSSERVER] section: pwrkaliashidden=no 7-18 Restrictions in PATHWORKS V6.0B These settings do not function the same way under PATHWORKS Advanced Server. The Browser service included with PATHWORKS Advanced Server interprets the srvhidden parameter setting and fails to announce the availability of the browser on the network. Compaq recommends making sure that the srvhidden parameter is not set to "yes" when you start the PATHWORKS Advanced Server. 7.9.2 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, and SYLOGIN.COM encounters errors, PATHWORKS Advanced Server startup hangs. When this problem occurs, process startup either fails to generate log file messages or fails to complete. 7.9.3 PATHWORKS Alias Cannot Be Used Across Subnets Problem: Two PATHWORKS Advanced Servers in the same OpenVMS cluster cannot share the same PATHWORKS alias across two different TCP/IP subnets. Solution: Use a different PATHWORKS alias for each server. 7.10 PATHWORKS Advanced Server Interaction with DEC Rdb (Oracle) Restrictions This section describes a restriction in PATHWORKS Advanced Server interaction with DEC Rdb (Oracle). 7.10.1 PATHWORKS Advanced Server Fails to Start Correctly on Systems Running DEC Rdb Problem: PATHWORKS Advanced Server fails to start correctly on systems that are also configured to run DEC Rdb (Relational Database) software, because of the way that Rdb uses the system-wide login command procedure Restrictions in PATHWORKS V6.0B 7-19 SYLOGIN.COM and the way that PATHWORKS Advanced Server creates processes. Solution: To correct this problem: 1. Remove the following line in the system login procedure SYLOGIN.COM: $ @DECRDB$SETVER.COM 2. Replace it with the following lines: $ SET NOON $ @DECRDB$SETVER.COM $ SET ON 7-20 Restrictions in PATHWORKS V6.0B