       $                               Compaq   Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Advanced Server V7.2 for OpenVMS        SPD 30.50.25 @                and PATHWORKS V6.0B for OpenVMS (Advanced Server)   INTRODUCTION  F This Software Product Description describes two separate products that' provide similar PC server capabilities:   # o  Advanced Server V7.2 for OpenVMS   = Advanced Server V7.2 for OpenVMS requires OpenVMS Alpha V7.2.   0 o  PATHWORKS V6.0B for OpenVMS (Advanced Server)  D PATHWORKS V6.0B for OpenVMS (Advanced Server) requires OpenVMS Alpha or VAX[TM] V7.1 or V7.2.  D Both products are included in the CD-ROM media kit (QA-A93AA-H8) and@ are available on both the Operating System and Layered Products * Consolidated Software Distribution CD-ROM.  ; This Software Product Description (SPD) has three sections:   # o  Advanced Server V7.2 for OpenVMS   0 o  PATHWORKS V6.0B for OpenVMS (Advanced Server)  . o  Software Licensing and Ordering Information    C                                                        January 1999   C                                                         AE-RD64B-TE      7 PRODUCT NAME:  Advanced Server V7.2 for OpenVMS            DESCRIPTION   F Advanced Server for OpenVMS[TM] is an OpenVMS layered application thatI provides networking functions that are compatible with the Windows NT[TM] I Server - with additional features. Advanced Server is based on Windows NT 1 Server source code from Microsoft[R] and AT&T[R].   J The Advanced Server is based on PATHWORKS V6 for OpenVMS (Advanced Server)F - with new capabilities to support the Windows NT integration featuresC introduced with OpenVMS V7.2 on Alpha. These capabilities provide a F tighter integration with the OpenVMS V7.2 Operating System and includeD support for the ODS-5 based Enhanced File Specifications - includingH long names and deep directories, support for the OpenVMS Registry (basedF on the Windows NT registry) and COM capabilities that deliver enhancedG integration of the Windows NT and OpenVMS environments. (The ODS-2 file & system will continue to be supported.)  ? As a server for workstations on a network, the Advanced Server  G provides file and print shares that enable a community of desktop users A to share computing resources efficiently. The Advanced Server can A function as a simple file and print server for a small, isolated  G community of users or as the foundation of a large network distributed   over a wide geographical area.  ? The Advanced Server software lets DOS, Windows[R], Windows NT,  G Windows 95[R], Windows 98[R], OS/2[R], and OpenVMS users share printers D connected to Alpha computers or OpenVMS cluster systems - as well asM network-based printers such as LAT[TM] printers and DIGITAL PrintServers[TM].   H The Advanced Server represents the Windows NT Server systems technology.@ It enhances the Windows NT Server functionality by incorporating> Microsoft technology to deliver powerful features for network E administration and enhanced security. The Advanced Server can operate F independently or in cooperation with systems running Windows NT Server	 software.           "                                  2        FEATURES  C The Advanced Server adds an additional dimension to general purpose A OpenVMS systems. In addition to providing traditional support for G business, scientific, and engineering applications, the Advanced Server H allows an OpenVMS system to appear to PC clients as a Windows NT Server.  ? The major features of the Advanced Server are described in the   following sections.   
 File Services   C An Advanced Server provides clients with a remote file system that  @ appears as a transparent extension of the client system's local  computing environment.  D Advanced Server file shares are based on Microsoft's Advanced 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   @ Files stored in a file service are accessible to PC clients, to F OpenVMS users, and to applications that can interpret the content and 9 organization of a file written by the client application.   E Multiple clients can concurrently access files stored on the server's B disk through the file access modes and byte-range locking support  provided by Advanced Server.  ? An Advanced Server lets users share OpenVMS files. You can use  F discretionary Windows NT access controls on each file and directory to  "                                  3       B specify the groups and users that can access files, to define the F levels of access that each group or user is permitted, and to control E auditing supported by Windows NT-like security. Additional, optional  ? security is provided by OpenVMS file and directory protections.    Print Shares  ? The Advanced Server software lets DOS, Windows[R], Windows NT,  G Windows 95[R], Windows 98[R], OS/2[R], and OpenVMS users share printers D connected to Alpha computers or OpenVMS cluster systems - as well asM network-based printers such as LAT[TM] printers and DIGITAL PrintServers[TM]. D Print shares are supported in local area network (LAN) and wide areaD network (WAN) environments. PC clients can print files from the DOS,@ OS/2, Windows, Windows 95, Windows 98, and Windows NT operating ( systems as well as from PC applications.  G Multiple print shares can be defined for a single printer. For example, @ separate services can be created for landscape-mode printing andC portrait-mode printing. Similarly, separate services can be created D for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer.   C The Advanced Server supports the DECprint[TM] Supervisor (DCPS) for G OpenVMS product, which provides PostScript[R] and DEC[TM] ANSI printing 2 to selected industry-standard PostScript printers.  3 Sharing of Network Resources by Heterogeneous Users   D Services provided by the Advanced Server are accessible to PATHWORKS? clients as well as to Microsoft clients. All clients using the  D services of an Advanced Server must be properly licensed. (For more 1 information, see the Software Licensing section.)   B Files are stored on the server in native OpenVMS RMS format. This G allows information stored by the PCs using Advanced Server to be shared A with traditional OpenVMS users. In addition, this feature allows  + information to be shared among all clients.       "                                  4        Network Transport Support   J The Advanced Server for OpenVMS supports DECnet[TM] (Phase IV) and DECnet-G Plus[TM] (formerly known as DECnet/OSI) transport software as supported G by the OpenVMS V7.2 Operating System. The Advanced Server also supports D TCP/IP and NetBEUI network transport software. One or more transport+ stacks can work concurrently on the server.   B Both the TCP/IP and DECnet transports are sold as separate Compaq H products (require a separate license). The TCP/IP product must include aE PATHWORKS IP driver (PWIP) in order to work with the Advanced Server.   @ NetBEUI transport software is included with the Advanced Server I software. Using NetBEUI transport software, clients can access the server C in the LAN for file and print shares. See the Software Requirements @ section for information on supported network transport software.   NetBIOS[TM] Interface Support   E The Advanced Server supports the NetBIOS interface in DECnet, TCP/IP, F and NetBEUI networks. Advanced Server uses NetBIOS naming services andC datagram services. However, a NetBIOS programming interface is not  D provided. NetBIOS interface support includes the support of multiple> transport stacks on a single or different network controllers.  D NetBIOS support under TCP/IP includes both a p-node and a b-node RFCG 1001/1002 implementation. Therefore, the NetBIOS interface is supported C under TCP/IP in both LAN and WAN environments. The Advanced Server  F 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 Name Server (WINS)   Flexible Security Models  C As an option, the Advanced Server security model can implement the  I windows NT security model with the OpenVMS security model. The server can C be configured to use the security implementation best suited to the  environment.  "                                  5       H o  In Advanced Server Only mode, only the Advanced Server security model    is enforced.   E The Advanced Server employs a user-level security model that provides @ precise control over access to shared resources, including disk B devices, directories, and printers. Control is based on a passwordB assigned to each user account and the specific access permissions  defined for the resources.  F The Advanced Server incorporates enhanced features that provide a highG level of control over user and resource permissions and auditing. These D features include support of discretionary access control permissionsE on individual files, directories, and resources and complete auditing 
 capabilities.   D Like Windows NT Servers, the 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  L    OpenVMS and Advanced Server security models are enforced. Advanced ServerE    security is enhanced with OpenVMS security. Users who require this F    additional security support can continue to protect their resources    based on OpenVMS security.    Domain Support  D The Advanced Server allows the network to be subdivided into domainsF (administrative groups of servers and clients). An Advanced Server canC be a member of a single domain. An Advanced Server can be a Primary D Domain Controller (PDC) or a Backup Domain Controller (BDC). DomainsE are a convenient mechanism for controlling user access to the network   and for managing large networks.  B An Advanced Server for DIGITAL UNIX[R], as well as any Windows NT G compatible server, can be part of the same domain as an Advanced Server ? for OpenVMS and can be designated as either the Primary Domain  ' Controller or Backup Domain Controller.       "                                  6       ? The Advanced Server for OpenVMS provides support for wide area  4 networks using one or both of the following methods:   o  LMHosts file   C The presence of the LMHosts file on the Advanced Server allows Net- F Logon services and security database replication over wide area TCP/IPF configurations. This file contains a list of nodes from geographicallyB dispersed sites synchronized by the Primary Domain Controller and I accessible to clients in the server's domain. However, use of the LMHosts D file for replication over extreme distances or in networks with slow' transmission speeds is not recommended.   & o  WINS (Windows Internet Name Server)  D Support for WINS allows the Advanced Server to act as a WINS client;@ that is, to use the name registration and resolution facilities H available from a Microsoft WINS across routed wide area TCP/IP networks,C thus enabling WAN support from WINS for domain functions, NetLogon  , services, and security database replication.   Trust Relationships   H The Advanced Server supports trusts. Trust relationships can allow usersB from other domains to access resources in the local domain and/or 8 local domain users to access resources in other domains.   NetLogon Services   E A single domain-wide logon lets a user access resources on any server A in a domain or on servers in other domains that trust the domain.   C The domain capabilities of the Advanced Server make it possible for C a user to issue a single logon request to authenticate the user for D access to multiple servers in a network. The NetLogon service forces? the validation of users' logon requests. The logon server that  M processes a request checks its copy of the domain-wide user accounts database < for the username and password supplied in the logon request.    "                                  7        Network Browser Services  @ The Advanced Server can act as a Master Browser in a Windows NT  network.   TimeSource Services   D DOS, Windows, and OS/2 clients can request date and time informationD from the Advanced Server and set the local workstation date and time to coincide with it.   User Environment Management   H Logon scripts can be used to configure MS-DOS[R] and Windows workstationJ user environments by making network connections and starting applications.I User profiles can make workstations easier to use, as well as controlling ( workstation access to network resources.   Server Management and Control   D The Advanced Server can be managed from either the OpenVMS server orC a client workstation, using one of the following server management   interfaces:   C o  The Advanced Server ADMINISTER command line interface, which can C    be accessed from a terminal or terminal emulator. It conforms to     standard DCL command syntax.   D o  Windows NT Server administration tools, which are included in the>    Advanced Server software kit to be installed on Windows NT G    workstations, Windows 95 workstations, Windows 98 workstations, and  F    Windows for Workgroups workstations. These tools, including Server E    Manager, User Manager for Domains, and Event Viewer, allow you to  C    administer 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.     "                                  8     , Server management interfaces can be used to:  < o  Manage file and printer shares, user accounts, and groups  B o  Display and control server resources currently in use, such as .    active sessions, connections, and services.  C o  View context-sensitive online help that provides command syntax, 9    options, and qualifiers for each menu item and command   C The Advanced Server can be remotely administered from PATHWORKS and C Microsoft Windows client workstations. The Advanced Server can also A be managed remotely from Windows NT Server, Advanced Server, and  " PATHWORKS Advanced Server systems.  A Other Advanced Server tools are provided for management of other  G aspects of the file server. These tools are to be used for local server  management only and include:  F o  The Advanced Server Configuration Manager utility (a character cell@    interface) to manage the local Advanced Server configuration.  B o  The License Manager (a character cell interface) to manage the     License Server.  D o  The Advanced Server Parameter Management utility (PWRK$REGUTL) to*    manage server configuration parameters.  - Advanced Server Configuration Manager Utility   E The Advanced Server Configuration Manager utility is a character cell E user interface that allows the user to set up and modify the server's G configuration. For example, the user can configure the data cache size, B the security model, the number of supported clients, the types of H transports, the type of WAN capabilities, and more. Any adjustments that@ need to be made to the OpenVMS SYSGEN parameters to support the F running of the server are automatically performed by the Configuration Manager utility.   Integrating with OpenVMS  F The Advanced Server encompasses many features of the OpenVMS OperatingA System, including OpenVMS clusters and symmetric multiprocessing.   "                                  9       A OpenVMS cluster configurations provide failover availability and  E extensive resource capacities by integrating multiple OpenVMS systems 1 that can be accessed using a single cluster name.   A The Advanced Server includes support for a transport-independent  I cluster alias NetBIOS name that allows multiple cluster members to appear C as a single server to the connecting clients. This support provides A higher availability. The cluster alias name has a load-balancing oL feature that connects clients to the cluster member that is the least loadedD at the time the session is established. The Advanced Server includesE a high performance, cluster-wide distributed data cache that providesB' scalability in a clustered environment.C  H The Advanced Server can run on OpenVMS V7.2 Alpha members of homogeneousD or mixed architecture OpenVMS clusters. The Advanced Server supports? the use of ODS-2 disk volumes and ODS-5 disk volumes, a featureMD of OpenVMS V7.2, for share and file access by clients. The new ODS-5B based Enhanced File Specifications provide support for long names.  ( Integrating with External Authentication  C External authentication is an optional feature that allows OpenVMS nH systems to authenticate designated OpenVMS users with an Advanced ServerJ or a Windows NT username and password combination. External authenticationN can be set up for any OpenVMS user, mapped to an Advanced Server user account.  G External authentication allows users to log on to the OpenVMS Operating @ System using their Advanced Server usernames and passwords. ThisF feature is useful to OpenVMS system managers who want to provide usersD with a single username and password combination for both OpenVMS andM the Advanced Server logon. For more information about external authenticationoC for OpenVMS, refer to the OpenVMS Operating System Software Productn Description (SPD 25.01.xx).d  ! Integrating with OpenVMS Security   D The Advanced Server provides an extension to the Windows NT security@ model by supporting OpenVMS security enforcement as an optional  enhancement.  "                                 10 n  s  ! Integrating with OpenVMS Registryw  > The Advanced Server provides network users with access to the G OpenVMS Registry. The Advanced Server also stores its own configurationoE data in the OpenVMS Registry. The server configuration parameters area? automatically migrated from the LANMAN.INI file to the OpenVMS tI Registry, when a PATHWORKS Advanced Server is upgraded to Advanced Servert? V7.2 for OpenVMS. The Advanced Server provides the PWRK$REGUTL  D utility for managing server configuration parameters in the OpenVMS J Registry. The server parameters in the OpenVMS Registry can also be viewed4 and managed from a Windows NT-based registry editor.   Alerter Servicet  D The Advanced Server includes an Alerter Service that sends automaticG alert messages to clients and users as specified in the Advanced Serverr5 AlertNames parameter setting in the OpenVMS Registry..   Event Log Servicee  D Event logs provide valuable information about server activities. TheE administrator can select from several event types and can select, form> each, whether successful or unsuccessful attempts at specific G operations are to generate event messages. Security event messages are aI generated based on the audit policy specified for the Advanced Server ande for files and directories.   Replicator Service  ? Windows NT Servers provide user data replication across domain  G controllers using the Replicator service. The Replicator service is not F provided by Advanced Servers. Therefore, automatic replication of user; files and directories on Advanced Servers is not supported.    Installation Utilities  A The Advanced Server is installed on the OpenVMS system using the  J standard VMSINSTAL procedure. An Installation Verification Procedure (IVP)? is also included, which can be used to confirm that the server a% software has been installed properly.s  "                                 11 t  s  D The installation procedure allows you to install the Advanced ServerH with the integrated license server or just the standalone license server& or the external authentication images.   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.eC This product will no longer be supported, and licenses to use this t product will no longer be sold.i  D If you are running the PATHWORKS for OpenVMS (NetWare) server on theD same system with Advanced Server, you must remove the NetWare server@ software from the system before you install the Advanced Server.   YEAR 2000 Readinessr  C This product is capable of accurately processing, providing, and/or H receiving date data from, into and between the twentieth and the twenty-B first centuries, and the years 1999 and 2000, including leap year B calculations, when used in accordance with the associated product H documentation and provided that all hardware, firmware and software usedD in combination with the product properly exchange accurate date data with the product.r   License Management  @ The Advanced Server offers license management for Client Access H licenses, which can be used in either client-based or server-based mode.1 (See the Software Licensing section for details.)l  = The license deliverables for the Advanced Server are Product eF Authorization Keys (PAKs) that are then used with the OpenVMS License J Management Facility (LMF). These PAKs must be loaded into an LMF database,C using standard LMF procedures, on an OpenVMS system that is hostingO8 an Advanced Server or an Advanced Server license server.  ( The two types of license management are:  C o  Client-based license management. The Advanced Server provides a  F    facility called Advanced Server license server that acts as a proxy  "                                 12 a  r  J    for client systems that require license keys stored in the LMF database    on an OpenVMS system.  I A single copy of the license server software provides and verifies Clientl0 Access licenses being used in client-based mode.  G The Advanced Server License Manager, which must be run on the same node A as the license server, provides a user interface that allows the  F administrator to monitor client-based license usage, to manage licenseH groups, to set alert levels, to set logging levels for licensing events,I to enable or disable the license server, and to revoke assigned licenses.c? The Advanced Server License Manager is also used to preallocatelA licenses to specific "groups," (including the special, predefinedR& "server-based" group described later).  C Each LAN needs only one active Advanced Server license server. (ThetA license server provided with the Advanced Server supports Client s+ Access licenses for all supported clients.)s  D The Advanced Server License Registrar, which must be run on the sameG system as the file server, verifies the licenses for clients requestingi@ access to the server functions. Clients that can produce a validC Client Access license are allowed access to the services offered byn the Advanced Server.  C o  Server-based license management. The Advanced Server also allows D    client access based on the availability of Client Access licensesI    in the local LMF database being used in server-based mode. If a clientIC    requesting access to the server fails to produce a valid client-tG    based license, the Advanced Server License Registrar software checksoC    for the availability of a valid Client Access license being usedhC    in server-based mode. If one is available, the client is alloweda
    access.  F Client Access licenses can be put into server-based mode in one of two ways:K  F    -  If the Advanced Server license server was not configured for theD       system where the Advanced Server is executing, then all ClientA       Access licenses loaded into the local LMF database on that t/       system will be used in server-based mode.e  "                                 13 n  p  C    -  If the Advanced Server license server was configured for the  E       system where the Advanced Server is executing, then all Client  B       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,eF use the Advanced Server License Manager to allocate a portion of thoseC licenses to the special, predefined "server-based" group. Licenses nF available in the server-based group will then be available for use in  server-based mode.  B Note: The Advanced Server allows you to simultaneously use Client E Access licenses in both client-based and server-based mode. However, oE because clients using Client Access licenses in client-based mode ares@ already licensed to use the server software, they never consume I additional Client Access licenses allocated for use in server-based mode.e  
 Compatibility   C The Advanced Server maintains compatibility with LAN Manager clientcE and server software. The Advanced Server also maintains compatibilityo- with PATHWORKS for OpenVMS (Advanced Server).   2 A PATHWORKS V5.x for OpenVMS (LAN Manager) server:  , o  Can be upgraded to an Advanced Server.[1]  B o  Can continue running PATHWORKS LAN Manager and act as a Backup E    Domain Controller, member server, or standalone server in a domainiB    where the Primary Domain Controller is an Advanced Server or a     Windows NT Server computer.     ____________________G [1]You  can upgrade PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKSnC    V6 for OpenVMS (Advanced Server), then upgrade PATHWORKS V6 for uA    OpenVMS (Advanced Server) to Advanced Server V7.2 for OpenVMS.i    "                                 14 i  v   HARDWARE REQUIREMENTS   A The following systems, components, and peripherals specified are N supported except as noted.   Processors Supported  C All Alpha processors supported by the OpenVMS V7.2 Operating System 2 are also supported by Advanced Server for OpenVMS.   Memory Requirementsa  A Advanced Server requires a minimum of physical memory for proper sE installation, configuration, and execution of the software, dependinga on the processor type:  ' o  On Alpha systems, a minimum of 64 MB   @ Note: These memory requirements are a minimum requirement only. E Memory requirements can vary widely according to the server CPU, the rG number of clients using the server and their activities, and the numbernE and speed of the server's disks and the other applications running onC the server.   F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires annD Alpha system with approximately 64 MB of memory. This means that 80%G of the system memory and CPU time are dedicated to the Advanced Server, % even though some work might use less.   . Disk Space Requirements (Block Cluster Size=1)  E Table 1 provides the disk space requirements for the installation andaB configuration of the Advanced Server. By default, all entries are G directed to the same disk, but each can be directed to different disks.s  H You should also plan for additional, significant disk-space requirements? for items such as data files, virtual memory section files, andr4 log files - after the product is started and in use.  "                                 15       C ___________________________________________________________________o  ; Table 1: Installation/Configuration Disk Space RequirementsxC ___________________________________________________________________r  %                                 Alpha ' Item                            SystemshC ___________________________________________________________________r  ' Images and command files        139,500i&                                 blocks  ' PATHWORKS server data files      84,000 &                                 blocks  C ___________________________________________________________________e' Total                           223,500r&                                 blocksC ___________________________________________________________________d> Note: Sizes are approximate; actual sizes might vary depending= on the user's system environment, configuration, and softwarea options.C ___________________________________________________________________    OPTIONAL HARDWARE    PostScript Printers   J The Advanced Server supports all PostScript printers supported by DECprintH Supervisor (DCPS) for OpenVMS V1.7. Refer to SPD 44.15.xx for a completeJ list of the DIGITAL and non-DIGITAL PostScript printers supported by DCPS.  G DIGITAL PostScript printers connected by serial lines or DECservers[TM]i= and printers attached directly to the Ethernet are supported.i   Network Interface Controllers   D The Advanced Server supports the following Ethernet, FDDI, and Token Ring network hardware devices:  E o  For the TCP/IP transport, the Advanced Server supports the networkWB    hardware devices supported by the specific TCP/IP product. For >    DIGITAL TCP/IP Services for OpenVMS, refer to SPD 46.46.xx.  "                                 16 t  n  . For other TCP/IP products, contact the vendor.  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see%    the SPD for the following product:   6    -  DECnet-Plus V7.2 for OpenVMS Alpha, SPD 50.45.xx  C o  For the NetBEUI transport, the Advanced Server provides the samenC    level of support for Ethernet and FDDI as the OpenVMS Operating r2    System. For more information, see SPD 25.01.xx.  E Note: The Advanced Server does not support the DEFZA FDDI controller.    CLUSTER ENVIRONMENTn  H The Advanced Server runs on members of OpenVMS clusters. OpenVMS clusterB configurations are fully described in the OpenVMS Cluster Software+ Software Product Description (SPD 29.78.xx)i  C The Advanced Server supports up to 31 server nodes in a cluster. InoG other words, no more than 31 nodes in a cluster can run Advanced Server,D concurrently. In a typical scenario, the server is run on only a fewD central nodes - to exploit the cluster's shared disks and high-speed interconnect environment.d  C In a cluster, the Advanced Server supports simultaneous file accesssF by all nodes running the server. A central event log, central AdvancedD Server accounts, and share databases are maintained in a cluster. InC an Advanced Server domain, the OpenVMS cluster represents a single pG 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.2      "                                 17 o     C For minimum hardware requirements of the operating system, refer toaF the Software Product Description for the OpenVMS Operating System (SPD
 25.01.xx).   Network Transport Software  A The Advanced Server includes NetBEUI network transport software.  G DECnet or TCP/IP network transport software may also be required by therE Advanced Server, depending on the transport used by clients requiringl7 connections to the server, or for use of some features.n  B The following DECnet-Plus product is supported by Advanced Server:  % o  DECnet-Plus V7.2 for OpenVMS Alphao  H When the Advanced Server is to be used in a TCP/IP environment, OpenVMS-C based TCP/IP software is required. This software must be purchased eH separately. The following TCP/IP transports support the Advanced Server:  + o  DIGITAL TCP/IP Services for OpenVMS V5.0r  < o  Process Software Corporation[TM] MultiNet[R] V4.0, Rev. B  ; o  Process Software Corporation TCPWARE[R] for OpenVMS V5.1e   PATHWORKS Software  F The Advanced Server for OpenVMS cannot run on the same system as other7 PATHWORKS server products; specifically, this includes:p  A o  PATHWORKS V5.x for OpenVMS (LAN Manager). The Advanced Server sG    cannot be upgraded from the V5.x server. Running the Advanced Servera?    on a system also running the V5.x server is not possible or  C    supported. You cannot continue to run the PATHWORKS LAN Manager OL    software, once the PATHWORKS Advanced Server software has been installed.F    The Advanced Server cannot coexist on the same OpenVMS cluster with    PATHWORKS V5.x server.   E o  PATHWORKS V6.0B for OpenVMS (Advanced Server). The Advanced ServeraE    can be upgraded from the V6.0, V6.0A, or V6.0B server. Running thenH    V6.0, V6.0A, or V6.0B server on a system also running Advanced Server  "                                 18 s  t  @    is not possible or supported. You cannot continue to run the J    PATHWORKS V6.0, V6.0A, or V6.0B for OpenVMS (Advanced Server) software,F    once the PATHWORKS V6.0B for OpenVMS (Advanced Server) software hasB    been installed. The Advanced Server cannot coexist on the same C    OpenVMS cluster with the PATHWORKS V6.0, V6.0A, or V6.0B server.d  @ The Advanced Server maintains down-level compatibility with LAN I Manager client and server software. LAN Manager users can add an Advanced H Server to an existing network and migrate to the new technology at theirD own pace. A PATHWORKS LAN Manager server can be upgraded to act as aC Backup Domain Controller, member server, or standalone server in a VG network in which the Primary Domain Controller is an Advanced Server orc a Windows NT Server computer.s  E The Advanced Server can be deployed as a Primary Domain Controller ineA a network comprising other Advanced Servers, Windows NT Servers, yD PATHWORKS for OpenVMS (Advanced Server), PATHWORKS for OpenVMS (LAN G Manager) servers, or LAN Manager for OS/2 Servers. It can also act as aiF Backup Domain Controller for other Advanced Server, PATHWORKS Advanced' Server, or Windows NT Server computers.o   Client Softwaret  D The following versions of client software are supported for use with PATHWORKS Advanced Server:  9 o  Microsoft Windows NT workstation software V3.5 or V4.0s   o  Microsoft Windows 95d   o  Microsoft Windows 98o  ) o  Microsoft Windows for Workgroups V3.11r  # o  PATHWORKS 32 V7.1A, SPD 56.33.xxt  4 o  PATHWORKS V6.0A for DOS and Windows, SPD 55.07.xx      "                                 19 1  )   GROWTH CONSIDERATIONSe  E The minimum hardware and software requirements for any future versions? of this product may be different from the requirements for the   current version.  C ___________________________________________________________________i  D PRODUCT NAME:  DIGITAL PATHWORKS V6.0B for OpenVMS (Advanced Server)   DESCRIPTION   B DIGITAL[TM] PATHWORKS[TM] for OpenVMS[TM] (Advanced Server) is an G OpenVMS layered application that provides networking functions that areaB compatible with the Windows NT Server - with additional features. L PATHWORKS for OpenVMS (Advanced Server) is based on Windows NT Server source  code from Microsoft and AT&T[R].  D As a server for workstations on a network, PATHWORKS Advanced ServerG provides file and print shares that enable a community of desktop usersSC to share computing resources efficiently. PATHWORKS Advanced ServeriD 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.  D PATHWORKS Advanced Server software lets DOS, Windows[R], Windows NT,G Windows 95[R], Windows 98[R], OS/2[R], and OpenVMS users share printerst? connected to VAX computers, Alpha computers, or OpenVMS clusteraC systems, as well as network-based printers such as LAT[TM] printerss and DIGITAL PrintServers[TM].e  D PATHWORKS Advanced Server represents LAN Manager systems technology.D It enhances the LAN Manager functionality by incorporating MicrosoftF technology to deliver powerful features for network administration andF enhanced security. PATHWORKS Advanced Server can operate independentlyB or in cooperation with systems running Windows NT Server software.        "                                 20    e   FEATURES  B PATHWORKS Advanced Server adds an additional dimension to general I purpose OpenVMS systems. In addition to providing traditional support forNF business, scientific, and engineering applications, PATHWORKS AdvancedC Server allows an OpenVMS system to appear to LAN Manager clients asb a Windows NT Server.  D The major features of PATHWORKS Advanced Server are described in the following sections.i  
 File Servicese  C PATHWORKS Advanced Server provides LAN Manager-based clients with aeH remote file system that appears as a transparent extension of the client% system's local computing environment.a  G PATHWORKS Advanced Server file shares are based on Microsoft's Advancedo1 Server V3.0 SMB (Server Message Block) protocols.o  I Each file stored in a file service is stored as an OpenVMS file in RecordeC Management Services (RMS) format. Three types of RMS file or recordr1 formats are allowed and supported on each volume:l   o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefineda  @ Files stored in a file service are accessible to PC clients, to E OpenVMS users, and to applications that can interpret the content ande9 organization of a file written by the client application.s  D Multiple LAN Manager clients can concurrently access files stored on? the server's disk through the file access modes and byte-range a6 locking support provided by PATHWORKS Advanced Server.  E PATHWORKS Advanced Server lets users share OpenVMS files. You can usesC discretionary access Windows NT controls on each file and directorydD to specify the groups and users that can access files, to define theE levels of access that each group or user is permitted, and to controle  "                                 21 n     D auditing supported by Windows NT-like security. Additional, optional? security is provided by OpenVMS file and directory protections.    Print Shares  D PATHWORKS Advanced Server software lets DOS, Windows[R], Windows NT,G Windows 95[R], Windows 98[R], OS/2[R], and OpenVMS users share printers ? connected to VAX computers, Alpha computers, or OpenVMS clusterlC systems, as well as network-based printers such as LAT[TM] printers F and DIGITAL PrintServers[TM]. Print shares are supported in local areaF network (LAN) and wide area network (WAN) environments. PC clients canD print files from the DOS, OS/2, Windows, Windows 95, Windows 98, and= Windows NT operating systems as well as from PC applications.a  G Multiple print shares can be defined for a single printer. For example, @ separate services can be created for landscape-mode printing andC portrait-mode printing. Similarly, separate services can be createdtD for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer.t  E PATHWORKS Advanced Server supports the DECprint[TM] Supervisor (DCPS) C for OpenVMS product, which provides PostScript[R] and DEC[TM] ANSI p; printing to selected industry-standard PostScript printers.   3 Sharing of Network Resources by Heterogeneous Userss  A Services provided by PATHWORKS Advanced Server are accessible to tH PATHWORKS clients as well as to Microsoft clients. All clients using theG services of a PATHWORKS Advanced Server must be properly licensed. (Fore6 more information, see the Software Licensing section.)  B Files are stored on the server in native OpenVMS RMS format. This G allows information stored by the PCs using PATHWORKS Advanced Server toaC be shared with traditional OpenVMS users. In addition, this featuree2 allows information to be shared among all clients.   Network Transport Supports  I PATHWORKS Advanced Server supports DECnet[TM] (Phase IV), DECnet-Plus[TM]IE (formerly known as DECnet/OSI), TCP/IP, and NetBEUI network transport   "                                 22 e     C software. One or more transport stacks can work concurrently on thec server.n  C Both the TCP/IP and DECnet network transports are sold as separate tF Compaq products (require a separate license). The TCP/IP product must G include a PATHWORKS IP (PWIP) driver in order to work with the Advancede Server.a  E NetBEUI transport software is included with PATHWORKS Advanced ServertC software. Using NetBEUI transport software, LAN Manager clients can @ access the server in the LAN for file and print shares. See the C Software Requirements section for information on supported network n transport software.r   NetBIOS[TM] Interface Support   C PATHWORKS Advanced Server supports the NetBIOS interface in DECnet, D TCP/IP, and NetBEUI networks. PATHWORKS Advanced Server uses NetBIOSE naming services and datagram services. However, a NetBIOS programming B interface is not provided. NetBIOS interface support includes the F support of multiple transport stacks on a single or different network  controllers.  D NetBIOS support under TCP/IP includes both a p-node and a b-node RFCG 1001/1002 implementation. Therefore, the NetBIOS interface is supportedSE under TCP/IP in both LAN and WAN environments. The PATHWORKS Advanced E Server Configuration Manager utility allows you to select one or bothlE of the following methods for NetBIOS name resolution for WAN support:    o  LMHosts file,  1 o  Windows Internet Naming Services (WINS) Servere                "                                 23 l      Flexible Security Models  ? As an option, the PATHWORKS Advanced Server security model can TH implement the Windows NT security model with the OpenVMS security model.D The server can be configured to use the security implementation best suited to the environment.  H o  In Advanced Server Only mode, only the Advanced Server security model    is enforced.u  C PATHWORKS Advanced Server employs a user-level security model that iH provides precise control over access to shared resources, including diskC devices, directories, and printers. Control is based on a password pB assigned to each user account and the specific access permissions  defined for the resources.  E PATHWORKS Advanced Server incorporates enhanced features that providedH 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.r  C Like Windows NT Servers, PATHWORKS Advanced Server does not supportoC share-level security and operates in user-level security mode only.c  ? o  In the Advanced Server and OpenVMS security model, both the lG    OpenVMS and Advanced Server security models are enforced. PATHWORKS pH    Advanced Server security is enhanced with OpenVMS security. Users whoC    require this additional security support can continue to protecte-    their resources based on OpenVMS security.,   Domain Support  C PATHWORKS Advanced Server allows the network to be subdivided into eF domains (administrative groups of servers and clients). Each PATHWORKS@ Advanced Server can be a member of a single domain. A PATHWORKS E Advanced Server can be a Primary Domain Controller (PDC) or a Backup e@ Domain Controller (BDC). Domains are a convenient mechanism for G controlling user access to the network and for managing large networks.v  "                                 24 h  s  B An Advanced Server for DIGITAL UNIX[R], as well as any Windows NT E compatible server, can be part of the same domain as a PATHWORKS for rD OpenVMS Advanced Server and can be designated as either the Primary . Domain Controller or Backup Domain Controller.  A PATHWORKS Advanced Server provides support for wide area domains s+ using one or both of the following methods:f   o  LMHosts filey  A The presence of the LMHosts file on the PATHWORKS Advanced Server I allows NetLogon services and security database replication over wide area_? TCP/IP configurations. This file contains a list of nodes from lB geographically dispersed sites synchronized by the Primary Domain I Controller and accessible to clients in the server's domain. However, use A of the LMHosts file for replication over extreme distances or in _: networks with slow transmission speeds is not recommended.  1 o  WINS (Windows Internet Naming Services) Server   C Support for WINS Servers allows PATHWORKS Advanced Server to act as C a WINS client; that is, to use the name registration and resolution_D facilities available from a Microsoft WINS Server across routed wideD area TCP/IP networks, thus enabling WAN support from WINS for domain@ functions, NetLogon services, and security database replication.   Trust Relationships   B PATHWORKS Advanced Server supports trusts. Trust relationships canF allow users from other domains to access resources in the local domain? and/or local domain users to access resources in other domains.P   NetLogon Servicesc  E A single domain-wide logon lets a user access resources on any serversA in a domain or on servers in other domains that trust the domain.i  E The domain capabilities of PATHWORKS Advanced Server make it possible C for a user to issue a single logon request to authenticate the user[H for access to multiple servers in a network. The NetLogon service forces  "                                 25 c  S  H the validation of users' logon requests. The logon server that processesG a request checks its copy of the domain-wide user accounts database forh8 the username and password supplied in the logon request.   Network Browser Services  E PATHWORKS Advanced Server can act as a Master Browser in a Windows NT  network.   TimeSource Serviceso  D DOS, Windows, and OS/2 clients can request date and time informationE from the PATHWORKS Advanced Server and set the local workstation datei and time to coincide with it.u   User Environment Management0  H Logon scripts can be used to configure MS-DOS[R] and Windows workstationJ user environments by making network connections and starting applications.I User profiles can make workstations easier to use, as well as controllinge( workstation access to network resources.   Server Management and Controlh  G PATHWORKS Advanced Server can be managed from either the OpenVMS serverfE or a client workstation, using one of the following server managemente interfaces:r  E o  PATHWORKS Advanced Server ADMINISTER command line interface, whichdD    can be accessed from a terminal or terminal emulator. It conforms"    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 WindowsE    NT workstations, Windows 95 workstations, Windows 98 workstations,uI    and Windows for Workgroups workstations. These tools, including ServeraD    Manager, User Manager for Domains, and Event Viewer, allow you to>    administer PATHWORKS Advanced Server and Windows NT Server "    computers from network clients.  "                                 26 o  o  ? o  Windows NT Server tools, which are available as part of the      Windows NT Server.   , Server management interfaces can be used to:  < o  Manage file and printer shares, user accounts, and groups  B o  Display and control server resources currently in use, such as .    active sessions, connections, and services.  C o  View context-sensitive online help that provides command syntax,d9    options, and qualifiers for each menu item and commandn  E PATHWORKS Advanced Server can be remotely administered from PATHWORKSdD and Microsoft Windows client workstations. PATHWORKS Advanced ServerC can also be managed remotely from Windows NT Servers and PATHWORKS   Advanced Server systems.  D Other PATHWORKS Advanced Server tools are provided for management ofA other aspects of the file server. These tools are to be used for  ) local server management only and include:m  > o  PATHWORKS Advanced Server Configuration Manager utility (a J    character cell interface) to manage the local PATHWORKS Advanced Server    configuration.r  C o  PATHWORKS License Manager (a character cell interface) to manager     the PATHWORKS license server.  7 PATHWORKS Advanced Server Configuration Manager Utilitya  A The PATHWORKS Advanced Server Configuration Manager utility is a iO character cell interface that allows the user to set up and modify the server'snG configuration. For example, the user can configure the data cache size,aB the security model, the number of supported clients, the types of H transports, the type of WAN capabilities, and more. Any adjustments that@ need to be made to the OpenVMS SYSGEN parameters to support the F running of the server are automatically performed by the Configuration Manager utility.  "                                 27 R  V   Integrating with OpenVMS  C PATHWORKS Advanced Server encompasses many features of the OpenVMS oK Operating System, including OpenVMS clusters and symmetric multiprocessing.o@ OpenVMS cluster configurations provide failover availability andE extensive resource capacities by integrating multiple OpenVMS systems 1 that can be accessed using a single cluster name.d  F PATHWORKS Advanced Server includes support for a transport-independentB PATHWORKS cluster alias NetBIOS name that allows multiple cluster E members to appear as a single server to the connecting clients. This 0F support provides higher availability. The PATHWORKS cluster alias nameB has a load-balancing feature that connects clients to the cluster G member that is the least loaded at the time the session is established.eC PATHWORKS Advanced Server includes a high performance, cluster-widen@ distributed data cache that provides scalability in a clustered  environment.  C PATHWORKS Advanced Server can run on both VAX and Alpha members of vF homogeneous or mixed architecture OpenVMS clusters. PATHWORKS AdvancedE Server supports the use of ODS-2 disk volumes and ODS-5 disk volumes,gA a feature of OpenVMS V7.2, for share and file access by clients. MI However, PATHWORKS Advanced Server V6.0B for OpenVMS does not support theMD features of ODS-5 devices; instead, it treats the ODS-5 device as an
 ODS-2 device.v  ( Integrating with External Authentication  C External authentication is an optional feature that allows OpenVMS sD systems to authenticate designated OpenVMS users with a PATHWORKS or- Windows NT username and password combination.   > External authentication allows users to log on to the OpenVMS E Operating System using their PATHWORKS Advanced Server usernames and RH passwords. This feature is useful to OpenVMS system managers who want toB provide users with a single username and password combination for F access both OpenVMS login and PATHWORKS Advanced Server network logon.@ For more information about external authentication for OpenVMS, G refer to the OpenVMS Operating System Software Product Description (SPD_
 25.01.xx).  "                                 28 D  T  ! Integrating with OpenVMS Securityc  D The Advanced Server provides an extension to the Windows NT security@ model by supporting OpenVMS security enforcement as an optional  enhancement.   Alerter Service   D The Advanced Server includes an Alerter Service that sends automaticH alert messages to clients and users as specified in the LANMAN.INI file.   Event Log Servicen  D Event logs provide valuable information about server activities. TheE administrator can select from several event types and can select, fore> each, whether successful or unsuccessful attempts at specific G operations are to generate event messages. Security event messages are sH generated based on the audit policy specified for the PATHWORKS Advanced% Server and for files and directories.a   Replicator Service  ? Windows NT Servers provide user data replication across domain RG controllers using the Replicator service. The Replicator service is noto= provided on PATHWORKS Advanced Servers. Therefore, automatic aJ replication of user files and directories on PATHWORKS Advanced Servers is not supported.   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 PATHWORKS Advanced.A Server with the integrated license server or just the standalone  B license server, the external authentication images, or the Upgrade utility.  "                                 29 r  t   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.lC This product will no longer be supported, and licenses to use this   product will no longer be sold.o  D If you are running the PATHWORKS for OpenVMS (NetWare) server on theF same system with PATHWORKS Advanced Server, you must either remove theD NetWare server software from the system before you install PATHWORKS Advanced Server.   YEAR 2000 Readinessu  C This product is capable of accurately processing, providing, and/ornH receiving date data from, into and between the twentieth and the twenty-B first centuries, and the years 1999 and 2000, including leap year B calculations, when used in accordance with the associated product H documentation and provided that all hardware, firmware and software usedD in combination with the product properly exchange accurate date data with the product.a   License Management  E PATHWORKS Advanced Server offers license management for Client Access,H licenses, which can be used in either client-based or server-based mode.1 (See the Software Licensing section for details.)p  I The license deliverables for PATHWORKS products are Product AuthorizationdB Keys (PAKs) that are then used with the OpenVMS License Management? Facility (LMF). These PAKs must be loaded into an LMF database,eC using standard LMF procedures, on an OpenVMS system that is hostingW: a PATHWORKS Advanced Server or a PATHWORKS license server.  ( The two types of license management are:  F o  Client-based license management. PATHWORKS Advanced Server providesF    a facility called PATHWORKS License Server that acts as a proxy forF    client systems that require license keys stored in the LMF database    on an OpenVMS system.  "                                 30    A  C A single copy of the PATHWORKS license server software provides anddJ verifies Client Access licenses being used in client-based mode by clients running LAN Manager protocols.  D The PATHWORKS License Manager, which must be run on the same node as> the license server, provides a user interface that allows the G administrator to monitor client-based license usage, to manage license NK groups, to set alert levels, to set logging levels for licensing events, tooF enable or disable the license server, and to revoke assigned licenses.E The PATHWORKS License Manager is also used to preallocate licenses tonC specific "groups" (including the special, predefined "server-based"d group described later).m  E Each LAN needs only one active PATHWORKS license server. (The LicenseoE Server provided with PATHWORKS Advanced Server supports Client Accessr$ licenses for all supported clients.)  C The PATHWORKS License Registrar, which must be run on the same sys-iD tem as the file server, verifies the licenses for clients requestingG access to the server functions. Clients that can produce a valid ClienteF Access license are allowed access to the services offered by the PATH- WORKS Advanced Server.  F o  Server-based license management. PATHWORKS Advanced Server also al-D    lows client access based on the availability of Client Access li-D    censes in the local LMF database being used in server-based mode.G    If a client requesting access to the server fails to produce a validyH    client-based license, the PATHWORKS License Registrar software checksC    for the availability of a valid Client Access license being usedaC    in server-based mode. If one is available, the client is alloweda
    access.  F Client Access licenses can be put into server-based mode in one of two ways:   A    -  If the PATHWORKS license server was not configured for the  J       system where PATHWORKS Advanced Server is executing, then all ClientA       Access licenses loaded into the local LMF database on that t/       system will be used in server-based mode.e  "                                 31 m     C    -  If the PATHWORKS license server was configured for the systemeC       where PATHWORKS Advanced Server is executing, then all Client B       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,nA use the PATHWORKS License Manager to allocate a portion of those MB licenses to the special, predefined "server-based" group. LicensesF available in the server-based group will then be available for use in  server-based mode.  G Note: PATHWORKS Advanced Server allows you to simultaneously use Client D Access licenses in both client-based and server-based mode. However,E because clients using Client Access licenses in client-based mode areo@ already licensed to use the server software, they never consume I additional Client Access licenses allocated for use in server-based mode.e  ! Accommodation of Retired FeaturesL  E The following features of PATHWORKS V5.x for OpenVMS are not providedn in PATHWORKS V6.0 for OpenVMS:  D o  Standalone and member server roles. PATHWORKS Advanced Server can:    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 separateHD    system. Files held within shares on a FAT volume must be migratedC    to PATHWORKS LAN Manager shares before you upgrade to PATHWORKS f    Advanced Server.u  G o  Backward compatibility mode. This mode is used to ease the migrationeF    from PATHWORKS V4.x to PATHWORKS LAN Manager. Make sure all clients?    making use of this connection format are upgraded before theh-    installation of PATHWORKS Advanced Server.h  E o  Remote Boot service. If clients depend on remote booting, you mustoC    maintain the PATHWORKS LAN Manager server on a separate system. cF    Transfer this function to another server that supports Remote Boot     service before the upgrade.  "                                 32 o  o  D o  Share-level security. PATHWORKS Advanced Server manages access to-    all resources through user-level security.m  F o  LAN Manager and creator security mode. The server can be configuredE    for PATHWORKS Advanced Server Only security model or for PATHWORKSv.    Advanced Server and OpenVMS security model.  L o  PATHWORKS LAN Manager Net command line interface and ADMINISTER/PATHWORKSJ    character cell interface. These features were replaced by the PATHWORKSD    Advanced Server ADMINISTER command line interface. The ADMINISTERD    command line interface provides automatic translation of a subset<    of Net commands that have ADMINISTER command equivalents.  
 Compatibility,  I PATHWORKS Advanced Server maintains compatibility with LAN Manager clientiG and server software. A PATHWORKS V5.x for OpenVMS (LAN Manager) server:h  1 o  Can be upgraded to a PATHWORKS Advanced Serverl  B o  Can continue running PATHWORKS LAN Manager and act as a Backup E    Domain Controller, member server, or standalone server in a domainiE    where the Primary Domain Controller is a PATHWORKS Advanced Serverg#    or a Windows NT Server computer.    HARDWARE REQUIREMENTS   A The following systems, components, and peripherals specified are N supported except as noted.   Processors Supported  ? All VAX and Alpha processors supported by the OpenVMS V7.1 and eH OpenVMS V7.2 Operating Systems are also supported by PATHWORKS V6.0B for4 OpenVMS (Advanced Server), except for the following:          "                                 33 g  t     GPX II  A MicroVAX:   MicroVAX I, MicroVAX II, MicroVAX 2000, MicroVAX 3100d             Model 40 and lower  ? VAX:        VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAXc             11/782, VAX 11/785  A VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXsta- *             tion 4000 VLC, VAXstation 8000   Memory Requirements   C PATHWORKS Advanced Server requires a minimum of physical memory forrB proper installation, configuration, and execution of the software,  depending on the processor type:  ' o  On Alpha systems, a minimum of 64 MBu  % o  On VAX systems, a minimum of 64 MBd  @ Note: These memory requirements are a minimum requirement only. E Memory requirements can vary widely according to the server CPU, the SG number of clients using the server and their activities, and the number E and speed of the server's disks and the other applications running ons the server..  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires ancD Alpha system with approximately 64 MB of memory. This means that 80%E of the system memory and CPU time are dedicated to PATHWORKS Advancedl- Server, even though some work might use less.a  . Disk Space Requirements (Block Cluster Size=1)  E Table 2 provides the disk space requirements for the installation and C configuration of PATHWORKS Advanced Server. By default, all entriesaD are directed to the same disk, but each can be directed to different disks.  "                                 34    5  H You should also plan for additional, significant disk-space requirements? for items such as data files, virtual memory section files, andn4 log files - after the product is started and in use.  C ___________________________________________________________________S  ; Table 2: Installation/Configuration Disk Space Requirements C ___________________________________________________________________t  %                                 AlphaS9 Item                            Systems       VAX SystemsiC ___________________________________________________________________i  < Images and command files        152,500       130,500 blocks&                                 blocks  < PATHWORKS server data files      77,500        77,500 blocks&                                 blocks  C ___________________________________________________________________n< Total                           226,000       208,000 blocks&                                 blocksC ___________________________________________________________________r> Note: Sizes are approximate; actual sizes might vary depending= on the user's system environment, configuration, and softwarea options.C ___________________________________________________________________m   OPTIONAL HARDWAREi   PostScript Printers   D PATHWORKS Advanced Server supports all PostScript printers supportedE by DECprint Supervisor (DCPS) for OpenVMS V1.6. Refer to SPD 44.15.xx F for a complete list of the DIGITAL and non-DIGITAL PostScript printers supported by DCPS.  G DIGITAL PostScript printers connected by serial lines or DECservers[TM] = and printers attached directly to the Ethernet are supported.r      "                                 35        Non-PostScript Printersv  D PATHWORKS Advanced Server also supports the following non-PostScript	 printers:n  . DIGITAL LA75 Companion          EPSON[R] FX850 Printeri, DIGITAL LA210                   EPSON FX1050. DIGITAL LA324[TM]               IBM ProPrinter@ DIGITAL LJ250 Companion         NEC SilentWriter[R] II Model 290
 Color Printer- DIGITAL LN03[TM] PLUSh   Network Interface Controllerso  D PATHWORKS Advanced Server supports the following Ethernet, FDDI, and$ Token Ring network hardware devices:  C o  For the TCP/IP transport, PATHWORKS Advanced Server supports theSE    network hardware devices supported by the specific TCP/IP product.aB    For DIGITAL TCP/IP Services for OpenVMS, refer to SPD 46.46.xx.  . For other TCP/IP products, contact the vendor.  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see'    the SPDs for the following products:P  6    -  DECnet-Plus V7.2 for OpenVMS Alpha, SPD 50.45.xx  4    -  DECnet-Plus V7.2 for OpenVMS VAX, SPD 25.03.xx  9    -  DECnet for OpenVMS VAX and Alpha V7.2, SPD 48.48.xxn  D 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.  @ Note: PATHWORKS Advanced Server does not support the DEFZA FDDI  controller.i  "                                 36 p      CLUSTER ENVIRONMENTt  ? PATHWORKS Advanced Server runs on members of OpenVMS clusters. lG OpenVMS cluster configurations are fully described in the OpenVMS Clus- 8 ter Software Software Product Description (SPD 29.78.xx)  F PATHWORKS Advanced Server supports up to 31 server nodes in a cluster.D In other words, no more than 31 nodes in a cluster can run PATHWORKS? Advanced Server concurrently. In a typical scenario, the serveraD is run on only a few central nodes - to exploit the cluster's shared. disks and high-speed interconnect environment.  C In a cluster, PATHWORKS Advanced Server supports simultaneous file iD access by all nodes running the server. A central event log, centralB Advanced Server accounts, and share databases are maintained in a D cluster. In a PATHWORKS Advanced Server domain, the OpenVMS cluster F represents a single domain member, whether it is acting as the Primary3 Domain Controller or as a Backup Domain Controller.i   SOFTWARE REQUIREMENTSv   Operating System  / o  OpenVMS Alpha Operating System V7.1 and V7.2b  - o  OpenVMS VAX Operating System V7.1 and V7.2s  C For minimum hardware requirements of the operating system, refer toiF the Software Product Description for the OpenVMS Operating System (SPD
 25.01.xx).   Network Transport Software  F PATHWORKS Advanced Server includes NetBEUI network transport software.C DECnet or TCP/IP network transport software may also be required byeB PATHWORKS for OpenVMS, depending on the transport used by clients A requiring connections to the server, or for use of some features.S      "                                 37 M  o  H The following DECnet and DECnet-Plus products are supported by PATHWORKS Advanced Server:  % o  DECnet-Plus V7.1 for OpenVMS Alphae  % o  DECnet-Plus V7.2 for OpenVMS Alphah  # o  DECnet-Plus V7.1 for OpenVMS VAXt  # o  DECnet-Plus V7.2 for OpenVMS VAX   ( o  DECnet for OpenVMS VAX and Alpha V7.1  E When PATHWORKS Advanced Server is to be used in a TCP/IP environment,oA OpenVMS-based TCP/IP software is required. This software must be tG purchased separately. The following TCP/IP transports support PATHWORKSe Advanced Server:  E o  DIGITAL TCP/IP Services for OpenVMS V4.1 and V4.2 for OpenVMS V7.1v%    and V5.0 for OpenVMS V7.1 and V7.2s  < o  Process Software Corporation[TM] MultiNet[R] V4.0, Rev. B  ; o  Process Software Corporation TCPWARE[R] for OpenVMS V5.1r   Other PATHWORKS Server Softwaree  ? The following PATHWORKS server products cannot run on the same P8 system as PATHWORKS V6.0B for OpenVMS (Advanced Server):  A o  PATHWORKS V5.x for OpenVMS (LAN Manager). PATHWORKS V6.0B for dC    OpenVMS (Advanced Server) can be upgraded from the V5.x server. MG    Running the V6.0B server on a system also running the V5.x server is F    not possible or supported. You cannot continue to run the PATHWORKSD    LAN Manager software, once the PATHWORKS Advanced Server softwareF    has been installed. PATHWORKS Advanced Server cannot coexist on the3    same OpenVMS cluster with PATHWORKS V5.x server.o  E o  PATHWORKS V6.0A for OpenVMS (Advanced Server). PATHWORKS V6.0B fornC    OpenVMS (Advanced Server) can be upgraded from the V6.0 or V6.0AsD    server. Running the V6.0 or V6.0A server on a system also runningE    the V6.0B server is not possible or supported. You cannot continuecC    to run the PATHWORKS V6.0 or V6.0A for OpenVMS (Advanced Server)a  "                                 38    n  C    software, once the PATHWORKS V6.0B for OpenVMS (Advanced Server)AE    software has been installed. PATHWORKS V6.0B for OpenVMS (Advancedi?    Server) cannot coexist on the same OpenVMS cluster with the e"    PATHWORKS V6.0 or V6.0A server.  E PATHWORKS Advanced Server maintains down-level compatibility with LANa@ Manager client and server software. LAN Manager users can add a G PATHWORKS Advanced Server to an existing network and migrate to the newaC technology at their own pace. A PATHWORKS LAN Manager server can be C upgraded to PATHWORKS Advanced Server technology or act as a BackupeC Domain Controller, member server, or standalone server in a networktE in which the Primary Domain Controller is a PATHWORKS Advanced Server B or a Windows NT Server computer. PATHWORKS Advanced Server can be E deployed as a Primary Domain Controller in a network comprising otherlE PATHWORKS Advanced Servers, Windows NT Servers, PATHWORKS for OpenVMSbC (LAN Manager) servers, or LAN Manager for OS/2 Servers. It can alsorE act as a Backup Domain Controller for other PATHWORKS Advanced Server  or Windows NT Server computers.r   Client Softwaree  D The following versions of client software are supported for use with PATHWORKS Advanced Server:  9 o  Microsoft Windows NT workstation software V3.5 or V4.0    o  Microsoft Windows 95t   o  Microsoft Windows 98i  ) o  Microsoft Windows for Workgroups V3.11n  # o  PATHWORKS 32 V7.1A, SPD 56.33.xxu  4 o  PATHWORKS V6.0A for DOS and Windows, SPD 55.07.xx          "                                 39 d  f   GROWTH CONSIDERATIONSn  E The minimum hardware and software requirements for any future versiona? of this product may be different from the requirements for the e current version.  C ___________________________________________________________________v  E LICENSING AND ORDERING INFORMATION:  Advanced Server V7.2 for OpenVMS 1 and PATHWORKS V6.0B for OpenVMS (Advanced Server)d   SOFTWARE LICENSING  I Advanced Server V7.2 for OpenVMS[2] is purchased by licensing the clientsMD or applications that use the services provided by the product. There is no additional fee.e  F The license required for clients to use Advanced Server file and printH services[3] is referred to as a Client Access license (PAK Product Name:E PWLMXXXCA06.00 for V6.0B or PWLMXXXCA07.02 for either V6.0B or V7.2).t@ Though there is only one license sold for any client using this = Advanced Server, this license can be used in one of two ways:e  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 [2]PATHWORKS  V6.0B for OpenVMS (Advanced Server) is licensed for use inE    exactly the same way as Advanced Server V7.2 for OpenVMS (Advanced F    Server).  Though previously purchased licenses continue to be validG    for use with pre-V6 servers, only the new Client Access licenses mayt<    be purchased when adding new clients to existing systems.  F    In particular, all the licenses listed in Table 4, Previous VersionD    Licenses Qualifying for Upgrade Licenses, are no longer sold but I    continue to be valid and grant the right to use the PATHWORKS V5.0 forl"    OpenVMS (LAN Manager) software.  I  [3]COM  for OpenVMS users will not require a license to use the Advanced.G     Server.  Only clients using the file and print servers will requirel     a license.  "                                 40    H  H These two different licensing modes are described in the following text.  E o  Client-Based Licensing Mode. When a license for Advanced Server isvC    used in client-based licensing mode, the right to use the servereF    is assigned electronically to a particular client or seat. Once the?    right is assigned, the client system can access all systems dF    running Advanced Server as well as all systems running any previous,    version of the file and print server. [4]  ? This mode of licensing Advanced Server is normally used when a cH customer has more than one server and where clients normally access moreE than one server at the same time. Because only one license per clientfJ is required regardless of how many servers are being accessed, the client-D based licensing mode can be more economical in these situations when0 compared to server-based mode (described later).  E Because a client with a client-based license cannot be refused accessrB to a server due to license limits, this mode of licensing is also F useful when you need to guarantee that a particular system will always# have access to one or more servers.   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 agentF is distributed with the Advanced Server, is available free on the Web,1 and is also available on CD-ROM at a nominal fee.l  F o  Server-based licensing mode. When a license for Advanced Server [5]E    is used in server-based licensing mode, any client can then accessKE    the server and make as many connections to file services and printc    shares as needed. ____________________K [4]The  PAK associated with the Client Access license will work, in client-eI    based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversoI    that have been upgraded to a minimum of V5.0F. Prior revisions of thise.    product will not recognize or use this PAK.  K [5]The  PAK associated with the Client Access license will work, in server-,I    based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversnI    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.P  "                                 41 n  n  ? The Advanced Server will allow up to "n" clients to access its rF services concurrently, where "n" is the total number of licenses beingJ 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 hasa disconnected from the server.r  @ Note: Though a server may have only "n" licenses available, any H number of clients can potentially access that server. The restriction isH 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 an Advanced ServerD in server-based licensing mode, then any 100 clients can make use ofD all services offered by the Advanced Server at one time. However, ifC an additional client (the 101st) attempts to connect to the server,sC the client will be denied access until one of the connected clientsr disconnects from all services.  E Server-based licensing works best in situations where all clients useRD or access only one server and there are enough licenses available on? each system for all clients to access their assigned server. A eB "system" is defined as either a standalone system or a cluster.[6]  D Note: Customers can choose which mode to use or to use a combinationE of both modes. They can change the licensing mode, as their situationR4 dictates, without contacting or notifying Compaq[R].   ____________________B [6]When  using server-based licenses for access to file and print M    services in an OpenVMS cluster environment, Compaq recommends that clientstE    connect to the cluster using the Advanced Server cluster alias, iftA    this option is available.  Clients connecting using the alias LE    consume one server-based license.  Clients connecting directly to LF    specific cluster members consume one server-based license for each ,    connection to a different cluster member.  K    A client can map multiple drives and printers from a single server whiles+    consuming a single server-based license.i  "                                 42 e     ? Note also that any portion of multiple licenses delivered in a hG single PAK can be used in server-based mode, while the remainder can beeF 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.[7]r  D For complete terms and conditions related to Client Access licenses,A refer to the back of your PAK for these licenses, or consult the r Software Licensing Web site at:0  . http://www.digital.com/info/software-licensing   ORDERING INFORMATION   General Information0  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 one D system, it is important to order your licenses in a manner that best fits your needs.   New or Additional Licenses  E For new or additional users of Advanced Server software, use the partdC numbers in Table 3 to purchase the number of Client Access licensesuA required. When ordering, note that licenses related to each part qF number will be delivered in a single PAK and any one PAK can be loaded on only one system               ____________________D [7]PAKs  must be loaded into a cluster-wide, available LMF database.    "                                 43 c  o  C ___________________________________________________________________p  ! Table 3: New License Part NumberssC ___________________________________________________________________   1 Part Number            Number of Licenses per PAK C ___________________________________________________________________S   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           1000C ___________________________________________________________________a   Upgrade Licenses  C Customers with licenses for previous versions of the file and printuC server supporting the LAN Manager protocol are eligible to purchase C Upgrade licenses to Advanced Server V7.2 for OpenVMS. Combined witheC your original license, the Advanced Server Upgrade license provides_E the right to use Advanced Server V7.2 for OpenVMS and PATHWORKS V6.0B/D for OpenVMS. To be eligible to purchase an Upgrade license, you mustE have proof-of-license for any version of one of the licenses shown in C Table 4. Table 5 lists the part numbers for these Upgrade licenses.                               "                                 44    m  C ___________________________________________________________________   B Table 4: Previous Version Licenses Qualifying for Upgrade LicensesC ____________________________________________________________________  B License Name                                          Part NumbersC ___________________________________________________________________   C PATHWORKS V5.x for DOS and Windows (LAN Manager)      QM-0TLAA-A[*]_6 CCS                                                     C PATHWORKS V5.x for OS/2 (LAN Manager) CCS             QM-YFWAA-A[*]g6                                                       C PATHWORKS V5.0 (LAN Manager) FPA                      QM-2CLAA-A[*] 6                                                       C PATHWORKS V5.0 (LAN Manager) Designated Access        QM-2CLAA-A[*] 6                                                       C PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS          QM-A93AA-A[*]y6                                                       C PATHWORKS V5.0 for OpenVMS (LAN Manager) PC           QM-A93AA-A[*]e9 Concurrent                                                  C PATHWORKS V6.0 for OpenVMS (Advanced Server)          QM-A93AA-A[*]o6 Client Access                                         C ___________________________________________________________________  [*]Variable fieldPC ___________________________________________________________________J                                  "                                 45 I  A  C ___________________________________________________________________d  % Table 5: Upgrade License Part NumbersFC ___________________________________________________________________r                       Number of B Part Number         Licenses            Number of Licenses per PAKC ___________________________________________________________________   3 QM-5SUAA-CA            1                Variable[1]t, 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 [1]Equals total quantity ordered as a single line itemC ___________________________________________________________________D    Software Media and Documentation  ? Software media and documentation are available in the followinga formats:      QA-A93AA-H8, CD-ROM media!    QA-A93AA-GZ, Documentation kitt  A In addition, Advanced Server V7.2 for OpenVMS and PATHWORKS V6.0B = for OpenVMS (Advanced Server) software and documentation are   included in the following:  ?    QA-03XAA-H8, OpenVMS Alpha Software Layered Products Libraryr
    Package  ; PATHWORKS V6.0B for OpenVMS (Advanced Server) software and e, documentation are included in the following:  =    QA-5G88A-H8, OpenVMS VAX Software Layered Products Libraryc
    Package  "                                 46 r     A This information is valid at time of release. Please contact your 8 local Compaq office for the most up-to-date information.   SOFTWARE PRODUCT SERVICESn  @ A variety of service options are available from Compaq. For more. information, contact your local Compaq office.   SOFTWARE WARRANTYs  = This software is provided by Compaq with a 90-day conformancei@ warranty in accordance with the Compaq warranty terms applicable to the license purchase.                                                      "                                 47    t    B [R]  Apple, Appleshare, and Macintosh are registered trademarks of      Apple Computer, Inc.S= [R]  AT&T is a registered trademark of American Telephone andc      Telegraph Company.IE [R]  Compaq is a registered trademark of Compaq Computer Corporation.r; [R]  EPSON is a registered trademark of Epson America, Inc.oI [R]  IBM, OS/2, and ProPrinter are registered trademarks of Internationalo#      Business Machines Corporation. @ [R]  Microsoft, MS-DOS, and Windows are registered trademarks of      Microsoft Corporation.r> [TM] MultiNet and TCPWARE are registered trademarks of Process      Software Corporation.H [R]  PostScript is a registered trademark of Adobe Systems Incorporated.6 [TM] SCO is a trademark of Santa Cruz Operations, Inc.? [R]  SilentWriter is a registered trademark of NEC Corporation.s< [R]  UNIX is a registered trademark of The Open Group in the'      United States and other countries.a; [TM] NetBIOS is a trademark of Micro Computer Systems, Inc.OE [TM] Process Software Corporation is a trademark of Process Software n      Corporation.V= [TM] Windows 95, Windows 98, and Windows NT are trademarks ofw      Microsoft Corporation.RD [TM] Compaq, DEC, DECnet, DECnet-Plus, DECprint, DECserver, DIGITAL,=      LA75, LA324, LAT, LN03, OpenVMS, PATHWORKS, PrintServer,A?      VAX, and the Compaq logo are trademarks of Compaq ComputerO      Corporation.M  : (c) 1999 Compaq Computer Corporation. All Rights Reserved.                  "                                 48