DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: DIGITAL PATHWORKS V6.0A for OpenVMS SPD 30.50.24 (Advanced Server) and DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager) INTRODUCTION This Software Product Description describes two separate products that provide similar PC server capabilities: o PATHWORKS V6.0A for OpenVMS (Advanced Server) o PATHWORKS V5.0F1 for OpenVMS (LAN Manager) Though similar, these products are based on different versions of the LAN Manager protocol and require different versions of OpenVMS. o PATHWORKS V6.0A for OpenVMS (Advanced Server) is based on the current networking technology available with Microsoft[R] Windows NT[TM] Servers. It requires OpenVMS V7.1 and will run on any VAX[TM] or Alpha system that supports OpenVMS V7.1. o PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is based on LAN Manager V2.2 technology from Microsoft and is supported on both Alpha and VAX servers running a variety of OpenVMS versions. Both products are distributed in one package, and one license is valid for both products. This Software Product Description (SPD) has three sections: o PATHWORKS V6.0A for OpenVMS (Advanced Server) o PATHWORKS V5.0F1 for OpenVMS (LAN Manager) o Software Licensing and Ordering information September 1998 AE-RD64A-TE ___________________________________________________________________ PRODUCT NAME: DIGITAL PATHWORKS V6.0A for OpenVMS (Advanced Server) DESCRIPTION DIGITAL[TM] PATHWORKS[TM] for OpenVMS[TM] (Advanced Server) is an OpenVMS layered application that provides networking functions that are compatible with the Windows NT Server - with additional features. PATHWORKS Advanced Server is based on Windows NT Server source code from Microsoft and AT&T[R]. As a server for workstations on a network, PATHWORKS Advanced Server provides file and print shares that enable a community of desktop users to share computing resources efficiently. PATHWORKS Advanced Server can function as a simple file and print server for a small, isolated community of users or as the foundation of a large network distributed over a wide geographical area. PATHWORKS Advanced Server represents the newest generation of LAN Manager systems technology. It enhances the LAN Manager functionality by incorporating the latest Microsoft technology to deliver powerful new features for network administration and enhanced security. PATHWORKS Advanced Server can operate independently or in cooperation with systems running Windows NT Server software. FEATURES PATHWORKS Advanced Server adds a new dimension to general purpose OpenVMS systems. In addition to providing traditional support for business, scientific, and engineering applications, PATHWORKS Advanced Server allows an OpenVMS system to appear to LAN Manager clients as a Windows NT Server. The major features of PATHWORKS Advanced Server are described in the following sections. 2 File Services PATHWORKS Advanced Server provides LAN Manager-based clients with a remote file system that appears as a transparent extension of the client system's local computing environment. PATHWORKS Advanced Server file shares are based on Microsoft's Advanced Server V3.0 SMB (Server Message Block) protocols. Each file stored in a file service is stored as an OpenVMS file in Record Management Services (RMS) format. Three types of RMS file or record formats are allowed and supported on each volume: o Sequential stream o Sequential fixed length record (512 bytes per record) o Sequential undefined Files stored in a file service are accessible to PC clients, to OpenVMS users, and to applications that can interpret the content and organization of a file written by the client application. Multiple LAN Manager clients can concurrently access files stored on the server's disk through the file access modes and byte-range locking support provided by PATHWORKS Advanced Server. PATHWORKS Advanced Server lets network users share local OpenVMS files. You can use discretionary access controls on each file and directory to specify the groups and users that can access files, to define the levels of access that each group or user is permitted, and to control auditing supported by Windows NT-like security. Additional security is provided by OpenVMS file and directory protections. Print Shares PATHWORKS Advanced Server software lets DOS, Windows[R], Windows NT, Windows 95[R], OS/2[R], and OpenVMS users share printers connected to VAX computers, Alpha computers, or OpenVMS cluster systems, as well as network-based printers such as LAT[TM] printers and DIGITAL PrintServers[TM]. Print shares are supported in local area network (LAN) and wide area network (WAN) environments. PC clients can print files from the DOS, 3 OS/2, Windows, Windows 95, and Windows NT operating systems as well as from PC applications. Multiple print shares can be defined for a single printer. For example, separate services can be created for landscape-mode printing and portrait-mode printing. Similarly, separate services can be created for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer. PATHWORKS Advanced Server supports the DECprint[TM] Supervisor (DCPS) for OpenVMS product, which provides PostScript[R] and DEC[TM] ANSI printing to selected industry-standard PostScript printers. Sharing of Network Resources by Heterogeneous Users Services provided by PATHWORKS Advanced Server are accessible to PATHWORKS clients as well as to Microsoft clients. All clients using the services of a PATHWORKS Advanced Server must be properly licensed. (For more information, see the Software Licensing section.) Files are stored on the server in native OpenVMS RMS format. This allows information stored by the PCs using PATHWORKS Advanced Server to be shared with traditional OpenVMS users. In addition, this feature allows information to be shared among all clients, including those not based on PATHWORKS technology. Concurrent file access by host appli- cations or non-PATHWORKS clients is not supported. Network Transport Support PATHWORKS Advanced Server supports DECnet[TM] (Phase IV), DECnet-Plus[TM] (formerly known as DECnet/OSI), TCP/IP, and NetBEUI network transport software. One or multiple transport stacks can work concurrently on the server. The TCP/IP transport is sold as a separate DIGITAL product and must include a PATHWORKS IP (PWIP) driver. 4 NetBEUI transport software is included with PATHWORKS Advanced Server software. Using NetBEUI transport software, LAN Manager clients can access the server in the LAN for file and print shares. See the Software Requirements section for information on supported network transport software. NETBIOS[TM] Interface Support PATHWORKS Advanced Server supports the NETBIOS interface in DECnet, TCP/IP, and NetBEUI networks. PATHWORKS Advanced Server uses NETBIOS naming services and datagram services. However, a NETBIOS programming interface is not provided. NETBIOS interface support includes the support of multiple transport stacks on a single or different network controllers. NETBIOS support under TCP/IP includes both a p-node and a b-node RFC 1001/1002 implementation. Therefore, the NETBIOS interface is supported under TCP/IP in both LAN and WAN environments. The PATHWORKS Advanced Server Configuration Manager utility allows you to select one or both of the following methods for NETBIOS name resolution for WAN support: o LMHosts file o Windows Internet Naming Services (WINS) Server Flexible Security Models The PATHWORKS Advanced Server security model accommodates both the Advanced Server security model and the OpenVMS security model. The server can be configured to use the security implementation best suited to the environment. o In Advanced Server Only mode, only the Advanced Server security model is enforced. PATHWORKS Advanced Server employs a user-level security model that provides precise control over access to shared resources, including disk devices, directories, and printers. Control is based on a password assigned to each user account and the specific access permissions defined for the resources. 5 PATHWORKS Advanced Server incorporates enhanced features that provide a high level of control over user and resource permissions and auditing. These features include support of discretionary access control permissions on individual files, directories, and resources and complete auditing capabilities. Like Windows NT Servers, PATHWORKS Advanced Server does not support share-level security and operates in user-level security mode only. o In the Advanced Server and OpenVMS security model, both the OpenVMS and Advanced Server security models are enforced. PATHWORKS Advanced Server security is enhanced with OpenVMS security. Users who require this additional security support can continue to protect their resources based on OpenVMS security. Domain Support PATHWORKS Advanced Server allows the network to be subdivided into domains (administrative groups of servers and clients). Each PATHWORKS Advanced Server can be a member of a single domain. A PATHWORKS Advanced Server can be a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC). Domains are a convenient mechanism for control- ling user access to the network and for managing large networks. A PATHWORKS for DIGITAL UNIX[R] Advanced Server can be part of the same domain as a PATHWORKS for OpenVMS Advanced Server and can be desig- nated as either the Primary Domain Controller or Backup Domain Controller. PATHWORKS for OpenVMS Advanced Server provides support for wide area domains using one or both of the following methods: o LMHosts file The presence of the LMHosts file on the PATHWORKS Advanced Server allows NetLogon services and security database replication over wide area TCP/IP configurations. This file contains a list of nodes from geographically dispersed sites synchronized by the Primary Domain Controller and accessible to clients in the server's domain. However, use of the LMHosts file for replication over extreme distances or in networks with slow transmission speeds is not recommended. 6 o WINS (Windows Internet Naming Services) Server Support for WINS Servers allows PATHWORKS Advanced Server to act as a WINS client; that is, to use the name registration and resolution facilities available from a Microsoft WINS Server across routed wide area TCP/IP networks, thus enabling WAN support from WINS for domain functions, NetLogon services, and security database replication. Trust Relationships PATHWORKS Advanced Server supports trusts. Trust relationships allow users from other domains to access resources in the local domain and local domain users to access resources in other domains. NetLogon Services A single domain-wide logon lets a user access resources on any server in a domain or on servers in other domains that trust the domain. The domain capabilities of PATHWORKS Advanced Server make it possible for a user to issue a single logon request to gain access to multiple servers in a network. The NetLogon service forces the validation of users' logon requests. The logon server that processes a request checks its copy of the domain-wide user accounts database for the username and password supplied in the logon request. Network Browser Services PATHWORKS Advanced Server can act as a Master Browser in a Windows NT network. TimeSource Services DOS, Windows, and OS/2 clients can request date and time information from the PATHWORKS Advanced Server and set the local workstation date and time to coincide with it. 7 User Environment Management Logon scripts can be used to configure MS-DOS[R] and Windows workstation user environments by making network connections and starting applications. User profiles can make workstations easier to use, as well as controlling workstation access to network resources. Server Management and Control PATHWORKS Advanced Server can be managed from either the OpenVMS server or a client workstation, using one of the following server management interfaces: o PATHWORKS Advanced Server ADMINISTER command line interface, which can be accessed from a terminal or terminal emulator. It conforms to standard DCL command syntax. o Windows NT Server administration tools, which are included in the PATHWORKS Advanced Server software kit to be installed on Windows NT workstations, Windows 95 workstations, and Windows for Workgroups workstations. These tools, including Server Manager, User Manager for Domains, and Event Viewer, allow you to administer PATHWORKS Advanced Server and Windows NT Server computers from network clients. o Windows NT Server tools, which are available as part of the Windows NT Server. o PATHWORKS Advanced Server Configuration Manager utility (a character cell interface) to manage the local PATHWORKS Advanced Server configuration. o PATHWORKS License Manager (a character cell interface) to manage the PATHWORKS License Server. These management utilities can be used to: o Manage file and printer shares, user accounts, and groups o Display and control server resources currently in use, such as active sessions, connections, and services. 8 o View context-sensitive online help that provides command syntax, options, and qualifiers for each menu item and command PATHWORKS Advanced Server can be remotely administered from PATHWORKS and Microsoft Windows client workstations. PATHWORKS Advanced Server can also be managed remotely from Windows NT Servers and PATHWORKS Advanced Servers. PATHWORKS Advanced Server Configuration Manager Utility The PATHWORKS Advanced Server Configuration Manager utility is a character cell interface that allows the user to set up and modify the server's configuration. For example, the user can configure the data cache size, the security model, the number of supported clients, the types of transports, the type of WAN capabilities, and more. Any adjustments that need to be made to the OpenVMS SYSGEN parameters to support the running of the server are automatically performed by the Configuration Manager utility. Integrating with OpenVMS PATHWORKS Advanced Server encompasses many features of the OpenVMS operating System, including OpenVMS clusters and symmetric multiprocessing. OpenVMS cluster configurations provide failover availability and extensive resource capacities by integrating multiple OpenVMS systems that can be accessed using a single cluster name. PATHWORKS Advanced Server includes support for a transport-independent PATHWORKS cluster alias NetBIOS name that allows multiple cluster members to appear as a single server to the connecting clients. This support provides higher availability. The PATHWORKS cluster alias name has a load-balancing feature that connects clients to the cluster member that is the least loaded at the time the session is established. PATHWORKS Advanced Server includes a high performance, cluster-wide distributed data cache that provides scalability in a clustered environment. PATHWORKS Advanced Server can run on both VAX and Alpha members of homogeneous or mixed architecture OpenVMS clusters. 9 Integrating with External Authentication External authentication is an optional feature that allows OpenVMS systems to authenticate designated OpenVMS users with a PATHWORKS or Windows NT username and password combination. You can set up external authentication for any OpenVMS user, mapped to a PATHWORKS Advanced Server user account. External authentication allows users to log on to the OpenVMS Operating System using their PATHWORKS Advanced Server usernames and passwords. This feature is useful to OpenVMS system managers who want to provide users with a single username and password combination to access both OpenVMS login and PATHWORKS Advanced Server. For more information about external authentication for OpenVMS, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.xx). Integrating with OpenVMS Security PATHWORKS Advanced Server provides an extension to the Windows NT security model by supporting OpenVMS security enforcement as an optional enhancement. Alerter Service PATHWORKS Advanced Server includes an Alerter Service that sends automatic alert messages to clients and users as specified in the LANMAN.INI file. Event Log Service Event logs provide valuable information about server activities. The administrator can select from several event types and can select, for each, whether successful or unsuccessful attempts at specific operations are to generate event messages. Security event messages are generated based on the audit policy specified for the Advanced Server and for files and directories. Replicator Service Windows NT Servers provide user data replication across domain controllers using the Replicator service. The Replicator service is not 10 provided on PATHWORKS Advanced Servers. Therefore, automatic replication of user files and directories on PATHWORKS Advanced Servers is not supported. Installation Utilities PATHWORKS Advanced Server is installed on the OpenVMS system using the standard VMSINSTAL procedure. An Installation Verification Procedure (IVP) is also included, which can be used to confirm that the server software has been installed properly. The installation procedure allows you to install PATHWORKS Advanced Server with the integrated license server or just the standalone license server. PATHWORKS NetWare Server The PATHWORKS for OpenVMS (NetWare) server software has been retired. This product will no longer be supported, and licenses to use this product will no longer be sold. The code for this product continues to be distributed in the PATHWORKS V6.0A for OpenVMS (Advanced Server) software kit as a convenience for those who previously deployed it and who wish to continue to use it without support from DIGITAL. If you are running the PATHWORKS for OpenVMS (NetWare) server on the same system with PATHWORKS Advanced Server, you must either: o Upgrade the NetWare server as well as the PATHWORKS Advanced Server. The NetWare server is upgraded automatically when you install PATHWORKS Advanced Server. o Remove the NetWare server software from the system before you install PATHWORKS Advanced Server. 11 Year 2000 Ready PATHWORKS Advanced Server has been tested to ensure that the product is Year 2000 ready. License Management PATHWORKS Advanced Server offers license management for client-based licenses (CCS, FPA, Designated Access, System, and CNS) and Client Access licenses, which can be used in either client-based or server-based mode. (See the Software Licensing section for details.) The license deliverables for PATHWORKS products are Product Authorization Keys (PAKs) that are then used with the OpenVMS License Management Facility (LMF). These PAKs must be loaded into an LMF database, using standard LMF procedures, on an OpenVMS system that is hosting a PATHWORKS server or is acting as a PATHWORKS License Server.[1] The two types of license management are: o Client-based license management. PATHWORKS Advanced Server provides a facility called PATHWORKS License Server that acts as a proxy for client systems that require license keys stored in the LMF database on an OpenVMS system. A single copy of the PATHWORKS License Server software provides and verifies client-based licenses or Client Access licenses being used in client-based mode by clients running LAN Manager protocols. PATHWORKS Advanced Server clients and PATHWORKS LAN Manager clients use the DECnet, TCP/IP, or NetBEUI transport. The PATHWORKS License Manager, which executes on the same node as the License Server, provides a user interface that allows the administrator to monitor client-based license usage, to manage license groups, to set alert levels, to set logging levels for licensing events, to enable or disable the License Server, and to revoke assigned licenses. ____________________ The PATHWORKS License Server is active on only a single node in a cluster. If that node goes down for any reason, the License Server is automatically activated on another cluster node that is running PATHWORKS Advanced Server. 12 The PATHWORKS License Manager is also used to preallocate licenses to specific "groups" (including the special, predefined "server-based" group described later) and to reclaim a license from a client. Each LAN needs only one active PATHWORKS License Server. (The License Server provided with PATHWORKS Advanced Server can support every kind of PATHWORKS client-based license, as well as Client Access licenses for all supported clients.) The PATHWORKS License Registrar, which executes on the same system as the file server, verifies the licenses for clients requesting access to the server functions. Clients that can produce a valid Client Access license are allowed access to the services offered by the PATHWORKS Advanced Server. o Server-based license management. PATHWORKS Advanced Server also allows client access based on the availability of Client Access licenses in the local LMF database being used in server-based mode. If a client requesting access to the server fails to produce a valid client-based license, the PATHWORKS License Registrar software checks for the availability of a valid Client Access license being used in server-based mode. If one is available, the client is allowed access. Client Access licenses can be put into server-based mode in one of two ways: - If the PATHWORKS License Server was not configured for the system where PATHWORKS Advanced Server is executing, then all Client Access licenses loaded into the local LMF database on that system will be used in server-based mode. - If the PATHWORKS License Server was configured for the system where PATHWORKS Advanced Server is executing, then all Client Access licenses loaded into the local LMF database will, by default, be used in client-based mode. 13 To allow some or all of these licenses to be used in server-based mode, use the PATHWORKS License Manager to allocate those licenses to the special, predefined "server-based" group. Licenses available in the server-based group will then be available for use in server-based mode. Note: PATHWORKS Advanced Server allows you to simultaneously use Client Access licenses in both client-based and server-based mode. However, because clients using Client Access licenses in client-based mode are already licensed to use the server software, they never consume additional Client Access licenses allocated for use in server-based mode. Accommodation of Retired Features The following features of PATHWORKS V5.x for OpenVMS are not provided in PATHWORKS V6.0A for OpenVMS: o Standalone and member server roles. PATHWORKS Advanced Server can be configured as a Primary or Backup Domain Controller. o FAT volumes. To continue to provide FAT volume access to clients, you must maintain the PATHWORKS LAN Manager server on a separate system. Files held within shares on a FAT volume must be migrated to PATHWORKS LAN Manager shares before you upgrade to PATHWORKS Advanced Server. o Backward compatibility mode. This mode is used to ease the migra- tion from PATHWORKS V4.x to PATHWORKS LAN Manager. Make sure all clients making use of this connection format are upgraded before the installation of PATHWORKS Advanced Server. o Remote Boot service. If clients depend on remote booting, you must maintain the PATHWORKS LAN Manager server on a separate system. Transfer this function to another server that supports Remote Boot service before the upgrade. o Share-level security. PATHWORKS Advanced Server manages access to all resources through user-level security. 14 o LAN Manager and creator security mode. The server can be configured for PATHWORKS Advanced Server Only security model or for PATHWORKS Advanced Server and OpenVMS security model. o PATHWORKS LAN Manager Net command line interface and ADMINISTER/PATHWORKS character cell interface. These features were replaced by the PATHWORKS Advanced Server ADMINISTER command line interface. The ADMINISTER command line interface provides automatic translation of a subset of Net commands that have ADMINISTER command equivalents. PATHWORKS Advanced Server maintains compatibility with LAN Manager client and server software. A PATHWORKS LAN Manager server: o Can be upgraded to a PATHWORKS Advanced Server o Can continue running PATHWORKS LAN Manager and act as a Backup Domain Controller, member server, or standalone server in a domain where the Primary Domain Controller is a PATHWORKS Advanced Server or a Windows NT Server computer. HARDWARE REQUIREMENTS The following systems, components, and peripherals specified are supported except as noted. 15 Processors Supported All VAX and Alpha processors supported by the OpenVMS V7.1 Operating System are also supported by PATHWORKS V6.0A for OpenVMS (Advanced Server), except for the following: GPX II MicroVAX: MicroVAX I, MicroVAX II, MicroVAX 2000, MicroVAX 3100 Model 40 and lower VAX: VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAX 11/782, VAX 11/785 VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXstation 4000 VLC, VAXstation 8000 Memory Requirements PATHWORKS Advanced Server requires a minimum of physical memory for proper installation, configuration, and execution of the software, depending on the processor type: o On Alpha systems, a minimum of 64 MB o On VAX systems, a minimum of 64 MB Note: These memory requirements are a minimum requirement only. Memory requirements can vary widely according to the server CPU, the number of clients using the server and their activities, and the number and speed of the server's disks and the other applications running on the server. For example, a typical configuration supporting a light workload (word processing or spreadsheet applications) for 50 PC users requires an Alpha system with approximately 64 MB of memory. This means that 80% of the system memory and CPU time are dedicated to PATHWORKS Advanced Server, even though some work might use less. Disk Space Requirements (Block Cluster Size=1) Table 1 provides the disk space requirements for the installation and configuration of PATHWORKS Advanced Server. By default, all entries are directed to the same disk, but each can be directed to different disks. 16 You should also plan for additional, significant disk-space requirements for items such as data files, virtual memory section files, and log files - after the product is started and in use. ___________________________________________________________________ Table 1: Installation/Configuration Disk Space Requirements ___________________________________________________________________ Alpha Item Systems VAX Systems ___________________________________________________________________ Images and command files 148,500 blocks 130,500 blocks PATHWORKS server data files 77,500 blocks 77,500 blocks Total 226,000 blocks 208,000 blocks ___________________________________________________________________ Note: Sizes are approximate; actual sizes might vary depending on the user's system environment, configuration, and software options. ___________________________________________________________________ OPTIONAL HARDWARE PostScript Printers PATHWORKS Advanced Server supports all PostScript printers supported by DECprint Supervisor (DCPS) for OpenVMS V1.4. Refer to SPD 44.15.xx for a complete list of the DIGITAL and non-DIGITAL PostScript printers supported by DCPS. DECprint Supervisor software is included with PATHWORKS Advanced Server. DIGITAL PostScript printers connected by serial lines or DECservers[TM] and printers attached directly to the Ethernet are supported. The right to use DCPS-Open software by the PATHWORKS Advanced Server is granted by your license(s) for PATHWORKS Advanced Server. 17 Note: A separate DCPS-Open license (order number QL-09MA*-AA) is required for any other use of the DCPS-Open software. Non-PostScript Printers PATHWORKS Advanced Server also supports the following non-PostScript printers: DIGITAL LA75 Companion EPSON[R] FX850 Printer DIGITAL LA210 EPSON FX1050 DIGITAL LA310 DIGITAL LA324[TM] IBM ProPrinter DIGITAL LA424 DIGITAL LJ250 Companion NEC SilentWriter[R] II Model 290 Color Printer DIGITAL LN03[TM] PLUS Network Interface Controllers PATHWORKS Advanced Server supports the following Ethernet, FDDI, and Token Ring network hardware devices: o For the TCP/IP transport, PATHWORKS Advanced Server supports the network hardware devices supported by the specific TCP/IP product. For DIGITAL TCP/IP Services for OpenVMS, refer to SPD 46.46.xx. For other TCP/IP products, contact the vendor. o For the DECnet transport using Ethernet, FDDI, or Token Ring, see the SPDs for the following products: - DECnet-Plus V7.1 for OpenVMS Alpha, SPD 50.45.xx - DECnet-Plus V7.1 for OpenVMS VAX, SPD 25.03.xx - DECnet for OpenVMS VAX and Alpha V7.1, SPD 48.48.xx o For the NetBEUI transport, PATHWORKS Advanced Server provides the same level of support for Ethernet and FDDI as the OpenVMS Operating System. For more information, see SPD 25.01.xx. 18 Note: PATHWORKS Advanced Server does not support the DEFZA FDDI controller. CLUSTER ENVIRONMENT PATHWORKS Advanced Server runs on members of OpenVMS clusters. OpenVMS cluster configurations are fully described in the OpenVMS Cluster Software Software Product Description (SPD 29.78.xx) PATHWORKS Advanced Server supports up to 31 server nodes in a cluster. In other words, no more than 31 nodes in a cluster can run PATHWORKS Advanced Server concurrently. In a typical scenario, the server is run on only a few central nodes - to exploit the cluster's shared disks and high-speed interconnect environment. In a cluster, PATHWORKS Advanced Server supports simultaneous file access by all nodes running the server. A central event log, central Advanced Server accounts, and share databases are maintained in a cluster. In a PATHWORKS Advanced Server domain, the OpenVMS cluster represents a single domain member, whether it is acting as the Primary Domain Controller or as a Backup Domain Controller. SOFTWARE REQUIREMENTS Operating System o OpenVMS Alpha Operating System V7.1 o OpenVMS VAX Operating System V7.1 For minimum hardware requirements of the operating system, refer to the Software Product Description for the OpenVMS Operating System (SPD 25.01.xx). Network Transport Software PATHWORKS Advanced Server includes NetBEUI network transport software. DECnet or TCP/IP network transport software may also be required by PATHWORKS for OpenVMS, depending on the transport used by clients requiring connections to the server, or for use of some features. 19 The following DECnet and DECnet-Plus products are supported by PATHWORKS Advanced Server: o DECnet-Plus V7.1 for OpenVMS Alpha o DECnet-Plus V7.1 for OpenVMS VAX o DECnet for OpenVMS VAX and Alpha V7.1 When PATHWORKS Advanced Server is to be used in a TCP/IP environment, OpenVMS-based TCP/IP software is required. This software must be purchased separately. The following TCP/IP transports support PATHWORKS Advanced Server: o DIGITAL TCP/IP Services for OpenVMS V4.1, V4.2 o Process Software Corporation[TM] MultiNet[R] V4.0, Rev. B o Process Software Corporation TCPWARE[R] for OpenVMS V5.1 Other PATHWORKS Server Software The following PATHWORKS server products cannot run on the same system as PATHWORKS Advanced Server: o PATHWORKS V5.x for OpenVMS. PATHWORKS V6.0A for OpenVMS (Advanced Server) can be upgraded from the V5.x server. Running the V6.0A server on a system also running the V5.x server is not possible or supported. You cannot continue to run the PATHWORKS LAN Manager software, once the PATHWORKS Advanced Server software has been installed. PATHWORKS Advanced Server cannot coexist on the same OpenVMS cluster with PATHWORKS V5.x server. o PATHWORKS V6.0 for OpenVMS. PATHWORKS V6.0A for OpenVMS (Advanced Server) can be upgraded from the V6.0 server. Running the V6.0A server on a system also running the V6.0 server is not possible or supported. You cannot continue to run the PATHWORKS V6.0 for OpenVMS (Advanced Server) software, once the PATHWORKS V6.0a for OpenVMS (Advanced Server) software has been installed. PATHWORKS V6.0A for OpenVMS (Advanced Server) cannot coexist on the same OpenVMS cluster with the PATHWORKS V6.0 server. 20 PATHWORKS Advanced Server maintains full down-level compatibility with LAN Manager client and server software. LAN Manager users can add a PATHWORKS Advanced Server to an existing network and migrate to the new technology at their own pace. A PATHWORKS LAN Manager server can be upgraded to PATHWORKS Advanced Server technology or act as a Backup Domain Controller, member server, or standalone server in a network in which the Primary Domain Controller is a PATHWORKS Advanced Server or a Windows NT Server computer. PATHWORKS Advanced Server can be deployed as a Primary Domain Controller in a network comprising other PATHWORKS Advanced Servers, Windows NT Servers, DIGITAL PATHWORKS for OpenVMS (LAN Manager) servers, or LAN Manager for OS/2 Servers. It can also act as a Backup Domain Controller for other PATHWORKS Advanced Server or Windows NT Server computers. Client Software The following versions of client software are supported for use with PATHWORKS Advanced Server: o Microsoft Windows NT workstation software V3.5 or V4.0 o Microsoft Windows 95 o Microsoft Windows for Workgroups V3.11 o PATHWORKS 32 V7.1, SPD 56.33.xx o PATHWORKS V6.0 for DOS and Windows, SPD 55.07.xx o PATHWORKS V5.1 for OS/2, SPD 55.24.xx GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements for the current version. 21 ___________________________________________________________________ PRODUCT NAME: DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager) DESCRIPTION DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is an OpenVMS layered application that provides the functions of a Microsoft LAN Manager V2.2 server in a PC LAN environment - with additional features. It is a member of the PATHWORKS family of products, which provides a framework for integrating personal computers into an organization's total information system, allowing users to share information and network services across the entire organization. PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is functionally equivalent to PATHWORKS for OpenVMS (LAN Manager) V5.0F-ECO1. Customers who have V5.0F-ECO1 installed do not need to install V5.0F1 of the software. Likewise, installation of V5.0F1 precludes the need to install V5.0F-ECO1. The PATHWORKS family includes PC LAN server products running on OpenVMS, DIGITAL UNIX, ULTRIX[TM], SCO[TM] UNIX, and OS/2 platforms providing industry-standard Network operating system (NOS) services that use Microsoft's LAN Manager protocol. The PATHWORKS family also includes client software for these servers, include wide area transports (such as DECnet and TCP/IP), and applications such as Mail and Terminal Emulation, allowing DOS, Windows, Windows NT, Windows 95, Windows for Workgroups, and OS/2 to participate as full peers in a distributed computing environment. FEATURES PATHWORKS V5.0F1 for OpenVMS adds a new dimension to general purpose OpenVMS systems. In addition to providing traditional support for business, scientific, and engineering applications, this product allows an OpenVMS system to appear to LAN Manager clients as a Microsoft LAN Manager server. PATHWORKS V5.0F for OpenVMS is an implementation of industry-standard Microsoft LAN Manager V2.2. 22 The major features of PATHWORKS V5.0F1 for OpenVMS are described in the following sections. File Services PATHWORKS V5.0F1 for OpenVMS provides LAN Manager-based clients with a remote file system that appears as a transparent extension of the client system's local computing environment. PATHWORKS for OpenVMS file shares are based on Microsoft's LAN Manager V2.2 SMB (Server Message Block) protocols. Each file stored in a file service is stored as an OpenVMS file in RMS format. Three types of RMS file/record formats are allowed and supported on each volume: o Sequential stream o Sequential fixed length record (512 bytes per record) o Sequential undefined Files stored in a file service are accessible to PC clients, OpenVMS users, and to applications that can interpret the content and organization of the file as written by the client application. Multiple LAN Manager clients can concurrently access files stored on the server's disk through the file access modes and byte range locking support provided by the OpenVMS Operating System. Print Shares PATHWORKS for OpenVMS software allows DOS, Windows, Windows NT, Windows 95, OS/2, and OpenVMS users to share printers connected to Alpha, VAX, or VAXserver[TM] computers and to OpenVMS cluster systems, as well as network-based printers such as LAT printers and DIGITAL Printservers. Print shares are supported in local area and wide area network environments. PC clients can print files from the DOS, OS/2, Windows, Windows 95, and Windows NT operating systems as well as from PC applications. 23 Multiple print shares may be defined for a single printer. For example, separate services may be created for landscape-mode printing and portrait-mode printing. Similarly, separate services may be created for DIGITAL mode and IBM ProPrinter mode printing for a single LA75 printer. PATHWORKS V5.0F1 for OpenVMS includes the DECprint Supervisor (DCPS) Open product, which provides PostScript and DEC ANSI printing to selected industry-standard PostScript printers. Sharing of Network Resources by Heterogeneous Users Services provided by PATHWORKS for OpenVMS are accessible to PATHWORKS LAN Manager-based clients as well as to Microsoft LAN Manager clients. All clients using the services of a PATHWORKS V5.0F1 for OpenVMS server must be properly licensed. (See the Software Licensing section of this SPD.) Files are stored on the server in native OpenVMS Record Management Services (RMS) format. This allows information stored by the PCs using PATHWORKS for OpenVMS to be shared with traditional OpenVMS users. In addition, this feature allows information to be shared among all PATHWORKS clients, including those not based on LAN Manager technology. Concurrent file access by host applications or non-LAN Manager clients is not supported. Network Transport Support PATHWORKS V5.0F1 for OpenVMS supports DECnet, DECnet-Plus, TCP/IP, and NetBEUI network transport software. One or multiple transport stacks can work concurrently on the server. The TCP/IP transport, which is sold as a separate product and available from various vendors, must include a PATHWORKS IP (PWIP) driver. NetBEUI transport software is included with the PATHWORKS V5.0F1 for OpenVMS software. Using NetBEUI transport software, LAN Manager clients can access the server in the local area network for file and print shares. See the Software Requirements section of this SPD for information on supported network transport software. 24 NetBIOS Interface Support PATHWORKS V5.0F1 for OpenVMS supports the NetBIOS interface in DECnet, TCP/IP, and NetBEUI networks. PATHWORKS for OpenVMS utilizes NetBIOS naming services and datagram services. A NetBIOS programming interface is not provided, however. NetBIOS interface support includes the support of multiple transport stacks on a single or different network controllers. NetBIOS support under TCP/IP includes a b-node RFC 1001/1002 implementation. This implies that the NetBIOS interface is supported under TCP/IP in local area network environments only. Flexible Security Models The PATHWORKS V5.0F1 for OpenVMS security model accommodates both the LAN Manager security model and the OpenVMS security model. The server may be configured to use the security implementation best suited to the environment. In "LAN Manager Only" mode, the LAN Manager security model is enforced. In "LAN Manager and OpenVMS" mode, both the OpenVMS and LAN Manager security models are enforced. In "LAN Manager and Creator" mode, OpenVMS security is applied to files not created by users of the PATHWORKS server. Domain Support PATHWORKS V5.0F1 for OpenVMS allows the network to be subdivided into administrative groups of servers and clients called domains. A domain is a group of servers and clients on a LAN and is the basic unit of network administration. Each server running PATHWORKS for OpenVMS can be a member of a single domain. A PATHWORKS for OpenVMS server can be a Primary Domain Controller, Backup Domain Controller, Member Server, or a Standalone Server, depending on the environment. Domains are a convenient mechanism for controlling user access to the network, and for managing large networks. PATHWORKS V5.0F1 for OpenVMS also provides support for wide area domains using the LMHosts file. This file's presence on the PATHWORKS for OpenVMS (LAN Manager) server allows NET Logons and UAS replication over some wide area TCP/IP configurations. The LMHosts file contains a list of nodes from geographically disperse sites that are synchronized by the primary domain controller and accessible to clients 25 in the server's domain. However, use of the LMHosts file for repli- cation over extreme distances or in networks with slow transmission speeds is not recommended. Network Logon Services The domain capabilities of LAN Manager make it possible for a user to issue a single logon request in order to gain access to multiple servers in a LAN. Running the netlogon service forces the validation of users' logon requests. The logon server that processes the request checks its copy of the domain-wide user accounts database for the username and password supplied in the logon request. LAN Manager V2.2 API Support PATHWORKS V5.0F1 for OpenVMS supports the LAN Manager V2.2 Application Programming Interfaces, with the exception of Named Pipes and Mailslots. Note that LAN Manager APIs are not available to OpenVMS host-based applications, but are available to PATHWORKS LAN Manager-based clients, non-PATHWORKS LAN Manager clients, and OS/2 LAN Manager servers. Remote Boot Service The Remote Boot service included with PATHWORKS V5.0F1 for OpenVMS allows DOS and Windows workstations to start up using information stored on the server's hard disk instead of on their own local hard disks. The PATHWORKS V5.0F1 for OpenVMS Remote Boot service is based on the Microsoft LAN Manager Remote Boot service, which uses the Remote Program Load (RPL) protocol. Remote Boot is supported over NetBEUI on Ethernet networks. PATHWORKS V5.0F1 for OpenVMS supports MOP (Maintenance Operation Protocol) as a secondary loader for clients without an RPL ROM. Mail Services PATHWORKS V5.0F1 for OpenVMS includes a mail server component that allows clients to send and receive electronic mail. The mail server is 26 based on the OpenVMS MAIL-11 product and requires DECnet as its communications transport. It allows users of PATHWORKS Mail client software to send and receive electronic mail messages without having to log in to the OpenVMS system as an interactive user. A mail account may be established on the OpenVMS server for each user. Mail can be sent to this account by other PATHWORKS Mail users as well as traditional users of OpenVMS mail software. The mail server then routes messages to the appropriate client when the user logs onto the server. The PATHWORKS for OpenVMS mail server provides the PATHWORKS user with folders, distribution lists, and delivery capabilities. Realtime notification of new messages can be optionally enabled by the client. Time and Date Services DOS, Windows, and OS/2 clients can request date and time information from the server system and set the local workstation date and time to coincide with them. PATHWORKS FAT File System PATHWORKS V5.0F1 for OpenVMS includes the PATHWORKS FAT file system, which is an alternative to, and designed to coexist with the OpenVMS ODS-2 file system. It is based on the DOS File Allocation Table (FAT) file system. PC files stored in the FAT file system are stored in native DOS format in a container file on the server system. Features of the PATHWORKS FAT file system include: o Support for multiple readers and writers of the container file o Wide-area network access to files stored on the server in DOS format o Improved performance on file and directory operations over the OpenVMS ODS-2 file system The PATHWORKS FAT file system may be used as a migration path from existing PATHWORKS V4.x disk service container files. (See Accommoda- tion of Retired Features. 27 Server Management and Control PATHWORKS V5.0F1 for OpenVMS supports several server management interfaces: o A character cell utility called ADMINISTER/PATHWORKS o The LAN Manager NET ADMIN command line interface which may be accessed from a terminal or terminal emulator, or from a LAN Manager client, including the PATHWORKS for DOS and Windows client. The management utilities can be used to: o Manage file and printer shares, user accounts, and groups o Display and control server resources currently in use, such as active sessions, connections, and services o View context-sensitive Help for each menu item and command PATHWORKS Monitor The PATHWORKS Monitor utility is a Windows-based application provided with the PATHWORKS V5.0F1 for OpenVMS server software. PATHWORKS Monitor collects data on server resource utilization and provides a realtime graphical display of this information. PATHWORKS Configuration The PATHWORKS Configuration utility is an OpenVMS-based application that allows the user to modify the server's configuration. For example, the user can configure the data cache size, the security mode, the number of supported clients and more. Any adjustments that need to be made to the OpenVMS SYSGEN parameters are automatically performed by the Configuration utility. Enhanced Cluster Support PATHWORKS V5.0F1 for OpenVMS includes support for a transport-independent PATHWORKS cluster alias name service that allows multiple cluster members to appear as a single server to the connecting clients, providing higher availability. The PATHWORKS cluster alias name has a load balancing feature which connects clients to the cluster member that 28 is the least loaded at the time the session is established. PATHWORKS V5.0F1 for OpenVMS also includes a high performance cluster-wide distributed data cache that provides scalability in a clustered environ- ment. VAX clusters, Alpha clusters, and mixed-architecture clusters are supported by PATHWORKS V5.0F1 for OpenVMS. Enhanced Performance from XQP+ PATHWORKS V5.0F1 for OpenVMS includes a special release of the enhanced OpenVMS file system, known as XQP+ (eXtended QIO Processor Plus). XQP+ is separately installable to OpenVMS VAX V5.5-2. XQP+ is included with OpenVMS VAX and Alpha V6.1 and later. When PATHWORKS V5.0F1 for OpenVMS detects the existence of the enhanced file system, it automatically takes advantage of its improved concurrency, multithreading, and directory caching features to provide better performance to file system operations. Installation Utilities PATHWORKS V5.0F1 for OpenVMS is installed on the OpenVMS system using the standard VMSINSTAL procedure. An Installation Verification Procedure (IVP) is also included, which can be used to confirm that the server software has been installed properly. The installation procedure allows you to install the LAN Manager server with the integrated license server, or just the standalone PATHWORKS License Server. DIGITAL recommends that a customer's first purchase of this software product at each site include DIGITAL installation service. Contact your local DIGITAL representative for information on the service options available. 29 PATHWORKS NetWare Server The PATHWORKS for OpenVMS (NetWare) server software has been retired. This product will no longer be supported, and licenses to use this product will no longer be sold. The code for this product continues to be distributed in this package as a convenience for those who have previously deployed it and who wish to continue to use it without support from DIGITAL. Security External authentication is an optional feature introduced in OpenVMS V7.1 that enables OpenVMS systems to authenticate designated users using their LAN Manager domain using a single username/password combi- nation. This feature is supported in PATHWORKS V5.0E and later. For more information about external authentication for OpenVMS VAX, see SPD 25.01.xx. Year 2000 Ready DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager) has been tested to ensure that the product is Year 2000 ready. License Management PATHWORKS for OpenVMS offers license management for client-based licenses (CCS, FPA, Designated Access, System, and CNS), server-based licenses (FPS or PC Concurrent) and the Client Access licenses, which can be used in either client-based or server-based mode. (See Software Licensing section for details.) The license deliverables for PATHWORKS products are Product Authorization Keys (PAKs) that are then used with the OpenVMS License Management Facility (LMF). These PAKs must be loaded into an LMF database, using standard LMF procedures, on an OpenVMS system that is hosting a PATHWORKS server or is acting as a PATHWORKS License Server.[2] ____________________ [2] The PATHWORKS License Server is active on only a single node in a cluster. If that node goes down for any reason, the PATHWORKS License Server is automatically activated on another cluster node that is running PATHWORKS. 30 o Client-based license management. PATHWORKS for OpenVMS provides a facility called the PATHWORKS License Server that acts as a proxy for client systems that require license keys stored in the LMF database on an OpenVMS system. A single copy of the PATHWORKS License Server software provides and verifies client-based licenses or Client Access licenses being used in client-based mode. PATHWORKS LAN Manager clients and PATHWORKS Advanced Server clients use the DECnet, TCP/IP, or NetBEUI transport. The PATHWORKS License Manager, which must execute on the same node as the License Server, provides a user interface that allows the admin- istrator to monitor client-based license usage, to manage license groups, to set alert levels, to set logging levels for licensing events, to enable or disable the License Server, and to revoke assigned licenses. The PATHWORKS License Manager is also used to preallocate licenses to specific "groups" (including the special, predefined "server-based" group described later) and to reclaim a license from a client. Each LAN needs only one active PATHWORKS License Server. (The License Server provided with PATHWORKS V5.0F1 for OpenVMS (LAN Manager) can support every kind of PATHWORKS client-based license, as well as Client Access licenses, and all supported clients.) The PATHWORKS License Registrar, which executes on the same system as the file server, verifies the licenses for clients requesting access to the server functions. Clients that can produce a valid client-based license, or Client Access license, are allowed access to the services offered by the PATHWORKS V5.0F1 for OpenVMS (LAN Manager) server. o Server-based license management. The PATHWORKS V5.0F1 for OpenVMS (LAN Manager) server also allows client access based on the avail- ability of valid server-based licenses (either FPS and/or PC Con- current), and/or Client Access licenses being used in server-based mode in the local LMF database. If a client requesting access to the server fails to produce a sufficient client-based license, the PATHWORKS License Registrar software checks for the availability of a valid server-based license or Client Access license being used in server-based mode. If one is available the client is allowed access. 31 Client Access licenses can be put into server-based mode in one of two ways: o If the PATHWORKS License Server was not configured for the system where PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is executing, then all Client Access licenses loaded into the local LMF database on that system will be used in server-based mode. o If the PATHWORKS License Server was configured for the system where PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is executing, then all Client Access licenses loaded into the local LMF database will, by default, be used in client-based mode. To allow some or all of these licenses to be used in server-based mode, use the PATHWORKS License Manager and allocate those licenses to the special, predefined group called the "server-based" group. Licenses available in the "server-based" group will then be available for use in server-based mode. Note: PATHWORKS V5.0F1 for OpenVMS (LAN Manager) server allows you to use both client-based and server-based licensing, simultaneously. However, because clients using client-based licenses, or Client Access licenses in client-based mode, are already licensed to use the server software, they never consume additional server-based licenses, or Client Access licenses allocated for use in server-based mode, by a PATHWORKS V5.0F1 for OpenVMS (LAN Manager) server. Accommodation of Retired Features The following features of PATHWORKS V4.x for OpenVMS are not provided in PATHWORKS V5.0F1 for OpenVMS: o File services over LAST o Disk services o Remote Boot over LAST If PATHWORKS V5.0F1 for OpenVMS is installed on a server system which had been running V4.x of the product, some aspects of the V4.x environment related to the features listed above will be preserved. Disk 32 services will remain intact and available to pre-V5.0F1 clients. LAST- based Remote Boot services will also remain intact and available to pre-V5.0F1 clients. HARDWARE REQUIREMENTS The systems, components, and peripherals specified below are supported except as noted. Processors Supported All VAX and Alpha processors that are supported by the version of the OpenVMS Operating System in use are also supported by PATHWORKS V5.0F1 for OpenVMS (LAN Manager) with the following exceptions: MicroVAX: MicroVAX I, MicroVAX II, MicroVAX 2000 VAX: VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAX 11/782, VAX 11/785 VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXstation 8000 Memory Requirements PATHWORKS V5.0F1 for OpenVMS requires the following minimum physical memory for proper installation, configuration, and execution of the software: 16 MB on VAX systems (24 MB if used with DECnet-Plus) 64 MB on Alpha systems Note that the memory requirements indicated above are minimum requirements only, and that memory requirements can vary widely according to the server CPU, the number of clients using the server and their activities, the number and speed of the server's disks and the other applications running on the server. 33 For example, a typical configuration supporting a light workload (word processing or spreadsheet applications) for 50 PC users requires an Alpha system with approximately 64 MB of memory or a VAX system with approximately 16 - 24 MB of memory. This assumes that 80% of the system memory and CPU time are dedicated to PATHWORKS, even though some work loads may use less. Disk Space Requirements (Block Cluster Size=1) Table 2 provides the disk space requirements for the installation and configuration of PATHWORKS V5.0F1 for OpenVMS (LAN Manager). By default, all entries are directed to the same disk, but each can be directed to different disks. You should also plan for additional, significant disk-space requirements after the product is started and in use for items such as data files, virtual memory section files, log files, and so forth. ___________________________________________________________________ Table 2: Installation/Configuration Disk Space Requirements ___________________________________________________________________ Item VAX systems Alpha systems ___________________________________________________________________ Images and command files 40,000 blocks 60,000 blocks PATHWORKS server data files 12,500 blocks 12,500 blocks ___________________________________________________________________ Total 52,500 blocks 72,500 blocks ___________________________________________________________________ Note: Sizes are approximate; actual sizes might vary depending on the user's system environment, configuration, and software options. ___________________________________________________________________ 34 OPTIONAL HARDWARE PostScript Printers PATHWORKS V5.0F1 for OpenVMS supports those PostScript printers that are supported by DECprint Supervisor (DCPS) for OpenVMS. Refer to SPD 44.15.xx for a complete list of the DIGITAL and non-DIGITAL PostScript printers supported by DCPS. DECprint Supervisor software is included with PATHWORKS V5.0F1 for OpenVMS. The right to use the DCPS software is granted by the DCPS Open license, which is included in the PATHWORKS for OpenVMS (LAN Manager) PC Concurrent license, and the PATHWORKS for DOS and Windows (LAN Manager) Designated Access license. 35 Non-PostScript Printers PATHWORKS V5.0F1 for OpenVMS also supports the following non-PostScript printers: DIGITAL LA75 Companion EPSON FX850 Printer DIGITAL LA210 EPSON FX1050 DIGITAL LA310 DIGITAL LA324[TM] IBM ProPrinter DIGITAL LA424 NEC SilentWriter[R] II Model 290 DIGITAL LJ250 Companion Color Printer DIGITAL LN03[TM] PLUS DIGITAL PostScript printers connected by serial lines or DECservers, and printers attached directly to the Ethernet are supported. Network Interface Controllers PATHWORKS for OpenVMS (LAN Manager) supports Ethernet, FDDI, and Token Ring network hardware devices as described below: o For the TCP/IP transport, PATHWORKS for OpenVMS (LAN Manager) supports the network hardware devices supported by the specific TCP/IP product. For DIGITAL TCP/IP Services for OpenVMS, consult SPD 46.46.xx (for Alpha systems) or SPD 25.A4.xx (for VAX systems). For other TCP/IP products, contact the vendor. o For the DECnet transport using Ethernet, FDDI, or Token Ring, see: - SPD 42.25.xx for DECnet for OpenVMS AXP, V6.1 - SPD 25.03.xx for DECnet/OSI V7.0 (or DECnet-Plus) for OpenVMS on VAX systems - SPD 50.45.xx for DECnet/OSI, V7.0 (or DECnet-Plus V7.1) for OpenVMS Alpha - SPD 48.48.xx for DECnet for OpenVMS VAX and Alpha, V7.0 36 o For the NetBEUI transport, PATHWORKS for OpenVMS (LAN Manager) provides the same level of support for Ethernet and FDDI as the OpenVMS operating system. For more information, see SPD 25.01.xx. PATHWORKS V5.0F1 for OpenVMS (LAN Manager) does not support NetBEUI over Token Ring on VAX systems. The PATHWORKS V5.0F1 for OpenVMS server does not support the DEFZA FDDI controller. CLUSTER ENVIRONMENT PATHWORKS V5.0F1 for OpenVMS (LAN Manager) supports all OpenVMS cluster configurations. OpenVMS cluster configurations for Alpha systems are fully described in the OpenVMS Cluster Software for OpenVMS Alpha Software Product Description (SPD 42.18.xx). OpenVMS cluster configurations for VAX systems are fully described in the OpenVMS Cluster Software for OpenVMS VAX Software Product Description (SPD 29.78.xx). PATHWORKS V5.0F1 for OpenVMS (LAN Manager) supports up to 31 server nodes in cluster. In other words, no more than 31 nodes in a cluster can run PATHWORKS V5.0F1 for OpenVMS (LAN Manager) concurrently. In a typical scenario, the server is run on only a few central nodes, to exploit the cluster's shared disks and high speed interconnect environment. In a cluster, PATHWORKS V5.0F1 for OpenVMS (LAN Manager) supports simultaneous file access by all nodes running the server. A central event log and central LAN Manager accounts and share databases are maintained in a cluster. In a LAN Manager domain, the OpenVMS cluster represents a single domain member, whether it is acting as the primary domain controller or as a backup domain controller. SOFTWARE REQUIREMENTS Operating System For Alpha Systems: o OpenVMS Alpha Operating System V6.1, V6.2, V7.0, and V7.1. 37 For VAX Systems: o OpenVMS VAX Operating System V5.5-2, V6.1, V6.2, V7.0, and V7.1. For minimum hardware requirements of the operating system refer to the Software Product Description for the OpenVMS Operating System (SPD 25.01.xx). OpenVMS Tailoring For supported OpenVMS VAX V5.x systems, the following OpenVMS classes are required for full functionality of this layered product: o OpenVMS Required Saveset o Network Support (required only for DECnet support) o System Programming Support o Secure User's Environment o OPTL - Miscellaneous Files For more information on OpenVMS classes and tailoring, refer to the OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx). Network Transport Software PATHWORKS V5.0F1 for OpenVMS includes NetBEUI network transport software. DECnet or TCP/IP network transport software may also be required by PATHWORKS for OpenVMS, depending on the transport used by clients requiring connections to the server, or for use of some features. The following versions of DECnet and DECnet-Plus are supported by PATHWORKS V5.0F1 for OpenVMS: For Alpha Systems: o DECnet/OSI V6.3 for OpenVMS Alpha o DECnet/OSI V7.0 for OpenVMS Alpha o DECnet-Plus V7.1 for OpenVMS Alpha 38 For VAX Systems: o DECnet/OSI V6.3 for OpenVMS VAX o DECnet/OSI V7.0 for OpenVMS VAX o DECnet-Plus V7.1 for OpenVMS VAX When PATHWORKS V5.0F1 for OpenVMS is to be used in a TCP/IP environment, OpenVMS-based TCP/IP software is required. This software must be purchased separately. The following TCP/IP transports support PATHWORKS V5.0F1 for OpenVMS: o DIGITAL TCP/IP Services for OpenVMS V4.0 (supported on OpenVMS for VAX V5.5-2 only) o DIGITAL TCP/IP Services for OpenVMS V4.1 (supported on OpenVMS for VAX V6.1 or later) o MultiNet V3.5 rev A o Process Software Corporation's TCPWARE for OpenVMS V5.0-4 Other PATHWORKS Server Software The following PATHWORKS server products cannot run on the same system as PATHWORKS V5.0F1 for OpenVMS (LAN Manager): o PATHWORKS for OpenVMS V4.x. The PATHWORKS V5.0F1 for OpenVMS server can be installed and configured on a system running the V4.x server, but actually running the V5.0F1 server on a system also running the V4.x server is not possible or supported. o PATHWORKS V6.0A for OpenVMS (Advanced Server) The PATHWORKS V6.0A for OpenVMS software can be installed and configured on a system running the V5.0F1 server, but actually running the V5.0F1 server on a system also running the V6.0A server is not possible or supported. An Upgrade utility provided with PATHWORKS V6.0A for OpenVMS allows server databases to be upgraded from V5.0F1 to V6.0A. 39 Client Software The following versions of client software are supported for use with PATHWORKS for OpenVMS: o Microsoft Windows NT workstation software V3.1, V3.5, or V4.0 o Microsoft Windows 95 o Microsoft Windows for Workgroups V3.11 o PATHWORKS 32 V7.1, SPD 56.33.xx o PATHWORKS V6.0 for DOS and Windows (LAN Manager) (SPD 55.07.xx) o PATHWORKS for OS/2 V5.1 (SPD 55.24.xx) o LAN Manager V2.2 workstation software for DOS, Windows, and OS/2 GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements for the current version. 40 ___________________________________________________________________ LICENSING AND ORDERING INFORMATION: DIGITAL PATHWORKS V6.0A and V5.0F1 SOFTWARE LICENSING PATHWORKS V6.0A for OpenVMS (Advanced Server)[3] is purchased by licensing the clients or applications that use the services provided by the product. There is no additional fee. The license that clients require to use the PATHWORKS Advanced Server software is referred to as a Client Access license (PAK Product Name: PWLMXXXCA06.00). Though there is only one license sold for any client using this PATHWORKS server, this license can be used in one of two ways: o Client-based mode (also known as per-seat mode) o Server-based mode (also known as per-server or concurrent use mode) These two different licensing modes are described in the following text. o Client-Based Licensing Mode. When a license for PATHWORKS Advanced Server is used in client-based licensing mode, the right to use the server is assigned electronically to a particular client or seat. ____________________ All previous versions of PATHWORKS for OpenVMS (Advanced Server), including PATHWORKS V5.0F1 for OpenVMS (LAN Manager), are now licensed for use in exactly the same way as PATHWORKS for OpenVMS (Advanced Server). Though previously purchased licenses continue to be valid for use with pre-V6 servers, only the new Client Access licenses may be purchased when adding new clients to existing systems. In particular, all the licenses listed in Table 4, Previous Version Licenses Qualifying for Upgrade Licenses, are no longer sold but continue to be valid and grant the right to use the PATHWORKS V5.0 for OpenVMS (LAN Manager) software. 41 Once the right is assigned, the client system may access all systems running PATHWORKS Advanced Server as well as all systems running any previous version of PATHWORKS for OpenVMS.[4] This mode of licensing PATHWORKS servers is normally used when a customer has more than one PATHWORKS server and where clients normally access more than one server at the same time. Because only one license per client is required regardless of how many servers are being accessed, the client-based licensing mode can be more economical in these situations when compared to server-based mode (described later). Because a client with a client-based license cannot be refused access to a server due to license limits, this mode of licensing is also useful when you need to guarantee that a particular system will always have access to one or more servers. Note: To use this licensing mode, a small licensing agent must be loaded and enabled on each licensed client. The code for this licensing agent is distributed with the PATHWORKS Advanced Server, is available free on the Web, and is also available on CD-ROM at a nominal fee. o Server-based licensing mode. When a license for PATHWORKS Advanced Server[5] is used in server-based licensing mode, the right to use the server is assigned electronically to a particular server system running a copy of the software. Any client can then access this server and make as many connections to file services and print shares as needed. ____________________ The PAK associated with the Client Access license will work, in client- based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) servers that have been upgraded to a minimum of V5.0E. Prior revisions of this product will not recognize or use this PAK. The PAK associated with the Client Access license will work, in server- based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) servers that have been upgraded to a minimum of V5.0F. Prior revisions of this product will not recognize or use this PAK in this mode. 42 The PATHWORKS server will allow up to "n" clients to access its services concurrently, where "n" is the total number of licenses being used in server-based licensing mode. The server will not allow the "n+1st" client to access its services, until one of the first "n" clients has disconnected from the server. Note: Though a server may have only "n" licenses available, any number of clients can potentially access that server. The restriction is based only on the total number of clients that may connect to the server at one time. For example, if you have 100 licenses assigned to a PATHWORKS server in server-based licensing mode, then any 100 clients can make use of all services offered by the PATHWORKS server at one time. However, if an additional client (the 101st) attempts to connect to the server, the client will be denied access until one of the connected clients disconnects from all services. Server-based licensing works best in situations where all clients use or access only one server and there are enough licenses available on each system for all clients to access their assigned server. A "system" is defined as either a standalone system or a cluster. Note: Customers can choose which mode to use and can change the licensing mode, as their situation dictates, without contacting or notifying DIGITAL. Note also that any portion of multiple licenses delivered in a single PAK can be used in server-based mode, while the remainder can be used in client-based mode. Because a PAK can be legally loaded on only one system, it is only the system where the PAK is loaded that can use the licenses in server-based mode. For complete terms and conditions related to Client Access licenses, refer to the back of your PAK for these licenses, or consult the DIGITAL Software Licensing InfoCenter on the Web at: http://www.digital.com/info/software-licensing 43 ORDERING INFORMATION General Information Unless otherwise noted, licenses related to each part number will be delivered in a single PAK. Because each PAK can be loaded on only one system, it is important to order your licenses in a manner that best fits your needs. New or Additional Licenses For new or additional users of PATHWORKS for OpenVMS software, use the part numbers in Table 3 to purchase the number of Client Access licenses required. When ordering, note that licenses related to each part number will be delivered in a single PAK and any one PAK can be loaded on only one system ___________________________________________________________________ Table 3: New License Part Numbers ___________________________________________________________________ Part Number Number of Licenses per PAK ___________________________________________________________________ QM-5SUAA-AB 1 QM-5SUAA-AC 10 QM-5SUAA-AD 25 QM-5SUAA-AE 50 QM-5SUAA-AF 100 QM-5SUAA-AG 250 QM-5SUAA-AH 500 QM-5SUAA-AJ 1000 ___________________________________________________________________ Upgrade Licenses Customers with licenses for previous versions of PATHWORKS servers supporting the LAN Manager protocol are eligible to purchase Upgrade licenses to PATHWORKS V6.0A for OpenVMS (Advanced Server). Combined with your original license, the Upgrade license provides the right to use 44 PATHWORKS V6.0A for OpenVMS (Advanced Server). To be eligible to purchase an Upgrade license, you must have proof-of-license for any version of one of the licenses shown in Table 4. Table 5 lists the part numbers for these Upgrade licenses. ___________________________________________________________________ Table 4: Previous Version Licenses Qualifying for Upgrade Licenses ___________________________________________________________________ License Name Part Numbers ___________________________________________________________________ CCS A[*] PATHWORKS V5.x for OS/2 (LAN Manager) CCS QM-YFWAA-A[*] PATHWORKS V5.0 (LAN Manager) FPA QM-2CLAA-A[*] PATHWORKS V5.0 (LAN Manager) Designated Access QM-2CLAA-A[*] PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS QM-A93AA-A[*] PATHWORKS V5.0 for OpenVMS (LAN Manager) PC QM-A93AA-A[*] concurrent ___________________________________________________________________ [*]Variable field ___________________________________________________________________ 45 ___________________________________________________________________ Table 5: Upgrade License Part Numbers ___________________________________________________________________ Number of Part Number Licenses Number of Licenses per PAK ___________________________________________________________________ QM-5SUAA-CA 1 Variable[1] QM-5SUAA-CB 1 1 QM-5SUAA-CC 10 10 QM-5SUAA-CD 25 25 QM-5SUAA-CE 50 50 QM-5SUAA-CF 100 100 QM-5SUAA-CG 250 250 QM-5SUAA-CH 500 500 QM-5SUAA-CJ 1000 1000 ___________________________________________________________________ [1]Equals total quantity ordered as a single line item ___________________________________________________________________ Software Media and Documentation Software media and documentation are available in the following formats: QA-A93AA-H8, CD-ROM media QA-A93AA-H5, TK50 media QA-A93AA-GZ, Documentation kit In addition, PATHWORKS V6.0A for OpenVMS (Advanced Server) and PATHWORKS V5.0F1 for OpenVMS (LAN Manager) software and documentation are included in the following: QA-03XAA-H8, DIGITAL OpenVMS Alpha Software Layered Products Library Package PATHWORKS V5.0F1 for OpenVMS (LAN Manager) software and documentation are included in the following: QA-5G88A-H8, DIGITAL OpenVMS VAX Software Layered Products Library Package 46 This information is valid at time of release. Please contact your local DIGITAL office for the most up-to-date information. SOFTWARE PRODUCT SERVICES A variety of service options are available from DIGITAL. For more information, contact your local DIGITAL office. SOFTWARE WARRANTY This software is provided by DIGITAL with a 90-day conformance warranty in accordance with the DIGITAL warranty terms applicable to the license purchase. 47 [R] Apple, Appleshare, and Macintosh are registered trademarks of Apple Computer, Inc. [R] AT&T is a registered trademark of American Telephone and Telegraph Corporation. [R] EPSON is a registered trademark of Epson America, Inc. [R] IBM, OS/2, and ProPrinter are registered trademarks of International Business Machines Corporation. [R] Microsoft, MS-DOS, Windows, and Windows 95 are registered trademarks of Microsoft Corporation. [TM] MultiNet and TCPWARE are registered trademarks of Process Software Corporation. [R] PostScript is a registered trademark of Adobe Systems Incorporated. [TM] SCO is a trademark of Santa Cruz Operations, Inc. [R] SilentWriter is a registered trademark of NEC Corporation. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. [TM] NetBIOS is a trademark of Micro Computer Systems, Inc. [TM] Process Software Corporation is a trademark of Process Software Corporation. [TM] Windows NT is a trademark of Microsoft Corporation. [TM] DEC, DECnet, DECnet-Plus, DECprint, DECserver, DIGITAL, LA75, LA324, LAT, LN03, ManageWORKS, OpenVMS, PATHWORKS, PrintServer, TK, ULTRIX, VAX, VAXserver, VMS, and the DIGITAL logo are trademarks of Digital Equipment Corporation. (c) 1998 Digital Equipment Corporation. All Rights Reserved. 48