       $                               COMPAQ   Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq Advanced Server V7.3             SPD 30.50.30 8                for OpenVMS and Compaq PATHWORKS V6.1 for(                OpenVMS (Advanced Server)   INTRODUCTION  F This Software Product Description describes two separate products that' provide similar PC server capabilities:   * o  Compaq Advanced Server V7.3 for OpenVMS  C Advanced Server V7.3 for OpenVMS requires Compaq OpenVMS Alpha Ver-  sion 7.2-1, 7.2-2, or 7.3   6 o  Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server)  C PATHWORKS V6.1 for OpenVMS (Advanced Server) requires OpenVMS Alpha C Version 6.2, 7.2-1, 7.2-2, or 7.3, or OpenVMS VAX Version 6.2, 7.2,  or 7.3.   D Both products are included in the CD-ROM media kit (QA-A93AA-H8) andD are available on both the Operating System and Layered Products Con-' solidated Software Distribution CD-ROM.   ; This Software Product Description (SPD) has three sections:   * o  Compaq Advanced Server V7.3 for OpenVMS  6 o  Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server)  . o  Software Licensing and Ordering Information  C                                                        October 2001   C                                                         AE-RD64F-TE        C ___________________________________________________________________   6 PRODUCT NAME:  Compaq Advanced Server V7.3 for OpenVMS   DESCRIPTION   D Compaq Advanced Server for OpenVMS is an OpenVMS layered applicationG and network operating system that is compatible with the Microsoft net- E working technology. In particular, the Advanced Server for OpenVMS is D based on the Windows NT Server, but it provides additional features.E It enhances the Windows NT Server functionality by incorporating both F OpenVMS and Microsoft technology to deliver powerful features for net-H work administration and enhanced security. The Advanced Server for Open-E VMS can operate independently from or in cooperation with the Windows ) NT Server, or with a Windows 2000 server.   C The Advanced Server for OpenVMS software evolved from the PATHWORKS C V6.p for OpenVMS (Advanced Server) product to provide tighter inte- E gration with the OpenVMS operating system and the enhanced Windows NT ? integration features introduced with OpenVMS Alpha Version 7.2.   D Advanced Server for OpenVMS includes support for Extended File Spec-G ifications based on OpenVMS ODS-5 disk volumes. The server product sup- M ports long names and deep directories, certain Unicode or extended character- H set characters, the OpenVMS Registry (based on the Windows NT registry),E COM for OpenVMS, and other capabilities that integrate Windows NT and H OpenVMS environments. (The ODS-2 file system continues to be supported.)C As a result, the Advanced Server for OpenVMS takes advantage of the D OpenVMS operating system's native ability to function simultaneouslyC as a file, print, communications, and applications server while en- D suring compatibility with Microsoft networking features and interop-D erability with Microsoft desktop environments. DOS, Windows, WindowsE NT, Windows 95, Windows 98, Windows 2000, and OpenVMS users can share $ files and printers over the network.  H As a server for workstations on a network, the Advanced Server for Open-C VMS provides file and print shares that enable a community of desk- G top users to share computing resources efficiently. The Advanced Server G for OpenVMS can function as a simple file and print server for a small,   "                                  2       C isolated community of users or as the foundation of a large network * distributed over a wide geographical area.  D Desktop and OpenVMS users can share printers connected to Alpha com-E puters or to OpenVMS Cluster systems, as well as network-based print- H ers such as LAT printers and PrintServers. The Advanced Server for Open-C VMS gives you the option of configuring the server to allow manage- E ment of shared printers from Windows NT, thereby allowing you to take @ advantage of the features provided by Windows NT print services.   FEATURES  H The Advanced Server for OpenVMS adds an additional dimension to general-E purpose OpenVMS systems. Along with providing traditional support for E business, scientific, and engineering applications, the server allows C an OpenVMS operating system to appear to PC clients as a Windows NT  Server.   C The major features of the Advanced Server for OpenVMS are described  in the following sections.  
 File Services   C The Advanced Server for OpenVMS provides clients with a remote file E system that appears as a transparent extension of the client system's  local computing environment.  H The 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   "                                  3       E The Advanced Server for OpenVMS now provides improved performance for D access of sequential and VFC (variable length with fixed-length con-E trol) files. In previous versions of the Advanced Server, and on ODS- C 2 volumes, the file has to be read completely to determine the cor- C rect file size. The Advanced Server now supports file-size calcula- E tions for RMS sequential and VFC files on ODS-5 volumes. This reduces H the number of I/Os and the file-open time when the Advanced Server opens a file for the first time.  E Files stored in a file service are accessible to PC clients, to Open- E VMS users, and to applications that can interpret the content and or- 7 ganization of a file written by the client application.   E Multiple clients can concurrently access files stored on the server's F disk through the file-access modes and byte-range locking support pro- vided by the Advanced Server.   D The Advanced Server lets users share OpenVMS files. You can use dis-C cretionary Windows NT access controls on each file and directory to F specify the groups and users that can access files, to define the lev-F els of access that each group or user is permitted, and to control au-F diting supported by Windows NT-like security. Additional, optional se-= curity is provided by OpenVMS file and directory protections.   E The Advanced Server for OpenVMS ensures compatibility with a wide va- C riety of clients and legacy applications attempting to share server E resources. Some of the Advanced Server for OpenVMS features that help . ensure such compatibility include support for:   o  Extended File Specifications   G Extended File Specifications, based on ODS-5, includes support for deep $ directories and extended file names.  0 o  Unicode characters or extended character sets  C The Advanced Server for OpenVMS file server can now support certain F Unicode characters and extended character sets that are foreign to theC Western European languages, making available a broader set of char- D acters not only for file and share names, but also for other objectsF manageable by the Advanced Server, such as user names and group names.  "                                  4       F The Advanced Server for OpenVMS provides six additional character setsD with the potential of supporting over 40 different languages. ThoughC you can configure any one of these languages, Compaq has tested and , officially supports the following languages:      o  English (USA)       o  Hebrew  D By giving you a choice of languages, the Advanced Server for OpenVMSD can enable you to configure the server to support the local languageE of the server's users. Most of the Western European languages support  the Euro currency symbol.   D o  Legacy applications with more restrictive file-naming conventions  C Some legacy applications (such as MS-DOS) are more restrictive than F the Advanced Server, Windows NT, and other systems, in both the lengthC of file names and in the set of valid characters supported for file D names. As a result, these applications cannot take full advantage ofG the capabilities of the OpenVMS ODS-5 disk volume and longer file names F supported on the other systems. To enable compatibility with these ap-A plications, the Advanced Server for OpenVMS automatically creates D MS-DOS-compatible alias file names for files whose names do not com-F ply with the file-naming standards of those applications. As a result,D client applications that either must use or choose to use the MS-DOSD format for file names can access these shared files on the server by' using the file's associated alias name.    Print Shares  C The Advanced Server for OpenVMS software lets DOS, Windows, Windows H NT, Windows 95, Windows 98, Windows 2000, and OpenVMS users share print-E ers connected to Alpha computers or OpenVMS Cluster systems - as well F as network-based printers such as LAT printers and PrintServers. PrintC shares are supported in local area network (LAN) and wide area net- D work (WAN) environments. PC clients can print files from their desk-6 top operating systems as well as from PC applications.    "                                  5       D Multiple print shares can be defined for a single printer. For exam-E ple, separate services can be created for landscape-mode printing and C portrait-mode printing. Similarly, separate services can be created C for DIGITAL mode and IBM ProPrinter mode printing for a single LA75  printer.  E The Advanced Server for OpenVMS supports all PostScript printers sup- E ported by OpenVMS. Selected PostScript printers may need the DECprint D Supervisor for OpenVMS (DCPS) software to provide access through theC OpenVMS queuing system over TCP/IP or DECnet. The DECprint Supervi- F sor for OpenVMS (DCPS) product provides PostScript and DEC ANSI print-6 ing to selected industry-standard PostScript printers.  D By default, you manage shared printers using the Advanced Server forG OpenVMS ADMINISTER command-line interface. However, the Advanced Server E for OpenVMS gives you the option of configuring the server to support C management of shared printers from Windows NT, using the Windows NT G print services. Whichever style of management you choose, you have full D functionality only from the style chosen - you cannot have full man-C agement functionality with both. Advantages of the Windows NT style  of management include:  D o  Simple management of Advanced Server shared printers by using the*    Windows NT print services dialog boxes.  C o  When adding a printer to the Advanced Server, the Windows NT Add F    Printer Wizard installs the required drivers for the printer on theC    server; these drivers are provided by the administrator (such as D    from the Windows NT installation CD-ROM). When a client is set upC    to use the printer, these drivers are available for downloading. D    When new drivers are distributed, administrators have to update a    single location only.  I o  Use of Windows NT access permissions for Advanced Server shared print-     ers.           "                                  6       3 Sharing of Network Resources by Heterogeneous Users   H Services provided by Advanced Server are accessible to PATHWORKS clientsF as well as to Microsoft clients. All clients using the services of theD Advanced Server for OpenVMS must be properly licensed. (For more in-/ formation, see the section SOFTWARE LICENSING.)   E Files are stored on the server in native OpenVMS RMS format. This al- E lows information stored by the PCs using Advanced Server to be shared D with traditional OpenVMS users. In addition, this feature allows in-) formation to be shared among all clients.    Network Transport Support   F Advanced Server for OpenVMS supports DECnet (Phase IV) and DECnet-PlusG (formerly known as DECnet/OSI) transport software as supported by Open- H VMS Alpha Version 7.2-1, 7.2-2, and 7.3. The server also supports TCP/IPD and NetBEUI network transport software. One or more transport stacks$ can work concurrently on the server.  G Both the TCP/IP and DECnet transports are sold as separate Compaq prod- # ucts and require separate licenses.   E NetBEUI transport software is included with the Advanced Server soft- E ware. Using NetBEUI transport software, clients can access the server D in the LAN for file and print shares. NetBEUI is recommended for use3 in small LAN-only environments of 50 nodes or less.   E For information on supported network transport software, see the sec-  tion SOFTWARE REQUIREMENTS.    NetBIOS Interface Support   E The Advanced Server supports the NetBIOS interface in TCP/IP, DECnet, E and NetBEUI networks. However, a NetBIOS programming interface is not D provided. NetBIOS interface support includes the support of multipleD transport stacks on a single controller or on different network con-	 trollers.     "                                  7       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 G under TCP/IP in both LAN and WAN environments. The Advanced Server Con- G figuration Manager utility allows you to select one or more of the fol- ; lowing methods for NetBIOS name resolution for WAN support:    o  LMHOSTS file   ' o  Windows Internet Name Service (WINS)    o  DNS  C Note: Enabling DNS allows the server and clients to use a specified C DNS name server for NetBIOS name resolution as a last resort if all H other methods fail to resolve a NetBIOS name. DNS is also used by serverG clients to resolve the server cluster alias and to provide dynamic load D balancing and failover on servers in an OpenVMS Cluster in a WAN en-C vironment. The DNS name server used for load balancing must support E dynamic updates (Berkeley Internet Name Domain [BIND] server, Version  8.1.1 or later).  E DNS is not configured as a replacement for WINS or LMHOSTS but rather H as a supplement. The Advanced Server still uses WINS, LMHOSTS, or broad-! cast methods for resolving names.    Flexible Security Models  F The Advanced Server allows you to choose one of two modes of security,+ depending on the needs of your environment:   E o  In Advanced Server Only mode, only the Advanced Server (Windows NT ,    Server style) security model is enforced.  C This mode is sufficient for most network environments. The Advanced E Server employs a user-level security model that provides precise con- D trol over access to shared resources, including disk devices, direc-E tories, and printers. Control is based on a password assigned to each D user account and the specific access permissions defined for the re- sources.  "                                  8       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 permissionsC on individual files, directories, and resources and complete audit-  ing capabilities.   E Like Windows NT Servers, Advanced Server does not support share-level 7 security and operates in user-level security mode only.   C o  In the Advanced Server and OpenVMS security mode, both the Open- 8    VMS and Advanced Server security models are enforced.  E Use of both security models is never necessary to control user access E to resources, but is provided to allow administrators of systems with D complex OpenVMS security controls already in place to use those sameE controls to restrict access by client users. Note that use of the Ad- C vanced Server and OpenVMS security model results in the extra over- A head of validating both the Advanced Server and OpenVMS settings.   F In addition, the Advanced Server supports password synchronization be-C tween OpenVMS and Advanced Server systems, and it supports user ac-  count lockout.   Domain Support  E Advanced Server allows the network to be subdivided into domains (ad- E ministrative groups of servers and clients). Domains are a convenient C mechanism for controlling user access to the network and for manag-PC ing large networks. The Advanced Server can be a member of a single_E domain. The Advanced Server can be a primary domain controller (PDC),c5 a backup domain controller (BDC), or a member server.   D The Advanced Server can be deployed as the PDC in a network compris-C ing other Advanced Servers, Windows NT Servers, PATHWORKS for Open-cC VMS (LAN Manager) servers, or LAN Manager for OS/2 servers. It alsoiF can act as a BDC for other Advanced Servers and Windows NT Server com-D puters. In addition, the Advanced Server can act as a BDC in WindowsF 2000 mixed-mode domains, or as a member server in Windows 2000 native- mode and mixed-mode domains.  "                                  9 s     D The Advanced Server for UNIX can be part of the same domain with Ad-D vanced Server for OpenVMS and can be designated as either the PDC or the BDC.  C Advanced Server for OpenVMS provides support for wide area networks + using one or more of the following methods:r   o  LMHOSTS fileo  C The presence of the LMHOSTS file on Advanced Server allows NetLogonVE services and security database replication over wide area TCP/IP con-wC figurations. This file contains a list of nodes from geographically D dispersed sites synchronized by the PDC and accessible to clients inE the server's domain. However, use of the LMHOSTS file for replication_C over extreme distances or in networks with slow transmission speedsC is not recommended.   ' o  WINS (Windows Internet Name Service)A  D Support for WINS allows the Advanced Server to act as a WINS client;F that is, to use the name registration and resolution facilities avail-E able from Microsoft WINS services across routed wide area TCP/IP net-nD works, thus enabling WAN support for domain functions, NetLogon ser-) vices, and security database replication.i   o  DNS  C This allows the Advanced Server and clients to use a DNS server for D NetBIOS name resolution. The Advanced Server and clients use DNS forE name resolution as a last resort if all other methods fail to resolve  a NetBIOS name.S   Trust Relationshipss  H The Advanced Server supports trusts. Trust relationships can allow usersC from other domains to access resources in the local domain, and al-h= lows local domain users to access resources in other domains.n   NetLogon Servicesn  D A single domainwide logon lets a user access resources on any serverA in a domain or on servers in other domains that trust the domain.c  "                                 10 s  h  C The domain capabilities of the Advanced Server make it possible forUC a user to issue a single logon request to authenticate the user for(D access to multiple servers in a network. The NetLogon service forcesC the validation of users' logon requests. The logon server that pro-2I cesses a request checks its copy of the domainwide user accounts databasef= for the user name and password supplied in the logon request.n   Network Browser Services  D The Advanced Server can act as a Master Browser in a Windows NT net- work.n   TimeSource Servicesy  F DOS and Windows clients can request date and time information from theD Advanced Server and set the local workstation date and time to coin-
 cide with it.0   User Environment Management   E Logon scripts can be used to configure MS-DOS and Windows workstation C user environments by making network connections and starting appli-hC cations. User profiles can make workstations easier to use, as wellr3 as control workstation access to network resources.M   Server Management and Controln  D The Advanced Server can be managed from either the OpenVMS server orF a client workstation, using one of the following server management in-	 terfaces:u  C o  The Advanced Server ADMINISTER command-line interface, which canrC    be accessed from a terminal or terminal emulator. It conforms toe    standard DCL command syntax.t  D o  Windows NT server administration tools, which are included in theC    Advanced Server software kit to be installed on Windows NT, Win-aF    dows 95, Windows 98, and Windows for Workgroups workstations. TheseG    tools, including Server Manager, User Manager for Domains, and Event H    Viewer, allow you to administer Advanced Server and Windows NT Server"    computers from network clients.  "                                 11       I o  Windows NT Server tools, which are available as part of the Windows NTO
    Server.  C o  Windows 2000 file and print server tools, which are available asa#    part of the Windows 2000 server.o  , Server management interfaces 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-n+    tive sessions, connections, and services   C o  View context-sensitive online help that provides command syntax,s9    options, and qualifiers for each menu item and command.  C The Advanced Server can be administered remotely from PATHWORKS andRC Microsoft Windows client workstations. The Advanced Server can alsorF be managed remotely from Windows NT Server, Windows 2000 Server, PATH-E WORKS Advanced Server, and other Advanced Server for OpenVMS systems.   D Other Advanced Server tools are provided for management of other as-E pects of the file server. These tools are to be used for local servero management only and include:  F o  The Advanced Server Configuration Manager utility (a character cellG    interface) to manage local server configuration parameters that are,eD    for the most part, directly or indirectly related to the environ-C    ment in which the server operates, such as the server's usage ofCD    OpenVMS system resources. Any adjustments that need to be made toE    the OpenVMS SYSGEN parameters to support the running of the server D    are automatically performed by the Configuration Manager utility.  D o  The Advanced Server Parameter Management utility (PWRK$REGUTL) toE    manage server configuration parameters that affect the behavior ofeG    the Advanced Server but not, for the most part, file server resourceu    consumption.s  E o  The License Manager (a character cell interface) to manage the Li-     cense Server.  "                                 12        Windows 2000 Support  @ The Advanced Server provides the following Windows 2000 support:  " o  Support of Windows 2000 clients  E o  As a backup domain controller or member server, support of Windows D    2000 domain controllers in a Windows 2000 mixed-mode domain; as aF    member server, support of Windows 2000 domain controllers in a pure    (native) Windows 2000 domaine  ' Integrating with Microsoft Environmentsw  E The Advanced Server for OpenVMS provides numerous Windows NT integra-rH tion features, including those supported on OpenVMS Alpha systems. These features include support of:  E o  Extended File Specifications, based on ODS-5, with support of long     names and deep directories   1 o  Unicode characters and extended character setsf  C o  Alias file names, generated automatically to provide compatibil-dF    ity with legacy applications that only support file names that com-4    ply with the more limited MS-DOS name conventions   o  Remote management from:  C    -  Network clients, using Windows NT server administration toolsi7       that are provided for installation on the clientse  H    -  Windows NT Servers, using tools available on the Windows NT Server  + o  Windows NT management of shared printersS   o  Windows NT security model  6 o  PDC, BDC, or member server participation in domains  < o  Master Browser or Backup Browser participation in domains  G o  Windows NT-compatible Server Message Block (SMB) file and print pro-n	    tocols:  "                                 13    y  5 o  Connections from a wide variety of Windows clientsr   Integrating with OpenVMS  G Advanced Server encompasses many features of the OpenVMS operating sys-MD tem, including OpenVMS Clusters and symmetric multiprocessing. Open-E VMS Cluster configurations provide load-balancing failover availabil-tC ity and extensive resource capacities by integrating multiple Open-e= VMS systems that can be accessed using a single cluster name.b  F The Advanced Server includes support for a transport-independent clus-E ter alias NetBIOS name that allows multiple cluster members to appearaC as a single server to the connecting clients. This support providesrE higher availability. The cluster alias name has a load-balancing fea-iI ture that connects clients to the cluster member that is the least loadedaD at the time the session is established. The Advanced Server includesD a high-performance, clusterwide distributed data cache that provides' scalability in a clustered environment.u  C The Advanced Server supports the use of ODS-2 disk volumes and ODS-eG 5 disk volumes, a feature of OpenVMS V7.2 and later, for share and file C access by clients. The new ODS-5 based Enhanced File Specifications, provide support for long names.5  D The Advanced Server for OpenVMS is installed using the OpenVMS POLY-C CENTER Software Installation utility. The Advanced Server for Open-k9 VMS uses the OpenVMS Registry to store server parameters.t  ( Integrating with External Authentication  C External authentication is an optional feature that allows users tonC log in to an OpenVMS system using their Advanced Server (domain se-pF curity) user name and password. This feature is useful to OpenVMS sys-H tem managers who want to provide users with a single user name and pass-C word combination for both OpenVMS login and Advanced Server networkd logon.  C For more information about external authentication for OpenVMS, re-IF fer to the Software Product Description for OpenVMS Alpha and VAX (SPD
 25.01.xx).  "                                 14 s     ! Integrating with OpenVMS Securityi  D The Advanced Server provides an extension to the Windows NT securityC model by supporting OpenVMS security enforcement as an optional en-o
 hancement.  ! Integrating with OpenVMS Registry   F Advanced Server provides network users with access to the OpenVMS Reg-D istry. Advanced Server also stores its own configuration data in theD OpenVMS Registry. The Advanced Server provides the PWRK$REGUTL util-D ity for managing server configuration parameters in the OpenVMS Reg-G istry. The server parameters in the OpenVMS Registry can also be viewedr4 and managed from a Windows NT based registry editor.   Alerter Service   D The Advanced Server includes an Alerter Service that sends automaticG alert messages to clients and users as specified in the Advanced ServerA5 AlertNames parameter setting in the OpenVMS Registry.d   Event Log Servicee  D Event logs provide valuable information about server activities. TheE administrator can select from several event types and can select, forrC each, whether successful or unsuccessful attempts at specific oper-vG ations are to generate event messages. Security event messages are gen-aF erated based on the audit policy specified for the Advanced Server and for files and directories.   Replicator Service  C Windows NT Servers provide user data replication across domain con-iD trollers using the Replicator service. The Replicator service is notF provided by Advanced Servers. Therefore, automatic replication of user; files and directories on Advanced Servers is not supported.    Installation Utilities  C The Advanced Server for OpenVMS is installed on the OpenVMS operat-rC ing system using the POLYCENTER Software Installation utility. This.  "                                 15 d  c  H utility is also used to verify that the installation was performed prop-! erly and to remove installations.   D The installation procedure allows you to install either the completeG Advanced Server software, the standalone License Server only, the stan- C dalone external authentication images only, or both standalone com--
 ponents only.b  D The Advanced Server for OpenVMS installation procedure gives you theG option of delaying a reboot indefinitely, such as when you need to con-n0 figure or change more settings before rebooting.   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.wC This product is no longer supported, and licenses to use this prod-r uct are no longer sold.o  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 Advanced Server.   License Management  C The Advanced Server offers license management for Client Access li-BF censes, which can be used in either client-based or server-based mode.2 (For details, see the section SOFTWARE LICENSING.)  C The license deliverables for Advanced Server 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,E using standard LMF procedures, on an OpenVMS operating system that istA hosting the Advanced Server or an Advanced Server License Server.o  ( The two types of license management are:  F o  Client-based license management. The Advanced Server provides a fa-D    cility called Advanced Server License Server that acts as a proxyJ    for client systems that require license keys stored in the LMF database"    on an OpenVMS operating system.  "                                 16 o  o  I A single copy of the License Server software provides and verifies Clientf0 Access licenses being used in client-based mode.  G The Advanced Server License Manager, which must be run on the same nodeeD as the License Server, provides a user interface that allows the ad-D ministrator to monitor client-based license usage, to manage licenseH groups, to set alert levels, to set logging levels for licensing events,C to enable or disable the License Server, and to revoke assigned li-eD censes. The Advanced Server License Manager is also used to preallo-D cate licenses to specific "groups" (including the special predefined$ Server-Based group described later).  C Each LAN needs only one active Advanced Server License Server. (TheND License Server provided with the Advanced Server supports Client Ac-) cess licenses for all supported clients.)f  D The Advanced Server License Registrar, which must be run on the sameE system as the file server, verifies the licenses for clients request-eD ing access to the server functions. Clients that can produce a validC Client Access license are allowed access to the services offered byr the Advanced Server.  C o  Server-based license management. The Advanced Server also allowsaD    client access based on the availability of Client Access licensesI    in the local LMF database being used in server-based mode. If a clientsC    requesting access to the server fails to produce a valid client-tG    based license, the Advanced Server License Registrar software checks C    for the availability of a valid Client Access license being usedeC    in server-based mode. If one is available, the client is allowedr
    access.  F Client Access licenses can be put into server-based mode in one of two ways:n  F    -  If the Advanced Server License Server was not configured for theD       system where Advanced Server is executing, then all Client Ac-C       cess licenses loaded into the local LMF database on that sys-e,       tem will be used in server-based mode.    "                                 17    n  G    -  If the Advanced Server License Server was configured for the sys- D       tem where Advanced Server is executing, then all Client AccessC       licenses loaded into the local LMF database will, by default, #       be used in client-based mode.p  G To allow some or all of these licenses to be used in server-based mode,hF use the Advanced Server License Manager to allocate a portion of thoseF licenses to the special predefined Server-Based group. Licenses avail-H able in the Server-Based group will then be available for use in server- based mode.   E Note: The Advanced Server allows you to simultaneously use Client Ac-nF cess licenses in both client-based and server-based mode. However, be-C cause clients using Client Access licenses in client-based mode areiC already licensed to use the server software, they never consume ad-sG ditional Client Access licenses allocated for use in server-based mode.   ' LAN Manager and PATHWORKS Compatibilityd  C The Advanced Server maintains compatibility with LAN Manager clientiC and server software. The Advanced Server also maintains compatibil-e1 ity with PATHWORKS for OpenVMS (Advanced Server).e  2 A PATHWORKS V5.x for OpenVMS (LAN Manager) server:  , o  Can be upgraded to an Advanced Server.[1]  D o  Can continue running PATHWORKS LAN Manager and act as a BDC, mem-C    ber server, or standalone server in a domain where the PDC is anr3    Advanced Server or a Windows NT Server computer.,       ____________________H  [1]You  can upgrade PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKSE   V6.1 for OpenVMS (Advanced Server), then upgrade PATHWORKS V6.1 for @   OpenVMS (Advanced Server) to Advanced Server V7.3 for OpenVMS.    "                                 18 c  S   HARDWARE REQUIREMENTSs  D The following systems, components, and peripherals are supported ex- cept as noted.   Processors Supported  C All Alpha processors supported by OpenVMS Version 7.2-1, 7.2-2, andd6 7.3 are also supported by Advanced Server for OpenVMS.   Memory Requirementsi  D The Advanced Server requires a minimum of physical memory for properC installation, configuration, and execution of the software, depend-H ing on the processor type:  ' o  On Alpha systems, a minimum of 64 MBs  D Note: These memory requirements are a minimum requirement only. Mem-F ory requirements can vary widely according to the server CPU, the num-D ber of clients using the server and their activities, and the numberE and speed of the server's disks and the other applications running onr the server.r  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires an D Alpha system with approximately 64 MB of memory. This means that 80%F of the system memory and CPU time is dedicated to the Advanced Server,% even though some work might use less.o   OPTIONAL HARDWAREd   PostScript Printerse  G The Advanced Server supports all PostScript printers supported by Open-.F VMS. Selected PostScript printers may need the DECprint Supervisor forC OpenVMS (DCPS) software to provide access through the OpenVMS queu- D ing system over TCP/IP or DECnet. Refer to the DCPS Software ProductH Description (SPD 44.15.xx) for a complete list of the DIGITAL PostScript9 printers and other PostScript printers supported by DCPS.   "                                 19 o  n  C DIGITAL PostScript printers connected by serial lines or DECserverss= and printers attached directly to the Ethernet are supported.s   Network Interface Controllers.  E Advanced Server supports the following Ethernet, FDDI, and Token Ringe network hardware devices:e  G o  For the TCP/IP transport, Advanced Server supports the network hard-oF    ware devices supported by the specific TCP/IP product. Refer to theD    Software Product Description for Compaq TCP/IP Services for Open-C    VMS (SPD 46.46.xx). For information about what software versions D    of Compaq TCP/IP for OpenVMS are supported, see the section SOFT-G    WARE REQUIREMENTS. For information about other TCP/IP products, con-     tact the vendor.g  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see%    the SPD for the following product:e  9    -  Compaq DECnet-Plus for OpenVMS Alpha (SPD 50.45.xx)s  E For information about what software versions of DECnet are supported,c see SOFTWARE REQUIREMENTS.  E o  For the NetBEUI transport, Advanced Server provides the same leveloD    of support for Ethernet and FDDI as the OpenVMS Alpha and VAX op-F    erating systems. For more information, see the Software Product De-K    scription for the OpenVMS Alpha and VAX operating system (SPD 25.01.xx).o  A Note: Advanced Server does not support the DEFZA FDDI controller.t   CLUSTER ENVIRONMENTr  D Advanced Server runs on members of OpenVMS Clusters. OpenVMS ClusterC configurations are fully described in the Software Product Descrip-80 tion for OpenVMS Cluster Software (SPD 29.78.xx)  F The Advanced Server for OpenVMS can run on members of an OpenVMS Clus-G ter that are running OpenVMS Alpha Version 7.2-1, 7.2-2, or 7.3. Mixed- D version clusters are supported if all cluster members upon which theC Advanced Server for OpenVMS runs are running OpenVMS Versions 7.2-2   "                                 20 o  2  F or 7.3. The enhanced OpenVMS Registry components of Versions 7.2-2 andF 7.3 are compatible with each other, but they are incompatible with theF Registry components of Version 7.2-1. If you are currently running theC Advanced Server for OpenVMS in a cluster and you want to upgrade tovC OpenVMS Version 7.2-2 or 7.3, you must upgrade at the same time allnD the Version 7.2-1 cluster members upon which the Advanced Server for OpenVMS will run.n  D Advanced Server supports up to 31 server nodes in a cluster; no moreC than 31 nodes in a cluster can run Advanced Server concurrently. InrC a typical scenario, the server runs on only a few central nodes, toSD exploit the cluster's shared disks and high-speed interconnect envi- ronment.  F In a cluster, Advanced Server supports simultaneous file access by allF nodes running the server. A central event log, central Advanced ServerD accounts, and share databases are maintained in a cluster. In an Ad-D vanced Server domain, the OpenVMS Cluster represents a single domainA member, whether it is acting as the PDC, BDC, or a member server.e   SOFTWARE REQUIREMENTSd   Operating System  - o  OpenVMS Alpha Version 7.2-1, 7.2-2, or 7.3e  C For minimum hardware requirements of the operating system, refer todJ the Software Product Description for OpenVMS Alpha and VAX (SPD 25.01.xx).   Network Transport Software  C Advanced Server includes NetBEUI network transport software. TCP/IPeG or DECnet network transport software might also be required by AdvancediD Server, depending on the transport used by clients requiring connec-1 tions to the server, or for use of some features.u          "                                 21 h  c  H When the Advanced Server is to be used in a TCP/IP environment, OpenVMS-G based TCP/IP software is required. This software must be purchased sep- E arately. The following TCP/IP transports support the Advanced Server:0  F o  Compaq TCP/IP Services for OpenVMS. The versions supported for eachD    version of the OpenVMS operating system are indicated in Table 1,8    Compaq TCP/IP Services for OpenVMS Versions Supported  > o  MultiNet for OpenVMS (from Process Software Corporation)[2]  1 o  TCPware for OpenVMS (from Process Software)[2]S  C ___________________________________________________________________,  C Table_1:_Compaq_TCP/IP_Services_for_OpenVMS_Versions_Supported_____c  # OpenVMS         TCP/IP Services foreC Version_________OpenVMS____________________________________________    Alpha V7.3      V5.1   Alpha V7.2-2    V5.1  C Alpha_V7.2-1____V5.0A______________________________________________r  F The following DECnet products are supported by the Advanced Server forC OpenVMS. The versions supported for each version of the OpenVMS op-sC erating system are indicated in Table 2, DECnet Versions Supported.s  ! o  Compaq DECnet-Plus for OpenVMS    o  Compaq DECnet for OpenVMS     ____________________J  [2]Third-party  TCP/IP products must include a PATHWORKS IP (PWIP) driver,   in order to work with the Advanced Server.    "                                 22 ,     C ___________________________________________________________________r  C Table_2:_DECnet_Versions_Supported_________________________________g                   DECnet, OpenVMS         for          DECnet-Plus forC Version_________OpenVMS______OpenVMS_______________________________     Alpha V7.3      7.3          7.3  " Alpha V7.2-2    7.2          7.2-1  C Alpha_V7.2-1____7.2__________7.2-1_________________________________    PATHWORKS Software  F The Advanced Server for OpenVMS cannot run on the same system as other7 PATHWORKS server products. Specifically, this includes:t  F o  PATHWORKS V5.0 for OpenVMS (LAN Manager). You can upgrade the PATH-C    WORKS LAN Manager V5.0 server to PATHWORKS V6.1 for OpenVMS (Ad-tD    vanced Server). Running the Advanced Server on a system also run-E    ning the PATHWORKS LAN Manager V5.0 server is not possible or sup-sE    ported. You cannot continue to run the PATHWORKS LAN Manager soft-oF    ware, once the Advanced Server software has been installed. The Ad-D    vanced Server cannot coexist on the same OpenVMS Cluster with the%    PATHWORKS LAN Manager V5.0 server.n  D o  PATHWORKS V6.1 for OpenVMS (Advanced Server). You can upgrade theF    PATHWORKS V6.1 for OpenVMS (Advanced Server) to Advanced Server forF    OpenVMS. Running any PATHWORKS for OpenVMS (Advanced Server) serverC    on a system that is also running the Advanced Server for OpenVMSnE    is not possible or supported. You cannot continue to run the PATH-cC    WORKS for OpenVMS (Advanced Server) once the Advanced Server forfE    OpenVMS software has been installed. The Advanced Server for Open-eD    VMS cannot coexist on the same OpenVMS Cluster with PATHWORKS for    OpenVMS (Advanced Server).l      "                                 23 l  s  D The Advanced Server maintains down-level compatibility with LAN Man-F ager client and server software. LAN Manager users can add an AdvancedH 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 aF BDC, member server, or standalone server in a network in which the PDC6 is an Advanced Server or a Windows NT Server computer.  D The Advanced Server can be deployed as a PDC in a network comprisingD other Advanced Server for OpenVMS servers, Windows NT Servers, PATH-G WORKS for OpenVMS (Advanced Server) servers, PATHWORKS for OpenVMS (LANoE Manager) servers, or LAN Manager for OS/2 Servers. It can also act asnG a BDC for other Advanced Server for OpenVMS, PATHWORKS Advanced Server,s or Windows NT Server computers.   H In addition, the Advanced Server can act as a BDC in Windows 2000 mixed-C mode domains, or as a member server in Windows 2000 native-mode ando mixed-mode domains.f   Client Softwares  D The following versions of client software are supported for use with Advanced Server for OpenVMS:  1 o  Microsoft Windows NT workstation software V4.0r   o  Windows 2000    o  Microsoft Windows 98    o  Microsoft Windows 95a  ) o  Microsoft Windows for Workgroups V3.11   5 o  Compaq PATHWORKS 32 Version 7.2 (see SPD 56.33.xx)r   GROWTH CONSIDERATIONSe  E The minimum hardware and software requirements for any future version C of this product may be different from the requirements for the cur-v
 rent version.a  "                                 24 o  n  C ___________________________________________________________________s  B PRODUCT NAME:  Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server)   DESCRIPTIONf  G Compaq PATHWORKS for OpenVMS (Advanced Server), also known as the PATH-eD WORKS Advanced Server, is an OpenVMS layered application and networkG operating system that is compatible with the Microsoft networking tech- G nology. In particular, PATHWORKS for OpenVMS (Advanced Server) is basediE on the Windows NT Server, but it provides additional features. It en-iF hances the Windows NT Server functionality by incorporating both Open-E VMS and Microsoft technology to deliver powerful features for networklC administration and enhanced security. The Advanced Server can oper-s? ate independently or in cooperation with the Windows NT Server.r  D As a server for workstations on a network, PATHWORKS Advanced ServerG provides file and print shares that enable a community of desktop userseC to share computing resources efficiently. PATHWORKS Advanced ServereD 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.  F PATHWORKS Advanced Server software lets DOS, Windows, Windows NT, Win-C dows 95, Windows 98, Windows 2000, and OpenVMS users share printersrD connected to VAX computers, Alpha computers, or OpenVMS Cluster sys-N tems, as well as network-based printers such as LAT printers and PrintServers.  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.              "                                 25 e      FEATURES  F PATHWORKS Advanced Server adds an additional dimension to general pur-F pose OpenVMS systems. In addition to providing traditional support forF business, scientific, and engineering applications, PATHWORKS AdvancedG Server allows an OpenVMS system to appear to PC clients as a Windows NT  Server.S  D The major features of PATHWORKS Advanced Server are described in the following sections.   
 File Servicesd  D PATHWORKS Advanced Server provides clients with a remote file systemD that appears as a transparent extension of the client system's local computing environment.  G PATHWORKS Advanced Server file shares are based on Microsoft's Advanced 1 Server V3.0 SMB (Server Message Block) protocols.e  I Each file stored in a file service is stored as an OpenVMS file in RecordtC Management Services (RMS) format. Three types of RMS file or recordn1 formats are allowed and supported on each volume:    o  Sequential stream  8 o  Sequential fixed-length record (512 bytes per record)   o  Sequential undefinedu  E Files stored in a file service are accessible to PC clients, to Open-eE VMS users, and to applications that can interpret the content and or-s7 ganization of a file written by the client application.a  D To enable compatibility with legacy applications such as MS-DOS, the% Advanced Server automatically creates.D MS-DOS-compatible alias file names for files whose names do not com-F ply with the file naming standards of those applications. As a result,D client applications that must use, or choose to use, the MS-DOS for-F mat for file names, can access these shared files on the server by us-% ing the file's associated alias name.q  "                                 26 s  l  D Multiple LAN Manager clients can concurrently access files stored onD the server's disk through the file-access modes and byte-range lock-2 ing support provided by PATHWORKS Advanced Server.  E PATHWORKS Advanced Server lets users share OpenVMS files. You can use C discretionary access Windows NT controls on each file and directorynD 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 controleD auditing supported by Windows NT-like security. Additional, optional? security is provided by OpenVMS file and directory protections.    Print Shares  F PATHWORKS Advanced Server software lets DOS, Windows, Windows NT, Win-F dows 95, Windows 98, and OpenVMS users share printers connected to VAXK computers, Alpha computers, or OpenVMS Cluster systems, as well as network-eF based printers such as LAT printers and PrintServers. Print shares areE supported in local area network (LAN) and wide area network (WAN) en- E vironments. PC clients can print files from the DOS, Windows, WindowseC 95, Windows 98, and Windows NT operating systems as well as from PCe
 applications.l  D Multiple print shares can be defined for a single printer. For exam-E ple, separate services can be created for landscape-mode printing andaC portrait-mode printing. Similarly, separate services can be createdcC for DIGITAL mode and IBM ProPrinter mode printing for a single LA75  printer.  D PATHWORKS Advanced Server supports the DECprint Supervisor for Open-C VMS (DCPS) product, which provides PostScript and DEC ANSI printingo2 to selected industry-standard PostScript printers.  3 Sharing of Network Resources by Heterogeneous Usersd  F Services provided by PATHWORKS Advanced Server are accessible to PATH-D WORKS clients as well as to Microsoft clients. All clients using theG services of a PATHWORKS Advanced Server must be properly licensed. (Foro6 more information, see the section SOFTWARE LICENSING.)    "                                 27 n  n  E Files are stored on the server in native OpenVMS RMS format. This al-eE lows information stored by the PCs using PATHWORKS Advanced Server todC be shared with traditional OpenVMS users. In addition, this feature:2 allows information to be shared among all clients.   Network Transport SupportO  E PATHWORKS Advanced Server supports TCP/IP, DECnet (Phase IV), DECnet-eH Plus (formerly known as DECnet/OSI), and NetBEUI network transport soft-G ware. One or more transport stacks can work concurrently on the server.S  G Both the TCP/IP and DECnet network transports are sold as separate Com-r+ paq products and require separate licenses.n  E NetBEUI transport software is included with PATHWORKS Advanced Server C software. Using NetBEUI transport software, LAN Manager clients canlG access the server in the LAN for file and print shares. NetBEUI is rec-eD ommended for use in small LAN-only environments of 50 nodes or less.C For information about supported network transport software, see thee section SOFTWARE REQUIREMENTS.   NetBIOS Interface Support   C PATHWORKS Advanced Server supports the NetBIOS interface in TCP/IP,rC DECnet, and NetBEUI networks. However, a NetBIOS programming inter-tD face is not provided. NetBIOS interface support includes the supportC of multiple transport stacks on a single controller or on differentc 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 supportedeE under TCP/IP in both LAN and WAN environments. The PATHWORKS AdvancediE Server Configuration Manager utility allows you to select one or bothpE of the following methods for NetBIOS name resolution for WAN support:l   o  LMHOSTS fileT  ' o  Windows Internet Name Service (WINS)d   o  DNS  "                                 28 n  o  C Note: Enabling DNS allows the server and clients to use a specifiedtC DNS name server for NetBIOS name resolution as a last resort if alldH other methods fail to resolve a NetBIOS name. DNS is also used by serverG clients to resolve the server cluster alias and to provide dynamic loaduD balancing and failover on servers in an OpenVMS Cluster in a WAN en-C vironment. The DNS name server used for load balancing must supportoE dynamic updates (Berkeley Internet Name Domain [BIND] server, Version  8.1.1 or later).  E DNS is not configured as a replacement for WINS or LMHOSTS but ratheraH as a supplement. The Advanced Server still uses WINS, LMHOSTS, or broad-! cast methods for resolving names.o   Flexible Security Models  F The Advanced Server allows you to choose one of two modes of security,+ depending on the needs of your environment:v  E o  In Advanced Server Only mode, only the Advanced Server (Windows NTe,    Server style) security model is enforced.  C This mode is sufficient for most network environments. The Advanced(E Server employs a user-level security model that provides precise con-pD trol over access to shared resources, including disk devices, direc-E tories, and printers. Control is based on a password assigned to each D user account and the specific access permissions defined for the re- sources.  F The Advanced Server incorporates enhanced features that provide a highG level of control over user and resource permissions and auditing. TheseeD features include support of discretionary access control permissionsC on individual files, directories, and resources and complete audit-o ing capabilities.n  E Like Windows NT Servers, Advanced Server does not support share-levele7 security and operates in user-level security mode only.f  C o  In the Advanced Server and OpenVMS security mode, both the Open- 8    VMS and Advanced Server security models are enforced.  "                                 29 r     E Use of both security models is never necessary to control user accessfE to resources, but is provided to allow administrators of systems withtD complex OpenVMS security controls already in place to use those sameE controls to restrict access by client users. Note that use of the Ad-iC vanced Server and OpenVMS security model results in the extra over-lA head of validating both the Advanced Server and OpenVMS settings.a  F In addition, the Advanced Server supports password synchronization be-C tween OpenVMS and Advanced Server systems, and it supports user ac-s count lockout.   Domain Support  F PATHWORKS Advanced Server allows the network to be subdivided into do-D mains (administrative groups of servers and clients). Each PATHWORKSC Advanced Server can be a member of a single domain. A PATHWORKS Ad- D vanced Server can be a primary domain controller (PDC), a backup do-C main controller (BDC), or a member server. Domains are a convenient C mechanism for controlling user access to the network and for manag-  ing large networks.u  D The Advanced Server can be deployed as the PDC in a network compris-C ing other Advanced Servers, Windows NT Servers, PATHWORKS for Open-hC VMS (LAN Manager) servers, or LAN Manager for OS/2 servers. It alsorF can act as a BDC for other Advanced Servers and Windows NT Server com- puters.v  F Advanced Server for UNIX, as well as any Windows NT compatible server,C can be part of the same domain with PATHWORKS for OpenVMS (Advancedh7 Server) and can be designated as either the PDC or BDC.t  D PATHWORKS Advanced Server provides support for wide area domains us-) ing one or both of the following methods:A   o  LMHOSTS file   E The presence of the LMHOSTS file on the PATHWORKS Advanced Server al-eG lows NetLogon services and security database replication over wide area(C TCP/IP configurations. This file contains a list of nodes from geo-dE graphically dispersed sites synchronized by the PDC and accessible top  "                                 30 v  e  D clients in the server's domain. However, use of the LMHOSTS file forE replication over extreme distances or in networks with slow transmis-  sion speeds is not recommended.c  ' o  WINS (Windows Internet Name Service)i  J Support for WINS allows PATHWORKS Advanced Server to act as a WINS client;F that is, to use the name registration and resolution facilities avail-E able from Microsoft WINS services across routed wide area TCP/IP net-TD works, thus enabling WAN support for domain functions, NetLogon ser-) vices, and security database replication.C   o  DNS  C This allows the Advanced Server and clients to use a DNS server forcD NetBIOS name resolution. The Advanced Server and clients use DNS forE name resolution as a last resort if all other methods fail to resolve_ a NetBIOS name.a   Trust Relationshipsr  F PATHWORKS Advanced Server supports trusts. Trust relationships can al-E low users from other domains to access resources in the local domain,_C and allows local domain users to access resources in other domains.1   NetLogon Services_  D A single domainwide logon lets a user access resources on any serverA in a domain or on servers in other domains that trust the domain.e  C The domain capabilities of PATHWORKS Advanced Server make it possi- G ble 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 forcesC the validation of users' logon requests. The logon server that pro-dI cesses a request checks its copy of the domainwide user accounts database2= for the user name 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.  "                                 31 l  f   TimeSource Servicesn  D DOS, Windows, and clients can request date and time information fromD the PATHWORKS Advanced Server and set the local workstation date and time to coincide with it._   User Environment ManagementH  E Logon scripts can be used to configure MS-DOS and Windows workstationsC user environments by making network connections and starting appli-sC cations. User profiles can make workstations easier to use, as welle3 as control workstation access to network resources.    Server Management and Control   G PATHWORKS Advanced Server can be managed from either the OpenVMS serverHE or a client workstation, using one of the following server managementc interfaces:e  E o  PATHWORKS Advanced Server ADMINISTER command line interface, whicheD    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 theH    PATHWORKS Advanced Server software kit to be installed on Windows NT,C    Windows 95, Windows 98, and Windows for Workgroups workstations.HC    These tools, including Server Manager, User Manager for Domains,sF    and Event Viewer, allow you to administer PATHWORKS Advanced Server8    and Windows NT Server computers from network clients.  I o  Windows NT Server tools, which are available as part of the Windows NTa
    Server.  , Server management interfaces can be used to:  = o  Manage file and printer shares, user accounts, and groups.e  E o  Display and control server resources currently in use, such as ac-s,    tive sessions, connections, and services.  C o  View context-sensitive online help that provides command syntax,r:    options, and qualifiers for each menu item and command.  "                                 32       E PATHWORKS Advanced Server can be remotely administered from PATHWORKSmD and Microsoft Windows client workstations. PATHWORKS Advanced ServerD can also be managed remotely from Windows NT Server, Advanced Server9 for OpenVMS, and other PATHWORKS Advanced Server systems.d  D Other PATHWORKS Advanced Server tools are provided for management ofD other aspects of the file server. These tools are to be used for lo-' cal server management only and include:r  G o  The PATHWORKS Advanced Server Configuration Manager utility (a char-RD    acter cell interface) to manage local server configuration param-D    eters that are, for the most part, directly or indirectly relatedH    to the environment in which the server operates, such as the server'sE    usage of OpenVMS system resources. Any adjustments that need to berF    made to the OpenVMS SYSGEN parameters to support the running of theH    server are automatically performed by the Configuration Manager util-    ity.s  E o  The PATHWORKS License Manager (a character-cell interface) to man-3$    age the PATHWORKS License Server.  ' Integrating with Microsoft EnvironmentsA  F The Advanced Server provides numerous Windows NT integration features, such as:   o  Remote management from:  C    -  Network clients, using Windows NT server administration tools 7       that are provided for installation on the clients_  H    -  Windows NT Servers, using tools available on the Windows NT Server   o  Windows NT security model  6 o  PDC, BDC, or member server participation in domains  C o  Alias file names, generated automatically to provide compatibil-VF    ity with legacy applications that only support file names that com-4    ply with the more limited MS-DOS name conventions  < o  Master Browser or Backup Browser participation in domains  "                                 33 i  l  G o  Windows NT-compatible Server Message Block (SMB) file and print pro-t	    tocolse  5 o  Connections from a wide variety of Windows clientsu   Integrating with OpenVMS  F PATHWORKS Advanced Server encompasses many features of the OpenVMS op-F erating system, including OpenVMS Clusters and symmetric multiprocess-E ing. OpenVMS Cluster configurations provide failover availability andrE extensive resource capacities by integrating multiple OpenVMS systemsg1 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 nameOF 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.G PATHWORKS Advanced Server includes a high-performance, clusterwide dis-nE tributed data cache that provides scalability in a clustered environ-n ment.y  F PATHWORKS Advanced Server can run on both VAX and Alpha members of ho-D mogeneous or mixed architecture OpenVMS Clusters. PATHWORKS AdvancedG Server on Alpha systems supports the use of ODS-2 disk volumes and ODS-NE 5 disk volumes, a feature of OpenVMS Version 7.2 and later, for shareeD and file access by clients. However, PATHWORKS V6.1 for OpenVMS (Ad-G vanced Server) does not support the features of ODS-5 devices; instead,i. it treats the ODS-5 device as an ODS-2 device.  ( Integrating with External Authentication  C External authentication is an optional feature that allows users to F log in to an OpenVMS system using their PATHWORKS Advanced Server userD name and password. This feature is useful to OpenVMS system managersC who want to provide users with a single user name and password com- E bination for both OpenVMS login and PATHWORKS Advanced Server networkm logon.  "                                 34    e  D Note that external authentication is supported on OpenVMS. If exter-C nal authentication is being used in an OpenVMS Cluster, all clusterfG members should be configured to process OpenVMS logon requests for net- D work users. If one or more members do not support external authenti-E cation, user logins might result in unpredictable behavior. To ensurecE that external authentication works properly on the cluster, each nodeaD in the cluster should be at OpenVMS Alpha V7.2-1 or later or OpenVMS VAX 7.2 or later.   C For more information about external authentication for OpenVMS, re-nF fer to the Software Product Description for OpenVMS Alpha and VAX (SPD
 25.01.xx).  ! Integrating with OpenVMS SecurityS  E PATHWORKS Advanced Server provides an extension to the Windows NT se-tF curity model by supporting OpenVMS security enforcement as an optional enhancement.   Alerter Servicee  D PATHWORKS Advanced Server includes an Alerter Service that sends au-D tomatic alert messages to clients and users as specified in the LAN-
 MAN.INI file.    Event Log Service   D Event logs provide valuable information about server activities. TheE administrator can select from several event types and can select, for-C each, whether successful or unsuccessful attempts at specific oper-aG ations are to generate event messages. Security event messages are gen-cE erated based on the audit policy specified for the PATHWORKS Advancedo% Server and for files and directories.    Replicator Service  C Windows NT Servers provide user data replication across domain con-sD trollers using the Replicator service. The Replicator service is notC provided on PATHWORKS Advanced Servers. Therefore, automatic repli-sE cation of user files and directories on PATHWORKS Advanced Servers isi not supported.  "                                 35    n   Installation Utilities  C PATHWORKS Advanced Server is installed on OpenVMS systems using the D 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.o  C The installation procedure allows you to install PATHWORKS AdvancedsD Server with the integrated License Server or just the standalone Li-C cense Server, the external authentication images (except on OpenVMSc V6.2), or the Upgrade utility.   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.eC This product is no longer supported, and licenses to use this prod-H uct are no longer sold.p  D If you are running the PATHWORKS for OpenVMS (NetWare) server on theD same system with PATHWORKS Advanced Server, you must remove the Net-E Ware server software from the system before you install PATHWORKS Ad-r vanced Server.   License Management  E PATHWORKS Advanced Server offers license management for Client AccesssH licenses, which can be used in either client-based or server-based mode.2 (For details, see the section SOFTWARE LICENSING.)  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,C using standard LMF procedures, on an OpenVMS system that is hostingt: 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.  "                                 36 a  C  C A single copy of the PATHWORKS License Server software provides and J 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 asD the License Server, provides a user interface that allows the admin-I istrator to monitor client-based license usage, to manage license groups,eC to set alert levels, to set logging levels for licensing events, torF enable or disable the License Server, and to revoke assigned licenses.E The PATHWORKS License Manager is also used to preallocate licenses totG specific "groups" (including the special, predefined server-based groupf described later).   E Each LAN needs only one active PATHWORKS License Server. (The LicenseeE Server provided with PATHWORKS Advanced Server supports Client Access1$ licenses for all supported clients.)  C The PATHWORKS License Registrar, which must be run on the same sys-nD tem as the file server, verifies the licenses for clients requestingG access to the server functions. Clients that can produce a valid ClientmF 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 validlH    client-based license, the PATHWORKS License Registrar software checksC    for the availability of a valid Client Access license being usedDC    in server-based mode. If one is available, the client is allowed 
    access.  F Client Access licenses can be put into server-based mode in one of two ways:u  E    -  If the PATHWORKS License Server was not configured for the sys-eG       tem where PATHWORKS Advanced Server is executing, then all ClientsE       Access licenses loaded into the local LMF database on that sys-s,       tem will be used in server-based mode.  "                                 37 t     C    -  If the PATHWORKS License Server was configured for the systemeC       where PATHWORKS Advanced Server is executing, then all ClientiE       Access licenses loaded into the local LMF database will, by de--*       fault, be used in client-based mode.  G To allow some or all of these licenses to be used in server-based mode, D use the PATHWORKS License Manager to allocate a portion of those li-E censes to the special, predefined Server-Based group. Licenses avail- H able in the Server-Based group will then be available for use in server- based mode.e  G Note: PATHWORKS Advanced Server allows you to simultaneously use ClientrD Access licenses in both client-based and server-based mode. However,E because clients using Client Access licenses in client-based mode areaC already licensed to use the server software, they never consume ad-rG ditional Client Access licenses allocated for use in server-based mode.   ! Accommodation of Retired FeaturesM  F The following features of PATHWORKS V5.0 for OpenVMS (LAN Manager) are= not provided in PATHWORKS V6.1 for OpenVMS (Advanced Server):   C o  Standalone server role. PATHWORKS Advanced Server can be config-f(    ured as a PDC, BDC, or member server.  D o  FAT volumes. To continue to provide FAT volume access to clients,C    you must maintain the PATHWORKS LAN Manager server on a separatesD    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.t  D o  Backward-compatibility mode. This mode is used to ease the migra-C    tion from PATHWORKS V4.x to PATHWORKS LAN Manager. Make sure alluC    clients making use of this connection format are upgraded beforee1    the installation of PATHWORKS Advanced Server.n  E o  Remote Boot service. If clients depend on remote booting, you mustdI    maintain the PATHWORKS LAN Manager server on a separate system. Trans- E    fer this function to another server that supports Remote Boot ser-     vice before the upgrade.m  "                                 38 t  l  D o  Share-level security. PATHWORKS Advanced Server manages access to-    all resources through user-level security.i  C o  LAN Manager and creator security mode. The server can be config-AF    ured for PATHWORKS Advanced Server Only security model or for PATH-4    WORKS Advanced Server and OpenVMS security model.  L o  PATHWORKS LAN Manager Net command-line interface and ADMINISTER/PATHWORKSF    character-cell interface. These features were replaced by the PATH-C    WORKS Advanced Server ADMINISTER command-line interface. The AD-sD    MINISTER command-line interface provides automatic translation ofE    a subset of Net commands that have ADMINISTER command equivalents.   
 Compatibility   I PATHWORKS Advanced Server maintains compatibility with LAN Manager clientoG and server software. A PATHWORKS V5.0 for OpenVMS (LAN Manager) server:C  2 o  Can be upgraded to a PATHWORKS Advanced Server.  D o  Can continue running PATHWORKS LAN Manager and act as a BDC, mem-H    ber server, or standalone server in a domain where the PDC is a PATH-9    WORKS Advanced Server or a Windows NT Server computer.e   HARDWARE REQUIREMENTSs  D The following systems, components, and peripherals are supported ex- cept as noted.   Processors Supported  D All VAX and Alpha processors supported by OpenVMS Alpha Version 6.2,D 7.2-1, 7.2-2, and 7.3, and by OpenVMS VAX Version 6.2, 7.2, and 7.3,C are also supported by PATHWORKS V6.1 for OpenVMS (Advanced Server),e except for the following:t          "                                 39 t  o     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, VAXd             11/782, VAX 11/785  A VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXsta-O*             tion 4000 VLC, VAXstation 8000   Memory Requirementsr  C PATHWORKS Advanced Server requires a minimum of physical memory for F proper installation, configuration, and execution of the software, de- pending on the processor type:  ' o  On Alpha systems, a minimum of 64 MBi  % o  On VAX systems, a minimum of 64 MBo  D Note: These memory requirements are a minimum requirement only. Mem-F ory requirements can vary widely according to the server CPU, the num-D ber of clients using the server and their activities, and the numberE and speed of the server's disks and the other applications running on  the server.s  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%E of the system memory and CPU time are dedicated to PATHWORKS Advancede- Server, even though some work might use less.               "                                 40 i  n   OPTIONAL HARDWARE    PostScript Printerse  D PATHWORKS Advanced Server supports all PostScript printers supportedI by OpenVMS. Selected PostScript printers may optionally need the DECprintnD Supervisor for OpenVMS (DCPS) software to provide access through theE OpenVMS queuing system over TCP/IP or DECnet. Refer to the DCPS Soft-iG ware Product Description (SPD 44.15.xx) for a complete list of the DIG-s5 ITAL and other PostScript printers supported by DCPS.c  C DIGITAL PostScript printers connected by serial lines or DECservers = and printers attached directly to the Ethernet are supported.t   Non-PostScript Printersw  D PATHWORKS Advanced Server also supports the following non-PostScript	 printers:m  + DIGITAL LA75 Companion          EPSON FX850f Printerm, DIGITAL LA210                   EPSON FX1050. DIGITAL LA324                   IBM ProPrinter= DIGITAL LJ250 Companion         NEC SilentWriter II Model 290R
 Color Printerv DIGITAL LN03 PLUSb   Network Interface Controllersn  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 theTE    network hardware devices supported by the specific TCP/IP product. C    Refer to the Software Product Description for Compaq TCP/IP Ser-fE    vices for OpenVMS (SPD 46.46.xx). For information on what softwaredD    versions of Compaq TCP/IP for OpenVMS are supported, see the sec-G    tion SOFTWARE REQUIREMENTS. For information about other TCP/IP prod-s    ucts, contact the vendor.  "                                 41 t     D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see'    the SPDs for the following products:   9    -  Compaq DECnet-Plus for OpenVMS Alpha (SPD 50.45.xx)e  7    -  Compaq DECnet-Plus for OpenVMS VAX (SPD 25.03.xx)f  <    -  Compaq DECnet for OpenVMS VAX and Alpha (SPD 48.48.xx)  E For information about what software versions of DECnet are supported,M& see the section SOFTWARE REQUIREMENTS.  D o  For the NetBEUI transport, PATHWORKS Advanced Server provides theC    same level of support for Ethernet and FDDI as the OpenVMS oper-dC    ating system. For more information, see the Software Product De-S6    scription for OpenVMS Alpha and VAX (SPD 25.01.xx).  D Note: PATHWORKS Advanced Server does not support the DEFZA FDDI con- troller.   CLUSTER ENVIRONMENTa  D PATHWORKS Advanced Server runs on members of OpenVMS Clusters. Open-D VMS Cluster configurations are fully described in the Software Prod-< uct Description for OpenVMS Cluster Software (SPD 29.78.xx).  C PATHWORKS Advanced Server supports up to 31 server nodes in a clus-iE ter. In other words, no more than 31 nodes in a cluster can run PATH-PE WORKS Advanced Server concurrently. In a typical scenario, the servertC is run on only a few central nodes, to exploit the cluster's sharedt. disks and high-speed interconnect environment.  F In a cluster, PATHWORKS Advanced Server supports simultaneous file ac-F cess by all nodes running the server. A central event log, central Ad-E vanced Server accounts, and share databases are maintained in a clus-TD ter. In a PATHWORKS Advanced Server domain, the OpenVMS Cluster rep-E resents a single domain member, whether it is acting as the PDC, BDC,m or a member server.     "                                 42 o  t   SOFTWARE REQUIREMENTSy   Operating System  3 o  OpenVMS Alpha Version 6.2, 7.2-1, 7.2-2, and 7.3l  ( o  OpenVMS VAX Version 6.2, 7.2, and 7.3  C For minimum hardware requirements of the operating system, refer to J the Software Product Description for OpenVMS Alpha and VAX (SPD 25.01.xx).   Network Transport Software  F PATHWORKS Advanced Server includes NetBEUI network transport software.E TCP/IP or DECnet network transport software might also be required byeE PATHWORKS Advanced Server, depending on the transport used by clientsmA requiring connections to the server, or for use of some features.a  E When PATHWORKS Advanced Server is to be used in a TCP/IP environment,lE OpenVMS based TCP/IP software is required. This software must be pur-eD chased separately. The following TCP/IP transports support PATHWORKS Advanced Server:  F o  Compaq TCP/IP Services for OpenVMS; the versions supported for eachD    version of the OpenVMS operating system are indicated in Table 3,8    Compaq TCP/IP Services for OpenVMS Versions Supported  < o  MultiNet for OpenVMS[2] from Process Software Corporation  < o  TCPware for OpenVMS [2] from Process Software Corporation         ____________________J  [2]Third-party  TCP/IP products must include a PATHWORKS IP (PWIP) driver,   in order to work with the Advanced Server.    "                                 43 e  a  C ___________________________________________________________________t  C Table_3:_Compaq_TCP/IP_Services_for_OpenVMS_Versions_Supported_____r  +                         TCP/IP Services foriC OpenVMS_Version_________OpenVMS____________________________________n   Alpha V7.3              V5.1 Alpha V7.2-2            5.1  Alpha V7.2-1            V5.0Au Alpha V6.2              V4.2 VAX V7.3                V5.1$ VAX V7.2                V5.0A or 5.1C VAX_V6.2________________V4.2_______________________________________s  D The following DECnet and DECnet-Plus products are supported by PATH-E WORKS Advanced Server. The versions supported for each version of thetG OpenVMS operating system are indicated in Table 4, DECnet Versions Sup-a ported.s  ! o  Compaq DECnet-Plus for OpenVMSf   o  Compaq DECnet for OpenVMS  C ___________________________________________________________________   C Table_4:_DECnet_Versions_Supported_________________________________.  :                         DECnet for         DECnet-Plus forC OpenVMS_Version_________OpenVMS____________OpenVMS_________________o  . Alpha V7.3              7.3                7.30 Alpha V7.2-2            7.2                7.2-10 Alpha V7.2-1            7.2                7.2-1. Alpha V6.2              6.2                6.3. VAX V7.3                7.3                7.3. VAX V7.2                7.2                7.2C VAX_V6.2________________6.2________________6.3_____________________a    "                                 44 t  S   Other PATHWORKS Server Softwaren  C The following PATHWORKS server products cannot run on the same sys-S4 tem as PATHWORKS V6.1 for OpenVMS (Advanced Server):  F o  PATHWORKS V5.0 for OpenVMS (LAN Manager). You can upgrade the PATH-C    WORKS LAN Manager V5.0 server to PATHWORKS V6.1 for OpenVMS (Ad-aC    vanced Server). Running the PATHWORKS V6.1 for OpenVMS (Advanced D    Server) server on a system also running the PATHWORKS LAN ManagerC    V5.0 server is not possible or supported. You cannot continue touF    run the PATHWORKS LAN Manager software, once the PATHWORKS AdvancedE    Server software has been installed. PATHWORKS Advanced Server can-mE    not coexist on the same OpenVMS Cluster with PATHWORKS LAN Manager     V5.0 server.e  E o  PATHWORKS V6 for OpenVMS (Advanced Server). You can upgrade any ofnH    the previous PATHWORKS V6 for OpenVMS (Advanced Server) servers (V6.0G    through V6.0D) to PATHWORKS V6.1 for OpenVMS (Advanced Server). Run-sE    ning any of these earlier servers on a system that is also runningoC    the PATHWORKS V6.1 for OpenVMS (Advanced Server) is not possible F    or supported. Once the PATHWORKS V6.1 for OpenVMS (Advanced Server)D    has been installed, you cannot continue to run an earlier versionC    of the server. PATHWORKS V6.1 for OpenVMS (Advanced Server) can-sH    not coexist on the same OpenVMS Cluster with any of the earlier PATH-2    WORKS V6 for OpenVMS (Advanced Server) servers.  E PATHWORKS Advanced Server maintains down-level compatibility with LANtC Manager client and server software. LAN Manager users can add PATH-wC WORKS Advanced Server to an existing network and migrate to the neweC technology at their own pace. A PATHWORKS LAN Manager server can beoF upgraded to PATHWORKS Advanced Server technology or act as a BDC, mem-C ber server, or standalone server in a network in which the PDC is a D PATHWORKS Advanced Server or a Windows NT Server computer. PATHWORKSF Advanced Server can be deployed as a PDC in a network comprising otherC PATHWORKS Advanced Servers, Windows NT Servers, PATHWORKS for Open- G VMS (LAN Manager) servers, or LAN Manager for OS/2 servers. It can alsoKE act as a BDC for other PATHWORKS Advanced Server or Windows NT Servere      "                                 45 s  i  D computers. In addition, the Advanced Server can act as a BDC in Win-F dows 2000 mixed-mode domains, or as a member server in native-mode and  mixed-mode Windows 2000 domains.  $ Advanced Server for OpenVMS Software  D The Advanced Server for OpenVMS cannot run on the same system as theD PATHWORKS V6.1 for OpenVMS (Advanced Server). The PATHWORKS V6.1 forD OpenVMS (Advanced Server) cannot coexist on the same OpenVMS Cluster5 with any of the Advanced Server for OpenVMS products.f   Client Software   D The following versions of client software are supported for use with PATHWORKS Advanced Server:  1 o  Microsoft Windows NT workstation software V4.0    o  Microsoft Windows 2000l   o  Microsoft Windows 98M   o  Microsoft Windows 95S  ) o  Microsoft Windows for Workgroups V3.116  ) o  Compaq PATHWORKS 32 V7.2, SPD 56.33.xxc   GROWTH CONSIDERATIONSi  E The minimum hardware and software requirements for any future version C of this product may be different from the requirements for the cur-a
 rent version.s              "                                 46 v  s  C ___________________________________________________________________s  E Licensing and Ordering Information:  Advanced Server V7.3 for OpenVMS 0 and PATHWORKS V6.1 for OpenVMS (Advanced Server)   SOFTWARE LICENSING  C PATHWORKS V6.1 for OpenVMS (Advanced Server)[3] is licensed for use E in exactly the same way as the Advanced Server V7.3 for OpenVMS. EachtF product is purchased by licensing the clients or applications that useA 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[4] is referred to as a Client Access license (PAK Product Name:E PWLMXXXCA07.03). Though there is only one license sold for any clientcH using this Advanced 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)  ; A description of the two different licensing modes follows.l   o  Client-based licensing mode  D When a license for Advanced Server is used in client-based mode, theI right to use the server is assigned electronically to a particular clienttE or seat. Once the right is assigned, the client system can access allT   ____________________K  [3]Though  previously purchased licenses continue to be valid for use withiH   pre-V6.0 servers, only the new Client Access licenses can be purchased.   when adding new clients to existing systems.E   In particular, all the licenses listed in Table 6, Previous-VersionWD   Licenses That Qualify for Upgrade Licenses, are no longer sold butD   continue to be valid and grant the right to use the PATHWORKS V5.0%   for OpenVMS (LAN Manager) software.aG  [4] COM for OpenVMS users do not require a license to use the Advanced K   Server.  Only clients using the file and print servers require a license.   "                                 47 r  A  D systems that are running Advanced Server as well as all systems thatB are running any previous version of the file and print server. [5]  D This mode of licensing Advanced Server is typically used when a cus-D tomer has more than one server and in systems where clients normallyF 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-lG cessed, client-based licensing mode can be more economical than server-dE based mode. In addition, because a client with a client-based license D cannot be refused access to a server because of license limits, thisE mode also guarantees that a particular system will always have accessd to one or more servers.r  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.e   o  Server-based licensing mode  F When a license for Advanced Server [6] is used in server-based licens-C ing mode, any client can access the server and make as many connec-s2 tions to file services and print shares as needed.  E Server-based licensing works best in situations where all clients useFD or access only one server and there are enough licenses available onE each system for all clients to access their assigned server. (A "sys-b? tem" is defined as either a standalone system or a cluster.)[7]T   ____________________H  [5]In  client-based mode, the PAK associated with the Client Access li-H   cense works only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversE   that have been upgraded to a minimum of V5.0F. Earlier revisions ofm.   PATHWORKS V5.0x will not recognize this PAK.H  [6]In  server-based mode, the PAK associated with the Client Access li-H   cense works only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversE   that have been upgraded to a minimum of V5.0F. Earlier revisions ofA5   PATHWORKS V5.0x will not recognize or use this PAK.uG  [7]When  using server-based licenses to access file and print services H   in an OpenVMS Cluster environment, clients should connect to the clus-G   ter using the Advanced Server cluster alias, if this option is avail-.E   able.  Clients connecting in this way use one server-based license.PI   Clients connecting directly to specific cluster members use one server-PE   based license for each connection to a different cluster member.  ADH   client can map multiple drives and printers from a single server while&   using a single server-based license.  "                                 48 b  t  C The Advanced Server will allow up to "n" clients to access its ser-rC vices concurrently, where "n" is the total number of licenses beinggH used in server-based licensing mode. The server will not allow the "n+1"D client to access its services until one of the first "n" clients has disconnected from the server.   C Though a server can have only "n" licenses available, any number ofdD clients can potentially access that server. The restriction is basedE only on the total number of clients that can connect to the server at  the same 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, C the client will be denied access until one of the connected clientsM disconnects from all services.  F Customers can choose to operate in either client-based or server-basedF mode, or in a combination of both. They can change the licensing mode,D as their situation dictates, without contacting or notifying Compaq.  D Note that any portion of multiple licenses delivered in a single PAKD can be used in server-based mode, while the remainder can be used inG client-based mode. Because a PAK can legally be loaded on only one sys-eD tem, only the system on which the PAK is loaded can use the licenses in server-based mode.[8]  D For complete terms and conditions related to Client Access licenses,F refer to the back of your PAK for these licenses, or consult the Soft- ware Licensing Web site at:r  , http://www.compaq.com/products/software/info ____________________  D  [8]PAKs  must be loaded into a clusterwide, available LMF database.  "                                 49 h  o   ORDERING INFORMATION   General Informationt  D Unless otherwise noted, licenses related to each part number are de-C livered in a single PAK. Because each PAK can be loaded on only onerD 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 partAD numbers in Table 5, New License Part Numbers, to purchase the number# of Client Access licenses required.s  C ___________________________________________________________________a  C Table_5:_New_License_Part_Numbers__________________________________   C Part_Number___________Number_of_Licenses_per_PAK___________________x   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_________________________________________    Upgrade Licenses  C Customers with licenses for previous versions of the file and printaE server that support the LAN Manager protocol are eligible to purchasePC Upgrade licenses to Advanced Server V7.3 for OpenVMS. Combined withJC your original license, the Advanced Server Upgrade license provides D the right to use Advanced Server V7.3 for OpenVMS and PATHWORKS V6.1D for OpenVMS (Advanced Server). To be eligible to purchase an UpgradeE license, you must have proof-of-license for any version of one of theeE licenses shown in Table 6, Previous-Version Licenses That Qualify fore  "                                 50 o  a  G Upgrade Licenses. Table 7, Upgrade License Part Numbers, lists the part6# numbers for these Upgrade licenses.w  D Note: Advanced Server V7.2A for OpenVMS and Advanced Server V7.2 forF OpenVMS customers with a "right to new version contract" will be given a free upgrade license.e  C ___________________________________________________________________C  ? Table 6: Previous-Version Licenses That Qualify for Upgrade Li- C _________censes____________________________________________________A  C License_Name_____________________________________Part_Numbers______5  > PATHWORKS V5.x for DOS and Windows (LAN          QM-0TLAA-A[*] Manager) CCS> PATHWORKS V5.x for OS/2 (LAN Manager) CCS        QM-YFWAA-A[*]> PATHWORKS V5.0 (LAN Manager) FPA                 QM-2CLAA-A[*]> PATHWORKS V5.0 (LAN Manager) Designated          QM-2CLAA-A[*] Access> PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS     QM-A93AA-A[*]> PATHWORKS V5.0 for OpenVMS (LAN Manager) PC      QM-A93AA-A[*]
 Concurrent> PATHWORKS V6.1 for OpenVMS (Advanced Server)     QM-A93AA-A[*]
 Client Accesss> Advanced Server V7.2 for OpenVMS Client          QM-5SUAA-A[*] Access> Advanced Server V7.2A for OpenVMS Client         QM-5SUAA-A[*] AccessC ___________________________________________________________________i [*]Variable fieldlC ___________________________________________________________________u                "                                 51 n  o  C ___________________________________________________________________c  C Table_7:_Upgrade_License_Part_Numbers______________________________r  !                     Number of Li-aC Part_Number_________censes______________Number_of_Licenses_per_PAK_   3 QM-5SUAA-CA            1                Variable[1]-, QM-5SUAA-CB            1                   1, QM-5SUAA-CC           10                  10, QM-5SUAA-CD           25                  25, QM-5SUAA-CE           50                  50, QM-5SUAA-CF          100                 100, QM-5SUAA-CG          250                 250, QM-5SUAA-CH          500                 500, QM-5SUAA-CJ         1000                1000C ___________________________________________________________________.7 [1]Equals total quantity ordered as a single line item.aC ___________________________________________________________________r    Software Media and Documentation  D Software media and documentation are available in the following for- mats:        QA-A93AA-H8.7.3, CD-ROM media!    QA-A93AA-GZ, Documentation kit.  D In addition, Advanced Server V7.3 for OpenVMS and PATHWORKS V6.1 forD OpenVMS (Advanced Server) software and documentation are included in the following:  E    QA-03XAA-H8, OpenVMS Alpha Software Layered Products Library Pack-A    age  D PATHWORKS V6.1 for OpenVMS (Advanced Server) software and documenta-# tion are included in the following:   C    QA-5G88A-H8, OpenVMS VAX Software Layered Products Library Pack-T    age  "                                 52 i     E This information is valid at time of release. Please contact your lo-p6 cal Compaq office for the most up-to-date information.   SOFTWARE PRODUCT SERVICESo  D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   SOFTWARE WARRANTYn  F This software is provided by Compaq with a 90-day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.   "  2001 Compaq Computer Corporation  F Compaq, the Compaq logo, Alpha, AlphaStation, DECnet, DECnet-Plus, theI DIGITAL logo, MicroVAX, OpenVMS PATHWORKS, POLYCENTER, and VAX are trade- C marks of Compaq Information Technologies Group, L.P. Microsoft, MS-_E DOS, Windows, and Windows NT are trademarks of Microsoft Corporation. E Intel is a trademark of Intel Corporation. UNIX is a trademark of ThelF Open Group. All other product names mentioned herein may be trademarks of their respective companies.  F Confidential computer software. Valid license from Compaq required forC possession, use, or copying. Consistent with FAR 12.211 and 12.212,aH Commercial Computer Software, Computer Software Documentation, and Tech-C nical Data for Commercial Items are licensed to the U.S. Governments+ under vendor's standard commercial license.C  E Compaq shall not be liable for technical or editorial errors or omis-_D sions contained herein. The information in this document is providedC "as is" without warranty of any kind and is subject to change with- C out notice. The warranties for Compaq products are set forth in the_E express limited warranty statements accompanying such products. Noth-hF ing herein should be construed as constituting an additional warranty.        "                                 53