       %                               DIGITAL    Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  DIGITAL PATHWORKS V6.0 for OpenVMS      SPD 30.50.22 6                (Advanced Server) and DIGITAL PATHWORKS.                V5.0F for OpenVMS (LAN Manager)   INTRODUCTION  F This Software Product Description describes two separate products that' provide similar PC server capabilities:   / o  PATHWORKS V6.0 for OpenVMS (Advanced Server)   , o  PATHWORKS V5.0F for OpenVMS (LAN Manager)  E Though similar, these products are based on different versions of the C LAN Manager protocol and have very different requirements regarding ! the versions of OpenVMS required.   D PATHWORKS V6.0 for OpenVMS (Advanced Server) is based on the currentG networking technology available from Microsoft[R], as delivered in Win- C dows NT servers. It requires OpenVMS V7.1 and will run on any Alpha " system that supports OpenVMS V7.1.  D PATHWORKS V5.0F for OpenVMS (LAN Manager) is based on older LAN Man-F ager V2.2 technology from Microsoft but is supported on both Alpha and6 VAX[TM] servers running a variety of OpenVMS versions.  E Both products are distributed in one package and one license is valid  for both products.   This SPD has three sections:  / o  PATHWORKS V6.0 for OpenVMS (Advanced Server)   , o  PATHWORKS V5.0F for OpenVMS (LAN Manager)  C                                                      September 1997   C                                                         AE-HD94Y-TK        . o  Software Licensing and Ordering information                                                                              "                                  2       C ___________________________________________________________________   C PRODUCT NAME:  DIGITAL PATHWORKS V6.0 for OpenVMS (Advanced Server)    DESCRIPTION   G DIGITAL[TM] PATHWORKS[TM] for OpenVMS[TM] (Advanced Server) is an Open- D VMS layered application that provides networking functionally equiv-F alent to that of the Windows NT[TM] Server - with additional features.  H As a server for workstations on a network, the PATHWORKS Advanced ServerG provides file and print shares that enable a community of desktop users G to share computing resources efficiently. The PATHWORKS Advanced Server D can function as a simple file and print server for a small, isolatedF community of users or as the foundation of a large network distributed over a wide geographical area.  E The PATHWORKS Advanced Server represents the newest generation of LAN C Manager systems technology. It enhances the LAN Manager functional- D ity by incorporating the latest Microsoft technology to deliver pow-D erful new features for network administration and enhanced security.C The PATHWORKS Advanced Server can operate independently or in coop- 8 eration with systems running Windows NT Server software.   FEATURES  G PATHWORKS Advanced Server adds a new dimension to general purpose Open- C VMS systems. In addition to providing traditional support for busi- I ness, scientific, and engineering applications, PATHWORKS Advanced Server C allows an OpenVMS system to appear to LAN Manager clients as a Win- G dows NT Server. PATHWORKS Advanced Server is based on Windows NT Server ' source code from Microsoft and AT&T[R].   D The major features of PATHWORKS Advanced Server are described in the following sections.           "                                  3       
 File Services   D PATHWORKS V6.0 for OpenVMS provides LAN Manager-based clients with aH remote file system that appears as a transparent extension of the client% system's local computing environment.   C PATHWORKS for OpenVMS file shares are based on Microsoft's Advanced 1 Server V3.0 SMB (Server Message Block) protocols.   I Each file stored in a file service is stored as an OpenVMS file in Record C Management Services (RMS) format. Three types of RMS file or record 1 formats are allowed and supported on each volume:    o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefined   D Files stored in a file service are accessible to PC clients, OpenVMSC users, and to applications that can interpret the content and orga- : nization of the file as written by the client application.  D Multiple LAN Manager clients can concurrently access files stored onD the server's disk through the file access modes and byte-range lock-" ing support provided by PATHWORKS.  D The PATHWORKS Advanced Server lets network users share local OpenVMSE files. You can use discretionary access controls on each file and di- E rectory to specify the groups and users that can access files, to de- C fine the levels of access that each group or user is permitted, and C to control auditing as supported by Windows NT-like security. Addi- F tional security is provided by OpenVMS file and directory protections.   Print Shares  E PATHWORKS for OpenVMS software lets DOS, Windows[R], Windows NT, Win- F dows 95[R], OS/2[R], and OpenVMS users share printers connected to Al-F pha computers and to OpenVMS cluster systems, as well as network-basedE printers such as LAT[TM] printers and DIGITAL PrintServers[TM]. Print   "                                  4       C shares are supported in local area network (LAN) and wide area net- G work (WAN) environments. PC clients can print files from the DOS, OS/2, E Windows, Windows 95, and Windows NT operating systems as well as from  PC applications.  D Multiple print shares may be defined for a single printer. For exam-E ple, separate services may be created for landscape-mode printing and C portrait-mode printing. Similarly, separate services may be created D for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer.   E PATHWORKS Advanced Server includes the DECprint[TM] Supervisor (DCPS) D Open product, which provides PostScript[R] and DEC[TM] ANSI printing2 to selected industry-standard PostScript printers.  3 Sharing of Network Resources by Heterogeneous Users   F Services provided by PATHWORKS for OpenVMS are accessible to PATHWORKSD LAN Manager clients as well as to Microsoft LAN Manager clients. AllD clients using the services of a PATHWORKS for OpenVMS server must beD properly licensed. (For more information, see the Software LicensingC section.) Files are stored on the server in native OpenVMS RMS for- H mat. This allows information stored by the PCs using PATHWORKS for Open-G VMS to be shared with traditional OpenVMS users. In addition, this fea- E ture allows information to be shared among all PATHWORKS clients, in- F cluding those not based on Advanced Server technology. Concurrent fileF access by host applications or non-Advanced Server clients is not sup- ported.    Network Transport Support   I PATHWORKS Advanced Server supports DECnet[TM] (Phase IV), DECnet-Plus[TM] E (formerly known as DECnet/OSI), TCP/IP, and NetBEUI network transport C software. One or multiple transport stacks can work concurrently on  the server.   D The TCP/IP transport, which is sold as a separate product and avail-E able from various vendors, must include a PATHWORKS IP (PWIP) driver.     "                                  5       H NetBEUI transport software is included with the PATHWORKS V6.0 for Open-G VMS software. Using NetBEUI transport software, Advanced Server clients ; can access the server in the LAN for file and print shares.   D See the Software Requirements section of this SPD for information on% supported network transport software.    NetBIOS[TM] Interface Support   C PATHWORKS Advanced Server supports the NetBIOS interface in DECnet, D TCP/IP, and NetBEUI networks. PATHWORKS Advanced Server uses NetBIOSC naming services and datagram services. A NetBIOS programming inter- E face is not provided, however. NetBIOS interface support includes the E support of multiple transport stacks on a single or different network  controllers.  F NetBIOS support under TCP/IP includes a both a p-node and a b-node RFCD 1001/1002 implementation. This implies that the NetBIOS interface isD supported under TCP/IP in both LAN and WAN environments. The Config-F uration Manager provides the ability to select name resolution for WANF support with either LMHosts or Windows Internet Naming Services (WINS) Server name resolution.    Flexible Security Models  F The PATHWORKS Advanced Server security model accommodates both the Ad-G vanced Server security model and the OpenVMS security model. The server C may be configured to use the security implementation best suited to F the environment. In Advanced Server Only mode, the Advanced Server se- curity model is enforced.   D PATHWORKS Advanced Server employs a user-level security model. User-H level security provides precise control over access to shared resources,C including disk devices, directories, and printers. Control is based E on a password assigned to each user account and the access granted to  the resources.        "                                  6       F The PATHWORKS Advanced Server incorporates enhanced features that pro-C vide a high level of control over user and resource permissions and E auditing. These features include support of discretionary access con- E trol permissions on individual files, directories, and resources, and  complete auditing capabilities.   D Like Windows NT Servers, the PATHWORKS Advanced Server does not sup-H port share-level security and operates in user-level security mode only.  G In the Advanced Server and OpenVMS model, both the OpenVMS and Advanced F Server security models are enforced. The PATHWORKS Advanced Server en-E hances the Windows NT security model with OpenVMS security. Users who E require the additional security support can continue to protect their  resources based on OpenVMS.    Domain Support  F PATHWORKS Advanced Server allows the network to be subdivided into ad-C ministrative groups of servers and clients called domains. A domain D is a group of servers and clients on a network and is the basic unitD of network administration. Each server running PATHWORKS for OpenVMSF can be a member of a single domain. A PATHWORKS for OpenVMS server canI be a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC). E Domains are a convenient mechanism for controlling user access to the ( network and for managing large networks.  G A PATHWORKS for DIGITAL UNIX[R] Advanced Server can be part of the same C domain as a PATHWORKS for OpenVMS Advanced Server and can be desig- C nated as either the Primary Domain Controller or Backup Domain Con-  troller.  D PATHWORKS for OpenVMS Advanced Server provides support for wide areaD domains using either the LMHosts file or WINS (Windows Internet Nam- ing Services).  C This presence of the LMHosts file on the PATHWORKS for OpenVMS (Ad- D vanced Server) server allows NetLogon services and security databaseD replication over wide area TCP/IP configurations. This file containsC a list of nodes from geographically dispersed sites synchronized by   "                                  7       G the Primary Domain Controller and accessible to clients in the server's E domain. However, use of the LMHosts file for replication over extreme D distances or in networks with slow transmission speeds is not recom- mended.   C Support for WINS integration allows PATHWORKS for OpenVMS (Advanced E Server) servers to act as WINS clients; that is, to use the name reg- C istration and resolution facilities available from a Microsoft WINS F Server across routed wide area TCP/IP networks, thus enabling WAN sup-C port via WINS for domain functions, NetLogon services, and security  database replication.    Trust Relationships   F The PATHWORKS Advanced Server supports trusts. Trust relationships al-E low users from other domains to access resources in the local domain, = and local domain users may access resources in other domains.    NetLogon Services   E A single domain-wide logon lets a user access resources on any server E in this domain or on servers in other domains that trust this domain.   C The domain capabilities of PATHWORKS Advanced Server make it possi- E ble for a user to issue a single logon request to gain access to mul- C tiple servers in a network. Running the NetLogon service forces the D validation of users' logon requests. The logon server that processesE the request checks its copy of the domain-wide user accounts database = for the user name and password supplied in the logon request.    TimeSource Services   D DOS, Windows, and OS/2 clients can request date and time informationE from the server system and set the local workstation date and time to  coincide with them.           "                                  8        User Environment Management   E Logon scripts can be used to configure MS-DOS[R] and Windows worksta- E tion user environments by making network connections and starting ap- D plications. User profiles can be created to make workstations easierE to use as well as to control workstation access to network resources.    Server Management and Control   D The PATHWORKS Advanced Server can be managed from either the OpenVMSF server or a client workstation, using one of the following server man- agement interfaces:   C o  The PATHWORKS Advanced Server ADMINISTER command line interface, F    which can be accessed from a terminal or terminal emulator. It con-(    forms to standard DCL command syntax.  D o  Windows NT server administration tools, which are included in theD    PATHWORKS Advanced Server software kit to be installed on WindowsG    NT workstations, Windows 95 workstations, and Windows for Workgroups G    workstations. This set of tools, including Server Manager, User Man- C    ager for Domains, and Event Viewer, allows you to administer the F    PATHWORKS Advanced Server and Windows NT Server computers from net-    work clients.  E o  Windows NT ADMIN tools, which are available as part of the Windows 
    NT Server.   G o  PATHWORKS Configuration Manager (a character cell interface) to man- "    age local server configuration.  C 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  E o  Display and control server resources currently in use, such as ac- ,    tive sessions, connections, and services.  "                                  9       C o  View context-sensitive online help that provides command syntax, 9    options, and qualifiers for each menu item and command   E The PATHWORKS Advanced Server can be remotely administered from PATH- C WORKS and Microsoft Windows client workstations. These workstations D include Windows 3.1, Windows for Workgroups, Windows 95, Windows NT.C PATHWORKS Advanced Server can also be managed remotely from Windows * NT Servers and PATHWORKS Advanced Servers.  ' PATHWORKS Configuration Manager Utility   C The PATHWORKS Configuration Manager utility is a character cell in- C terface that allows the user to set up and modify the server's con- D figuration. For example, the user can configure the data cache size,H the security model, the number of supported clients, the types of trans-C ports, the type of WAN capabilities, and more. Any adjustments that D need to be made to the OpenVMS SYSGEN parameters to support the run-C ning of the server are automatically performed by the Configuration  Manager utility.   Integrating with OpenVMS  E The PATHWORKS Advanced Server encompasses many of the features of the G OpenVMS Operating System, including OpenVMS clusters and symmetric mul- D tiprocessing. OpenVMS cluster configurations provide failover avail-G ability and extensive resource capacities by integrating multiple Open- = VMS systems that can be accessed using a single cluster name.   F PATHWORKS Advanced Server includes support for a transport-independentF PATHWORKS cluster alias NetBIOS name that allows multiple cluster mem-F bers to appear as a single server to the connecting clients. This sup-C port provides higher availability. The PATHWORKS cluster alias name F has a load-balancing feature that connects clients to the cluster mem-D ber that is the least loaded at the time the session is established.E PATHWORKS V6.0 for OpenVMS also includes a high performance, cluster-_D wide distributed data cache that provides scalability in a clusteredG environment. Alpha clusters are supported by PATHWORKS Advanced Server.       "                                 10 R     ( Integrating with External Authentication  D External authentication is an optional feature introduced in OpenVMSH V7.1 that lets OpenVMS systems authenticate designated users using theirC Advanced Server domain with a single username and password combina-eD tion. You can configure an external authentication for any PATHWORKSC Advanced Server user account mapped to an OpenVMS user account. Ex-rC ternal authentication allows PATHWORKS Advanced Server users to logKF on to the OpenVMS system, using PATHWORKS Advanced Server username andF password. For more information about external authentication for Open- VMS Alpha, see SPD 25.01.xx.  ! Integrating with OpenVMS Securitym  E PATHWORKS Advanced Server provides an extension to the Windows NT se- F curity model by supporting OpenVMS security enforcement as an optional enhancement.   Alerter ServiceM  D The PATHWORKS Advanced Server includes an Alerter Service that sendsF automatic alert messages to clients and users as specified in the LAN-
 MAN.INI file.t   Event Log ServiceP  D Event logs provide valuable information about server activities. TheH administrator can select from several event types and, for each, whetherF successful or unsuccessful attempts at specific operations are to gen-C erate event messages. Event messages are generated based on the au-r> dit policy specified for the server and files and directories.                  "                                 11        Installation Utilities  F PATHWORKS Advanced Server is installed on the OpenVMS system using theD standard VMSINSTAL procedure. An Installation Verification ProcedureD (IVP) is also included, which can be used to confirm that the server% software has been installed properly.e  C The installation procedure allows you to install just the PATHWORKSrD Advanced Server server, just the NetWare[R] server, or both. It alsoG allows you to install just the PATHWORKS License Server or the Advancedn Server Upgrade utility.o  G If you are running the PATHWORKS for OpenVMS NetWare Server on the sameSD system, you must upgrade the NetWare server as well as the PATHWORKSF Advanced Server. The NetWare Server is upgraded automatically when you& install the PATHWORKS Advanced Server.  C The first purchase of PATHWORKS for OpenVMS at each site should in- C clude DIGITAL installation service. Contact your local DIGITAL rep- = resentative for information on the service options available.e   Year 2000-Readye  C PATHWORKS V6 for OpenVMS has been tested to ensure that the product  will run in the Year 2000.   License Management  D PATHWORKS for OpenVMS offers license management for client-based li-C censes (CCS, FPA, Designated Access, System, and CNS), server-basedsD licenses (FPS or PC Concurrent), and the new Client Access licenses,C which can be used in either client-based or server-based mode. (Seed, the Software Licensing section for details.)  F The license deliverables for PATHWORKS products are Product Authoriza-D tion Keys (PAKs) that are then used with the OpenVMS License Manage-D ment Facility (LMF). These PAKs must be loaded into an LMF database,      "                                 12       C using standard LMF procedures, on an OpenVMS system that is hosting6A a PATHWORKS server or is acting as a PATHWORKS License Server.[1]l  D o  Client-Based License Management. PATHWORKS for OpenVMS provides aD    facility called the PATHWORKS License Server that acts as a proxyJ    for client systems that require license keys stored in the LMF database    on an OpenVMS system.  C A single copy of the PATHWORKS License Server software provides andtD verifies client-based licenses, or Client Access licenses being usedC in client-based mode, for clients using NetWare or LAN Manager pro- C tocols. NetWare clients use the IPX transport to communicate with aaE PATHWORKS License Server, while PATHWORKS Advanced Server clients andeG PATHWORKS LAN Manager clients use the DECnet, TCP/IP, or NetBEUI trans-n port.   E The PATHWORKS License Manager, which must execute on the same node asLD the License Server, provides a user interface that allows the admin-I istrator to monitor client-based license usage, to manage license groups,vD set alert levels, set logging levels for licensing events, enable orC disable the License Server, and revoke assigned licenses. The PATH-sF WORKS License Manager is also used to preallocate licenses to specificE "groups" (including the special, predefined "Server-Based" group; seee; below for details), and to reclaim a license from a client.d  E Each LAN needs only one active PATHWORKS License Server. (The new Li- F cense Server provided with PATHWORKS for OpenVMS (Advanced Server) canG support every kind of PATHWORKS client-based license, as well as Cliente+ Access licenses and all supported clients.)h  E The PATHWORKS License Registrar, which executes on the same system asnD the file server, verifies the licenses for clients requesting accessD to the server functions. Clients that can produce a valid Client Ac-D cess license are allowed access to the services offered by the PATH-0 WORKS V6.0 for OpenVMS (Advanced Server) server.   ____________________F  Although  the License Server is active on a single node in a cluster,D   if that node goes down for any reason, the License Server will au-D   tomatically activate itself on another node in the cluster that is     still running PATHWORKS.  "                                 13    I  G o  Server-Based License Management. The PATHWORKS V6.0 for OpenVMS (Ad-tF    vanced Server) server also allows client access based on the avail-D    ability of Client Access licenses in the local LMF database beingI    used in server-based mode. If a client requesting access to the servertD    fails to produce a sufficient client-based license, the PATHWORKSD    License Registrar software checks for the availability of a validC    Client Access license being used in server-based mode. If one iss+    available, the client is allowed access.r  F Client Access licenses can be put into server-based mode in one of two ways:e  E    -  If the PATHWORKS License Server facility was not configured foriE       the system where PATHWORKS for OpenVMS (Advanced Server) is ex-dD       ecuting, then all Client Access licenses loaded into the localD       LMF database on that system will be used in server-based mode.  E    -  If the PATHWORKS License Server facility was configured for theoE       system where PATHWORKS for OpenVMS (Advanced Server) is execut- D       ing, then all Client Access licenses loaded into the local LMF>       database will, by default, be used in client-based mode.  G To allow some or all of these licenses to be used in server-based mode,pD use the PATHWORKS License Manager and allocate those licenses to theC special, predefined group called the "Server-Based" group. LicensesuD available in the "Server-Based" group will then be available for use in server-based mode.5  D Note: PATHWORKS V6.0 for OpenVMS (Advanced Server) server allows youC to use Client Access licenses in both client-based and server-baseddF mode, simultaneously. However, because clients using Client Access li-H censes in client-based mode are already licensed to use the server soft-D ware, they never consume additional Client Access licenses allocatedI for use in server-based mode by a PATHWORKS for OpenVMS (Advanced Server)n server./          "                                 14 e  s  ! Accommodation of Retired Featuresr  E The following features of PATHWORKS V5.x for OpenVMS are not provided. in PATHWORKS V6.0 for OpenVMS:  D o  Standalone and member server roles. PATHWORKS Advanced Server may:    be configured as a Primary or Backup Domain Controller.  D o  FAT volumes. To continue to provide FAT volume access to clients,C    you must maintain the PATHWORKS LAN Manager server on a separateND    system. Files held within shares on a FAT volume must be migratedF    to PATHWORKS LAN Manager shares before you upgrade to PATHWORKS Ad-    vanced Server.g  E o  Backward compatibility mode. This mode was used to ease the migra- C    tion from PATHWORKS V4.x to PATHWORKS LAN Manager. Make sure all-C    clients making use of this connection format are upgraded beforer1    the installation of PATHWORKS Advanced Server.n  E o  Remote Boot service. If clients depend on remote booting, you musteI    maintain the PATHWORKS LAN Manager server on a separate system. Trans-eE    fer this function to another server that supports Remote Boot ser-r    vice before the upgrade.s  D o  Share-level security. PATHWORKS Advanced Server manages access to-    all resources through user-level security.u  C o  LAN Manager and Creator security mode. The server can be config- F    ured for PATHWORKS Advanced Server Only security model or for PATH-4    WORKS Advanced Server and OpenVMS security model.  G o  PATHWORKS LAN Manager Net command line interface and ADMIN/PATHWORKSrF    character cell interface. These features were replaced by the PATH-C    WORKS Advanced Server ADMINISTER command line interface. The AD-aD    MINISTER command line interface provides automatic translation of9    Net commands that have ADMINISTER command equivalents.s        "                                 15    v  F A PATHWORKS LAN Manager server can be upgraded to a PATHWORKS AdvancedH Server or can continue running PATHWORKS LAN Manager and act as a BackupE Domain Controller, member server, or standalone server in a domain inlE which the Primary Domain Controller is a PATHWORKS Advanced Server oreF a Windows NT Server computer. PATHWORKS Advanced Server maintains com-7 patibility with LAN Manager client and server software.s                                                                    "                                 16 t  f   HARDWARE REQUIREMENTSE  E The following systems, components, and peripherals specified are sup-a ported except as noted.M   Processors Supported  C All Alpha processors supported by the OpenVMS V7.1 Operating SystemnC are also supported by PATHWORKS V6.0 for OpenVMS (Advanced Server).w   Memory Requirementsr  D On Alpha systems, PATHWORKS Advanced Server requires a minimum of 64E MB of physical memory for proper installation, configuration, and ex-  ecution of the software.  C Note: This memory requirement is a minimum requirement only. Memory D requirements can vary widely according to the server CPU, the numberD of clients using the server and their activities, and the number andE speed of the server's disks and the other applications running on ther server.(  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires ansD Alpha system with approximately 64 MB of memory. This means that 80%I of the system memory and CPU time are dedicated to PATHWORKS, even thoughl some work may use less.e  . Disk Space Requirements (Block Cluster Size=1)  D The following table provides the disk space requirements for the in-D stallation and configuration of PATHWORKS V6.0 for OpenVMS (AdvancedC Server) either standalone or with PATHWORKS V1.0G for OpenVMS (Net- F Ware) software. By default, all entries are directed to the same disk,, but each may be directed to different disks.  C These sizes are approximate; actual sizes may vary depending on theA? user's system environment, configuration, and software options.d    "                                 17    a  D You should also plan for additional, significant disk-space require-E ments for items such as data files, virtual memory section files, logo0 files - after the product is started and in use.                                                                          "                                 18 y  r    C Installation/Configuration_________Alpha_Systems___________________nC Requirements_______________________(Blocks)________________________s   Images and command files: *     Advanced Server software       105,000 only*     with NetWare software          141,000* NetWare SYS Volume[1]               34,000   PATHWORKS server data files:*     Advanced Server software        77,500 only+     with NetWare software           Same[2]h* NetWare Configuration files,       __1,000 etc.[3]t   Totals:o*     Advanced Server software       182,500 only*     with NetWare software          219,500C ___________________________________________________________________n@ [1]The NetWare SYS Volume contains the NetWare utilities used by, NetWare clients to interact with the server.  ? [2]No additional space is required for configuration of NetWarei with Advanced Server. C [3]These_files_are_typically_stored_on_the_OpenVMS_system_disk.____e   OPTIONAL HARDWAREa   PostScript Printers   E PATHWORKS V6.0 for OpenVMS supports all PostScript printers supported D by DECprint Supervisor (DCPS) for OpenVMS. Refer to SPD 44.15.xx forG a complete list of the DIGITAL and non-DIGITAL PostScript printers sup-nC ported by DCPS. DECprint Supervisor software is included with PATH-RE WORKS V6.0 for OpenVMS. The right to use the DCPS software is granted     "                                 19 o  I  E by the DCPS Open license which is included in the PATHWORKS for Open-aE VMS (Advanced Server) PC Concurrent license and the PATHWORKS for DOSe& and Windows Designated Access license.  G DIGITAL PostScript printers connected by serial lines or DECservers[TM]p= and printers attached directly to the Ethernet are supported.r   Non-PostScript Printerso  E PATHWORKS V6.0 for OpenVMS also supports the following non-PostScriptn	 printers.a  & LA75 Companion Printer     EPSON FX850' LA210                      EPSON FX1050o LA310i) LA324[TM]                  IBM ProPrinter 7 LA424                      SilentWriter[R] II Model 290r LJ250 Companion Coloro Printer 
 LN03[TM] PLUSe   Network Interface ControllersL  C PATHWORKS for OpenVMS (Advanced Server) supports the following Eth-S5 ernet, FDDI, and Token Ring network hardware devices:s  D o  For the TCP/IP transport, PATHWORKS for OpenVMS (Advanced Server)F    supports the network hardware devices supported by the specific TCPF    /IP product. For DIGITAL's TCP/IP Services for OpenVMS, consult SPDC    46.46.xx (for Alpha systems). For other TCP/IP products, contacto    the vendor.  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see'    the SPDs for the following products:l  6    -  DECnet-Plus V7.1 for OpenVMS Alpha, SPD 50.45.xx  1    -  DECnet for OpenVMS Alpha V7.1, SPD 48.48.xxw    "                                 20 W  o  E o  For the NetBEUI transport, PATHWORKS for OpenVMS (Advanced Server)wH    provides the same level of support for Ethernet and FDDI as the Open-@    VMS Operating System. For more information, see SPD 25.01.xx.  E The PATHWORKS V6.0 for OpenVMS server does not support the DEFZA FDDI  controller.c   CLUSTER ENVIRONMENTx  F PATHWORKS V6.0 for OpenVMS (Advanced Server) supports Alpha-supported,F OpenVMS cluster configurations. OpenVMS cluster configurations for Al-C pha systems are fully described in the OpenVMS Cluster Software fort: OpenVMS Alpha Software Product Description (SPD 42.18.xx).  E PATHWORKS V6.0 for OpenVMS (Advanced Server) supports up to 31 servertD nodes in cluster. In other words, no more than 31 nodes in a clusterE can run PATHWORKS V6.0 for OpenVMS (Advanced Server) concurrently. In C a typical scenario, the server is run on only a few central nodes -oE to exploit the cluster's shared disks and high speed interconnect en-p
 vironment.  C In a cluster, PATHWORKS V6.0 for OpenVMS (Advanced Server) supportsnC simultaneous file access by all nodes running the server. A centralaD event log, central Advanced Server accounts, and share databases areH maintained in a cluster. In an Advanced Server domain, the OpenVMS clus-G ter represents a single domain member, whether it is acting as the Pri-c8 mary Domain Controller or as a Backup Domain Controller.   SOFTWARE REQUIREMENTSe   Operating System   For Alpha Systems:  & o  OpenVMS Alpha Operating System V7.1  C For minimum hardware requirements of the operating system, refer todF the Software Product Description for the OpenVMS Operating System (SPD
 25.01.xx).  "                                 21 e  e   Network Transport Software  C PATHWORKS V6.0 for OpenVMS includes NetBEUI network transport soft- F ware. DECnet or TCP/IP network transport software may also be requiredD by PATHWORKS for OpenVMS, depending on the transport used by clients@ requiring connections to the server or for use of some features.  D The following DECnet and DECnet-Plus products are supported by PATH- WORKS V6.0 for OpenVMS:r   For Alpha Systems:  3 o  DECnet-Plus V7.1 for OpenVMS Alpha, SPD 50.45.xxs  . o  DECnet for OpenVMS Alpha V7.1, SPD 48.48.xx  F When PATHWORKS V6.0 for OpenVMS is to be used in a TCP/IP environment,E OpenVMS-based TCP/IP software is required. This software must be pur-,D chased separately. The following TCP/IP transports support PATHWORKS V6.0 for OpenVMS:v  - o  DIGITAL's TCP/IP Services for OpenVMS V4.1m  ? o  Process Software Corporation's[TM] Multinet[TM] V4.0, Rev. Ba  = o  Process Software Corporation's TCPware[R] for OpenVMS V5.1l   Other PATHWORKS Server Software   D PATHWORKS V6.0 for OpenVMS (Advanced Server) and PATHWORKS V1.0G forF OpenVMS (NetWare) share some common components. As a result, only cer-F tain combinations of PATHWORKS server software can run on the same ma- chine at the same time.e  E The following PATHWORKS server products can run on the same system asa- PATHWORKS V6.0 for OpenVMS (Advanced Server):s  - o  PATHWORKS V1.3A for OpenVMS (Macintosh[R])i  ( o  PATHWORKS V1.0G for OpenVMS (NetWare)  "                                 22       C The following PATHWORKS server products cannot run on the same sys-e4 tem as PATHWORKS V6.0 for OpenVMS (Advanced Server):  G o  PATHWORKS V1.0x for OpenVMS (NetWare). If the V1.0x (NetWare) serversF    is installed on a system to which the V6.0 (Advanced Server) serverC    is added, the V1.0 (NetWare) server is automatically upgraded toiE    the V1.0G (NetWare) server. Only PATHWORKS V1.0G for OpenVMS (Net- F    Ware) can run on the same system as PATHWORKS V6.0 for OpenVMS (Ad-    vanced Server).  G o  PATHWORKS for OpenVMS V5.x. The PATHWORKS V6.0 for OpenVMS (AdvancedeC    Server) server can be upgraded from the V5.x server. Running theeC    V6.0 server on a system also running the V5.x server is not pos- C    sible or supported. You cannot continue to run the PATHWORKS LANrG    Manager software, once the PATHWORKS Advanced Server server has beennE    installed. PATHWORKS V6.0 for OpenVMS (Advanced Server) cannot co- @    exist on the same OpenVMS cluster with PATHWORKS V5.x server.  F PATHWORKS Advanced Server maintains full down-level compatibility withD LM client and server software. LM users can add a PATHWORKS AdvancedH Server to an existing network and migrate to the new technology at theirE own pace. A PATHWORKS LAN Manager server can be upgraded to PATHWORKSsE Advanced Server technology or act as a Backup Domain Controller, mem-aF ber server, or standalone server in a network in which the Primary Do-E main Controller is a PATHWORKS Advanced Server or a Windows NT ServerWD computer. The PATHWORKS Advanced Server can be deployed as a PrimaryK Domain Controller in a network comprising other PATHWORKS Advanced Servers, H Windows NT Servers, DIGITAL PATHWORKS for OpenVMS (LAN Manager) servers,C or LAN Manager for OS/2 Servers. It can also act as a Backup DomainoC Controller for other PATHWORKS Advanced Server or Windows NT Server.
 computers.   Client Software   D The following versions of client software are supported for use with PATHWORKS V6.0 for OpenVMS:t  " o  PATHWORKS 32 V7.0, SPD 56.33.xx    "                                 23 a  a  3 o  PATHWORKS V6.0 for DOS and Windows, SPD 55.07.xxT  - o  PATHWORKS V4.1 for Window NT, SPD 51.56.xxi  ( o  PATHWORKS V5.1 for OS/2, SPD 55.24.xx  9 o  Microsoft Windows NT workstation software V3.5 or V4.0   ) o  Microsoft Windows for Workgroups V3.11    o  Microsoft Windows 95r   GROWTH CONSIDERATIONS   E The minimum hardware and software requirements for any future versionAC of this product may be different from the requirements for the cur-n
 rent version.                                               "                                 24 r  r  C ___________________________________________________________________e  @ PRODUCT NAME:  DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager)   DESCRIPTIONe  D DIGITAL PATHWORKS V5.0F for OpenVMS (LAN Manager) is an OpenVMS lay-D ered application that provides the functions of a Microsoft LAN Man-D ager V2.2 server in a PC LAN environment - with additional features.D It is a member of the PATHWORKS family of products, which provides aC framework for integrating personal computers into an organization'sWF total information system, allowing users to share information and net-- work services across the entire organization.r  E The PATHWORKS family includes PC LAN server products running on Open-nD VMS, DIGITAL UNIX, ULTRIX[TM], SCO[TM] UNIX, and OS/2 platforms pro-E viding industry-standard Network Operating System (NOS) services thateD use Novell[R]'s NetWare, Microsoft's LAN Manager, and Apple[R]'s Ap-F pleShare[R] protocols. The PATHWORKS family also includes client soft-C ware for these servers, consisting of a multi-NOS management inter-rF face called ManageWORKS[TM], enterprise-wide support capabilities suchE as wide area transports (DECnet and TCP/IP), and applications such asrD Mail and Terminal Emulation, allowing DOS, Windows, Windows NT, Win-D dows 95, Windows for Workgroups, OS/2, and Macintosh clients to par-> ticipate as full peers in a distributed computing environment.   FEATURES  C PATHWORKS V5.0F for OpenVMS adds a new dimension to general purpose G OpenVMS systems. In addition to providing traditional support for busi-eC ness, scientific, and engineering applications, this product allowsfE an OpenVMS system to appear to LAN Manager clients as a Microsoft LANcC Manager server. PATHWORKS V5.0F for OpenVMS is an implementation ofr- industry-standard Microsoft LAN Manager V2.2.i  F The major features of PATHWORKS V5.0F for OpenVMS are described in the following sections.o      "                                 25       
 File Services   C PATHWORKS V5.0F for OpenVMS provides LAN Manager-based clients withiC a remote file system that appears as a transparent extension of thee, client system's local computing environment.  C PATHWORKS for OpenVMS file shares are based on Microsoft's LAN Man-a/ ager V2.2 SMB (Server Message Block) protocols.d  F Each file stored in a file service is stored as an OpenVMS file in RMSC format. Three types of RMS file/record formats are allowed and sup-c ported on each volume:   o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefinedd  D Files stored in a file service are accessible to PC clients, OpenVMSC users, and to applications that can interpret the content and orga- : nization of the file as written by the client application.  D Multiple LAN Manager clients can concurrently access files stored onD the server's disk through the file access modes and byte range lock-5 ing support provided by the OpenVMS Operating System.    Print Shares  D PATHWORKS for OpenVMS software allows DOS, Windows, Windows NT, Win-C dows 95, OS/2, and OpenVMS users to share printers connected to Al-rD pha, VAX, or VAXserver[TM] computers and to OpenVMS cluster systems,P as well as network-based printers such as LAT printers and DIGITAL PrintServers.D Print shares are supported in local area and wide area network envi-F ronments. PC clients can print files from the DOS, OS/2, Windows, Win-C dows 95, and Windows NT operating systems as well as from PC appli-. cations.      "                                 26 e  r  D Multiple print shares may be defined for a single printer. For exam-E ple, separate services may be created for landscape-mode printing andiC portrait-mode printing. Similarly, separate services may be createdLC for DIGITAL mode and IBM ProPrinter mode printing for a single LA75  printer.  C PATHWORKS V5.0F for OpenVMS includes the DECprint Supervisor (DCPS)pD Open product, which provides PostScript and DEC ANSI printing to se-- lected industry-standard PostScript printers.   3 Sharing of Network Resources by Heterogeneous Usersa  F Services provided by PATHWORKS for OpenVMS are accessible to PATHWORKSF LAN Manager-based clients as well as to Microsoft LAN Manager clients.F All clients using the services of a PATHWORKS V5.0F for OpenVMS serverF must be properly licensed. (See the Software Licensing section of thisE SPD.) Files are stored on the server in native OpenVMS Record Manage-vE ment Services (RMS) format. This allows information stored by the PCs H using PATHWORKS for OpenVMS to be shared with traditional OpenVMS users.C In addition, this feature allows information to be shared among all D PATHWORKS clients, including those not based on LAN Manager technol-C ogy. Concurrent file access by host applications or non-LAN ManagerR clients is not supported.l   Network Transport SupportO  E PATHWORKS V5.0F for OpenVMS supports DECnet, DECnet-Plus, TCP/IP, andTD NetBEUI network transport software. One or multiple transport stacks$ can work concurrently on the server.  D The TCP/IP transport, which is sold as a separate product and avail-E able from various vendors, must include a PATHWORKS IP (PWIP) driver.   C NetBEUI transport software is included with the PATHWORKS V5.0F foraG OpenVMS software. Using NetBEUI transport software, LAN Manager clientsaJ can access the server in the local area network for file and print shares.  D See the Software Requirements section of this SPD for information on% supported network transport software.K  "                                 27 i  w   NetBIOS Interface Supportr  E PATHWORKS V5.0F for OpenVMS supports the NetBIOS interface in DECnet, D TCP/IP, and NetBEUI networks. PATHWORKS for OpenVMS utilizes NetBIOSC naming services and datagram services. A NetBIOS programming inter-iE face is not provided, however. NetBIOS interface support includes thelE support of multiple transport stacks on a single or different networkoD controllers. NetBIOS support under TCP/IP includes a b-node RFC 1001E /1002 implementation. This implies that the NetBIOS interface is sup-a< ported under TCP/IP in local area network environments only.   Flexible Security Models  D The PATHWORKS V5.0F for OpenVMS security model accommodates both theE LAN Manager security model and the OpenVMS security model. The servereC may be configured to use the security implementation best suited tosE the environment. In "LAN Manager Only" mode, the LAN Manager securitytD model is enforced. In "LAN Manager and OpenVMS" mode, both the Open-E VMS and LAN Manager security models are enforced. In "LAN Manager andoH Creator" mode, OpenVMS security is applied to files not created by users of the PATHWORKS server.   Domain Support  D PATHWORKS V5.0F for OpenVMS allows the network to be subdivided intoE administrative groups of servers and clients called domains. A domain C is a group of servers and clients on a LAN and is the basic unit oflE network administration. Each server running PATHWORKS for OpenVMS canrE be a member of a single domain. A PATHWORKS for OpenVMS server can beoE a Primary Domain Controller, Backup Domain Controller, Member Server,hC or a Standalone Server, depending on the environment. Domains are aaD convenient mechanism for controlling user access to the network, and for managing large networks.              "                                 28    o  C PATHWORKS V5.0F for OpenVMS also provides support for wide area do-tC mains using the LMHosts file. This file's presence on the PATHWORKSiC for OpenVMS (LAN Manager) server allows NET Logons and UAS replica- E tion over some wide area TCP/IP configurations. The LMHosts file con- F tains a list of nodes from geographically disperse sites that are syn-D chronized by the primary domain controller and accessible to clientsC in the server's domain. However, use of the LMHosts file for repli-SC cation over extreme distances or in networks with slow transmission  speeds is not recommended.   Network Logon Services  E The domain capabilities of LAN Manager make it possible for a user to0H issue a single logon request in order to gain access to multiple serversF in a LAN. Running the netlogon service forces the validation of users'F logon requests. The logon server that processes the request checks itsD copy of the domain-wide user accounts database for the user name and' password supplied in the logon request.e   LAN Manager V2.2 API Support  E PATHWORKS V5.0F for OpenVMS supports the LAN Manager V2.2 ApplicationrC Programming Interfaces, with the exception of Named Pipes and Mail-eD slots. Note that LAN Manager APIs are not available to OpenVMS host-D based applications, but are available to PATHWORKS LAN Manager-basedI clients, non-PATHWORKS LAN Manager clients, and OS/2 LAN Manager servers.R   Remote Boot1  E The remote boot service included with PATHWORKS V5.0F for OpenVMS al-eF lows DOS and Windows workstations to start up using information storedC on the server's hard disk instead of on their own local hard disks. C The PATHWORKS V5.0F for OpenVMS remote boot service is based on Mi-PE crosoft's LAN Manager remote boot service, which uses the Remote Pro-nG gram Load (RPL) protocol. Remote boot is supported over NetBEUI on Eth- E ernet networks. PATHWORKS V5.0F for OpenVMS supports MOP (Maintenances        "                                 29 t  e  D Operation Protocol) as a secondary loader for clients without an RPL ROM.  
 Mail Servicese  E PATHWORKS V5.0F for OpenVMS includes a mail server component that al-aD lows clients to send and receive electronic mail. The mail server isD based on the OpenVMS MAIL-11 product and requires DECnet as its com-E munications transport. It allows users of PATHWORKS Mail client soft-eC ware to send and receive electronic mail messages without having to 4 log in to the OpenVMS system as an interactive user.  F A mail account may be established on the OpenVMS server for each user.F Mail can be sent to this account by other PATHWORKS Mail users as wellC as traditional users of OpenVMS mail software. The mail server thentE routes messages to the appropriate client when the user logs onto thef server.s  F The PATHWORKS for OpenVMS mail server provides the PATHWORKS user withD folders, distribution lists, and delivery capabilities. Realtime no-C tification of new messages can be optionally enabled by the client.A   Time and Date Services  D DOS, Windows, and OS/2 clients can request date and time informationE from the server system and set the local workstation date and time top coincide with them.r   PATHWORKS FAT File Systeml  C PATHWORKS V5.0F for OpenVMS includes the PATHWORKS FAT file system,.D which is an alternative to, and designed to coexist with the OpenVMSE ODS-2 file system. It is based on the DOS File Allocation Table (FAT)NE file system. PC files stored in the FAT file system are stored in na-hE tive DOS format in a container file on the server system. Features oft& the PATHWORKS FAT file system include:  A o  support for multiple readers and writers of the container fileo    "                                 30 K  6  E o  wide-area network access to files stored on the server in DOS for-t    mat  G o  improved performance on file and directory operations over the Open-O    VMS ODS-2 file system  F The PATHWORKS FAT file system may be used as a migration path from ex-E isting PATHWORKS V4.x disk service container files (see Accommodationr of Retired Features)..   Server Management and Controlf  E PATHWORKS V5.0F for OpenVMS supports several server management inter-o faces:  C o  ManageWORKS, a Windows-based utility supplied with the PATHWORKS,+    V5.0F for DOS and Windows client products  7 o  A character cell utility called ADMINISTER/PATHWORKSe  D o  The LAN Manager NET ADMIN command line interface which may be ac-E    cessed from a terminal or terminal emulator, or from a LAN ManagerE>    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  E o  Display and control server resources currently in use, such as ac-.+    tive sessions, connections, and servicese  = o  View context-sensitive Help for each menu item and commandu   PATHWORKS Monitorr  E The PATHWORKS Monitor utility is a Windows-based application providedoD with the PATHWORKS V5.0F for OpenVMS server software. PATHWORKS Mon-F itor collects data on server resource utilization and provides a real-+ time graphical display of this information.s  "                                 31 6  f   PATHWORKS Configurationy  C The PATHWORKS Configuration utility is an OpenVMS-based applicationCD that allows the user to modify the server's configuration. For exam-C ple, the user can configure the data cache size, the security mode,fC the number of supported clients and more. Any adjustments that needeG to be made to the OpenVMS SYSGEN parameters are automatically performedD by the Configuration utility.e   Enhanced Cluster Support  H PATHWORKS V5.0F for OpenVMS includes support for a transport-independentF PATHWORKS cluster alias name service that allows multiple cluster mem-D bers to appear as a single server to the connecting clients, provid-E ing higher availability. The PATHWORKS cluster alias name has a load-lC balancing feature which connects clients to the cluster member that E is the least loaded at the time the session is established. PATHWORKSoD V5.0F for OpenVMS also includes a high performance cluster-wide dis-E tributed data cache that provides scalability in a clustered environ-PC ment. VAX clusters, Alpha clusters, and mixed-architecture clusters - are supported by PATHWORKS V5.0F for OpenVMS.p   Enhanced Performance via XQP+s  F PATHWORKS V5.0F for OpenVMS includes a special release of the enhancedF OpenVMS file system, known as XQP+ (eXtended QIO Processor Plus). XQP+F is separately installable to OpenVMS VAX V5.5-2. XQP+ is included withD OpenVMS VAX and Alpha V6.1 and later. When PATHWORKS V5.0F for Open-C VMS detects the existence of the enhanced file system, it automati-cC cally takes advantage of its improved concurrency, multi-threading,eD and directory caching features to provide better performance to file system operations.                "                                 32 u  n   Installation Utilities  D PATHWORKS V5.0F for OpenVMS is installed on the OpenVMS system usingC the standard VMSINSTAL procedure. An Installation Verification Pro-,D cedure (IVP) is also included, which can be used to confirm that the, server software has been installed properly.  E The installation procedure allows you to install just the LAN Manager.F server, just the NetWare server or both. It also allows you to install" just the PATHWORKS License Server.  D DIGITAL recommends that a customer's first purchase of this softwareG product at each site include DIGITAL installation service. Contact your C local DIGITAL representative for information on the service optionsc
 available.   Security  D External authentication is an optional feature introduced in OpenVMSC Version 7.1 that enables OpenVMS systems to authenticate designatediE users using their LAN Manager domain using a single username/passwordeD combination. This feature is supported in PATHWORKS V5.0E and later.C For more information about external authentication for OpenVMS VAX,n see SPD 25.01.xx.e   License Management  D PATHWORKS for OpenVMS offers license management for client-based li-C censes (CCS, FPA, Designated Access, System, and CNS), server-basedlD licenses (FPS or PC Concurrent), and the new Client Access licenses,C which can be used in either client-based or server-based mode. (See0( Software Licensing section for details.)  F The license deliverables for PATHWORKS products are Product Authoriza-D tion Keys (PAKs) that are then used with the OpenVMS License Manage-D ment Facility (LMF). These PAKs must be loaded into an LMF database,        "                                 33 W  g  C using standard LMF procedures, on an OpenVMS system that is hostinghA a PATHWORKS server or is acting as a PATHWORKS License Server.[2]A  D o  Client-Based License Management. PATHWORKS for OpenVMS provides aD    facility called the PATHWORKS License Server that acts as a proxyJ    for client systems that require license keys stored in the LMF database    on an OpenVMS system.  C A single copy of the PATHWORKS License Server software provides and)D verifies client-based licenses, or Client Access licenses being usedC in client-based mode, for clients using NetWare or LAN Manager pro- C tocols. NetWare clients use the IPX transport to communicate with adG PATHWORKS License Server, while PATHWORKS LAN Manager clients and PATH-hG WORKS Advanced Server clients use the DECnet, TCP/IP, or NetBEUI trans-n port.'  E The PATHWORKS License Manager, which must execute on the same node as-D the License Server, provides a user interface that allows the admin-I istrator to monitor client-based license usage, to manage license groups,TD set alert levels, set logging levels for licensing events, enable orC disable the License Server, and revoke assigned licenses. The PATH-WF WORKS License Manager is also used to preallocate licenses to specificE "groups" (including the special, predefined "Server-Based" group; sees; below for details), and to reclaim a license from a client.a  E Each LAN needs only one active PATHWORKS License Server. (The new Li-aD cense Server provided with PATHWORKS V5.0F for OpenVMS (LAN Manager)D can support every kind of PATHWORKS client-based license, as well as3 Client Access licenses, and all supported clients.)-  E The PATHWORKS License Registrar, which executes on the same system asRD the file server, verifies the licenses for clients requesting accessF to the server functions. Clients that can produce a valid client-basedE license, or Client Access license, are allowed access to the servicesl@ offered by the PATHWORKS V5.0F for OpenVMS (LAN Manager) server.   ____________________G  Although  the License Server can be active on a single node in a clus-rE   ter, if that node goes down for any reason, the License Server will F   automatically activate itself on another node in the cluster that is     still running PATHWORKS.  "                                 34 o  p  C o  Server-Based License Management. The PATHWORKS V5.0F for OpenVMSaE    (LAN Manager) server also allows client access based on the avail-pD    ability of valid server-based licenses (either FPS and/or PC Con-E    current), and/or Client Access licenses being used in server-based C    mode in the local LMF database. If a client requesting access toRE    the server fails to produce a sufficient client-based license, thecC    PATHWORKS License Registrar software checks for the availabilityeF    of a valid server-based license or Client Access license being usedF    in server-based mode. If one is available the client is allowed ac-    cess.  F Client Access licenses can be put into server-based mode in one of two ways:r  E    -  If the PATHWORKS License Server facility was not configured foruC       the system where PATHWORKS V5.0F for OpenVMS (LAN Manager) iscD       executing, then all Client Access licenses loaded into the lo-H       cal LMF database on that system will be used in server-based mode.  E    -  If the PATHWORKS License Server facility was configured for the C       system where PATHWORKS V5.0F for OpenVMS (LAN Manager) is ex-tD       ecuting, then all Client Access licenses loaded into the localB       LMF database will, by default, be used in client-based mode.  G To allow some or all of these licenses to be used in server-based mode,lD use the PATHWORKS License Manager and allocate those licenses to theC special, predefined group called the "Server-Based" group. Licenses D available in the "Server-Based" group will then be available for use in server-based mode.e  D Note: PATHWORKS V5.0F for OpenVMS (LAN Manager) server allows you toF use both client-based and server-based licensing, simultaneously. How-C ever, because clients using client-based licenses, or Client Access7E licenses in client-based mode, are already licensed to use the servervH software, they never consume additional server-based licenses, or ClientF Access licenses allocated for use in server-based mode, by a PATHWORKS' V5.0F for OpenVMS (LAN Manager) server.       "                                 35 a  a  ! Accommodation of Retired Featuresa  E The following features of PATHWORKS V4.x for OpenVMS are not providedn in PATHWORKS V5.0F for OpenVMS:0   o  File services over LAST   o  Disk services   o  Remote boot over LAST  D If PATHWORKS V5.0F for OpenVMS is installed on a server system whichD had been running V4.x of the product, some aspects of the V4.x envi-D ronment related to the features listed above will be preserved. DiskE services will remain intact and available to pre-V5.0F clients. LAST-eC based remote boot services will also remain intact and available toA pre-V5.0F clients.   HARDWARE REQUIREMENTSs  F The systems, components, and peripherals specified below are supported except as noted.   Processors Supported  E All VAX and Alpha processors that are supported by the version of therE OpenVMS operating system in use are also supported by PATHWORKS V5.0Fr8 for OpenVMS (LAN Manager) with the following exceptions:  2 MicroVAX    MicroVAX I, MicroVAX II, MicroVAX 2000  A VAXstation  VAXstation I, VAXstation II, VAXstation 2000, VAXsta-p             tion 8000d  ? VAX         VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAXn             11/782, VAX 11/785        "                                 36 e  r   Memory Requirementsa  C PATHWORKS V5.0F for OpenVMS requires the following minimum physicaloC memory for proper installation, configuration, and execution of the 	 software:7  8    16 MB on VAX systems (24 MB if used with DECnet-Plus)      64 MB on Alpha systemsS  F Note that the memory requirements indicated above are minimum require-E ments only, and that memory requirements can vary widely according tooD the server CPU, the number of clients using the server and their ac-F tivities, the number and speed of the server's disks and the other ap-! plications running on the server.t  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires anID Alpha system with approximately 64 MB of memory or a VAX system withE approximately 16 - 24 MB of memory. This assumes that 80% of the sys-eD tem memory and CPU time are dedicated to PATHWORKS, even though some work loads may use less.  . Disk Space Requirements (Block Cluster Size=1)  D The following table provides the disk space requirements for the in-E stallation and configuration of PATHWORKS V5.0F for OpenVMS (LAN Man- F ager) either stand-alone or with PATHWORKS V1.0F for OpenVMS (NetWare)D software. By default, all entries are directed to the same disk, but( each may be directed to different disks.                    "                                 37 b  i    C Installation/Configuration_________________________________________dC Requirements______________________VAX_systems_____Alpha_systems____n   Installation Space Require-  ments:   Images and command files:n@         LAN Manager software,      40,000          60,000 blocks( only                              blocks@         with NetWare software      44,000          66,000 blocks(                                   blocks@   NetWare SYS Volume[1]            34,000          34,000 blocks(                                   blocks     PATHWORKS server data files:@         LAN Manager software,      12,500          12,500 blocks( only                              blocks:         with NetWare software      same[2]         same[2]@   NetWare Configuration files,      1,000           1,000 blocks( etc.[3]                           blocks        Totals:@         LAN Manager software,      52,500          72,500 blocks( only                              blocks@         with NetWare software      91,500         113,500 blocks(                                   blocksC ___________________________________________________________________a@ [1]The NetWare SYS Volume contains the NetWare utilities used by, NetWare clients to interact with the server.  ? [2]No additional space is required for configuration of NetWareo with LAN Manager.tC [3]These_files_are_typically_stored_on_the_OpenVMS_system_disk.____a  C These sizes are approximate; actual sizes may vary depending on theu? user's system environment, configuration, and software options.r  D You should also plan for additional, significant disk-space require-D ments after the product is started and in use for items such as data= files, virtual memory section files, log files, and so forth.p  "                                 38 t  h   OPTIONAL HARDWAREr   PostScript PrintersV  C PATHWORKS V5.0F for OpenVMS supports those PostScript printers thatrE are supported by DECprint Supervisor (DCPS) for OpenVMS. Refer to SPDrF 44.15.xx for a complete list of the DIGITAL and non-DIGITAL PostScriptD printers supported by DCPS. DECprint Supervisor software is includedD with PATHWORKS V5.0F for OpenVMS. The right to use the DCPS softwareF is granted by the DCPS Open license which is included in the PATHWORKSF for OpenVMS (LAN Manager) PC Concurrent license, and the PATHWORKS for8 DOS and Windows (LAN Manager) Designated Access license.   Non-PostScript Printers   D PATHWORKS V5.0F for OpenVMS also supports the printers listed below:      LN03 PLUS       LJ250 Companion Color Printer      LA75 Companion Printer       LA210    LA310    LA324    LA424      IBM ProPrinter.      SilentWriter II Model 290      EPSON FX850    EPSON FX1050e  D DIGITAL PostScript printers connected by serial lines or DECservers,= and printers attached directly to the Ethernet are supported.d      "                                 39 n  r   Network Interface Controllersa  D PATHWORKS for OpenVMS (LAN Manager) supports Ethernet, FDDI, and To-5 ken Ring network hardware devices as described below:r  E o  For the TCP/IP transport, PATHWORKS for OpenVMS (LAN Manager) sup-oC    ports the network hardware devices supported by the specific TCPlF    /IP product. For DIGITAL's TCP/IP Services for OpenVMS, consult SPDF    46.46.xx (for Alpha systems) or SPD 25.A4.xx (for VAX systems). For-    other TCP/IP products, contact the vendor.n  E o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see:i  :    -  SPD 42.25.xx for DECnet for OpenVMS AXP, Version 6.1  C    -  SPD 25.03.xx for DECnet/OSI V7.0 (or DECnet-Plus) for OpenVMSe       on VAX systems  C    -  SPD 50.45.xx for DECnet/OSI, Version 7.0 (or DECnet-Plus Ver-e!       sion 7.1) for OpenVMS Alphai  D    -  SPD 48.48.xx for DECnet for OpenVMS VAX and Alpha, Version 7.0  F o  For the NetBEUI transport, PATHWORKS for OpenVMS (LAN Manager) pro-E    vides the same level of support for Ethernet and FDDI as the Open-DF    VMS operating system. For more information, see SPD 25.01.xx. PATH-F    WORKS V5.0F for OpenVMS (LAN Manager) does not support NetBEUI over    Token Ring on VAX systems.l  F The PATHWORKS V5.0F for OpenVMS server does not support the DEFZA FDDI controller.o   CLUSTER ENVIRONMENT   D PATHWORKS V5.0F for OpenVMS (LAN Manager) supports all OpenVMS clus-D ter configurations. OpenVMS cluster configurations for Alpha systems        "                                 40 c  n  C are fully described in the OpenVMS Cluster Software for OpenVMS Al-mE pha Software Product Description (SPD 42.18.xx). OpenVMS cluster con-eD figurations for VAX systems are fully described in the OpenVMS Clus-I ter Software for OpenVMS VAX Software Product Description (SPD 29.78.xx).   H PATHWORKS V5.0F for OpenVMS (LAN Manager) supports up to 31 server nodesF in cluster. In other words, no more than 31 nodes in a cluster can runD PATHWORKS V5.0F for OpenVMS (LAN Manager) concurrently. In a typicalC scenario, the server is run on only a few central nodes, to exploitlC the cluster's shared disks and high speed interconnect environment.   D In a cluster, PATHWORKS V5.0F for OpenVMS (LAN Manager) supports si-G multaneous file access by all nodes running the server. A central event G log and central LAN Manager accounts and share databases are maintainedaE in a cluster. In a LAN Manager domain, the OpenVMS cluster representssG a single domain member, whether it is acting as the primary domain con-c) troller or as a backup domain controller.o   SOFTWARE REQUIREMENTSo   Operating System   For Alpha Systems:  = o  OpenVMS Alpha Operating System V6.1, V6.2, V7.0, and V7.1.A   For VAX Systems:  C o  OpenVMS VAX Operating System V5.5-2, V6.1, V6.2, V7.0, and V7.1.g  F For minimum hardware requirements of the operating system refer to theC Software Product Descriptions for the OpenVMS operating system (SPD 
 25.01.xx).   OpenVMS Tailoringc  E For supported OpenVMS VAX V5.x systems, the following OpenVMS classesa< are required for full functionality of this layered product:   o  OpenVMS Required Savesetr  "                                 41 t  e  5 o  Network Support (required only for DECnet support)a   o  System Programming Supportu   o  Secure User's Environment   o  OPTL - Miscellaneous Fileso  C For more information on OpenVMS classes and tailoring, refer to theeI OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx).    Network Transport Software  D PATHWORKS V5.0F for OpenVMS includes NetBEUI network transport soft-F ware. DECnet or TCP/IP network transport software may also be requiredD by PATHWORKS for OpenVMS, depending on the transport used by clientsA requiring connections to the server, or for use of some features.n  G The following versions of DECnet and DECnet-Plus are supported by PATH-u WORKS V5.0F 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                         "                                 42    a   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 VAXi  C When PATHWORKS V5.0F for OpenVMS is to be used in a TCP/IP environ-FC ment, OpenVMS-based TCP/IP software is required. This software must F be purchased separately. The following TCP/IP transports support PATH- WORKS V5.0F for OpenVMS:  - o  DIGITAL's TCP/IP Services for OpenVMS V4.1i   o  Multinet V3.5 rev A  < o  Process Software Corporation's TCPware for OpenVMS V5.0-4  & o  The Wollongong Group's PathWay V1.1   Other PATHWORKS Server Software   G PATHWORKS V5.0F for OpenVMS (LAN Manager) and PATHWORKS V1.0F for Open-nF VMS (NetWare) now share some common components. As a result, only cer-F tain combinations of PATHWORKS server software can run on the same ma- chine at the same time.s  E The following PATHWORKS server products can run on the same system asl* PATHWORKS V5.0F for OpenVMS (LAN Manager):  ) o  PATHWORKS V1.x for OpenVMS (Macintosh)   ( o  PATHWORKS V1.0F for OpenVMS (NetWare)  C The following PATHWORKS server products cannot run on the same sys- 1 tem as PATHWORKS V5.0F for OpenVMS (LAN Manager):h  ) o  PATHWORKS V1.0x for OpenVMS (NetWare). F    If the V1.0x (NetWare) server is installed on a system to which theD    V5.0F (LAN Manager) server is added, the V1.0 (NetWare) server is  "                                 43 a  n  C    automatically upgraded to the V1.0F (NetWare) server. Only PATH-OH    WORKS V1.0F for OpenVMS (NetWare) can run on the same system as PATH-)    WORKS V5.0F for OpenVMS (LAN Manager).e   o  PATHWORKS for OpenVMS V4.x.C    The PATHWORKS V5.0F for OpenVMS server can be installed and con-AD    figured on a system running the V4.x server, but actually runningC    the V5.0F server on a system also running the V4.x server is note    possible or supported.    Client Software(  D The following versions of client software are supported for use with PATHWORKS for OpenVMS:  B 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).  C o  LAN Manager V2.2 workstation software for DOS, Windows, and OS/2   @ o  Microsoft Windows NT workstation software V3.1, V3.5, or V4.0  ) o  Microsoft Windows for Workgroups V3.11    o  Microsoft Windows 95T   GROWTH CONSIDERATIONSA  E The minimum hardware and software requirements for any future version C of this product may be different from the requirements for the cur- 
 rent version.y                "                                 44 a     C ___________________________________________________________________e  E LICENSING AND ORDERING INFORMATION:  DIGITAL PATHWORKS V6.0 and V5.0Fs   SOFTWARE LICENSING  E PATHWORKS V6 for OpenVMS (Advanced Server)[3] is purchased by licens-oE ing the clients or applications that use the services provided by theO$ product. There is no additional fee.  D The license that clients require to use the PATHWORKS V6 for OpenVMSD (Advanced Server) software is referred to as a Client Access licenseD (PAK Product Name: PWLMXXXCA06.00). Though there is only one licenseD sold for any client using this PATHWORKS server, this license can be used in one of two ways:  2 o  Client-based mode (also known as per-seat mode)  F o  Server-based mode (also known as per-server or concurrent use mode)  H These two different licensing modes are described in the following text.  C o  Client-Based Licensing Mode. When a license for PATHWORKS V6 foriD    OpenVMS (Advanced Server) is used in client-based licensing mode,   ____________________G  All  previous versions of PATHWORKS for OpenVMS (Advanced Server), in- E   cluding PATHWORKS V5.0F for OpenVMS (LAN Manager), are now licensedaD   for use in exactly the same way as PATHWORKS for OpenVMS (AdvancedE   Server).  Though previously purchased licenses continue to be valideF   for use with pre-V6 servers, only the new Client Access licenses may;   be purchased when adding new clients to existing systems.r  F    In particular, all the licenses listed in Table 2, Previous VersionG   Licenses Qualifying for Upgrade Licenses, are no longer sold but con-eE   tinue to be valid and grant the right to use the PATHWORKS V5.0 for_!   OpenVMS (LAN Manager) software.a      "                                 45 e  i  C    the right to use the server is assigned electronically to a par-aF    ticular client or seat. Once the right is assigned, the client sys-C    tem may access all systems running PATHWORKS V6 for OpenVMS (Ad- E    vanced Server) as well as all systems running any previous version     of PATHWORKS for OpenVMS.[4]   E This mode of licensing PATHWORKS servers is normally used when a cus-nC tomer has more than one PATHWORKS server and where clients normallyeF access more than one server at the same time. Because only one licenseC per client is required regardless of how many servers are being ac-iG cessed, the client-based licensing mode can be more economical in these @ situations when compared to server-based mode (described later).  E Because a client with a client-based license cannot be refused accessaF to a server due to license limits, this mode of licensing is also use-C ful when you need to guarantee that a particular system will alwaysP# have access to one or more servers.n  H Note: To use this licensing mode, a small licensing agent must be loadedF and enabled on each licensed client. The code for this licensing agentE is distributed with the PATHWORKS V6 for OpenVMS server, is availablerB free on the Web, and is also available on CD-ROM at a nominal fee.  C o  Server-Based Licensing Mode. When a license for PATHWORKS V6 for G    OpenVMS (Advanced Server)[5] is used in server-based licensing mode,nC    the right to use the server is assigned electronically to a par-bC    ticular server system running a copy of the software. Any clientrC    can then access this server and make as many connections to filee'    services and print shares as needed.u   ____________________I  The  PAK associated with the Client Access license will work, in client-aH   based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversH   that have been upgraded to a minimum of V5.0E. Prior revisions of this  -   product will not recognize or use this PAK. I  The  PAK associated with the Client Access license will work, in server-bH   based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversH   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.  "                                 46       D The PATHWORKS server will allow up to "n" clients to access its ser-C vices concurrently, where "n" is the total number of licenses beingeJ used in server-based licensing mode. The server will not allow the "n+1st"E client to access its services, until one of the first "n" clients hasS disconnected from the server.m  D Note: Though a server may have only "n" licenses available, any num-E ber of clients can potentially access that server. The restriction isiH based only on the total number of clients that may connect to the server at one time.  D For example, if you have 100 licenses assigned to a PATHWORKS serverD in server-based licensing mode, then any 100 clients can make use ofE all services offered by the PATHWORKS server at one time. However, ifoC an additional client (the 101st) attempts to connect to the server,nC the client will be denied access until one of the connected clientsO disconnects from all services.  E Server-based licensing works best in situations where all clients useID or access only one server and there are enough licenses available onD each system for all clients to access their assigned server. A "sys-; tem" is defined as either a standalone system or a cluster.A  C Note: Customers can choose which mode to use and can change the li-RD censing mode, as their situation dictates, without contacting or no- tifying DIGITAL.  C Note also that any portion of multiple licenses delivered in a sin-tD gle PAK can be used in server-based mode, while the remainder can beF used in client-based mode. Because a PAK can be legally loaded on onlyF one system, it is only the system where the PAK is loaded that can use" the licenses in server-based mode.                "                                 47 e  a  D For complete terms and conditions related to Client Access licenses,C refer to the back of your PAK, your PAK for these licenses, or con-i= sult the DIGITAL Software Licensing InfoCenter on the Web at:d  . http://www.digital.com/info/software-licensing   ORDERING INFORMATION   General Information   D Unless otherwise noted, licenses related to each part number will beE delivered in a single PAK. Because each PAK can be loaded on only oneSD system, it is important to order your licenses in a manner that best fits your needs.   New or Additional Licenses  F For new or additional users of PATHWORKS for OpenVMS software, use theC part numbers in Table 1 to purchase the number of Client Access li-oG censes required. When ordering, note that licenses related to each partlF number will be delivered in a single PAK and any one PAK can be loaded on only one system  C ___________________________________________________________________a  C Table_1:_New_License_Part_Numbers__________________________________n  C Part_Number___________Number_of_Licenses_per_PAK___________________i   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            500C QM-5SUAA-AJ___________1000_________________________________________l      "                                 48 0      Upgrade Licenses  G Customers with licenses for previous versions of PATHWORKS servers sup-:E porting the LAN Manager protocol are eligible to purchase Upgrade li-yE censes to PATHWORKS V6.0 for OpenVMS (Advanced Server). Combined with D your original license, the Upgrade license provides the right to useD PATHWORKS V6.0 for OpenVMS (Advanced Server). To be eligible to pur-E chase an Upgrade license, you must have proof-of-license for any ver-c- sion of one of the licenses shown in Table 2.   C ___________________________________________________________________   C Table_2:_Previous_Version_Licenses_Qualifying_for_Upgrade_Licenses__  C License_Name__________________________________________Part_Numbers_N  ? PATHWORKS V5.x for DOS and Windows (LAN Manager)      QM-0TLAA-e: CCS                                                   A[*]? PATHWORKS V4.1 for Windows NT (LAN Manager) CCS       QM-2K5AA-e:                                                       A[*]? PATHWORKS V5.x for OS/2 (LAN Manager) CCS             QM-YFWAA-i:                                                       A[*]? PATHWORKS V5.0 (LAN Manager) FPA                      QM-2CLAA- :                                                       A[*]? PATHWORKS V5.0 (LAN Manager) Designated Access        QM-2CLAA-p:                                                       A[*]? PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS          QM-A93AA-u:                                                       A[*]? PATHWORKS V5.0 for OpenVMS (LAN Manager) PC Con-      QM-A93AA-a: current                                               A[*]C ___________________________________________________________________i [*]Variable fieldfC ___________________________________________________________________S  : Table 3 lists the part numbers for these Upgrade licenses.          "                                 49 W  S  C ___________________________________________________________________o  C Table_3:_Upgrade_License_Part_Numbers______________________________n  !                     Number of Li- C Part_Number_________censes______________Number_of_Licenses_per_PAK_L  3 QM-5SUAA-CA            1                Variable[*]., 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                1000C ___________________________________________________________________ 6 [*]Equals total quantity ordered as a single line itemC ___________________________________________________________________    Migration Licenses  C Customers who have licenses for the following software are eligiblesF to purchase Migration licenses to PATHWORKS V6.0 for OpenVMS (Advanced Server):  & o  PATHWORKS for OpenVMS (NetWare), or  $ o  PATHWORKS for OpenVMS (Macintosh)  D Combined with your original license, this Migration license providesD the right to use PATHWORKS V6.0 for OpenVMS (Advanced Server). To beH eligible to purchase a Migration license, you must have proof-of-licenseG for any version of one of the licenses listed in Table 4. Table 5 listsx. the part numbers for these Migration licenses.          "                                 50    n  C ___________________________________________________________________   C Table_4:_PATHWORKS_Licenses_Qualifying_for_Migration_Licenses______s  C License_Name__________________________________________Part_Numbers_o  ? PATHWORKS V5.x for DOS and Windows (NetWare) CCS      QM-0EKAA-O:                                                       A[*]? PATHWORKS V5.x for OS/2 (NetWare) CCS                 QM-506AA-n:                                                       A[*]? PATHWORKS V5.0 (NetWare) FPA                          QM-2CMAA- :                                                       A[*]? PATHWORKS V5.0 (NetWare) Designated Access            QM-2CMAA-e:                                                       A[*]? PATHWORKS V1.0 for OpenVMS (NetWare) FPS              QM-0ENAA-u:                                                       A[*]? PATHWORKS V1.0 for OpenVMS (NetWare) PC Concurrent    QM-0ENAA-u:                                                       A[*]? PATHWORKS V1.x for Macintosh CCS                      QM-YPHAA-n:                                                       A[*]? PATHWORKS V1.x (Macintosh) FPA                        QM-0EAAA-e:                                                       A[*]? PATHWORKS V1.x (Macintosh) Designated Access          QM-0EAAA-s:                                                       A[*]C ___________________________________________________________________t [*]Variable fieldeC ___________________________________________________________________e                          "                                 51    a  C ___________________________________________________________________E  C Table_5:_Migration_License_Part_Numbers____________________________e  B                                                 Number of LicensesC Part_Number_____________Number_of_Licenses______per_PAK____________o  ; QM-5UFAA-CA                1                    Variable[*]o4 QM-5UFAA-CB                1                       14 QM-5UFAA-CC               10                      104 QM-5UFAA-CD               25                      254 QM-5UFAA-CE               50                      504 QM-5UFAA-CF              100                     1004 QM-5UFAA-CG              250                     2504 QM-5UFAA-CH              500                     5004 QM-5UFAA-CJ             1000                    1000C ___________________________________________________________________i6 [*]Equals total quantity ordered as a single line itemC ___________________________________________________________________     Software Media and Documentation  D Software media and documentation are available in the following for- mats:t      QA-A93AA-H8, CD-ROM media    QA-A93AA-H5, TK50 media!    QA-A93AA-GZ, Documentation kit   C In addition, PATHWORKS V6.0 for OpenVMS (Advanced Server) and PATH-oD WORKS V5.0F for OpenVMS (LAN Manager) software and documentation are included in the following:  C    QA-03XAA-H8, DIGITAL OpenVMS Alpha Software Layered Products Li-     brary Package  D PATHWORKS V5.0F for OpenVMS (LAN Manager) software and documentation are included in the following:  E    QA-5G88A-H8, DIGITAL OpenVMS VAX Software Layered Products Library 
    Package  "                                 52 7  f  E This information is valid at time of release. Please contact your lo-V7 cal DIGITAL office for the most up-to-date information.t   SOFTWARE PRODUCT SERVICESr  E A variety of service options are available from DIGITAL. For more in-g- formation, contact your local DIGITAL office.o  B [R]  Apple, Appleshare, and Macintosh are registered trademarks of      Apple Computer, Inc.e= [R]  AT&T is a registered trademark of American Telephone andW      Telegraph Corporation.1B [R]  IBM, OS/2, and ProPrinter are registered trademarks of Inter-,      national Business Machines Corporation.@ [R]  Macintosh is a registered trademark of Apple Computer, Inc.> [R]  Microsoft, MS-DOS, Windows, and Windows 95 are registered)      trademarks of Microsoft Corporation.hA [R]  NetWare and Novell are registered trademarks of Novell, Inc.lA [R]  PostScript is a registered trademark of Adobe Systems Incor-o
      porated.n6 [TM] SCO is a trademark of Santa Cruz Operations, Inc.? [R]  SilentWriter is a registered trademark of NEC Corporation. A [R]  TCPware is a registered trademark of Process Software Corpo-S      ration.B [R]  UNIX is a registered trademark in the United States and otherA      countries, licensed exclusively through X/Open Company, Ltd.1) [TM] MultiNet is a trademark of TGV, Inc. ; [TM] NetBIOS is a trademark of Micro Computer Systems, Inc.VA [TM] Process Software Corporation is a trademark of Process Soft-W      ware Corporation.8 [TM] Windows NT is a trademark of Microsoft Corporation.< [TM] DEC, DECnet, DECnet-Plus, DECprint, DECserver, DIGITAL,=      LA75, LA324, LAT, LN03, ManageWORKS, OpenVMS, PATHWORKS,yB      PrintServer, TK, ULTRIX, VAXserver, VMS, and the DIGITAL logo5      are trademarks of Digital Equipment Corporation.   :  1997 Digital Equipment Corporation. All Rights Reserved.      "                                 53