DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager),_ECO1________________________________ Server Release Notes These Release Notes supplement the product documentation. Always read the release notes before you install the software January 1998 Revision/Update Information: This document supersedes the DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) Release Notes. Operating System: DIGITAL OpenVMS VAX, Versions 5.5-2, 6.1, 6.2, 7.0, and 7.1; DIGITAL OpenVMS Alpha, Versions 6.1, 6.2, 7.0, and 7.1 Software Version: DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Printing, January 1998 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1998. All rights reserved. The following are trademarks of Digital Equipment Corporation: Alpha AXP, DEClaser, DECnet, Digital, LA50, LN03, LN03 PLUS, MicroVAX, OpenVMS, PATHWORKS, VAX, VAXserver, VAXstation, VMS, and the DIGITAL logo. The following are third-party trademarks: Windows is a trademark and Microsoft and MS are registered trademarks of Microsoft Corporation. Macintosh, is a registered trademark of Apple Computer, Inc. OS/2 is a registered trademark of International Business Machines Corporation. PostScript is a registered trademark of Adobe Systems, Inc. Proteon is a trademark of Proteon Associates, Inc. TCPware is a trademark of Process Software. PATHWAY is a trademark of WOLLONGONG. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. xii 1 Distribution Kit 2 Features of DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 2.1 XQP+......................................... 2-1 2.2 Optional DECprint Supervisor (DCPS) Available.................................... 2-2 2.3 PATHWORKS Monitor Utility.................... 2-3 2.4 New Features in Version 5.0F................. 2-3 2.4.1 Client Access License Support............ 2-3 3 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.1 System and Network Configuration Guidelines................................... 3-1 3.1.1 Running in an OpenVMS Cluster............ 3-1 3.1.2 Running in a Windows NT Domain........... 3-2 3.1.2.1 Interoperating in a Windows NT Domain................................. 3-2 3.1.2.2 Managing OpenVMS Print Shares from a Windows NT Server...................... 3-3 3.1.2.3 Letting LAN Manager V2.x Server Users Browse Windows NT Servers.............. 3-3 iii 3.1.3 Defining Communications Devices.......... 3-3 3.1.3.1 Processes Fail When Devices Are Not Defined................................ 3-4 3.1.3.2 DECnet NETBIOS Initializes on New FDDI Controllers............................ 3-5 3.1.4 PATHWORKS Transports..................... 3-6 3.1.4.1 PATHWORKS for OpenVMS TCP/IP Support... 3-6 3.1.4.2 UCX and PATHWORKS Interaction.......... 3-7 3.1.4.3 PATHWORKS V5 with DECnet-Plus.......... 3-7 3.2 Installing, Configuring, and Starting the Server....................................... 3-8 3.2.1 PWRK$CONFIG Configuration Command Procedure................................ 3-8 3.2.2 Upgrading from PATHWORKS for VMS V4.x to PATHWORKS V5 for OpenVMS................. 3-8 3.2.2.1 Differences Between V4.x and V5.x...... 3-8 3.2.2.2 Changes to the Security Model.......... 3-10 3.2.2.3 Features No Longer Available........... 3-10 3.3 Formatting OpenVMS Files..................... 3-11 3.4 License Server and License Management........ 3-16 3.4.1 Running the License Server............... 3-16 3.4.2 License Server Startup and Shutdown...... 3-17 3.4.2.1 Integrated License Server Startup...... 3-18 3.4.2.2 Integrated License Server Shutdown..... 3-19 3.4.2.3 Joint LAN Manager and NetWare Startup................................ 3-19 3.4.2.4 Joint LAN Manager and NetWare Shutdown............................... 3-19 3.4.2.5 Standalone License Server Startup and Shutdown............................... 3-20 3.4.3 Upgrading License Server State Files..... 3-20 3.4.3.1 Upgrading License Server State Files on a Node Not Previously Configured to Run the License Server..................... 3-21 3.5 Using LAN Manager Server Net Commands........ 3-22 3.5.1 Autoshare List Updating.................. 3-23 3.5.2 Using the Net Share Command to Create Personal Shares.......................... 3-23 3.5.3 Use Quotations Marks to Include Exclamation Mark......................... 3-23 3.5.4 Use Quotation Marks to Delineate Command Options That Contain Spaces.............. 3-24 3.6 Changing LAN Manager Passwords............... 3-24 iv 3.6.1 OpenVMS-Generated Passwords.............. 3-25 3.6.2 Length of OpenVMS-Generated Passwords.... 3-26 3.6.3 OpenVMS Password Synchronization......... 3-27 3.6.4 Password History and Dictionary Checking................................. 3-29 3.7 OpenVMS External Authentication Support...... 3-29 3.7.1 Enabling External Authentication......... 3-30 3.7.1.1 Enabling External Authorization for OpenVMS Systems........................ 3-31 3.7.1.2 Enabling External Authentication for a User................................... 3-31 3.7.1.3 Establishing the User Host Mapping..... 3-32 3.7.1.4 Synchronizing Passwords................ 3-32 3.7.1.5 External Authentication Over a Network................................ 3-33 3.8 OpenVMS Operating System Delta Time Restriction.................................. 3-34 3.9 Support for Large FAT Container Files........ 3-35 3.10 Implementing a Wide Area Domain Using TCP/IP....................................... 3-37 3.10.1 Planning and Setup....................... 3-37 3.10.2 LMHOSTS Directory and Syntax............. 3-38 3.10.3 Managing the LMHOSTS File................ 3-39 3.10.3.1 LMHOSTS Log File....................... 3-39 3.11 Time Zone Setup Required for OpenVMS V7.0.... 3-40 3.12 OpenVMS V7.1 Requires Patch.................. 3-40 4 Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) 4.1 NETBIOS Names Cannot Be Resolved Over DECnet When the Controller is FDDI.................. 4-1 4.2 Session Context Switch Problem Caused by Windows NT V4.0 SP2.......................... 4-1 4.3 Server Fails with an Access Violation While Displaying Sessions.......................... 4-2 4.4 Server Loops on Session Delete............... 4-2 4.5 Server Buffers Exhausted..................... 4-2 4.6 OpenVMS Cluster Netlogons Fail............... 4-3 v 5 Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 5.1 Error in Flow Control........................ 5-1 5.2 LAN Manager Server Crash in ODS2Fidcache..... 5-1 5.3 Server Crash in PFS_setextattr When Called From Copyfile................................ 5-1 5.4 Time Zone Replication Problem................ 5-2 5.5 Invalid Time Conversion in calloutadd........ 5-2 5.6 ADMIN/PATH Hangs............................. 5-2 5.7 Replication Stops Due to Windows NT Bug...... 5-3 5.8 Panic in GC.C................................ 5-3 5.9 DIGITAL PATHWORKS V5 for OpenVMS (LAN Manager) Should Not Assign CU Licenses for V4.1 Clients................................. 5-3 5.10 License Server t_accept/t_listen Errors...... 5-3 5.11 Use of Logical LICENSE_SERVER_INHIBIT Has Been Changed................................. 5-4 6 Restrictions and Limitations 6.1 System and Network Configuration Restrictions................................. 6-1 6.1.1 OpenVMS Cluster Restrictions............. 6-1 6.1.1.1 Changing the PATHWORKS Cluster Alias Prevents Net Logons.................... 6-1 6.1.2 Windows NT Interoperability Restrictions............................. 6-2 6.1.2.1 Server Manager Does Not Recognize OpenVMS Path Names..................... 6-2 6.1.2.2 Print Manager Option Does Not Work..... 6-2 6.1.2.3 PATHWORKS Windows NT V4.1B Client Fails to Get License Over DECnet............. 6-2 6.1.3 OS/2 Access and Connections Restrictions............................. 6-3 6.1.3.1 OS/2 Version 2.1 Application Files Cannot Be Copied to FAT Volume......... 6-3 6.1.4 PATHWORKS for VMS (Macintosh) Restrictions............................. 6-4 6.1.4.1 Interacting with PATHWORKS for VMS (Macintosh) V1.2....................... 6-4 6.1.4.2 Installing Macintosh Server Redefines ADMIN Command.......................... 6-4 vi 6.1.4.3 Shares Common Between Macintosh Server and LAN Manager Server................. 6-4 6.1.5 Windows for Workgroups Interoperability Restrictions............................. 6-5 6.1.5.1 PATHWORKS LAN Manager Server Domains are Invisible to Windows for Workgroups File Manager Browser................... 6-5 6.1.6 Transports Restrictions.................. 6-5 6.1.6.1 DEFZA FDDI Controller Is Not Supported in PATHWORKS for OpenVMS............... 6-5 6.1.6.2 LAN Manager Server Does Not Support the Ordering of Network Transports......... 6-6 6.1.6.3 Mail Server Works with DECnet Only..... 6-6 6.1.6.4 Problem Getting License After Client Changes Transport Protocol............. 6-6 6.1.6.5 Clients Disconnect When Using DECnet-Plus Versions 5.6 Prior to ECO10.................................. 6-7 6.1.7 Configuration Failures and Performance Problems Due to Physical Memory Shortage................................. 6-7 6.2 Installation, Configuration, and Startup Restrictions................................. 6-7 6.2.1 DEINSTALL Procedure is Broken............ 6-7 6.2.2 Configuration Utility (ADMIN/CONFIG) Restrictions............................. 6-8 6.2.2.1 ADMIN/CONFIG May Provide an Inappropriate Default for the Open File Limit.................................. 6-8 6.2.2.2 ADMIN/CONFIG Appears to Set Parameters, But Does Not........................... 6-8 6.2.2.3 ADMIN/CONFIG Allocates Insufficient Resources to Support Any Clients....... 6-9 6.2.3 Configuration Command Procedure Restrictions............................. 6-9 6.2.3.1 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure...................... 6-10 6.2.3.2 Extraneous Warning Messages During PWRK$CONFIG.COM........................ 6-10 vii 6.2.4 Upgrade Utility Restrictions............. 6-10 6.2.4.1 Upgrade Fails to Upgrade an Environment with More than 252 Groups.............. 6-10 6.2.4.2 The Upgrade Utility Parses Special Characters Incorrectly in Report Files.................................. 6-11 6.2.4.3 Upgrade Procedure May Fail Over DECnet with PCSA V4.2 Running................. 6-12 6.2.5 Server Startup Restrictions.............. 6-12 6.2.5.1 Server Startup Slowed Down if DFS Devices are in Mount Verification...... 6-12 6.2.5.2 Server Fails to Start on Non-English Language Versions of OpenVMS........... 6-12 6.3 Server Management Interface Restrictions..... 6-13 6.3.1 Server Admin Interface (ADMIN/PATHWORKS) Restrictions............................. 6-13 6.3.1.1 ADMIN/PATH Cannot Delete FAT Container File Using FAT Volume Screen........... 6-13 6.3.1.2 ADMIN/PATH Defining a Share - Information Not Set.................... 6-13 6.3.1.3 ADMIN/PATHWORKS Does Not Support Mapping a Print Queue to Multiple Destinations........................... 6-14 6.3.1.4 ADMIN/PATH Fails to Set RMS Protections on Top-Level Directory................. 6-14 6.3.1.5 ADMIN/PATH Password Last Changed Field Changes When Displaying a User......... 6-14 6.3.1.6 ADMIN/PATH View => Users Options May Display Incomplete List of Users....... 6-15 6.3.1.7 ADMIN/PATH Add User Does Not Add Access Permissions to Personal Share.......... 6-15 6.3.1.8 ADMIN/PATH Cannot Attach to Another Server After Logging on to a Standalone Server................................. 6-15 6.3.1.9 ADMIN/PATH Leaves Extraneous File in SYS$LOGIN.............................. 6-16 6.3.1.10 Starting Netlogon Service Does Not Accept Options......................... 6-16 6.3.1.11 Ctrl/Z in Help Does Not Exit to the Menu................................... 6-16 6.3.1.12 ADMIN/PATH Config => Control services Buttons Unavailable.................... 6-17 6.3.1.13 ADMIN/PATH Message Boxes Skewed........ 6-17 viii 6.3.1.14 ADMIN/PATH Utilities => FAT Volume Dialog Box is Confusing................ 6-18 6.3.1.15 UAS Device Information Changed in Host Account Box............................ 6-18 6.3.1.16 Netlogon Does Not Start After PATHWORKS Cluster Alias Change................... 6-19 6.3.1.17 ADMIN/PATHWORKS Cannot Create a Queue or Destination with the System Name or Process Logical........................ 6-19 6.3.1.18 ADMIN/PATH Does Not Recognize Long File Names.................................. 6-20 6.3.1.19 Using Long File Names for FAT Files.... 6-20 6.3.2 Command Line Net Interface Restrictions............................. 6-20 6.3.2.1 Cannot Use Path Names to Reference Shares................................. 6-20 6.3.2.2 NET ACCESS Does Not Recognize the Volume Label as a Device Name.......... 6-20 6.3.2.3 NET PRINT Does Not Clean Up Files in the Spool Directory.................... 6-21 6.3.2.4 NET SHARE printshare /DELETE May Fail................................... 6-21 6.3.2.5 NET SHARE printshare /PRINT Does Not Create Queue from Client............... 6-21 6.3.2.6 NET SHARE - Displaying Data Greater than 64 Kbytes......................... 6-22 6.3.2.7 NET STOP Cannot Stop the Remote Boot Service................................ 6-22 6.3.2.8 NET WHO Displays Incomplete Results.... 6-22 6.3.2.9 Error Message Not Informative.......... 6-23 6.4 Services Restrictions........................ 6-23 6.4.1 Remote Boot Restrictions................. 6-23 6.4.1.1 Circuit Services Enabled............... 6-23 6.4.1.2 Server Cannot Remote Boot Token Ring Clients................................ 6-25 6.4.1.3 Subdirectories of the RPL and RPLFILES Shares Fail to be Backed Up............ 6-25 6.4.2 ADMIN/ANALYZE Utility Restrictions....... 6-26 6.4.2.1 Help is Not Available for the PATHWORKS Event Logger (ADMIN/ANALYZE)........... 6-26 ix 6.4.3 Creating Logon Scripts Restrictions...... 6-26 6.4.3.1 RMS Protection on Specific Logon Scripts................................ 6-26 6.4.3.2 Permissions Not Set For Logon Directories............................ 6-26 6.4.3.3 Directories Created in PWRK$ROOT:[LANMAN.ACCOUNTS.USERDIRS] Use Host Mode Security................. 6-27 6.4.4 Auditing Restrictions.................... 6-27 6.4.4.1 BADUSE Auditing Event Reports Uninformative Errors................... 6-27 6.4.5 LAN Manager GUEST Account Restrictions... 6-27 6.4.5.1 Logged in as GUEST to a Server Running LAN Manager & OpenVMS Security......... 6-27 6.4.5.2 LAN Manager GUEST Account Can Cause Domain Services to Fail................ 6-28 6.4.5.3 Backward Compatibility in Effect after Domain Role Is Changed................. 6-29 6.4.6 Disk Services Restrictions............... 6-29 6.4.6.1 Deadlock Messages Logged when Shared Infoserver Volume Goes Offline......... 6-29 6.4.6.2 Premature Disk Full Conditions......... 6-29 6.4.6.3 Server Does Not Enforce Disk Quotas by Default................................ 6-30 6.4.6.4 DECram Performance Problem............. 6-30 6.4.6.5 Unable to Delete FAT Container File When Using Device Logicals............. 6-31 6.4.6.6 Interoperating with a Shadow Set....... 6-31 6.4.6.7 Interoperating with a Volume Set....... 6-32 6.4.6.8 Interoperating with a Stripe Set....... 6-32 6.4.6.9 Access Denied to Files Restored From Backup of Another System............... 6-33 6.4.6.10 Using Long Volume Label for AutoShare Devices................................ 6-33 6.4.7 Licensing Subsystem Restrictions......... 6-33 6.4.7.1 Running More Than One License Server... 6-33 6.4.7.2 License Manager Server Node Name....... 6-34 6.4.7.3 License Manager User Interface Changes Video Settings......................... 6-35 6.4.7.4 License Server Not Running Using the License Manager in an OpenVMS Cluster................................ 6-35 6.5 DECinspect Restrictions...................... 6-35 x 6.5.1 Default PATHWORKS User Accounts Deleted by DECinspect Lockdown Procedure......... 6-35 6.6 Client Access and Connnections Restrictions................................. 6-36 6.6.1 Supporting Multiple Sessions from the Same Client.............................. 6-36 6.6.2 Clients May Fail to Perform a Domain Logon.................................... 6-36 6.6.3 Intruder Flag's Relationship to PC Connections and Logons................... 6-37 6.6.4 Client Net Admin Fails to Handle the Devices Returned from a LAN Manager Server................................... 6-37 6.6.5 Unable to Connect More Than 2048 Clients to the Same Server....................... 6-38 6.6.6 User Path Specified in LANMAN.INI........ 6-38 6.7 PATHWORKS for OpenVMS Interaction with Oracle Rdb.......................................... 6-38 6.8 Log Files and Messages Restrictions.......... 6-39 6.8.1 XCCB Not in use Errors in LMMCP Log File..................................... 6-39 6.9 Monitor Utility Restrictions................. 6-39 6.9.1 Unable to Run Both CMT Data Cache Monitor and Performance Degradation on the Same Client Over NetBEUI...................... 6-39 7 Unsupported Software 7.1 PCSA MANAGER Clone........................... 7-1 7.2 The PWRK$DEFINE_COMMANDS Command Procedure... 7-5 7.3 Displaying Permissions....................... 7-7 7.4 The NET ACCESS Command....................... 7-7 7.5 LANMAN.INI Parameters........................ 7-7 Tables 3-1 Undefined Device Messages................ 3-4 3-2 DECnet-Plus with OpenVMS VAX............. 3-7 3-3 DECnet-Plus with OpenVMS Alpha........... 3-8 3-4 LANMAN.INI Keywords for Password Control.................................. 3-25 xi 3-5 OpenVMS Operating System Versions and ECO Kit Names................................ 3-34 7-1 Qualifiers and Parameters Not Supported in V5.................................... 7-4 xii ________________________________________________________________ Preface Purpose These release notes describe the features included in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1. It describes problems that have been corrected, and known limitations. This document serves as a complement to the PATHWORKS for OpenVMS product documentation set. This version of the software includes changes for DIGITAL PATHWORKS V5 for OpenVMS (LAN Manager) and all subsequent releases. Audience These release notes are intended for PATHWORKS for OpenVMS system administrators. It assumes you have: o A basic understanding of a PC LAN network o A basic understanding of OpenVMS system management o Access to PATHWORKS V5 software and documentation xii Related Documents The following manuals are referenced in these release notes. __________________________________________________________ Reference_______________________Topic_____________________ PATHWORKS for OpenVMS Describes the installation Installation and Upgrade and configuration of: o PATHWORKS for OpenVMS (LAN Manager) o PATHWORKS for OpenVMS (NetWare) o PATHWORKS for OpenVMS standalone license server This manual also describes: o The procedure for upgrading from PATHWORKS for VMS V4.x to PATHWORKS V5 for OpenVMS. o The XQP+ software, which is included with PATHWORKS for OpenVMS PATHWORKS V5 for OpenVMS Provides conceptual (LAN Manager) Server information that system Administrator's Guide administrators require to effectively set up and manage networks running PATHWORKS V5 for OpenVMS software. PATHWORKS V5 for OpenVMS Describes the Command Line (LAN Manager) Server Net Interface. Administrator's Command Reference xiii __________________________________________________________ Reference_______________________Topic_____________________ OpenVMS System Manager's Describes how to set up Manual and manage an OpenVMS operating system. PATHWORKS for DOS and Windows Lists and describes Commands Reference PATHWORKS client commands and utilities. Guide to Managing PATHWORKS How to set up and manage Licenses PATHWORKS licenses from the server PATHWORKS for OpenVMS Server How to upgrade your Migration Guide OpenVMS server from PATHWORKS for VMS V4.x to PATHWORKS V5 for OpenVMS. Also shows how to plan and set up the LAN Manager environment for your clients and servers. DECprint Supervisor for Describes the newest OpenVMS Features capabilities in the OpenVMS PostScript printer queuing and job management ________________________________software._________________ Terminology_____________________________________________________ Term__________________Interpretation______________________ personal computer standalone systems PC PC workstation client PC connected to the network using PATHWORKS software, which can access resources on a server server system that offers services to a client PATHWORKS PATHWORKS software xiv __________________________________________________________ Term__________________Interpretation______________________ PATHWORKS server DIGITAL PATHWORKS for OpenVMS software OpenVMS server file_server_______________________________________________ xv 1 ________________________________________________________________ Distribution Kit The DIGITAL PATHWORKS V5 for OpenVMS (LAN Manager) software media includes support for both VAX and Alpha systems, and consists of the following BACKUP savesets: __________________________________________________________ Saveset_Name________OpenVMS_System________________________ PWRKV50F_E01050.A VAX and Alpha PWRKV50F_E01050.B VAX PWRKV50F_E01050.C Alpha PWRKV50F_E01050.D VAX PWRKV50F_E01050.E Alpha PWRKV50F_E01050.F VAX PWRKV50F_E01050.G Alpha PWRKV50F_E01050.H VAX and Alpha VAXPWF11X01_060.A VAX VAXPWF11X01_060.B VAX VAXPWF11X01_060.C___VAX___________________________________ Distribution Kit 1-1 2 ________________________________________________________________ Features of DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 This section describes highlights and features of the DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 product. The following OpenVMS operating system versions are supported: o OpenVMS VAX Versions 5.5-2, 6.1, 6.2, 7.0, and 7.1 o OpenVMS Alpha Versions 6.1, 6.2, 7.0, and 7.1 This release of PATHWORKS for OpenVMS is distributed as part of the PATHWORKS for OpenVMS software kit, which includes the following: o DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 software o DIGITAL PATHWORKS V1.0F for OpenVMS (NetWare), ECO1 software o PATHWORKS license server software o Optionally installable improved OpenVMS file system (XQP+) o DECprint Supervisor for OpenVMS software 2.1 XQP+ A PATHWORKS-only special release of the enhanced OpenVMS file system, also known as XQP+, is included as a separately installable kit, called VAXPWF11X01_060. The XQP+ in this release supports OpenVMS VAX V5.5-2. Features of DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 2-1 ________________________Note ________________________ By default, XQP+ is installed with OpenVMS version 6.0 and higher. For these versions of OpenVMS, no special installation of the XQP+ is necessary. However, in order for applications to use XQP+, you must specifically enable it using the SYSGEN utility. Refer to the OpenVMS system management documentation for more information. _____________________________________________________ XQP+ provides improved concurrency in the I/O subsystem, asynchronous cache writes, and multithreading. The XQP+ also provides a special interface to the PATHWORKS V5 server that lets you enable the PATHWORKS directory caching feature. DIGITAL PATHWORKS for OpenVMS is designed to take full advantage of XQP+. No modification is necessary to enable these features. ________________________Note ________________________ Digital recommends that you install the XQP+ component if you are running OpenVMS VAX V5.5-2. Although only XQP+ aware applications can take full advantage of the performance enhancing features of XQP+, layered products that run on the OpenVMS system benefit from the improved concurrency and asynchronous cache writes. _____________________________________________________ 2.2 Optional DECprint Supervisor (DCPS) Available The PATHWORKS for OpenVMS distribution media includes two kits for the DECprint Supervisor for OpenVMS (DCPS) family of layered products, which runs on OpenVMS VAX and Alpha to provide access through the OpenVMS queuing system to selected PostScript printers. To use DCPS, you must install the kit for either VAX or Alpha accordingly. You do not need a separate license to use DCPS with LAN Manager clients. 2-2 Features of DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 2.3 PATHWORKS Monitor Utility The PATHWORKS Monitor utility provides a Microsoft Windows V3.1-based server monitoring interface. It provides remote access to the server's internal data structures and statistical information. This utility communicates with the PATHWORKS Monitor Server through NETBIOS over DECnet, NetBEUI, or TCP/IP. For more information, see the DIGITAL PATHWORKS for OpenVMS Server Administrator's Guide and the Monitor utility's online help. 2.4 New Features in Version 5.0F This section describes the new features of PATHWORKS V5.0F for OpenVMS (LAN Manager). 2.4.1 Client Access License Support The primary purpose of the Version 5.0F release of PATHWORKS for OpenVMS (LAN Manager) is to provide new license management software that will be able to support and use the new Client Access licenses, which are required for the next major release of this product: Version 6.0. The following licenses have been discontinued and replaced by the new Client Access license. Specifically, the following licenses are no longer sold: o PATHWORKS V5.0 (LAN Manager) Designated Access (PWLMXXXFP05.00) o PATHWORKS V5.0 for OpenVMS (LAN Manager) PC Concurrent (PWLMVMSCU05.00) Although these licenses continue to be valid for accessing the PATHWORKS V5.0x for OpenVMS (LAN Manager) server, in order to buy licenses for additional clients, the new Client Access license is the only available option. The Client Access license can be used as either a "Designated Access" license or as a "PC Concurrent" license, as determined by the system manager. ________________________Note ________________________ Versions of PATHWORKS for OpenVMS (LAN Manager) prior to V5.0F neither support nor recognize the Features of DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 2-3 Client Access license. Therefore, if you are using PATHWORKS for OpenVMS (LAN Manager) and plan to buy more licenses to give more clients access to this system in the future, you must upgrade to Version 5.0F in order to use the only license that will be available for this purpose (that is, the Client Access license). _____________________________________________________ 2-4 Features of DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 3 ________________________________________________________________ Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server This chapter describes guidelines for using PATHWORKS V5 for OpenVMS (LAN Manager) that are not included in the PATHWORKS for OpenVMS documentation set. 3.1 System and Network Configuration Guidelines The following sections describe guidelines on using PATHWORKS for OpenVMS in particular system and network configurations. 3.1.1 Running in an OpenVMS Cluster DIGITAL PATHWORKS for OpenVMS can be executed on multiple members in an OpenVMS cluster. Each member is called a server node. You must run the configuration procedure (PWRK$CONFIG) on each node in the OpenVMS cluster to ensure that adequate resources are available on each server node. You must start the server on each node. You can do this in one operation by using the following SYSMAN utility commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT /NODE=(PENCIL,ERASER) SYSMAN> DO @SYS$STARTUP:PWRK$SHUTDOWN SYSMAN> DO @SYS$STARTUP:PWRK$STARTUP ________________________Note ________________________ Digital recommends that you start the server and shut it down using the same account on all cluster nodes (preferably the SYSTEM account). _____________________________________________________ for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-1 3.1.2 Running in a Windows NT Domain The PATHWORKS V5 for OpenVMS (LAN Manager) server is a LAN Manager V2.x-based server that works in a Windows NT domain, with certain requirements and restrictions, as described in the following sections. ________________________Note ________________________ To avoid these incompatibilities with Windows NT servers, DIGITAL recommends that you upgrade to DIGITAL PATHWORKS V6 for OpenVMS (Advanced Server), a Windows NT-based file and print server for OpenVMS V7.1 systems. _____________________________________________________ 3.1.2.1 Interoperating in a Windows NT Domain To interoperate in a Windows NT domain, you need to perform the following tasks. From each Windows NT Server, configure the Windows NT Server to make the Browser broadcast to LAN Manager 2.x clients. For example, on a Windows NT V3.5 machine, follow this procedure: 1. From the Main window, choose Control Panel. 2. From the Control Panel window, choose Network. 3. From the Installed Network Software list box, choose Server. 4. In the Server dialog box, mark the check box next to the following text: Make Browser Broadcasts to LAN Manager 2.x Clients From the PATHWORKS server: 1. Change the domain name by executing @SYS$UPDATE:PWRK$CONFIG. Specify the Windows NT domain name as the new domain name: Enter item number, or RETURN to use these values [done]: 7 Enter LAN Manager domain name for this system [LANGROUP]: NTDOMAIN 3-2 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 2. Run the SYS$STARTUP:PWRK$STARTUP command procedure to restart the server. 3. Change the role of the server to Backup Domain Controller, or Member server, as follows: a. Enter the Server Admin interface (ADMIN/PATHWORKS) and log on to the network. b. From the Accounts menu, select Security settings. c. In the Role in Domain box, choose Backup Domain Controller, or Member server, as appropriate. 4. From the Config menu, select the Control services option and start the Netlogon service. 3.1.2.2 Managing OpenVMS Print Shares from a Windows NT Server To successfully manage the PATHWORKS V5 for OpenVMS (LAN Manager) server from a Windows NT server, all queues must have the same name as the print share. 3.1.2.3 Letting LAN Manager V2.x Server Users Browse Windows NT Servers To let a LAN Manager V2.x server user browse Windows NT servers, do the following on the Windows NT V3.5 Servers: 1. From the Main window, choose Control Panel. 2. From the Control Panel window, choose Network. 3. In the Network Settings dialog box, choose Server from the Installed Network Software list box. 4. Choose Configure. 5. In the Server dialog box, mark the check box next to the following text: Make Browser Broadcasts to LAN Manager 2.x Clients 6. Choose OK. 3.1.3 Defining Communications Devices This section describes how to add new communications devices that are not automatically recognized by the PATHWORKS LAN Manager server, as well as restrictions and limitations on communications devices. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-3 3.1.3.1 Processes Fail When Devices Are Not Defined The PWRK$KNBDAEMON, NETBIOS, and PWRK$LMRIPL processes require the communications device to be defined in an internal device table. It is possible for new communications devices to be released before updated PATHWORKS images are available to customers. Therefore, this section describes how to define the communications device you want the PATHWORKS server to use. If the communications device is not recognized by PATHWORKS, each failing process writes an error message to its log file. The following table shows each process, the log file that records the error message from the process, and examples of the text of the error message. In the following examples, the server node name is MYNODE. Table_3-1_Undefined_Device_Messages_____________________________ Process__________Log_File_Name__________________________________ PWRK$KNBDAEMON PWRK$LOGS:PWRK$KNBDAEMON_MYNODE.LOG Message: Tue May 31 13:13:50 1994 get_phys_addr: Failed to get Ethernet device characteristics NETBIOS PWRK$LMLOGS:LMMCP_MYNODE.LOG Message: lmu6035: Unable to post the name on any network: MYNODE PWRK$LMRIPL PWRK$LMLOGS:PWRK$LMRIPL_MYNODE.LOG Message: 31-MAY-1994 15:30:35.64 000000BC:0063EEA0 Caught a very bad signal 10 %SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=80296A5C,_PS=0000001B________________________________________ The device tables in the current release include all known communications devices. However, if you are running the latest release and you find any of the messages listed in Table 3-1, you can explicitly specify the communications device in the internal device table for all three processes, using the following procedure: 3-4 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 1. Define the physical communications device type for the PWRK$KNBDAEMON, NETBIOS, and NetBEUI processes. For example, if the physical communications device type is EWA0, enter: $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0: $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0: $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0: 2. Edit the LANMAN.INI file to define the communications device type for the PWRK$LMRIPL process. For example, if the communications device type is EW, add the following to the LANMAN.INI file: [REMOTEBOOT] RPL1=DLVMS EW 3. Restart the server: $ @SYS$STARTUP:PWRK$STARTUP 3.1.3.2 DECnet NETBIOS Initializes on New FDDI Controllers Previous to PATHWORKS V5.0B for OpenVMS (LAN Manager), the NETBIOS component relied on the fact that all Ethernet users share the same physical address. When NETBIOS asked the Ethernet datalink for its physical address, the older FDDI controllers returned the DECnet physical address, if DECnet was running. For newer FDDI controllers, the DECnet physical address is not returned, even when DECnet is running. Therefore, if NETBIOS$DEVICE is defined to be a different Ethernet controller than the one on which DECnet is running, NETBIOS returns the wrong address in the FIND NAME response packet. In PATHWORKS V5.0B for OpenVMS and higher, the NETBIOS component functions correctly for the newer FDDI controllers. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-5 3.1.4 PATHWORKS Transports PATHWORKS for OpenVMS supports the following types of transports: o DECnet o NetBEUI o TCP/IP o IPX (in order to use the PATHWORKS for OpenVMS (NetWare) file server) 3.1.4.1 PATHWORKS for OpenVMS TCP/IP Support PATHWORKS for OpenVMS provides transparent support for the following TCP/IP network transport products: o DEC TCP/IP Services for OpenVMS, Version 4.0 o MultiNet Version 3.5, Revision A o Process Software Corporation's TCPWare for OpenVMS, Version 5.0-4 o Wollongong Group's Pathway Version 1.1 To use PATHWORKS 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: o For TGV MultiNet V3.3 Rev A, enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$SPECIFIC:[MULTINET]START_MULTINET This starts the MultiNet TCP/IP transport and loads the TGV PATHWORKS IP driver. o For Digital TCP/IP Services for OpenVMS, enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:UCX$STARTUP (For more information, refer to the documentation that comes with your TCP/IP product.) 3-6 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3. Configure PATHWORKS to use TCP/IP as a transport. To do so, enter the ADMIN/CONFIG command to run the Configuration utility, and then choose TCP/IP from the dialog box displayed. For detailed information on how to use the Configuration utility, use the utility's online help. 4. Start the LAN Manager server. To do so, enter the following OpenVMS command, or add it to the system startup procedure: $ @SYS$STARTUP:PWRK$STARTUP 3.1.4.2 UCX and PATHWORKS Interaction There are known problems in the TCP/IP Service for OpenVMS V3.1 software kit that will cause PATHWORKS to fail; these problems are noted in the TCP/IP V3.1 release notes. If you encounter one of the stated problems, you should upgrade to the latest version of UCX. If you encounter one of the stated problems, you need to acquire the following UCX V3.1 ECO3 patch images: o UCX$PWIPACP.EXE (UCX V3.1-32B) o UCX$PWIPDRIVER.EXE (UCX V3.1-32B) o UCX$PWIPSHUT.EXE (UCX V3.1-32B) 3.1.4.3 PATHWORKS V5 with DECnet-Plus The following versions of DECnet-Plus are supported: Table_3-2_DECnet-Plus_with_OpenVMS_VAX____________________ OpenVMS_Version__DECnet-Plus_Version______________________ Version 5.5-2 Version 5.6 Version 6.1 Version 5.7 Version 6.2 Version 6.3 Version 7.0 Version 7.0 Version_7.1______Version_7.1______________________________ for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-7 Table_3-3_DECnet-Plus_with_OpenVMS_Alpha__________________ OpenVMS_Version__DECnet-Plus_Version______________________ Version 6.1 Version 5.7 Version 6.2 Version 6.3 Version 7.0 Version 7.0 Version_7.1______Version_7.1______________________________ The minimum server configuration with DECnet-Plus is: o 24 Mbytes of physical memory on a VAX system o 64 Mbytes of physical memory on an Alpha system 3.2 Installing, Configuring, and Starting the Server This section describes server installation, configuration, and startup, as well as upgrading from previous versions. 3.2.1 PWRK$CONFIG Configuration Command Procedure If, during the execution of the PWRK$CONFIG command procedure, you need to run AUTOGEN, you must run PWRK$CONFIG again to complete the initial setup step. 3.2.2 Upgrading from PATHWORKS for VMS V4.x to PATHWORKS V5 for OpenVMS This section provides information about upgrading from PATHWORKS V4.x for VMS to PATHWORKS V5 for OpenVMS (LAN Manager). For more information about upgrading your servers and clients, please refer to the PATHWORKS for OpenVMS Server Migration Guide. 3.2.2.1 Differences Between V4.x and V5.x If you have PATHWORKS for VMS V4.x currently installed on your system, it is important for you to know that PATHWORKS V5 for OpenVMS (LAN Manager) is vastly different from previous versions of the server. Unlike the V4.x server, the V5 server is LAN Manager compliant. This means that the V5 server participates as a full peer with other servers in a LAN Manager network and supports LAN Manager features, including: 3-8 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server o Domains These are subdivisions of servers and clients on the network that: - Let each user work with a specific set of servers and other users. - Provide a simple way to control access to the network. - Make network administration easier. o Logon validation This feature allows users to log on to a network domain once and then connect to shared network resources without specifying their user name and password again. o User-level security This security is based on a password associated with the LAN Manager user account. o Share-level security This security is based on a password associated with each shared network resource. o Remote server management This feature allows you to manage the server remotely with either a Windows or command-line interface from an OpenVMS V5 server, an OS/2 server, an OS/2 client, or a DOS client on which the Enhanced Redirector is installed. ________________For More Information ________________ For detailed information about the LAN Manager features available in the V5 server, see the PATHWORKS V5 for OpenVMS Server Administrator's Guide. _____________________________________________________ The installation and configuration procedure also gives you the option to run the Upgrade utility, which upgrades a V4.x server to a V5 server. It lets you upgrade user information, group definitions, services, and access rights, allowing users to: for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-9 o Access upgraded services and files. o Take advantage of the V5 server's new LAN Manager features. ________________________Note ________________________ Digital Equipment Corporation recommends that you read the PATHWORKS for OpenVMS Server Installation and Upgrade Guide as well as these release notes. The guide contains detailed information that you need to know to execute the installation, configuration, and upgrade tasks properly. _____________________________________________________ 3.2.2.2 Changes to the Security Model The PATHWORKS V4.x implementation is based on the OpenVMS security model. The PATHWORKS V5 implementation is based on the LAN Manager security model. The OpenVMS file access security that you set up can still be in effect if you choose to run in LAN Manager & OpenVMS security mode. However, the LAN Manager user authentication subsystem is used for user logon requests. 3.2.2.3 Features No Longer Available The following features are no longer available: o The USE /SETDIR command o The NET PRINT /SET command o The NET ATTRIB command o The ability to access a UAF login area without a share o The ability to access an OpenVMS print queue without a share o The ability to access any OpenVMS directory without a share o The ability for multiple users to connect from the same workstation 3-10 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.3 Formatting OpenVMS Files You can tailor the format of non-stream files (such as RMS text files, indexed files, and Fortran files) using the PWRK$COMMON:PWRK.INI file, which lets you modify aspects of the server's operation. You can set the following three parameters in the [ODS2] section of the PWRK$COMMON:PWRK.INI file. (If the [ODS2] section does not exist, add it.) These parameters correspond to the three RMS record attributes that you can associate with a file. ________________________________________________________________ Parameter________Description____________________________________ TEXT_CR_MODE The most common text file format, which is created by most OpenVMS text editors and applications; corresponds to the RMS record attribute Carriage Return Carriage Control. TEXT_PR_MODE The file format that is created by the DCL command OPEN/WRITE, which is the mechanism DCL procedures use to create files; corresponds to the RMS record attribute Print File Carriage Control. TEXT_FTN_MODE The format Fortran-based applications use; corresponds to the RMS record attribute Fortran _________________Carriage_Control.______________________________ To control how each record is formatted, you can assign one of the following values to each parameter: for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-11 ________________________________________________________________ Value____________Description____________________________________ 0 (mode NONE) Ignores the specified carriage control information and treats the record as a standard text record. 1 (mode RMS) Generates the record sequences that RMS specifies, which is usually record. 2 (mode CRLF) Generates an equivalent postfix to delimit records. This is the server's default mode. Note that precise PRN sequences and some Fortran sequences may not work properly in this mode. 3 (mode LF) Generates an equivalent postfix to delimit _________________records._______________________________________ The following sections describe how carriage control is interpreted for each file format. TEXT_CR_MODE______________________________________________ If the value is_._._._________Then_the_carriage_control_format_is_._._. NONE record RMS record CRLF record LF_______________record_______________________________ Note that carriage control is implied for each record; single spacing is assumed. TEXT_PR_MODE For this parameter, the carriage control format is based on the fixed area of the record, which contains two bytes that define prefix and postfix control, respectively. If you set the TEXT_PR_MODE parameter to NONE, then carriage control information is ignored and implied CC is used (record). If you set the TEXT_PR_MODE parameter to RMS, then the first byte is interpreted as follows: 3-12 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server Bit 7 ! Bit 6-0 ------+---------------------------------------------------- 0 ! Count of sequences to generate, including ! none. ------+---------------------------------------------------- The second byte is interpreted as follows: Bit 7 ! Bit 6 ! Bit 5 ! Bit 4-0 ------+-------+-------+--------------------------------- 1 ! 0 ! 0 ! Character to be inserted in the ! ! ! range 0-1F hex. ------+-------+-------+--------------------------------- 1 ! 1 ! 0 ! Character to be inserted in the ! ! ! range 80-9F hex. ------+-------+-------+--------------------------------- 1 ! X ! 1 ! Reserved. ------+-------+-------+--------------------------------- If you set TEXT_PR_MODE to CRLF, then the first byte is interpreted as follows: Bit 7 ! Bit 6-0 ------+-------------------------------------------------------- 0 ! Count plus 1 of sequences to generate, ! including none. For example, 1 generates no s, ! 2 generates 1, and so on. ------+-------------------------------------------------------- The second byte is interpreted as follows: Bit 7 ! Bit 6 ! Bit 5 ! Bit 4-0 ------+-------+-------+------------------------------------- 1 ! 0 ! 0 ! Character to be inserted in the ! ! ! range 0-1F hex. If the character is ! ! ! 0D hex, a sequence is ! ! ! generated. ------+-------+-------+------------------------------------- 1 ! 1 ! 0 ! Character to be inserted in the ! ! ! range 80-9F hex. ------+-------+-------+------------------------------------- 1 ! X ! 1 ! Reserved. ------+-------+-------+------------------------------------- for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-13 If you set TEXT_PR_MODE to LF, the first byte is interpreted as follows: Bit 7 ! Bit 6-0 ------+------------------------------------------------------- 0 ! Count plus 1 of sequences to generate, including ! none. For example, 1 generates no s, 2 generates ! 1, and so on. ------+------------------------------------------------------- The second byte is interpreted as follows: Bit 7 ! Bit 6 ! Bit 5 ! Bit 4-0 ------+-------+-------+------------------------------------- 1 ! 0 ! 0 ! Character to be inserted in the ! ! ! range 0-1F hex. If the character is ! ! ! 0D hex, a is generated. ------+-------+-------+------------------------------------- 1 ! 1 ! 0 ! Character to be inserted in the ! ! ! range 80-9F hex. ------+-------+-------+------------------------------------- 1 ! X ! 1 ! Reserved. ------+-------+-------+------------------------------------- TEXT_FTN_MODE For this parameter, carriage control format is based on the first byte of the record. If you set TEXT_FTN_MODE to NONE, the record is treated as an implied CC. If you set TEXT_FTN_MODE to RMS, the first byte is interpreted as follows: 3-14 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server Byte ! ASCII ! Sequence ------+-------+---------------------------------- 0 ! NULL ! No carriage control. ------+-------+---------------------------------- 20 ! ! Single space. record ------+-------+---------------------------------- 30 ! 0 ! Double space. record ------+-------+---------------------------------- 31 ! 1 ! Page eject. record ------+-------+---------------------------------- 28 ! + ! Overprint. record ------+-------+---------------------------------- 24 ! $ ! Prompt. record ------+-------+---------------------------------- All others ! Single space. record --------------+---------------------------------- If you set TEXT_FTN_MODE to CRLF, the first byte is interpreted as follows: Byte ! ASCII ! Sequence ------+-------+-------------------------------------- 0 ! NULL ! No carriage control. ------+-------+-------------------------------------- 20 ! ! Single space. record ------+-------+-------------------------------------- 30 ! 0 ! Double space. record ------+-------+-------------------------------------- 31 ! 1 ! Page eject. record ------+-------+-------------------------------------- 28 ! + ! Overprint. record ------+-------+-------------------------------------- 24 ! $ ! Prompt. record ------+-------+-------------------------------------- All others ! Single space. record --------------+-------------------------------------- If you set TEXT_FTN_MODE to LF, the first byte is interpreted as follows: for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-15 Byte ! ASCII ! Sequence ------+-------+------------------------------ 0 ! NULL ! No carriage control. ------+-------+------------------------------ 20 ! ! Single space. record ------+-------+------------------------------ 30 ! 0 ! Double space. record ------+-------+------------------------------ 31 ! 1 ! Page eject. record ------+-------+------------------------------ 28 ! + ! Overprint. record ------+-------+------------------------------ 24 ! $ ! Prompt. record ------+-------+------------------------------ All others ! Single space. record --------------+------------------------------ Note that Fortran carriage control bytes are translated into equivalent print control format sequences. 3.4 License Server and License Management The following sections describe aspects of the licensing subsystem provided by PATHWORKS for OpenVMS. 3.4.1 Running the License Server The PATHWORKS for OpenVMS software kit contains a license server component, which verifies licenses from clients on DECnet, NetBEUI, and TCP/IP, as well as NetWare clients on IPX. You only need to run one license server on your LAN to grant PATHWORKS file and print licenses to PCs so that they can connect to PATHWORKS servers. Install the PATHWORKS client-based PAKs on the same system where the license server is running. You can install the license server separately from the file servers; for example, on a dedicated license server system. Refer to the PATHWORKS for OpenVMS Installation and Upgrade Guide for more information about installing the standalone license server. 3-16 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.4.2 License Server Startup and Shutdown PATHWORKS for OpenVMS supports running both the LAN Manager file server and the NetWare file server. The PATHWORKS license server can provide license verification for both LAN Manager and NetWare clients. The LAN Manager clients can connect to the file server using any of the following types of transports: o DECnet o TCP/IP o NetBEUI NetWare clients connect to the file server using the IPX transport. Because the license server supports all of these types of transports, the startup and shutdown procedures have been carefully designed to prevent unexpected interruptions in service. The license server is started up and shut down using the file server command procedures. The integrated PATHWORKS license server runs with the file servers. For information about integrated license server startup and shutdown, refer to Section 3.4.2.1. The standalone license server is installed on a system without the file servers. For information about the standalone license server, refer to Section 3.4.2.5. For more information about the installation and configura- tion of file servers and the license server, refer to the PATHWORKS for OpenVMS Installation and Upgrade Guide. For more information about the PATHWORKS license server and using the License Manager, refer to the Guide to Managing PATHWORKS Licenses. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-17 3.4.2.1 Integrated License Server Startup The integrated license server runs with one or both of the file servers, if it was included in the configuration with the appropriate configuration procedure. The license server is started by the same command procedures that start the file servers. PWRK$STARTUP.COM Starts up the LAN Manager file server and license server components PWVN$STARTUP.COM Starts up the NetWare file server and license server components The following table shows how the two startup command procedures differ: __________________________________________________________ If the Command following is Then the following is Procedure________configured_______started_________________ PWRK$STARTUP.COM DECnet DECnet transport NetBEUI NetBEUI transport TCP/IP TCP/IP transport license server IPX tunnel and IPX DECnet DECnet transport for PATHWORKS mail notification license server license server component and license registrar component PWVN$STARTUP.COM IPX IPX transport and IPX tunnel license server DECnet transport and DECnet license server NetBEUI transport and NetBEUI license server NETBIOS transport _________________and_TCP/IP_______________________________ 3-18 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.4.2.2 Integrated License Server Shutdown To shut down the license server, use the same command procedures that shut down the file servers. The shutdown command procedures are: PWRK$SHUTDOWN.COM Shuts down the LAN Manager file server and license server components PWVN$SHUTDOWN.COM Shuts down the NetWare file server and license server components Both procedures shut down the license server, license registrar and all the PATHWORKS transports, including IPX and the IPX tunnel. 3.4.2.3 Joint LAN Manager and NetWare Startup When both the LAN Manager and NetWare file servers are in- stalled, and the integrated license server is configured, run both PWRK$STARTUP.COM and PWVN$STARTUP.COM. These command procedures cannot run at the same time. One must complete before the other can run. If the license server, license registrar, or any of the PATHWORKS transports are already running, those processes are not started. 3.4.2.4 Joint LAN Manager and NetWare Shutdown If you use both PWRK$STARTUP.COM and PWVN$STARTUP.COM to start the servers, then use both procedures to shut down the file servers and license server. In this type of configuration, the following components are shut down only when you run both shutdown procedures: o License server o License registrar o All of the PATHWORKS transports When both shutdown procedures are executed, the second procedure to execute shuts down the license server, license registrar, and all PATHWORKS for OpenVMS transports, including IPX and the IPX tunnel. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-19 3.4.2.5 Standalone License Server Startup and Shutdown The standalone license server runs on a system without the file servers. However, the transports are configured for supporting license services to the appropriate clients. Therefore, the standalone license server startup and shutdown is similar to that described above for the integrated license server. Either PWRK$STARTUP.COM or PWVN$STARTUP.COM will start the license server and the transports it requires, but you should run both PWRK$STARTUP.COM and PWVN$STARTUP.COM if the license server serves both LAN Manager and NetWare clients. Similarly, you should run both PWRK$SHUTDOWN.COM and PWVN$SHUTDOWN.COM when shutting down the license server if the license server serves both LAN Manager and NetWare clients. 3.4.3 Upgrading License Server State Files When a new version of the license server is installed, it automatically upgrades earlier versions of the license server state file into the format used by the new version. This upgrade operation takes place the first time the new license server is started after installation. If a PATHWORKS Version 5.0B for OpenVMS (LAN Manager) state file and a PATHWORKS V1.0 for OpenVMS (NetWare) state file are both found, the contents of both files are merged into a new license server state file. Any old state files that are used as part of an upgrade process are renamed so that further attempts to upgrade the old state files will not be made. At startup, the new license server checks to see if there are old state files to be merged or upgraded to form a new license server state file. The following are the file names of the old and new li- cense server state files that may be found in PWRK$LICENSE: New state file PWRK$LICENSE_SERVER_STATE.DAT 3-20 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server Old LAN Manager PWRK$LICENSE_SERVER.DAT state file Old NetWare state PWL$SERVER_STATE.DAT file If a new state file and any old state file both exist in the PWRK$LICENSE directory, the license server fails to start, and posts both an operator message and a message to the license server log file, indicating that an illegal configuration of old and new state files was found. To start the license server, you must remove either the old state files or the new state file. For example, if you intend to use the old state files, delete the new state file. This allows the license server to upgrade the old state file into a new license server state file. On the other hand, if the contents of the old state files are not important, rename or delete the old state files. 3.4.3.1 Upgrading License Server State Files on a Node Not Previously Configured to Run the License Server The PATHWORKS for OpenVMS installation procedure places a template license server state file into the PWRK$LICENSE directory, if the template file is not already there. Even when the node is not configured to run the license server, the template state file is stored as: PWRK$LICENSE:PWRK$LICENSE_SERVER.DAT If you install PATHWORKS for OpenVMS and configure it to run the license server, the configuration procedure detects the presence of the template state file in PWRK$LICENSE, and attempts to upgrade it. This results in a partial license server name (for example, PWRK$L, instead of PWRK$Lnodename). Because the license server fails to form the license server name properly, clients are unable to connect to the node running the license server. The problem is made apparent by the announcement message in the license server log file, PWRK$LOGS:PWRK$LICENSE_ SERVER_nodename.LOG for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-21 The announcement message is one of the first messages posted in the log file, and will look similar to the following, if the license server node name was constructed properly. In the following example, the license server node name is MYNODE: 17-FEB-1995 10:49:56.00 MESSAGE: License Server "MYNODE" is now processing LAN Manager license requests on node "MYNODE" If the license server upgraded a template file, the license server node name is missing from the message. For example: 17-FEB-1995 10:49:56.00 MESSAGE: License Server "" is now processing LAN Manager license requests on node "MYNODE" To fix this problem, rename or delete the template state file from the PWRK$LICENSE area. Shut down and restart the license server as described below. 1. Rename the template license server state file from PWRK$LICENSE. For example: $ RENAME PWRK$LICENSE:PWRK$LICENSE_SERVER.DAT - _$ SYS$BACKUP:V50C_LICENSE_SERVER.DAT 2. Shut down the PATHWORKS servers and start them again. The license server starts, creates a new state file, and remains disabled. 3. Run the License Manager utility, as follows: $ RUN SYS$SYSTEM:PWRK$LICENSE_MANAGER Choose Exit. The license server is automatically enabled. The clients should now be able to obtain licenses. 3.5 Using LAN Manager Server Net Commands The following information supplements the PATHWORKS V5 for OpenVMS (LAN Manager) Commands Reference Manual. 3-22 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.5.1 Autoshare List Updating Problems with updating disks are corrected in V5.0D and later. Previously, disks on the autoshare list could not be changed without restarting the server. With V5.0D and later, a new command allows you to synchronize the autoshare list with the disks currently online. When you add a disk, use the following command to update the device list with the new device: $ NET SHARE /SYNC 3.5.2 Using the Net Share Command to Create Personal Shares The OpenVMS Net Share command supports the /PERSONAL qualifier when adding and displaying shares. Shares added with this qualifier are defined to be personal shares. Only personal shares are displayed with this qualifier. ________________________Note ________________________ The permissions on the share must be set using the Net Access command, to allow the desired users to access the created personal share. For more information about using the Net Access command, refer to the PATHWORKS for OpenVMS Commands Reference Manual. _____________________________________________________ 3.5.3 Use Quotations Marks to Include Exclamation Mark When using exclamation marks in LAN Manager user names and group names, the server software interprets the exclamation mark (!) as a comment character, ignoring it and all the following text on the command line. To include an exclamation mark in a user name or group name, enclose the exclamation mark in quotes. For example, in the following command, "SYSTEM /ADD" is ignored: $ NET USER MY!SYSTEM /ADD To ensure that this command interprets the command correctly, enter it as follows: $ NET USER "MY!SYSTEM" /ADD for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-23 3.5.4 Use Quotation Marks to Delineate Command Options That Contain Spaces When using the Command Line Net Interface with options that contain spaces you must put the option in quotes ("") for the command to complete successfully. For example: $ NET SEND /USERS "This server will shut down in 5 minutes." 3.6 Changing LAN Manager Passwords Users of PATHWORKS for OpenVMS (LAN Manager) have two passwords: one for the LAN Manager account and another for the OpenVMS account. The PATHWORKS client user running the Enhanced Redirector can change the OpenVMS password using the NETD PASSWORD client command, and can change both the LAN Manager and OpenVMS passwords using the NETPASS client command. For more information about the PATHWORKS client commands, refer to the PATHWORKS for DOS and Windows Commands Reference manual. The LAN Manager administrator or user on OpenVMS can change the OpenVMS account password and the LAN Manager password using the DCL command NET PASSWORD. By default, the passwords are sychronized, so that the LAN Manager password and the OpenVMS password are the same. Password synchronization is discussed in Section 3.6. For more information about the NET PASSWORD command, refer to the PATHWORKS V5 for OpenVMS (LAN Manager) Commands Reference manual. On the server, you can change the way the OpenVMS NET PASSWORD command works by setting keyword values in the [VMSSERVER] section in the LANMAN.INI file. Some of the keywords that affect the NET PASSWORD command, and the sections where they are described in these Release Notes, are listed in the following table. 3-24 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server Table_3-4_LANMAN.INI_Keywords_for_Password_Control______________ Function of Default Section Parameter_____________Parameter_Name______Value_______Number____ Force users to VMSGENPWD NO 3.6.1 choose a password from a list generated by OpenVMS Set the minimum MIN_VMSGENPWD_LEN 6 3.6.2 length of an OpenVMS-generated password Force the OpenVMS HOSTPASSWORDSYNC YES 3.6.3 account password to be the same as the LAN Manager password Check the password HOSTPASSWORDFORCE NO 3.6.4 history and the dictionary before granting a new password________________________________________________________ ________________________Note ________________________ The LANMAN.INI file must be world-readable. To set the file to be world-readable, enter the following command: $ SET PROTECTION PWRK$LMROOT:LANMAN.INI/PROT=W=R _____________________________________________________ 3.6.1 OpenVMS-Generated Passwords The OpenVMS (LAN Manager) server supports use of OpenVMS- generated passwords. This feature provides the ability to force LAN Manager users to use OpenVMS generated passwords when using the OpenVMS NET PASSWORD command. This feature is controlled by a parameter in the LANMAN.INI file. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-25 If in the [VMSSERVER] section of the LANMAN.INI file the parameter VMSGENPWD=YES, the NET PASSWORD command forces the user to select a password from a list of OpenVMS- generated passwords. By default, VMSGENPWD=NO and the use of OpenVMS-generated passwords through the NET PASSWORD command is not enabled. ________________________Note ________________________ The maximum length of a LAN Manager password is 14 characters. Therefore, if the minimum length of the OpenVMS password is greater than 14 characters, you should not set VMSGENPWD=YES. _____________________________________________________ 3.6.2 Length of OpenVMS-Generated Passwords The length of the OpenVMS generated password is governed by the LAN Manager accounts security settings, as well as the MIN_VMSGENPWD_LEN parameter in the [VMSSERVER] section of the LANMAN.INI file. If the LAN Manager accounts security sets a minimum password length of zero, it is overridden with the default value of 6. If the MIN_ VMSGENPWD_LEN parameter is specified in the LANMAN.INI file, the parameter value is used as the minimum length of the OpenVMS-generated passwords. The value for MIN_ VMSGENPWD_LEN can be from 1 to 14 characters, which is the maximum for LAN Manager passwords. If VMSGENPWD parameter is set in LANMAN.INI, the NET PASSWORD command functions as shown in the following example. (The LAN Manager user name is LM_USER. The old password is OLDPASS.) $ NET PASSWORD LM_USER OLDPASS * miuving antimetrown idecced lourgultorn cardwiland 3-26 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server Choose a password from this list, or press return to get a new list New password: IDECCED The LM password has been changed. The OpenVMS password has been changed. The command completed successfully. 3.6.3 OpenVMS Password Synchronization The OpenVMS command NET PASSWORD changes both the the LAN Manager password and the OpenVMS password. By default, two passwords are synchronized to match. Therefore, when you change the password using the NET PASSWORD on the OpenVMS system, both the LAN Manager password and the OpenVMS account password are changed. (The client command NETD PASSWORD does not set both passwords; it sets only the OpenVMS password.) The password synchronization feature is controlled by the HOSTPASSWORDSYNC parameter in the [VMSSERVER] section of the LANMAN.INI file. By default, HOSTPASSWORDSYNC=YES. Therefore, the NET PASSWORD command sets the LAN Manager password and attempts to set the OpenVMS password. By default, the LAN Manager ADMIN account is mapped to the OpenVMS system account. If password synchronization is enabled, changing the ADMIN account password alters the OpenVMS system password. The NET PASSWORD command initially tries to set the password for the OpenVMS user that exactly matches the LAN Manager user. If this fails, NET PASSWORD prompts you for an OpenVMS user name and password. Examples o Setting a password when the OpenVMS and LAN Manager user names and passwords are the same: $ NET PASSWORD LM_USER OLDPASS NEWPASS The LM password has been changed. The OpenVMS password has been changed. The command completed successfully. Result: the LAN Manager and OpenVMS accounts for LM_ USER both have a new password: NEWPASS. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-27 o Setting the password when the OpenVMS and LAN Manager user names are different, or when the OpenVMS user name has a different old-password: $ NET PASSWORD LM_USER OLDPASS NEWPASS The LM password has been changed. Enter the OpenVMS username, or press RETURN if it is LM_USER: Enter the old OpenVMS password: OLDVMS The OpenVMS password has been changed. The command completed successfully. Result: the LAN Manager and OpenVMS accounts for LM_ USER both have a new password: NEWPASS. o Synchronizing a password of a local OpenVMS user with the LAN Manager password: $ NET PASSWORD LM_USER LMPASS LMPASS Enter the OpenVMS username, or press RETURN if it is LM_USER: Enter the old OpenVMS password: OLDVMS The OpenVMS password has been changed. The command completed successfully. Result: the LAN Manager password remains the same (LMPASS) and the OpenVMS password has been changed to match (LMPASS). o Synchronizing OpenVMS passwords on multiple servers in the domain: On the OpenVMS server (SERVER1), change the LAN Manager password on the local server and the primary domain controller: $ NET PASSWORD LM_USER LMPASS NEWPASS To set the OpenVMS password and LAN Manager password on the other servers (for example, SERVER2 and SERVER3), enter the following commands: $ NET PASSWORD \\SERVER2 LM_USER LMPASS NEWPASS $ NET PASSWORD \\SERVER3 LM_USER LMPASS NEWPASS 3-28 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server ________________________Note ________________________ Repeat the sequence for each server whose OpenVMS password you want to synchronize with the domain's LAN Manager password. _____________________________________________________ Result: the LAN Manager password is changed to NEWPASS. Then the OpenVMS account passwords on all the remaining servers are also changed to NEWPASS. 3.6.4 Password History and Dictionary Checking The OpenVMS password will be set only after it passes the history and dictionary check, if the parameter HOSTPASSWORDFORCE=NO in the LANMAN.INI file. OpenVMS password history and dictionary checking is done before the OpenVMS password is set. If HOSTPASSWORDSYNC=YES and HOSTPASSWORDFORCE=YES, the OpenVMS password is set, but password history and dictionary checking are not performed. The default setting for this keyword is NO. 3.7 OpenVMS External Authentication Support The PATHWORKS V5.0E for OpenVMS (LAN Manager) software and later versions support OpenVMS external authentication. OpenVMS Version 7.1 includes support for external authentication. This feature allows the OpenVMS system manager to set up a user account for which login authentication is based on a security mechanism other than OpenVMS security. PATHWORKS for OpenVMS software takes advantage of this feature by providing the ability to use the LAN Manager user authentication mechanism to authenticate OpenVMS user logons. This allows users to log in at the OpenVMS login prompt using the LAN Manager user name and password. In addition, it provides automatic password synchronization for OpenVMS user accounts. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-29 Externally authenticated users are considered to have a single password and are not subject to OpenVMS password policies, such as password expiration, password history, and minimum and maximum password length restrictions. However, users are subject to the LAN Manager policy that is defined. All other OpenVMS account restrictions remain in effect, such as disabled accounts, modal time restrictions, quotas, and so on. 3.7.1 Enabling External Authentication OpenVMS operating system Version 7.1 and higher provides support for external authentication. PATHWORKS for OpenVMS (LAN Manager) Version 5.0E and higher takes advantage of external authorization to allow LAN Manager users to log in to the OpenVMS operating system using the LAN Manager user name and password. To provide external authentication for a user, perform the following procedures. Each procedure is described in the section listed below. __________________________________________________________ Step___Procedure___________Section________________________ 1. Enable external Section 3.7.1.1 authentication for the system. 2. Set the OpenVMS Section 3.7.1.2 user account to allow external authentication. 3. Establish host Section 3.7.1.3 mapping between the PATHWORKS LAN Manager user account and the OpenVMS operating system user _______account.___________________________________________ 3-30 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.7.1.1 Enabling External Authorization for OpenVMS Systems To enable external authentication for the system, include the following commands in the SYS$STARTUP:SYSTARTUP_VMS.COM after you install, configure, and start up the required networking software: $ @SYS$STARTUP:PWRK$STARTUP $ DEFINE/SYS/EXE SYS$ACME_MODULE PWRK$ACME_MODULE $ DEFINE/SYS/EXE SYS$SINGLE_SIGNON 1 3.7.1.2 Enabling External Authentication for a User To enable external authentication for a user, set the EXTAUTH flag in the SYSUAF record. When set, the EXTAUTH flag denotes that the user is to be externally authenticated at OpenVMS logon. You can modify this flag using the AUTHORIZE utility. For example, to create a user account with external authentication enabled, enter the following commands (where nnn,nnn is the UIC for the new user account): $ MCR AUTHORIZE UAF> ADD username /FLAG=(EXTAUTH,NODISUSER) /UIC=[nnn,nnn] To modify an existing user account to allow external authentication, enter the following commands: $MCR AUTHORIZE UAF> MODIFY username /FLAG=(EXTAUTH) ________________________Note ________________________ By default, the EXTAUTH flag in the AUTHORIZE utility is not set. _____________________________________________________ Refer to the "OpenVMS System Management Utilities Reference Manual" for more information on the AUTHORIZE utility EXTAUTH flag. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-31 3.7.1.3 Establishing the User Host Mapping To allow an OpenVMS user to be externally authenticated, you must establish the hostmapping for the corresponding LAN Manager user account. Host mapping identifies a LAN Manager user with an OpenVMS user account. To establish the host mapping for the user to be externally authenticated, use the ADMIN/PATH utility, as follows: 1. Invoke the ADMIN/PATH utility with the following command: $ADMIN/PATH 2. Log on as ADMIN. 3. From the Accounts menu, select Users. 4. Select the user to establish mapping. 5. Choose Zoom. 6. Enter the corresponding OpenVMS user name in the hostmap field. 7. Choose OK. After you complete these steps, the user identified as externally authenticated can use the LAN Manager user name and password to log in to OpenVMS at the login prompt. If the verification is successful, the appropriate OpenVMS user name and profile are obtained and used. For more information about user account host mapping, refer to the PATHWORKS for OpenVMS Server Administrator's Guide. 3.7.1.4 Synchronizing Passwords The password of an externally authenticated OpenVMS user is automatically synchronized with the hostmapped LAN Manager user, regardless of the role of the LAN Manager server in the domain. When the user set up for external authentication uses the SET PASSWORD command, OpenVMS will forward the password change request to the LAN Manager server. When the password change request is successfully processed, OpenVMS updates the OpenVMS user password. OpenVMS also synchronizes the LAN Manager passwords with the local 3-32 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server OpenVMS passwords whenever the user logs in to the OpenVMS system. ________________________Note ________________________ Password synchronization may fail due to the different sets of valid characters allowed by OpenVMS and the LAN Manager server. Keep this in mind when changing the password of an externally- authenticated hostmapped user. _____________________________________________________ Password synchronization is enabled by default for externally-authenticated OpenVMS users. You can selec- tively disable it. Refer to the chapter Managing System Access in the OpenVMS Guide to System Security, for more information on how to selectively disable this feature. The keywords in the LANMAN.INI file for controlling user passwords are described in Section 3.6. Digital recommends that the keyword values be set to default conditions, as described in Table 3-4, to ensure external authentication is enabled properly. 3.7.1.5 External Authentication Over a Network External authentication cannot occur if a network connection is required for external authentication and the network is down. However, privileged users can enter the /LOCAL_PASSWORD qualifier after their OpenVMS user name at the login prompt to specify local authentication. Users should specify their OpenVMS user names and passwords when using the /LOCAL_PASSWORD qualifier. Because using the /LOCAL_PASSWORD qualifier effectively overrides the security policy established by the system manager, it is only allowed under the following conditions: o When the user's account has SYSPRV as an authorized privilege. This allows the system manager to gain access to the system when the network is down. o When Bit 1 is set in the SYS$SINGLE_SIGNON logical name, which allows nonprivileged users who are normally externally authenticated to log in locally. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-33 Refer to the OpenVMS Utility Routines Manual for more information about the /LOCAL_PASSWORD qualifier to the LOGINOUT command. 3.8 OpenVMS Operating System Delta Time Restriction OpenVMS versions prior to V7.1 have a documented delta- time restriction that may cause a serious error in the PATHWORKS for OpenVMS software, such as wrong file creation dates, beginning on or around 19-MAY- 1997. Digital Equipment Corporation has provided ECOs (Engineering Change Orders), that remove the delta-time limit. Digital Equipment Corporation strongly recommends that all customers running the affected versions of OpenVMS install the appropriate ECO, as follows: Table 3-5 OpenVMS Operating System Versions and ECO Kit __________Names___________________________________________ For_these_versions_of_OpenVMS:__Install_this_ECO_kit:_____ OpenVMS Alpha Version ALPLIBR05_070 6.1 through Version 7.0, including: - V6.1 - V6.1-1H1 - V6.1-1H2 - V6.2 - V6.2-1H1 - V6.2-1H2 - V6.2-1H3 - V7.0 (continued on next page) 3-34 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server Table 3-5 (Cont.) OpenVMS Operating System Versions and __________________ECO_Kit_Names___________________________ For_these_versions_of_OpenVMS:__Install_this_ECO_kit:_____ OpenVMS VAX Version 5.5 VAXLIBR06_070 through Version 7.0, including: - V5.5 - V5.5-1 - V5.5-2 - V5.5-2HW - V5.5-2H4 - V5.5-2HF - V6.0 - V6.1 - V6.2 - VAX V7.0 __________________________________________________________ ________________________Note ________________________ Systems running OpenVMS VAX Version 7.1 or OpenVMS Alpha Version 7.1 are not impacted and do not need to install the ECO. _____________________________________________________ 3.9 Support for Large FAT Container Files The maximum FAT container size is 4 gigabytes (GB). In addition to the sizes supported in previous versions of PATHWORKS for OpenVMS, you can use ADMIN/PATHWORKS or PCDISK to create FAT containers with the following sizes: o 768MB o 1GB o 1.5GB for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-35 o 2GB o 3GB o 4GB If the amount of free space available on a FAT share is greater than 2 GB, it will be shown as 1.99 GB, in order to remain compatible with older DOS applications. Use the FAT Volume dialog box, available under the Utilities menu in ADMIN/PATHWORKS to create these containers. ADMIN/PATHWORKS creates containers fully allocated to the maximum size of the container. Use PCDISK to create containers with minimum allocation, which makes it possible to create a 4GB container with as little allocation as 256MB. After 256MB of data has been written to the 4GB share, the allocation is extended, eventually reaching its maximum allocation of 4GB. This behavior is identical to other size FAT containers created using PCDISK with a minimum allocation. The minimum allocation for each file or directory in a FAT container depends on the cluster size: __________________________________________________________ For these contain- ers...______The_minimum_allocation_is...__________________ 3 or 4 GB 64K 1.5 or 2 32K GB 768 MB or 16K 1_GB______________________________________________________ Therefore, large FAT containers may only be appropriate for shares that contain large files. 3-36 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3.10 Implementing a Wide Area Domain Using TCP/IP This section describes how to set up a wide area domain using the TCP/IP transport. PATHWORKS for OpenVMS provides this capability through the use of the LMHOSTS file. This file contains a list of nodes (server members and domain controllers) from geographically disperse sites, which are synchronized by the primary domain controller and accessible to clients in the server's domain. The LMHOSTS file allows the PATHWORKS for OpenVMS server to participate in a Windows NT Wide Area Domain. Unlike a Windows NT server, PATHWORKS for OpenVMS does not support remote LMHOSTS files (called into the NT LMHOSTS file using #INCLUDE). To include the same files as a Windows NT server, copy the files to the PATHWORKS server and manually add the entries into the PATHWORKS server LMHOSTS file. 3.10.1 Planning and Setup To implement the TCP/IP Wide Area Domain, create the LMHOSTS file on the PATHWORKS for OpenVMS server. You can create the file at any time; as long as the LMHOSTS file exists, users can establish connections to any server list in the file using TCP/IP connections. To disable wide area capabilities, rename the file to any name other than LMHOSTS. To create the LMHOSTS file, you must first determine the nodes in the Wide Area Network that are in the same domain. When you include a node and its domain in the LMHOSTS file, the primary domain controller replicates the user account database on that node and keeps it up to date. If you omit a node, it may have a user account database that may become out of date. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-37 3.10.2 LMHOSTS Directory and Syntax You can implement a Wide Area Domain by creating the following file: PWRK$LMROOT:[LANMAN]LMHOSTS. ________________________Note ________________________ The LMHOSTS file has no file extension. _____________________________________________________ The LMHOSTS file contains a list of nodes (servers and domain controllers). You specify the following line for each node: address nodename #PRE #DOM:domain_name Where: o address is an Internet address of form x.x.x.x, where x is a decimal number from 0 to 255. o nodename is a name from 1 to 16 characters long, and may include a control character. (The format of a control character is \0Xnn or \nn, where n is a hexadecimal digit. To preserve the casing of the characters, enclose the nodename in double quotation marks. If the nodename is not enclosed in quotes, the alphabetic characters are set to uppercase before the nodename is loaded into cache (see parameter #PRE) or used for matching. If the node name includes a control character in the last byte, you should include blank characters to explicitly control the placement of the control character. When the name is less than 16 characters in length, it is padded out with blank characters. Examples of Node Names 1. hydral 2. "hydral\0X03" 3-38 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3. "hydral \0X03" In Example 1, the node name will be interpreted as uppercase and will be padded with blank characters. In Example 2, the node name will not be interpreted as uppercase, will be padded out with blank characters for bytes 8 through 16. In Example 3, the node name will not be interpreted as uppercase, and no padding needs to be inserted because blank spaces are already included in order that the control character resides in byte 16. o #PRE is an optional parameter that indicates that the entry should be preloaded into the cache. o #DOM:domainname is an optional parameter that specifies the domain for the node. For example, the following entry might be included in the LMHOSTS file: 12.13.14.15 server #PRE #DOM:PATHWORKS This entry would result in NetBIOS name SERVER with Internet address 12.13.14.15 being preloaded into the cache. The NetBIOS name SERVER would be available for matching, and the NetBIOS name PATHWORKS (the name of the domain) would be available for matching. 3.10.3 Managing the LMHOSTS File To change the list of available nodes, edit the file at any time. Domain names are resolved by checking the LMHOSTS file. 3.10.3.1 LMHOSTS Log File If there are any errors trying to open or close the LMHOSTS file, the error is recorded in the following file: PWRK$LMROOT:[LOGS]PWRK$KNBDAEMON_nodename.LOG This file is open and being written to while PATHWORKS is running. To close the file, you must stop the PATHWORKS server. for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 3-39 Each error is logged the first time the problem is encountered. The error is logged again only if the error message is removed and then reoccurs (for example, if the log file is deleted and recreated and then the error occurs again). 3.11 Time Zone Setup Required for OpenVMS V7.0 For OpenVMS V6.2, the time zone could be set as an optional feature. With Version 7.0, the time zone setup is required. If the time zone is not set up, the PATHWORKS server software fails to start. To set the time zone, run the following command procedure: $ @SYS$MANAGER:UTC$TIME_SETUP.COM 3.12 OpenVMS V7.1 Requires Patch If the customer is running OpenVMS V7.1 of VAX or Alpha, it is required that they install the DEC C RTL patch at the level of VAXACRT02 (or higher) and ALPACRT02 (or higher) on VAX and Alpha respectively. 3-40 Guidelines for Using the PATHWORKS V5 for OpenVMS (LAN Manager) Server 4 ________________________________________________________________ Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) The problems described in this chapter are corrected in PATHWORKS V5.0F for OpenVMS (LAN Manager) and future ECOs. 4.1 NETBIOS Names Cannot Be Resolved Over DECnet When the Controller is FDDI Problem: PATHWORKS is unable to resolve a NETBIOS name on the DECnet transport when the network controller is FDDI. Instead, the DECnet node name is used when defined in the local database. Solution: This problem is corrected in V5.0F and later versions. During initialization the NETBIOS process determines whether the network controller is a FDDI device. If it is a FDDI device, the DECnet physical address is used instead of the default hardware physical address in its responses. 4.2 Session Context Switch Problem Caused by Windows NT V4.0 SP2 Problem: When the client is a Windows NT 4.0 workstation, in addition to the real session, the Windows NT 4.0 workstation requests an extra session that has a null username. The PATHWORKS for OpenVMS (LAN Manager) server allows two sessions to be established and switches the context of the two sessions. Solution: Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) 4-1 This problem is corrected in V5.0F and later versions. ________________________Note ________________________ The extra null user session problem is caused by the Windows NT 4.0 workstation. _____________________________________________________ 4.3 Server Fails with an Access Violation While Displaying Sessions Problem: Using ADMIN/PATHWORKS to enumerate sessions may result in an Access Violation (ACCVIO) error if the number of sessions is very large (that is, greater than 800). Solution: This problem is corrected in V5.0F and later versions. 4.4 Server Loops on Session Delete Problem: In rare situations where network errors cause packets to get lost and when sessions were forced to be deleted, it was possible for the server to enter a compute-bound loop for some time. Solution: This problem is corrected in V5.0F and later versions. The software was corrected by adjusting the time interval between attempts to delete sessions. 4.5 Server Buffers Exhausted Problem: o In rare situations where network errors cause packets to get lost, it is possible for the software to enter a synchronous wait state, which eventually causes PCOMS buffer space to become exhausted. Netlogon requests, replication, and alert messages are not handled during this time. 4-2 Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) o For each findname request on the DECnet transport, the findname is done synchronously. This can cause the software to enter LEF state for a short time. Solution: This problem is corrected in V5.0F and later versions. This operation is done asynchronously now, so that other operations can be handled. 4.6 OpenVMS Cluster Netlogons Fail Problem: In a OpenVMS cluster environment netlogon will not start occasionaly. Solution: This problem is corrected in V5.0F and later versions. Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) 4-3 5 ________________________________________________________________ Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 The problems described in this chapter are corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 and future versions. 5.1 Error in Flow Control Problem: The daemon process could be stalled on very busy TCP/IP networks because of a stalled stream situation. Solution: This problem is corrected in V5.0F ECO1. The stream is now correctly resumed. 5.2 LAN Manager Server Crash in ODS2Fidcache Problem: The LMSRV process crashes with the following error: FID cache corrupted queue links. Solution: This problem is corrected in V5.0F ECO1. 5.3 Server Crash in PFS_setextattr When Called From Copyfile Problem: The server crashes in PFS_setextattr due to an unnecessary sanity check. Solution: This problem is corrected in V5.0F ECO1. in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 5-1 5.4 Time Zone Replication Problem Problem: When the primary domain controller (PDC) is in a different time zone than the backup domain controller (BDC), and you change the role of the BDC to standalone server, then the BDC password will be changed at each LOGONQUERY interval (every 900 seconds). Solution: This problem is corrected in V5.0F ECO1. 5.5 Invalid Time Conversion in calloutadd Problem: The PWRK$LMSRV process enters a compute-bound loop if the expiration date of a LAN Manager user account is far in the future. Solution: This problem is corrected in V5.0F ECO1. 5.6 ADMIN/PATH Hangs Problem: Using PATHWORKS V5.0F for OpenVMS (LAN Manager), some customers experienced a situation where the ADMIN /PATHWORKS process would hang after the login screen. A patch was made available to those customers to fix that problem. Solution: A permanent fix for this problem was not completed in time to be included in ECO1. Customers experiencing this problem may contact their DIGITAL support representative to receive a new patch for the PATHWORKS V5.0F (ECO1) LAN Manager server. 5-2 Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 5.7 Replication Stops Due to Windows NT Bug Problem: Replication stops when Windows NT calculates the number of UAS entries incorrectly in its NetAccountSync responses. Solution: This problem is corrected in V5.0F ECO1. 5.8 Panic in GC.C Problem: The PWRK$LMSRV process exits unexpectedly after writing a line similar to the following in the PWRK$LMSRV_nodename.LOG file: PANIC: aborting from module LM$BLD_ROOT:[LM.UTIL.SRC]GC.C;1 at line 421! Solution: This problem is corrected in V5.0F ECO1. 5.9 DIGITAL PATHWORKS V5 for OpenVMS (LAN Manager) Should Not Assign CU Licenses for V4.1 Clients Problem: V5.0F inadvertently assigns a CU license (PWLMVMSCU05.00) for V4.1 clients, if CU licenses are available. Solution: This problem is corrected in V5.0F ECO1. With this correction, V4.1 clients do not unnecessarily consume server-based CU licenses. 5.10 License Server t_accept/t_listen Errors Problem: When the license server is using the DECnet transport and it is busy, it fails to handle some client license requests. A series of messages is written to the log file (PWRK$LOGS:PWRK$LICENSE_SERVER_nodename.LOG) similar to the following: in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 5-3 18-AUG-1997 01:08:58.00 MESSAGE: t_accept failure t_errno is 9 18-AUG-1997 01:08:58.00 MESSAGE: listener state is 4 accepter state is 2 18-AUG-1997 01:08:58.00 MESSAGE: t_look error on the listener fd is 16 t_look error is on accepter fd is 0 Solution: This problem is corrected in V5.0F ECO1. 5.11 Use of Logical LICENSE_SERVER_INHIBIT Has Been Changed Problem: In PATHWORKS V5.0E ECO1 and earlier versions, defining the logical PWRK$LICENSE_SERVER_INHIBIT to "0" on a system would inhibit the License Server from running on that node. The value of the logical has changed for V5.0F. Solution: In V5.0F and later versions, you must set the logical to a non-zero value, such as 1. 5-4 Problems Corrected in DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager), ECO1 6 ________________________________________________________________ Restrictions and Limitations This chapter describes restriction and limitations on using the current version of PATHWORKS V5 for OpenVMS (LAN Manager), and troubleshooting suggestions. ________________________Note ________________________ If you are running PATHWORKS V5 for OpenVMS in a LAN together with Windows NT servers, refer to Section 6.1.2. _____________________________________________________ 6.1 System and Network Configuration Restrictions The following sections describe restrictions specific to certain hardware configurations. 6.1.1 OpenVMS Cluster Restrictions The following section describes restrictions specific to servers running in an OpenVMS cluster. 6.1.1.1 Changing the PATHWORKS Cluster Alias Prevents Net Logons Problem: If you change the PATHWORKS cluster alias after the server has been configured to run in a domain, subsequent attempts to connect to the server from the clients will fail. The clients receive an error message indicating the alias name is not a member of the server group. Solution Restrictions and Limitations 6-1 If you change the cluster alias using the PWALIAS field, you must reconfigure the server in order to allows clients to connect to the server using the new cluster alias. To configure the server so that the cluster alias is included in the server group information, enter the NET ACCOUNTS/ROLE command. 6.1.2 Windows NT Interoperability Restrictions 6.1.2.1 Server Manager Does Not Recognize OpenVMS Path Names Problem: You cannot create a share on an OpenVMS server with the Windows NT Server Manager, because the Windows NT system does not recognize the path name that the OpenVMS server returns. Solution: Use the ADMIN/PATH utility to perform management tasks that require OpenVMS path names. 6.1.2.2 Print Manager Option Does Not Work Problem: If you choose Printer => Server Viewer from the Windows NT Print Manager, the following error message is displayed: Could not access \\server_name: The printer name is invalid. Solution: None available. We should revise the next section based on input from PATHWORKS client group. You can no longer get PATHWORKS for Windows NT. You must get PATHWORKS 32. Does this apply to PATHWORKS 32? 6.1.2.3 PATHWORKS Windows NT V4.1B Client Fails to Get License Over DECnet Problem: PATHWORKS Windows NT V4.1B client fails to obtain a license over DECnet. Solution: 6-2 Restrictions and Limitations If you fail to get a license with the released version of PATHWORKS for Windows NT V4.1B, perform the following sequence in response to the Windows NT command prompt: 1. Check the status your DECnet remote node database, using the following command: NCP LIST KNOWN REMOTE Known Remote-Adapter Permanent Summary as of Wed Jan 04 16:39:52 1995 Remote-Adapter Node Object Remote-Adapter in hex PWRK$LSRVRNODE 13.13 (SRVRNODE) 0 You should see an entry for your license server that starts with PWRK$Lnodename, followed by the address, then the name of the server, and an object number of 0. 2. If the object number is not 0, remove the entry using the following command: NCP PURGE REMOTE PWRK$Lnodename If no entry is displayed or you removed an erroneous entry with the above NCP command, then add a license server entry with the following command: NCP DEFINE REMOTE-ADAPTER-NAME PWRK$Lnodename NODE address OBJECT 0) 3. For DOS, run the PWLICLM.EXE program and request the license again. After PWLICLM.EXE finishes, verify that the requested license has been obtained. For example, use the following command: PWLICLM /SHOW 6.1.3 OS/2 Access and Connections Restrictions 6.1.3.1 OS/2 Version 2.1 Application Files Cannot Be Copied to FAT Volume Problem: Because some OS/2 Version 2.1 application files use extended attributes, you cannot copy them to a FAT container file. In this case, the following error message is displayed: SYS0266: The specified file was not copied. Solution: Restrictions and Limitations 6-3 Copy OS/2 Version 2.1 application files that use extended attributes to an ODS-2 share. 6.1.4 PATHWORKS for VMS (Macintosh) Restrictions 6.1.4.1 Interacting with PATHWORKS for VMS (Macintosh) V1.2 Problem: The LAN Manager V5 server may generate a directory or file that the DECshare file server has a problem accessing. This interaction problem is caused by a known bug in the DECshare file server when it accesses files with an Access Control List (ACL) larger than 512 bytes, and directories with an ACL larger than 1024 bytes. Solution: Upgrade to PATHWORKS for VMS (Macintosh) V1.3. 6.1.4.2 Installing Macintosh Server Redefines ADMIN Command Problem: Installing PATHWORKS for VMS (Macintosh) overrides the PATHWORKS for OpenVMS (LAN Manager) definition for the ADMIN command, making the ADMIN/PATH utility, the Configuration utility (ADMIN/CONFIG), and the PATHWORKS Event Logger (ADMIN/ANALYZE) unavailable. Solution: To make the PATHWORKS for OpenVMS (LAN Manager) ADMIN utilities available, use the SYS$UPDATE:PWRK$INSTALL_ COMMANDS command procedure to restore the previous definition of the ADMIN command. 6.1.4.3 Shares Common Between Macintosh Server and LAN Manager Server Problem: The PATHWORKS for Macintosh server encounters problems with DECshare volumes that are also LAN Manager shares. A client running Windows 95 or Windows NT can copy the directory tree from one LAN Manager share to another. In the process, these clients copy the MSAF$CAT file, which is used as a control file by the Macintosh server. The copied MSAF$CAT files will not be in a format and organization that the Macintosh server recognizes. 6-4 Restrictions and Limitations If both shares are set up as Macintosh volumes, when the Macintosh server accesses the unrecognizable MSAF$CAT files in the process of mounting DECshare volumes, it sends errors to the file server log and fails to mount volumes, preventing services from starting. Solution: Macintosh volumes that are also used as LAN Manager shares should not be included in directory trees copied using Windows 95 or Windows NT. 6.1.5 Windows for Workgroups Interoperability Restrictions 6.1.5.1 PATHWORKS LAN Manager Server Domains are Invisible to Windows for Workgroups File Manager Browser Problem: When you use the Windows for Workgroups File Manager to browse existing domains, the V5 domains are not displayed (by default) in the scroll region of the File Manager's Connect Network drive, Show-shared-directories menu. If you manually enter the V5 server name, the server's name and domain are displayed properly and the shares are listed in the Show-shared-directories menu. However, when you select the domain name, the other servers do not show up and the following message is displayed: The list of servers for this workgroup is not available Solution: To find the shared directories of any V5 server, reenter the server's name. 6.1.6 Transports Restrictions 6.1.6.1 DEFZA FDDI Controller Is Not Supported in PATHWORKS for OpenVMS The DEFZA FDDI controller is not supported with PATHWORKS for OpenVMS Versions 5 and later. Digital recommends that you use the newer DEFTA, which is supported and provides better performance. Restrictions and Limitations 6-5 6.1.6.2 LAN Manager Server Does Not Support the Ordering of Network Transports Problem: The PATHWORKS server does not let you specify the order in which network transports operate. The server uses transports in the following order: 1. DECnet 2. NetBEUI 3. TCP/IP Solution: None available. 6.1.6.3 Mail Server Works with DECnet Only Problem: 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 Solution: None available. 6.1.6.4 Problem Getting License After Client Changes Transport Protocol Problem: A client that previously has obtained a license using one transport, may fail to get a license after changing the transport protocol that it is running. Solution: 1. Delete the file C:\PWV50\PWLICLM.DAT 2. Use the License Manager to revoke the client's license. 3. Reboot the client. 6-6 Restrictions and Limitations 6.1.6.5 Clients Disconnect When Using DECnet-Plus Versions 5.6 Prior to ECO10 Problem: Running PATHWORKS for OpenVMS with a version of DECnet-Plus earlier than V5.6 ECO10 may cause problems, such as clients losing their connections because the non-paged pool is used up. Solution: Install DECnet-Plus V5.6 ECO10 (also known as DNVOSIB_ECO10056) or later. 6.1.7 Configuration Failures and Performance Problems Due to Physical Memory Shortage Problem: The percent of physical memory used when running both the LAN Manager and NetWare servers may cause configuration failures and performance problems. Solution: When you configure the LAN Manager server on systems running both the LAN Manager server and the NetWare server, set the the percent of physical memory used by the LAN Manager server below the default of 80 percent. Digital recommends that you set the percent of physical memory used by the LAN Manager server to 50 percent or lower. 6.2 Installation, Configuration, and Startup Restrictions The following sections describe restrictions in in- stalling, configuring, and starting PATHWORKS for OpenVMS, as well as upgrading from a previous version of the server. 6.2.1 DEINSTALL Procedure is Broken The command procedure PWRK$DEINSTALL that was distributed with PATHWORKS V5.0C for OpenVMS (LAN Manager), ECO3, does not function properly. Digital recommends that you use the PWRK$DEINSTALL procedure from a previous kit if you want to deinstall PATHWORKS V5.0C for OpenVMS before you install a later version of PATHWORKS for OpenVMS. Restrictions and Limitations 6-7 6.2.2 Configuration Utility (ADMIN/CONFIG) Restrictions 6.2.2.1 ADMIN/CONFIG May Provide an Inappropriate Default for the Open File Limit Problem: By default, the maximum number of open files allowed for all clients is based on an average of 12 files for each client currently connected. When an open file request would exceed this maximum, the following message is written to PWRK$LMLOGS:PWRK$LMSRV_node.LOG: date time Warning: data cache open-file limit has been reached The server does not satisfy the open request and the error is reported to the client. However, some utilities, like XCOPY, do not report the error even though the requested file has not been opened. Solution: You can change the value that specifies the average number of open files, in the PWRK$LMROOT:[PARAMS]PWRK$CURRENT.DAT file. Add the following line in the [CONFIG] section of the file: [CONFIG] FILES_PER_CLIENT = new_value New_value specifies the new average number of files that can be open at one time. On an OpenVMS cluster, this value pertains to the OpenVMS cluster as a whole. To specify the average for a single node in a OpenVMS cluster, add the line to the node-specific section of the file. For example, look for the section [NODE_name] section, where name is the node name. Add the FILES_PER_CLIENT parameter and value below the [NODE_name] line. 6.2.2.2 ADMIN/CONFIG Appears to Set Parameters, But Does Not Problem: If you modify any parameter in the Advanced Configuration Parameters dialog box, choose the OK button, choose the No button (to reject the configuration and leave the screen), and then reenter the screen, it displays the parameter as changed when, in fact, it was not. 6-8 Restrictions and Limitations To change parameters using the Advanced Configuration Parameters dialog box, you must choose the OK button and accept the configuration. Solution: To clear the display and reset the Configuration utility, exit and reenter the utility. 6.2.2.3 ADMIN/CONFIG Allocates Insufficient Resources to Support Any Clients Problem: After you successfully configure the server, it may not start, reporting that there are insufficient resources to support any clients. PATHWORKS requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for non-PATHWORKS use, and these resources have already been consumed when PATHWORKS is started, there may be insufficient resources left for PATHWORKS to support any clients. Solution: Before you run the Configuration utility, make sure that all software that will run concurrently with PATHWORKS is installed and started, especially if you run TCP/IP or PATHWORKS for OpenVMS (NetWare). If you still experience problems, examine the following file to determine the system resource that needs to be increased: PWRK$LOGS:PWRK$CONFIG_ERROR_node.LOG To increase the resource, make the appropriate modifica- tions to the MODPARAMS.DAT file and then run AUTOGEN. 6.2.3 Configuration Command Procedure Restrictions Restrictions and Limitations 6-9 6.2.3.1 PWRK$CONFIG Fails to Move the PATHWORKS On-Disk Structure Problem: If the PATHWORKS on-disk structure contains directories more than eight levels deep, the PWRK$CONFIG procedure cannot move the on-disk structure to another disk because of an OpenVMS RMS restriction. Solution: Before running the PWRK$CONFIG procedure to move the PATHWORKS on-disk structure, either delete files and directories that are greater than 8 levels deep or rename them, so that the standard OpenVMS BACKUP command is able to move them correctly. 6.2.3.2 Extraneous Warning Messages During PWRK$CONFIG.COM Problem: If none of the LAN Manager transports (DECnet, NetBEUI, or TCP/IP) is configured to run, and PWRK$CONFIG is executed, the following error messages is displayed: ...Ini parameter string too short (network) ...GetCmtConfigParams: no transport specified in ADMIN/CONFIGURE ...PLG_PostEvent: failed to attach to the named pipe Solution: These messages can be ignored if you have a server system with none of the LAN Manager transports configured. To avoid the messages in the future, run the PWRK$CONFIG procedure again. When asked if you want to change the system configuration, answer YES and select at least one of the PATHWORKS transports. 6.2.4 Upgrade Utility Restrictions 6.2.4.1 Upgrade Fails to Upgrade an Environment with More than 252 Groups Problem: The Upgrade utility cannot upgrade more than 252 groups. Under LAN Manager V2.2, the maximum group number is limited to 256, where 4 of these groups are reserved for 6-10 Restrictions and Limitations ADMINS, USERS, GUESTS, and SERVERS. To help enable Domain services, the SERVERS group contains only server names. If a server upgrade reaches the 256 group limit, the server cannot run as a domain member with existing unreserved groups. However, the system can run as a standalone server in that domain. Solution: If you are running PATHWORKS for OpenVMS V4.x in a large OpenVMS cluster, Digital recommends that you use the Create Upgrade Reports option in the Upgrade utility to generate reports that can be used to assist in your migration process. Closely examine your V4.x server database and make sure it conforms to the LAN Manager group limit. If not, you may want to merge UIC groups together into one LAN Manager group, or map some groups into the groups USERS and GUESTS. Alternatively, you can elect to bypass the LAN Manager security model by enabling the OpenVMS security mode option for the V5 server and granting USERS and GUESTS full access to all shares. 6.2.4.2 The Upgrade Utility Parses Special Characters Incorrectly in Report Files Problem: The Upgrade utility incorrectly parses report files. Invalid characters for LAN Manager user names are accepted, and the exclamation point (!), valid in a LAN Manager user name, is rejected. Solution: Do not use special characters in user names that you want upgraded to LAN Manager user names. LAN Manager user names can be up to 20 characters in length and can include letters, numbers, and the following special characters: ! # $ % & ( ) - . ^ _ ` { } ~ Restrictions and Limitations 6-11 6.2.4.3 Upgrade Procedure May Fail Over DECnet with PCSA V4.2 Running Problem: If the PCSA V4.x server is running at the time the V5 server is installed, the PCSA V4.x server must be shut down prior to running the PATHWORKS Upgrade procedure in a domain over DECnet. Failure to stop the PSCA V4.x server may result in failures in the PATHWORKS V5 Upgrade procedures as well as the PCSA Mail Server. Solution: After installation, shut down the PCSA V4.x file server before running the PATHWORKS V5 Upgrade procedure or the PCSA Mail Server. 6.2.5 Server Startup Restrictions 6.2.5.1 Server Startup Slowed Down if DFS Devices are in Mount Verification Problem: When the server starts, it automatically shares all mounted devices on the system. When the server encounters a DFS device that is in mount verification state, the server waits for the mount verification process to time out. Solution: Make sure DFS is included in the following line in the LANMAN.INI file: NOAUTOSHARE = DFS 6.2.5.2 Server Fails to Start on Non-English Language Versions of OpenVMS Problem: There is a limitation in the server that causes startup to fail on any non-English version of the OpenVMS operating system. This is due to the reliance of PATHWORKS on the English language output of the DCL SHOW MEMORY command. Solution: None. 6-12 Restrictions and Limitations 6.3 Server Management Interface Restrictions The following sections describe restrictions in the ADMIN /PATHWORKS user interface and the LAN Manager Net Command Line interface. 6.3.1 Server Admin Interface (ADMIN/PATHWORKS) Restrictions 6.3.1.1 ADMIN/PATH Cannot Delete FAT Container File Using FAT Volume Screen Problem: You cannot use the ADMIN/PATH utility FAT Volume Screen to dismount or delete a FAT container file. Solution: To dismount a FAT container file using ADMIN/PATH, use the following procedure: 1. Choose View => Shared resources. The Shared Resources dialog box is displayed. a. Select "Show Hidden Shares." b. Delete (that is, stop sharing) any directories within the fat container. 2. In the list box of shared resources, highlight the FAT container file that you want to dismount and choose the StopShar button. To delete the FAT container file, use the OpenVMS DCL command DELETE. 6.3.1.2 ADMIN/PATH Defining a Share - Information Not Set Problem: If you create a share using the ADMIN/PATH utility (View => Shared resources => Add Share => OK), and mark the Admin Only field, this information is not set when the share is created. Solution: After you create the share, choose View => Shared resources => Zoom to modify the share and mark the Admin Only field to set this information. Restrictions and Limitations 6-13 6.3.1.3 ADMIN/PATHWORKS Does Not Support Mapping a Print Queue to Multiple Destinations Problem: You cannot use the Add a Printer Queue dialog box to map a print queue to zero destinations or to multiple destinations. Solution: Use ManageWORKS to perform this function. 6.3.1.4 ADMIN/PATH Fails to Set RMS Protections on Top-Level Directory Problem: When using the ADMIN/PATH utility to add a share, it prompts you to specify the default RMS protections for all files and directories stored in the share. When you do so, ADMIN/PATH fails to properly set the RMS protections on the top-level directory of the share. Solution: Use the following OpenVMS DCL command to set the RMS protection of the directory. $ SET FILE dir_name.DIR /PROT=(protection-code) 6.3.1.5 ADMIN/PATH Password Last Changed Field Changes When Displaying a User Problem: If you choose Accounts => Users => Zoom to display the View the User Account dialog box, the time shown in the Password Last Changed field changes if you zoom on a user repeatedly (in others words, alternately choose the Zoom and OK command buttons), even though you did not change the password. The time field is changed; the password is not affected. Solution: None available. 6-14 Restrictions and Limitations 6.3.1.6 ADMIN/PATH View => Users Options May Display Incomplete List of Users Problem: If you choose View => Users on a server or View => Users on a domain, some users may be omitted from the display. Solution: None available 6.3.1.7 ADMIN/PATH Add User Does Not Add Access Permissions to Personal Share Problem: If you choose Accounts => User => Add User, the following errors may be displayed in successive message boxes: Failure to add access to personal share NET2225E: The resource permission list already exists. This means that the personal share is created, but no access permissions are added for this user. Solution: Do the following to manually grant the user access permissions to the personal share: 1. Choose View => Shared Resources. 2. Mark the Show personal shares option. 3. In the list box, highlight the personal share and choose the Permit button. 4. Specify permissions as usual. For more information, choose the Help button. 6.3.1.8 ADMIN/PATH Cannot Attach to Another Server After Logging on to a Standalone Server Problem: If you run ADMIN/PATH from a privileged OpenVMS account, but do not log in as a LAN Manager user with Administrator privileges, you will not be recognized as a user in the domain. Therefore, you cannot attach to another server in that domain, even if you enter the correct password when you attempt to switch servers. Restrictions and Limitations 6-15 Solution: Log on as a LAN Manager user with Administrator privi- leges, so that you are recognized as a user on the domain. 6.3.1.9 ADMIN/PATH Leaves Extraneous File in SYS$LOGIN Problem: When you add a user account with a hostmap entry, a temporary file called PWRK_ACCT_CREATE_MESSAGES.COM is created in the SYS$LOGIN directory. This file is not deleted when ADMIN/PATH finishes using it. Solution: Periodically purge this file from the SYS$LOGIN directory of users who add accounts with the ADMIN/PATH utility. Alternatively, you can use the OpenVMS DCL command SET FILE /VERSION_LIMIT to limit the accumulation of such files. 6.3.1.10 Starting Netlogon Service Does Not Accept Options Problem: When you are using the ADMIN/PATH utility, if you choose Config => Control services, highlight the Netlogon service, and choose the Start button, a dialog box with a number of options is displayed. However, if you change any of these options, the server does not recognize the changes. Solution: Ignore the options dialog box when starting the Netlogon service. 6.3.1.11 Ctrl/Z in Help Does Not Exit to the Menu Problem: When you are using the ADMIN/PATH utility, if you press Ctrl/Z when reading online Help, you do not return to the screen from which you entered Help (as is documented online). Solution: Press the Return key one or more times to exit Help and return to the screen from which you entered Help. 6-16 Restrictions and Limitations 6.3.1.12 ADMIN/PATH Config => Control services Buttons Unavailable Problem: When you are using the ADMIN/PATH utility, if you choose Config => Control services to start a service, a dialog box is displayed that contains several buttons across the bottom (OK, Cancel, Set, Reset, ResetAll, Help). Only the OK, Cancel, and Help buttons work. They do the following: o The OK button starts the highlighted service. o The Cancel button aborts the attempt to start the service. o The Help button displays the online help associated with the screen displayed. Solution: To access the functions of the Set, Reset, and ResetAll buttons, use the corresponding Windows Net Admin interface that supports these operations. Online help is available for all the buttons. 6.3.1.13 ADMIN/PATH Message Boxes Skewed Problem: You may see message boxes with the text slightly skewed to the right and truncated. For example, if you try to add a share using a sharename that already exists, the message that is displayed should be: NET2118E: The name has already been shared. Solution: Exit the interface and type NET HELPMSG and the error number to display the full text of the error message, an explanation as to why the error occurred, and a troubleshooting suggestion. For example, to display this information for the message shown in the previous example, enter: $ NET HELPMSG 2118 The following is displayed: NET2118: The name has already been shared. Restrictions and Limitations 6-17 This sharename is already in use on this server. Choose a sharename that is not currently used on this server. To see a list of resources currently shared on this server, type: $ NET SHARE 6.3.1.14 ADMIN/PATH Utilities => FAT Volume Dialog Box is Confusing Problem: If you choose Utilities => FAT Volume to create a FAT container file, the behavior of the FAT File Operations dialog box is confusing. Assume the following sequence: 1. Highlight a disk in the Disk list box and choose the Set Dir button. 2. Type a name in the FAT Container Filename field. 3. Press until the cursor is located in Disk list box. The Create button is enabled. 4. Press until the cursor is located in the Directory/File list box. The Create button is disabled, and the FAT Container Filename field is cleared. Solution: After you type a name in the FAT Container Filename field, press the Tab key once, and then press the accelerator keys PF1 C to create the FAT container file. 6.3.1.15 UAS Device Information Changed in Host Account Box Problem: When you are using the ADMIN/PATH utility, if you choose Accounts => Users => Zoom => HostName, the Host Account: username dialog box is displayed. You can change UAF information by typing in the Device field any logical name associated with an actual device. However, if the logical name points to a root directory, the UAS information will be incorrect, preventing the user from logging in to the OpenVMS system. Solution: 6-18 Restrictions and Limitations In the Device field of the Host Account: username dialog box, always specify an actual device name, not a logical name. 6.3.1.16 Netlogon Does Not Start After PATHWORKS Cluster Alias Change Problem: After using the ADMIN/PATH utility to change the PATHWORKS cluster alias, the Netlogon service does not start; it returns the messages net 3100 and LMU 6022 and another net message stating that the alias name was not a member of the group servers. Solution: If you change the PATHWORKS cluster alias after you are fully configured to work in a domain, you must reconfigure the server with domain participation. 6.3.1.17 ADMIN/PATHWORKS Cannot Create a Queue or Destination with the System Name or Process Logical Problem: Unexpected results may occur when creating a queue or destination with the name of a system or server process logical. This is caused by a side effect of the $SNDJBC system service. It translates the logical before sending the request to the job controller. For example, creating a queue named SYS$SYSTEM or TT does not work. The result may be a queue or destination created with the translated name from the logical, an invalid queue or destination name, or an internal error, depending on the actual translation of logicals. Solution: None available. Restrictions and Limitations 6-19 6.3.1.18 ADMIN/PATH Does Not Recognize Long File Names Problem: The ADMIN/PATH utility does not recognize file names or directory names that are longer than eight characters for the file name and 3 characters for the file extension. If you create a directory with a long name (over 8 characters), the directory is not created properly. Solution: Restrict file names and directory names created with the ADMIN/PATH utility to 8 characters or less. 6.3.1.19 Using Long File Names for FAT Files The ADMIN/PATH interface does not allow file names longer than 10 characters for FAT files. If you try to enter a longer file name, ADMIN/PATH issues a warning message and fails to create the personal share name. 6.3.2 Command Line Net Interface Restrictions 6.3.2.1 Cannot Use Path Names to Reference Shares Problem: When using NET commands, you cannot use the device:pathname format to reference shares. Solution: Use the actual share names when referring to shares. 6.3.2.2 NET ACCESS Does Not Recognize the Volume Label as a Device Name Problem: The NET ACCESS command does not recognize the OpenVMS volume label as a device name. For example, when a share's location is shown as USERDISK:[PCCOMMON] (where USERDISK is the volume label for DKA300:), specifying USERDISK:[PCCOMMON] with NET ACCESS results in an error locating the directory. Solution: Use the actual device name in the file specification (for example, DKA300:[PCCOMMON]). 6-20 Restrictions and Limitations 6.3.2.3 NET PRINT Does Not Clean Up Files in the Spool Directory Problem: The NET PRINT sharename /DELETE and /PURGE commands do not clean up files in the spool directory. Solution: Use the OpenVMS DCL command PURGE to purge the spool directory. 6.3.2.4 NET SHARE printshare /DELETE May Fail Problem: Using the NET SHARE printshare /DELETE command to delete a print share may fail, displaying the following error message: NET3694: The shared queue cannot be deleted while a print job is being spooled to the queue. Solution: Use the ADMIN/PATH utility to delete the print share. 6.3.2.5 NET SHARE printshare /PRINT Does Not Create Queue from Client Problem: Using the NET ADMIN \\SERVER /COMMAND NET SHARE printshare /PRINT command from a client to create a print queue displays the following prompt: The queue does not exist. Do you want to create it? (Y/N)[Y]: If you press the Return key or enter Y to create the queue, the following error message is displayed: NET3757: No valid response was provided. Solution: From the V5 server, use the NET SHARE printshare /PRINT command to create the print queue. Restrictions and Limitations 6-21 6.3.2.6 NET SHARE - Displaying Data Greater than 64 Kbytes Problem: When displaying share data greater than 64 Kbytes, the NET SHARE command notes the problem, displays as much of the data as it can, and displays the following message: The command completed with one or more errors. This is the secondary message. The initial message (shown below) has already scrolled off the screen: LMU6130: There are more shares than can be displayed. A partial list of sharenames follows. Only the sharename itself is listed, as no resource names or comments are available. To see the complete list, use the SYS$MANAGER:PWRK$LMSHARE command procedure. Solution: Instead of the NET SHARE command, use the ADMIN/PATH utility to display share information. 6.3.2.7 NET STOP Cannot Stop the Remote Boot Service Problem: You cannot use NET STOP to stop the Remote Boot service if it is part of the initial startup (SRVSERVICES=REMOTEBOOT in LANMAN.INI), because the local PID known to the PWRK$LMMCP process is not set properly. Solution: Use the OpenVMS DCL command STOP/ID to terminate the PWRK$LMRIPL process. 6.3.2.8 NET WHO Displays Incomplete Results Problem: When you use the NET WHO command, the result may be incomplete; that is, some users may be omitted from the display. Solution: None available 6-22 Restrictions and Limitations 6.3.2.9 Error Message Not Informative Problem: If you use NET START to initiate the Netlogon service, it may fail without providing any informative message. The primary domain controller may not recognize the local server. Solution: Make sure that the primary domain controller is running. 6.4 Services Restrictions The following sections describe restrictions in using the services offered by PATHWORKS for OpenVMS. 6.4.1 Remote Boot Restrictions 6.4.1.1 Circuit Services Enabled Problem: When the remote boot server defines MOP secondary loading, it does not check to see if the DECnet circuit service is enabled. To solve this problem, enable the DECnet circuit using one of the following procedures: Solution for DECnet Phase IV: To make sure that the DECnet circuit service is enabled, enter the following command to display the state of the circuit: $ MCR NCP SHOW CIRCUIT circuit_name CHARACTERISTICS If the service state is disabled, enter the following commands to enable the service: $ MCR NCP SET CIRCUIT circuit_name STATE OFF $ MCR NCP SET CIRCUIT circuit_name SERVICE ENABLED $ MCR NCP DEFINE CIRCUIT circuit_name SERVICE ENABLED $ MCR NCP SET CIRCUIT circuit_name STATE ON ________________________Note ________________________ When entering these commands, you must be logged in through the console or another terminal that is directly attached to the server. If not, your LAT Restrictions and Limitations 6-23 session is disconnected after you execute the first command. _____________________________________________________ Solution for DECnet-Plus: Make sure that MOP is started and that the MOP circuit is enabled. To see if the MOP circuit is enabled, enter the following command: $ MCR NCL SHOW MOP CIRCUIT * FUNCTIONS For a properly configured circuit, a message similar to the following is displayed: Node 0 MOP Circuit CSMACD-0 at 1996-01-26-15:39:10.058-05:00I0.143 Status Functions = { Loop Requester , Console Requester , Load Server , Dump Server } ________________________Note ________________________ Only the Load Server function is required. _____________________________________________________ If MOP is not running, error messages similar to the following are displayed: %NCL-E-CMLSENDFAILED, error sending command request -CML-E-EMAAPROB, error returned from VMS EMA agent -NCL-E-ENTCLSNOTSUPP, entity class not supported If MOP is not running, enter the following to start MOP and configure a MOP circuit: $ @SYS$SYSTEM:STARTUP NETWORK MOP 6-24 Restrictions and Limitations Once MOP is running and a circuit is configured, make sure that the Load Server function is enabled. If the Load Server function is not enabled, boot requests cannot be serviced. To enable the Load Server function, enter the following: $ MCR NCL ENABLE MOP CIRCUIT CSMACD-0 FUNCTION = {LOAD SERVER} To start MOP automatically when DECnet starts, add the following line to your system's SYS$MANAGER:NET$LOGICALS.COM file: $ DEFINE/SYSTEM/NOLOG NET$STARTUP_MOP TRUE For more information on configuring MOP on your DECnet- Plus network, see the DECnet for OpenVMS Network Management documentation. 6.4.1.2 Server Cannot Remote Boot Token Ring Clients Problem: If you were previously running PATHWORKS V5.0 for OpenVMS and upgrade to the latest version of PATHWORKS for OpenVMS (LAN Manager), token ring clients fail to remote boot. Solution: This release of the server includes two new files, RPL.NEW and RPLMGR.NEW, which are stored in the RPL shared directory and provide support for the remote boot of Token Ring clients. If you are upgrading your server from V5.0 to a later version of PATHWORKS V5 for OpenVMS (LAN Manager), you must manually add the information to the RPL.INI and RPLMGR.INI files from the information in the RPL.NEW and RPLMGR.NEW files. 6.4.1.3 Subdirectories of the RPL and RPLFILES Shares Fail to be Backed Up Problem: The RPL and RPLFILES shares are installed at an OpenVMS directory depth of 8 levels. If any additional subdi- rectories are added to the depth of the share, OpenVMS non-image BACKUP may fail to back up all lower-level subdirectories. Solution: Restrictions and Limitations 6-25 Avoid creating subdirectories to the RPL and RPLFILES shares. 6.4.2 ADMIN/ANALYZE Utility Restrictions 6.4.2.1 Help is Not Available for the PATHWORKS Event Logger (ADMIN/ANALYZE) Problem: If you enter ADMIN/ANALYZE HELP, the utility displays all logged events. However, online help is not available for the PATHWORKS Event Logger. Solution: For detailed information about the PATHWORKS Event Logger, see the PATHWORKS V5 for OpenVMS (LAN Manager) Server Administrator's Guide. 6.4.3 Creating Logon Scripts Restrictions 6.4.3.1 RMS Protection on Specific Logon Scripts Problem: When you use the ADMIN account in the NETLOGON directory to create a logon script for a user or group, the RMS file ownership is given to the SYSTEM account. The RMS file access is granted to System and Owner. Solution: Set the RMS ownership or file protection so that the appropriate users can execute the appropriate Logon Script. 6.4.3.2 Permissions Not Set For Logon Directories Problem: When you create a LAN Manager user account, the proper permissions are not assigned to the user's logon directory if it is a subdirectory of one that is already assigned LAN Manager permissions. Therefore, the user cannot access his or her logon directory. Solution: 6-26 Restrictions and Limitations After you create the user account, use one of the following to grant the user access to his or her logon directory: o The Server Admin interface (ADMIN/PATHWORKS) o The NET ACCESS /GRANT command line command 6.4.3.3 Directories Created in PWRK$ROOT:[LANMAN.ACCOUNTS.USERDIRS] Use Host Mode Security Problem: When you use the ADMIN account and a PATHWORKS management interface to create a user directory in PWRK$ROOT:[LANMAN.ACCOUNTS.USERDIRS], the RMS file ownership is given to the SYSTEM account. Solution: Set RMS ownership and LAN Manager file permissions so that the appropriate user(s) can access the directory. 6.4.4 Auditing Restrictions 6.4.4.1 BADUSE Auditing Event Reports Uninformative Errors Problem: When you edit a server's LANMAN.INI file to enable auditing for the BADUSE event, and a user tries connecting to a nonexistent service on that server, the auditing message is logged as "Admin Priv required". This message does not accurately reflect the event that occurred. Solution: None available. 6.4.5 LAN Manager GUEST Account Restrictions 6.4.5.1 Logged in as GUEST to a Server Running LAN Manager & OpenVMS Security Problem: If you log in as an OpenVMS user with privileges, you may be logged in as GUEST and unable to perform some functions for which you have privileges, such as creating print queues. Restrictions and Limitations 6-27 Solution: Use the NET LOGON command and specify a LAN Manager account that has been hostmapped to an OpenVMS account with privileges. 6.4.5.2 LAN Manager GUEST Account Can Cause Domain Services to Fail Problem: LAN Manager domain services can only connect to servers whose LAN Manager GUEST account has no password. If a non-null password is associated with the LAN Manager GUEST account, LAN Manager domain services (such as UAS replication and Netlogon) fail unpredictably. For example, if UAS replication fails, the following type of error message is displayed: NET3210: Failed to authenticate with node, the domain controller for domain domain_name Solution: Make sure that no password is associated with the GUEST account. If a password is associated with the GUEST account, do one of the following: o Delete and recreate the GUEST account without a password. o Make sure the GUEST account password is set to NULL, which is the default setting at installation. Use the following procedure: 1. Enter the following to display the current minimum password length. NET ACCOUNTS Write down the minimum password length displayed. 2. Set the minimum password length to zero: NET ACCOUNTS /MINPWLEN=0 3. Set the guest account password to NULL: NET USER GUEST "" 6-28 Restrictions and Limitations 4. Reset the minimum password length to its original value (from Step 1): NET ACCOUNTS /MINPWLEN=n Where n is the original value. 6.4.5.3 Backward Compatibility in Effect after Domain Role Is Changed Problem: After you change the server's role to backup domain controller or member server, it continues to operate in backward compatibility mode, using the GUEST account to log on clients that use the Basic Redirector. Solution: Stop and restart the server. 6.4.6 Disk Services Restrictions 6.4.6.1 Deadlock Messages Logged when Shared Infoserver Volume Goes Offline Problem: If clients are connected to a shared Infoserver volume when it goes offline, the server repeatedly writes the following message to the server log file: EXCL_lock possible deadlock situation at line=1671 This message is written to the log file about every 15 seconds, wasting disk space. Solution: None available. 6.4.6.2 Premature Disk Full Conditions Problem: The file server may receive a disk full message when thousands of free blocks remain on the device or within the FAT container file. This occurs 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. Restrictions and Limitations 6-29 Solution: Make sure that at least 1 MB of free space is available on the device or the container file at all times. If this does not work, add the following to the PWRK$COMMON:PWRK.INI file to lower the default file extent quantity. Create this file if necessary. Note, however, that this will significantly affect the performance of file up-loading. [ODS2] create_quantity = 1 extend_quantity = 1 [FAT] create_quantity = 1 extend_quantity = 1 6.4.6.3 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 6.4.6.4 DECram Performance Problem Problem: The 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 accesses. If you omit the /NOCACHE qualifier from the MOUNT command, the XQP+ cache is 6-30 Restrictions and Limitations enabled for the RAM disk, allowing the PATHWORKS internal caches to operate effectively. 6.4.6.5 Unable to Delete FAT Container File When Using Device Logicals Problem: FAT container files that are created using a logical name to specify the device cannot subsequently be deleted. The error displayed is: -RMS-E-FLK, file currently locked by another user Solution: Do not create FAT container files using logical names for the device. Instead, use the physical device name. 6.4.6.6 Interoperating with a Shadow Set Problem: If you have shares defined on disk drives in a shadow set, you must define them in the LANMAN.INI file, as follows: o Any disk drives in a shadow set must be added to the NOAUTOSHARE list. o The virtual disk unit must be added to the AUTOSHARE list. Failure to do so results in problems if you try to add a share to these devices. For example, during the configuration procedure, you may specify the PATHWORKS on-disk structure as the destination for disk drives that are in a shadow set. In this case, you see an error message similar to the following when shares on the on-disk structure, such as ADMIN$ or PWUTIL, are referenced: SYS0003E: The system cannot find the path specified SYS0067I: The network name cannot be found. Solution: Make sure that you include any disk drives in a shadow set in the NOAUTOSHARE list in the LANMAN.INI file. Also, include the virtual disk unit in the AUTOSHARE list. Restrictions and Limitations 6-31 6.4.6.7 Interoperating with a Volume Set Problem: OpenVMS does not support direct access to any non-root volume within a volume set. Solution: To avoid violating this requirement, if you plan to have shares defined on disk drives in a bound volume set, you must define them in the LANMAN.INI file, as follows: o All disk drives in a volume set which are not the root volume must be added to the NOAUTOSHARE list. o If the volume label of the root device of the volume set is greater than 10 characters, the root volume must be added to the AUTOSHARE list. Failure to do so could result in problems when you try to add a share to the volume set. 6.4.6.8 Interoperating with a Stripe Set If you have shares defined on disk drives in a stripe set, you must define them in the LANMAN.INI file, as follows: o All disk drives in a stripe set must be added to the NOAUTOSHARE list. o The logical volume STAnnnn must be added to the AUTOSHARE list. Failure to do so could result in problems when you try to add a share to the stripe set. ________________________Note ________________________ Direct access to a component drive is not supported by either PATHWORKS or OpenVMS. _____________________________________________________ 6-32 Restrictions and Limitations 6.4.6.9 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 cause the file server to deny access to users even though they have access to the parent directory. Solution: Delete the ACLs on the files after they are restored, using the following DCL command: $ SET ACL/DELETE file-name 6.4.6.10 Using Long Volume Label for AutoShare Devices In order to use a device for shared files that has a volume label longer than 10 characters, you must include the device in the argument to the AUTOSHARE keyword in the LANMAN.INI file. The AUTOSHARE argument specifies the drive letter for client access. For example, if the device DKA100 has a volume label LONGERVOLUME, add the following line to the LANMAN.INI file: AUTOSHARE = DKA100 = "D" This line defines the device to be drive D:, which users can specify to access files on that drive. 6.4.7 Licensing Subsystem Restrictions The following sections describe limitations and restric- tions in managing PATHWORKS licenses. 6.4.7.1 Running More Than One License Server Problem: Known problems exist with versions of PATHWORKS for OpenVMS (LAN Manager) previous to V5.0E that prevents some clients using the TCP/IP transport from obtaining licenses from the license server. Digital recommends that you use only one license server per LAN; however, if you choose to use more than one license server Digital recommends that all operating license servers be upgraded to V5.0E Restrictions and Limitations 6-33 or higher. Failure to bring all license servers up to the V5.0E version level or higher can create a situation where older versions of PATHWORKS for OpenVMS (LAN Manager) software may continue to prevent clients using TCP/IP from obtaining licenses. Solution: Upgrade all operating license servers to V5.0E or higher. 6.4.7.2 License Manager Server Node Name Problem: The License Manager server name display only displays one name. The name displayed is the node name portion of the license server name that the License Manager is communicating with. LAN Manager clients connect to license servers using the name PWRK$Lnodename. NetWare clients connect to license servers using the name PWL_nodename_PNW. By default, nodename is the node or cluster on which the license server is running for both the LAN Manager and NetWare clients. There are some situations in which the nodename portion of the LAN Manager and NetWare license server names being used by a single license server may not be the same. In this case, the License Manager displays the node name portion of the LAN Manager license server name. In other cases, the node name displayed may not be the name of the node on which the license server is executing. This can occur if the license server state file was moved from one node to another. Solution: If there is any question about the node name being used by the license server, check the license server log file for the name being used by the license server. The license server logs this information when it starts up. The file specification of the license server log file is: PWRK$LOGS:PWRK$LICENSE_SERVER_nodename.LOG. 6-34 Restrictions and Limitations 6.4.7.3 License Manager User Interface Changes Video Settings Problem: When you start the PATHWORKS License Manager, it sets the terminal's video to light text on dark background. If the previous setting was different, it is not restored when you exit the License Manager. Solution: After exiting the interface, reset the terminal display manually. 6.4.7.4 License Server Not Running Using the License Manager in an OpenVMS Cluster Problem: When running the license server in an OpenVMS cluster, only one node of the cluster is the "active" license server at any one time. If the License Manager is run from an "inactive" cluster node, a message is displayed saying that the license server is not running, rather than simply not active. Solution: Run the License Manager from the node in the cluster on which the license server is active. To determine the node, examine the license server log file for each node. 6.5 DECinspect Restrictions 6.5.1 Default PATHWORKS User Accounts Deleted by DECinspect Lockdown Procedure Problem: If you run the DECinspect lockdown command procedure without modification, it deletes the PWRK$DEFAULT and PWRK$GUEST accounts. Solution: Before you run the DECinspect lockdown command proce- dure, edit it and remove the commands that delete the PWRK$DEFAULT and PWRK$GUEST user accounts. Restrictions and Limitations 6-35 6.6 Client Access and Connnections Restrictions The following sections describe restrictions in the client interface to PATHWORKS for OpenVMS. 6.6.1 Supporting Multiple Sessions from the Same Client Problem: DIGITAL PATHWORKS for OpenVMS includes support for multiple sessions from a single client. All remote management functions are modified to enable this feature. When a session delete management request is received, the server deletes not only the selected session, but all sessions from the same PC. When you use the ADMIN/PATH utility to display a session, the server displays connections from all sessions from the client to the server, even though you chose (highlighted) only one session. The other information (such as idle time, session time, and so on) is for the first connection from the client to the server. All the information on this screen (Status => Session status => Zoom) is the same regardless of the session you chose to display. Solution: None available. 6.6.2 Clients May Fail to Perform a Domain Logon Problem: The LANMAN.INI file on a PATHWORKS client contains the WRKNETS keyword in the [WORKSTATION] section. This keyword specifies the network transports that the client can use and the order in which they are used. On Enhanced Redirector clients, these network transports are represented by local area network adapter (LANA) numbers. The NET LOGON command works over LANA0 only, regardless of how many transports are loaded on the client. This may affect your ability to log on to a domain. For example, if a client runs both NetBEUI and DECnet, and WRKNETS associates NetBEUI with LANA0, NET LOGON fails if NetBEUI is not running on the server. If domain logon fails, you can still connect to servers, but you must provide a password for each session established. 6-36 Restrictions and Limitations Solution: Run all transports on the server. Alternatively, you can change the WRKNETS parameter to load a common server-client transport on LANA0. 6.6.3 Intruder Flag's Relationship to PC Connections and Logons Problem: When a PC user does not provide a correct password with a logon request, the file server logs an OpenVMS intrusion record, which indicates a possible break-in attempt. The file server also sets the intruder flag. This flag may be safely ignored; it does not affect any PC connections or logons. Solution: To delete the intrusion record, use the DELETE/INTRUSION_RECORD command. 6.6.4 Client Net Admin Fails to Handle the Devices Returned from a LAN Manager Server Problem: Using Windows Net Admin to share a directory on a V5 server may result in one of the following problems: 1. The "SYS0234-More DATA is available" error message is displayed. This occurs when the result buffer contains more than 78 bytes of return data, which exceeds the DOS limitation of 26 device letters. 2. The list of devices includes an invalid device name. This occurs when the result buffer contains a device name that is greater than a single letter. Solution: Use the ADMIN/PATH utility to perform these functions. Restrictions and Limitations 6-37 6.6.5 Unable to Connect More Than 2048 Clients to the Same Server Problem: Client connection requests fail due to a server limitation of allowing not more that 2048 clients to connect at any one time. Solution: None. 6.6.6 User Path Specified in LANMAN.INI Problem: LAN Manager supports the use of the USERPATH keyword to specify a system directory on the server to be used as a default parent directory for home directories for new user accounts. The default setting of this parameter is: PWRK$LMROOT:[LANMAN.ACCOUNTS.USERDIRS] If you use the keyword to override this default parent path, and the user home directory has not been created, the PWRK$LMDMN process will crash when attempting to create the directory. Solution: There are two possible ways to solve the problem: o Do not use userpath keyword to override the default directory setup. o If you need to redirect this setting, make sure that the user's home directory is created or exists before starting the server. 6.7 PATHWORKS for OpenVMS Interaction with Oracle Rdb Problem: PATHWORKS fails to start correctly on systems that are also configured to run Oracle Rdb (Relational Database) software. This is caused by Rdb's use of the system-wide login command procedure SYLOGIN.COM and the manner in which PATHWORKS creates subprocesses. 6-38 Restrictions and Limitations Solution: In the system login procedure SYLOGIN.COM, replace the line: $ @DECRDB$SETVER.COM with the lines: $ SET NOON $ @DECRDB$SETVER.COM $ SET ON 6.8 Log Files and Messages Restrictions The following sections describe restrictions related to log files and error messages. 6.8.1 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: None. The error message causes no problems and can be ignored. 6.9 Monitor Utility Restrictions The following section describes restrictions using the Monitor Utility. 6.9.1 Unable to Run Both CMT Data Cache Monitor and Performance Degradation on the Same Client Over NetBEUI Problem: The Client Monitor Utility (CMT) is unable to execute its data cache monitor at the same time as the Performance Degradation is running when using NetBEUI as the transport. This is due to a limitation in the NetBEUI transport on the PATHWORKS server. Restrictions and Limitations 6-39 Solution: You can run the CMT data cache monitor and Performance Degradation on separate clients. 6-40 Restrictions and Limitations 7 ________________________________________________________________ Unsupported Software This chapter describes software that is provided but not supported. 7.1 PCSA MANAGER Clone DIGITAL PATHWORKS for OpenVMS includes an unsupported utility that maps a subset of the PATHWORKS V4.x PCSA MANAGER command line commands to the PATHWORKS for OpenVMS (LAN Manager) Command Line Interface (Net commands). This PCSA Manager clone provides backward compatibility for existing site-specific command procedures. Please note the following differences between the Version 4.x PCSA Manager command line interface and the PATHWORKS for OpenVMS V5 PCSA Manager clone: Help Text The Help library has been updated to reflect changes. Privileges To communicate with the V5 server, you must run the PCSA Manager clone from a user account whose privileges include SYSPRV, CMKRNL, TMPMBX, and NETMBX. Default Location Based on Service Type In V4.x, when you add a file service with the ADD SERVICE command, the service directory is created automatically. If you do not use the /ROOT qualifier to specify the directory path, the directory location is based on the logical (PCFS$SYSTEM, PCFS$APPLICATION, or PCFS$COMMON) associated with the service type (SYSTEM, APPLICATION, or COMMON, respectively). Unsupported Software 7-1 In PATHWORKS for OpenVMS V5, no concept of service type exists. However, if you use the /TYPE qualifier, the PCSA Manager clone automatically creates the directory in the appropriate location. ________________________Note ________________________ Version 4.x logical names are defined during server startup. To use the PCSA Manager clone, make sure that the SYS$STARTUP:PCFS_LOGICALS command procedure is run as part of the PATHWORKS for OpenVMS V5 server startup. _____________________________________________________ Access Mapping The Version 4.x server supports Read, Write, and Create access permissions to a file service. The PATHWORKS for OpenVMS V5 server supports Read, Write, Create, eXecute, Delete, Attribute, and Permission access permissions to a shared directory. The following table shows how the PCSA Manager clone maps these access permissions from Version 4.x to PATHWORKS for OpenVMS V5: __________________________________________________________ Version_4.x___________PATHWORKS_for_OpenVMS_V5____________ Read Read Write Write Create Create Read, Write, and Read, Write, Create, eXecute, Create________________Delete,_Attribute,_and_Permission___ Service Names V5 service names must conform to LAN Manager limitations. That is, service names can contain up to 12 characters, including letters, numbers, and the following: ! # $ % & ( ) - . @ ^ _ ` { } ~ When you add a service, the default remark "This service was created by PCSA Manager" is included in the V5 share database. 7-2 Unsupported Software User and Group Names V5 user and group names must conform to LAN Manager limitations. That is, user and group names can contain up to 20 characters, including letters, numbers, and the following: ! # $ % & ( ) - . @ ^ _ ` { } ~ When you add a group, the default remark "This group was created by PCSA Manager" is included in the V5 user database. DIGITAL PATHWORKS for OpenVMS includes the new special groups ADMINS, USERS, GUESTS, LOCAL, and SERVERS, which you cannot add or remove. PUBLIC is no longer a special group. LAN Manager Share-level Security The PCSA Manager clone does not run with a V5 server that uses share-level security. Any attempt displays the following error message: %PCSA-E-SHARELEVEL, this interface is not allowed on a share-level server The SHOW VERSION Command In 4.x, the SHOW VERSION command polled the disk server and file servers for the version number, and then displayed it. Therefore, you could use SHOW VERSION to determine quickly whether the servers were running. You can continue to do so for the disk server, but not for the file server. PCSA MANAGER Commands The PCSA Manager clone does not support the following 4.x commands: o ADD USER o ADMINISTRATE o CONFIGURE o MENU o MODIFY USER o REMOVE USER Unsupported Software 7-3 o SET FILE_SERVER CHARACTERISTICS o SHOW FILE_SERVER COUNTERS o SHOW FILE_SERVER STATUS o START FILE_SERVER CONNECTIONS o START FILE_SERVER LOGGING o STOP FILE_SERVER CONNECTIONS o STOP FILE_SERVER LOGGING PCSA Manager Qualifiers and Parameters Table 7-1 lists the 4.x command qualifiers and parameters that the PCSA Manager clone does not support: Table_7-1_Qualifiers_and_Parameters_Not_Supported_in_V5_________ Command___________________________Qualifier________Parameter____ ADD SERVICE/DIR ATTRIBUTES FILE_LENGTH RMS_PROTECTION ADD SERVICE/PRINT FORM [NO]CONFIRM RMS_PROTECTION SPOOL DENY [/GROUP] ALIAS GRANT [/GROUP] RMS_PROTECTION ALIAS SET FILE_SERVER SERVICE ATTRIBUTES FILE_LENGTH RMS_PROTECTION SHOW FILE_SERVER OPEN_FILES CLIENT SHOW FILE_SERVER SERVICE/ACTIVE TYPE SHOW FILE_SERVER SERVICE ALIAS /AUTHORIZED SHOW FILE_SERVER SERVICE [NO]FULL /REGISTERED_____________________________________________________ 7-4 Unsupported Software 7.2 The PWRK$DEFINE_COMMANDS Command Procedure PWRK$DEFINE_COMMANDS defines unsupported commands you can use to run V5 server utilities and command procedures. To run PWRK$DEFINE_COMMANDS, enter the following at the system prompt: $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS To make sure that PWRK$DEFINE_COMMANDS is run automat- ically each time you login, enter the following line in your login script: $ @SYS$STARTUP:PWRK$DEFINE_COMMANDS The following table describes each command that PWRK$DEFINE_ COMMANDS defines, and where to get more information, if available. ________________________________________________________________ Command_____Description________________Where_Documented_________ PCDISK Manages DOS files stored PATHWORKS for VMS 4.x in a FAT container file Server Administrator's on the server. Command Reference PWLICENSE Counts the number of Server-Based CA licenses in use. PWSHOW Displays all currently Server Installation and running V5 server Upgrade Guide (as the processes. PWRK$SHOWSYS procedure) PWSTART Starts the V5 server. Server Installation and Upgrade Guide (as the PWRK$STARTUP procedure) Unsupported Software 7-5 ________________________________________________________________ Command_____Description________________Where_Documented_________ PWSTOP Stops the V5 server. Server Installation and Upgrade Guide, Server Administrator's Guide (as the PWRK$SHUTDOWN procedure) PWUPGRADE Server Upgrade utility. Server Installation and Upgrade Guide (as the PWRK$UPGRADE procedure) PWVERSION Lists the currently installed PATHWORKS executable images and the version number of each. SETINI A configuration procedure "How to change default that displays a list settings" under of default server Configuring the Server in configuration settings, Chapter 2 of the Server which you can change. Installation and Upgrade Guide SHOWINI Unsupported command line Online (type SHOWINI HELP interface that lets you at the system prompt) display keyword values defined in sections of the LANMAN.INI file. You can also create DCL symbols for keyword values, which you can use in DCL command ____________procedures._________________________________________ 7-6 Unsupported Software 7.3 Displaying Permissions DIGITAL PATHWORKS for OpenVMS does not support the option to display permission information for a device. This includes the option to view "Other Permission" using Windows Net Admin, or the Command Line Net Interface command NET ACCESS. 7.4 The NET ACCESS Command o The NET ACCESS command without parameters is not supported (except to an OS/2 server). If you enter the NET ACCESS command without parameters, the following message is displayed: Error 50 The network request is not supported o The NET ACCESS /TREE command is not supported (except to an OS/2 server). If you enter the NET ACCESS /TREE command, the following message is displayed: Error 50 The network request is not supported o To display permissions using the NET ACCESS command, you must specify a directory. 7.5 LANMAN.INI Parameters The following server LANMAN.INI parameters are not supported: Unsupported Software 7-7 [SERVER] alertsched autopath autoprofile diskalert guestacct maxchdevjob maxchdevq maxchdevs maxconnections maxlocks maxopens maxsearches maxsessopens maxsessreqs maxsessvcs maxshares maxusers netioalert numadmin numbigbuf numfiletasks numreqbuf sizreqbuf srvanndelta srvnets [UPS] batterytime cmdfile messdelay messtime recharge signals voltlevels [REMOTEBOOT] configfile 7-8 Unsupported Software