      Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq Advanced Server V7.3A            SPD 30.50.32 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.3A for OpenVMS   D Advanced Server V7.3A for OpenVMS requires Compaq OpenVMS Alpha Ver- sion 7.2-2, 7.3, or 7.3-1.  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-2, 7.3, or 7.3-1, or OpenVMS VAX Version 6.2, 7.2,  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.3A for OpenVMS   6 o  Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server)  . o  Software Licensing and Ordering Information  C                                                      September 2002   C                                                         AE-RD64H-TE        C ___________________________________________________________________   7 PRODUCT NAME:  Compaq Advanced Server V7.3A for OpenVMS    DESCRIPTION   D Compaq Advanced Server for OpenVMS is an OpenVMS layered applicationD providing a network operating system that is compatible with the Mi-E crosoft networking technology. In particular, the Advanced Server for E OpenVMS is based on the Windows NT Server, but it provides additional C features. It enhances the Windows NT Server functionality by incor- G porating both OpenVMS and Microsoft technology to deliver powerful fea- C tures for network administration and enhanced security. It combines D the networking strengths and rich application set of Windows NT withH the proven availability, reliability, scalability, and security of Open-C VMS. The Advanced Server for OpenVMS can operate independently from D 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 D V6 for OpenVMS (Advanced Server) product to provide tighter integra-F tion with the OpenVMS operating system and the enhanced Windows NT in-= tegration features introduced with OpenVMS Alpha Version 7.2.   G Advanced Server for OpenVMS supports Extended File Specifications based E on OpenVMS ODS-5 disk volumes. The server product supports long names E and deep directories, certain Unicode or extended character-set char- D acters, the OpenVMS Registry (based on the Windows NT registry), COMG for OpenVMS, and other capabilities that integrate Windows NT and Open- D VMS 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, WindowsF NT, Windows 95, Windows 98, Windows 2000, Windows XP Professional, and< OpenVMS users can share files and printers over the network.      "                                  2       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, 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.  G The Advanced Server lets users share OpenVMS files. The Advanced Server E file shares are based on Microsoft's Advanced Server V3.0 SMB (Server E Message Block) protocols. You can use discretionary Windows NT access C controls on each file and directory to specify the groups and users E that can access files, to define the levels of access that each group F or user is permitted, and to control auditing supported by Windows NT-C like security. Additional, optional security is provided by OpenVMS  file and directory protections.   "                                  3       I Each file stored in a file service is stored as an OpenVMS file in Record G Management Services (RMS) format. Four types of RMS file or record for- . mats are allowed and supported on each volume:   o  Sequential stream   o  Sequential stream_LF   8 o  Sequential fixed-length record (512 bytes per record)   o  Sequential undefined   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 Multiple clients can concurrently access files stored on the server's F disk through the file-access modes and byte-range locking support pro-D vided by the Advanced Server. In addition, opportunistic locking al-E lows clients to lock files and cache data locally without risk of an- D other user changing the file; this provides performance improvementsC and reduces network traffic related to client/server communication.   F Note: The Advanced Server does not support concurrent simultaneous ac-E cess to files by OpenVMS processes and the Advanced Server processes.   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 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:   o  Extended File Specifications   "                                  4       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  F The Advanced Server for OpenVMS file server can now allow certain Uni-C code characters and extended character sets that are foreign to the C 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.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 OpenVMSC can enable you to configure the server to the local language of the G 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.     "                                  5        Print Shares  C The Advanced Server for OpenVMS software lets DOS, Windows, Windows F NT, Windows 95, Windows 98, Windows 2000, Windows XP Professional, andD OpenVMS users share printers connected to Alpha computers or OpenVMSF Cluster systems - as well as network-based printers such as LAT print-C ers and PrintServers. Print shares are supported in local area net- C work (LAN) and wide area network (WAN) environments. PC clients can C print files from their desktop operating systems as well as from PC 
 applications.   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 up  "                                  6       C    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.   E Before considering whether to take advantage of this feature, consult 5 the latest Advanced Server for OpenVMS Release Notes.   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 Transports  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-2, 7.3, and 7.3-1. 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.   "                                  7        NetBIOS Interface   E The Advanced Server supports the NetBIOS interface in TCP/IP, DECnet, F and NetBEUI networks, using multiple transport stacks on a single con-D troller or on different network controllers. However, a NetBIOS pro-# gramming interface is not provided.   D NetBIOS support under TCP/IP includes both a p-node and a b-node RFCF 1001/1002 implementation. Therefore, the NetBIOS interface can be usedG 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- 4 lowing methods for NetBIOS name resolution for WANs:   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.   E Note Advanced Server for OpenVMS supports dynamic purging and reload- H ing of the NetBIOS name cache, and the ability to display the name cacheH contents - similar to the NBSTAT capabilities provided on some Microsoft clients.   Flexible Security Models  F The Advanced Server allows you to choose one of two modes of security,+ depending on the needs of your environment:   "                                  8       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.  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 external authentication (al-D lowing OpenVMS users to log in at the OpenVMS prompt using their do-G main user name and password) and password synchronization between Open- C VMS and Advanced Server systems, and it supports user account lock-  out.   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- C ing large networks. The Advanced Server can be a member of a single   "                                  9       E domain. The Advanced Server can be a primary domain controller (PDC), 5 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- C VMS (LAN Manager) servers, or LAN Manager for OS/2 servers. It also F 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-C mode and mixed-mode domains, in accord with the limitations imposed 1 by Microsoft on Windows NT V4-compatible servers.   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:    o  LMHOSTS file   C The presence of the LMHOSTS file on Advanced Server allows NetLogon E services and security database replication over wide area TCP/IP con- C 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 speeds  is not recommended.   ' o  WINS (Windows Internet Name Service)   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- D works, thus enabling WAN support for domain functions, NetLogon ser-) vices, and security database replication.    o  DNS    "                                 10       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.    Trust Relationships   H The Advanced Server supports trusts. Trust relationships can allow usersC from other domains to access resources in the local domain, and al- = lows local domain users to access resources in other domains.    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.   C The domain capabilities of the Advanced Server make it possible for C a user to issue a single logon request to authenticate the user for D access to multiple servers in a network. The NetLogon service forcesC the validation of users' logon requests. The logon server that pro- I cesses a request checks its copy of the domainwide user accounts database = for the user name and password supplied in the logon request.    Network Browser Services  D The Advanced Server can act as a Master Browser in a Windows NT net- work.    TimeSource Services   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.    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- C cations. User profiles can make workstations easier to use, as well 3 as control workstation access to network resources.   "                                 11        Server Management and Control   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:   C o  The Advanced Server ADMINISTER command-line interface, which can C    be accessed from a terminal or terminal emulator. It conforms to     standard DCL command syntax.   D o  Windows NT server administration tools, which are included in theC    Advanced Server software kit to be installed on Windows NT, Win- F    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.  I o  Windows NT Server tools, which are available as part of the Windows NT 
    Server.  C o  Windows 2000 file and print server tools, which are available as #    part of the Windows 2000 Server.   , 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- +    tive sessions, connections, and services   C o  View context-sensitive online help that provides command syntax, 9    options, and qualifiers for each menu item and command   C The Advanced Server can be administered remotely from PATHWORKS and C Microsoft Windows client workstations. The Advanced Server can also F 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 server  management only and include:  "                                 12       F o  The Advanced Server Configuration Manager utility (a character cellG    interface) to manage local server configuration parameters that are, D    for the most part, directly or indirectly related to the environ-C    ment in which the server operates, such as the server's usage of D    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 of G    the Advanced Server but not, for the most part, file server resource     consumption.   E o  The License Manager (a character cell interface) to manage the Li-     cense Server.  # Windows 2000 and Windows XP Support    The Advanced Server supports:   C o  Windows 2000 and Windows XP Professional clients. For Windows XP <    Professional support, check with Compaq customer support.  C o  Windows 2000 domain controllers in a Windows 2000 mixed-mode do- G    main, when the Advanced Server is a backup domain controller or mem- F    ber server; Windows 2000 domain controllers in a pure (native) Win-A    dows 2000 domain, when the Advanced Server is a member server.   ' Integrating with Microsoft Environments   E The Advanced Server for OpenVMS provides numerous Windows NT integra- G tion features, including those provided on OpenVMS Alpha systems. These  features include:   E o  Extended File Specifications, based on ODS-5, with support of long     names and deep directories   1 o  Unicode characters and extended character sets   C o  Alias file names, generated automatically to provide compatibil- F    ity with legacy applications that only support file names that com-4    ply with the more limited MS-DOS name conventions  "                                 13        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 management of shared printers    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- 	    tocols   5 o  Connections from a wide variety of Windows clients    Integrating with OpenVMS  G Advanced Server encompasses many features of the OpenVMS operating sys- D tem, including OpenVMS Clusters and symmetric multiprocessing. Open-E VMS Cluster configurations provide load-balancing failover availabil- C ity and extensive resource capacities by integrating multiple Open- = VMS systems that can be accessed using a single cluster name.   F The Advanced Server includes support for a transport-independent clus-E ter alias NetBIOS name that allows multiple cluster members to appear I as a single server to the connecting clients. This provides higher avail- F ability. The cluster alias name has a load-balancing feature that con-C nects clients to the cluster member that is the least loaded at the E time the session is established. The Advanced Server includes a high- C performance, clusterwide distributed data cache that provides scal- # ability in a clustered environment.   C The Advanced Server supports the use of ODS-2 disk volumes and ODS- G 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.   "                                 14       D The Advanced Server for OpenVMS is installed using the OpenVMS POLY-C CENTER Software Installation utility. The Advanced Server for Open- 9 VMS uses the OpenVMS Registry to store server parameters.   ( Integrating with External Authentication  C External authentication is an optional feature that allows users to C log in to an OpenVMS system using their Advanced Server (domain se- F 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 network  logon.  C If external authentication is being used in an OpenVMS Cluster, all F cluster members should be configured to process OpenVMS logon requestsD for network users. You can set up external authentication support onH nodes that do not run Compaq OpenVMS file servers. In mixed-architectureD OpenVMS Clusters with the Advanced Server for OpenVMS running on theE Alpha members, the VAX members can still use external authentication. E For details about setting up external authentication in OpenVMS Clus- F ters, refer to the Advanced Server for OpenVMS Server Installation and Configuration Guide.  C For more information about external authentication for OpenVMS, re- F fer to the Software Product Description for OpenVMS Alpha and VAX (SPD
 25.01.xx).  ! Integrating with OpenVMS Security   D The Advanced Server provides an extension to the Windows NT securityC model by supporting OpenVMS security enforcement as an optional en- 
 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 the      "                                 15       D 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 viewed 4 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 Server 5 AlertNames parameter setting in the OpenVMS Registry.    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- G ations are to generate event messages. Security event messages are gen- F 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- D 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- C ing system using the POLYCENTER Software Installation utility. This 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.     "                                 16       D The Advanced Server for OpenVMS installation procedure gives you theG option of delaying a reboot indefinitely, such as when you need to con- 0 figure or change more settings before rebooting.   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired. C This product is no longer supported, and licenses to use this prod-  uct are no longer sold.   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- F 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 is A hosting the Advanced Server or an Advanced Server License Server.   ( 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.  I A single copy of the License Server software provides and verifies Client 0 Access licenses being used in client-based mode.  G The Advanced Server License Manager, which must be run on the same node D 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,  "                                 17       C to enable or disable the License Server, and to revoke assigned li- D 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. (The D License Server provided with the Advanced Server supports Client Ac-) cess licenses for all supported clients.)   D The Advanced Server License Registrar, which must be run on the sameE system as the file server, verifies the licenses for clients request- D ing access to the server functions. Clients that can produce a validC Client Access license are allowed access to the services offered by_ the Advanced Server.  C o  Server-based license management. The Advanced Server also allows D    client access based on the availability of Client Access licensesI    in the local LMF database being used in server-based mode. If a clientfC    requesting access to the server fails to produce a valid client-dG    based license, the Advanced Server License Registrar software checks C    for the availability of a valid Client Access license being used C    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:l  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-u,       tem will be used in server-based mode.  G    -  If the Advanced Server License Server was configured for the sys-CD       tem where Advanced Server is executing, then all Client AccessC       licenses loaded into the local LMF database will, by default,f#       be used in client-based mode.         "                                 18       G To allow some or all of these licenses to be used in server-based mode,_F 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.w  E Note: The Advanced Server allows you to simultaneously use Client Ac-tF cess licenses in both client-based and server-based mode. However, be-C cause clients using Client Access licenses in client-based mode arenC already licensed to use the server software, they never consume ad-nG ditional Client Access licenses allocated for use in server-based mode.   ' LAN Manager and PATHWORKS Compatibilitym  C The Advanced Server maintains compatibility with LAN Manager client C and server software. The Advanced Server also maintains compatibil- 1 ity with PATHWORKS for OpenVMS (Advanced Server).o  2 A PATHWORKS V5.x for OpenVMS (LAN Manager) server:  D o  Can be upgraded to an Advanced Server. (You can upgrade PATHWORKSG    V5 for OpenVMS (LAN Manager) to PATHWORKS V6.1 for OpenVMS (AdvancedaE    Server), then upgrade PATHWORKS V6.1 for OpenVMS (Advanced Server) )    to Advanced Server V7.3A for OpenVMS.)T  C o  Can continue running PATHWORKS for OpenVMS (LAN Manager) and act F    as a BDC, member server, or standalone server in a domain where the=    PDC is an Advanced Server or a Windows NT Server computer.n   HARDWARE REQUIREMENTSo  D The following systems, components, and peripherals are supported ex- cept as noted.   Processors Supported  F All Alpha processors supported by OpenVMS Version 7.2-2, 7.3, and 7.3-4 1 are also supported by Advanced Server for OpenVMS.    "                                 19 t  A   Memory RequirementsV  D The Advanced Server requires a minimum of physical memory for properC installation, configuration, and execution of the software, depend-c ing on the processor type:  ' o  On Alpha systems, a minimum of 64 MBg  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 ons the server.k  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires ancD Alpha system with approximately 64 MB of memory. This means that 80%F of the system memory and CPU time is dedicated to the Advanced Server,% even though some work might use less.    OPTIONAL HARDWAREi   PostScript Printersa  G The Advanced Server supports all PostScript printers supported by Open-lF VMS. Selected PostScript printers may need the DECprint Supervisor forC OpenVMS (DCPS) software to provide access through the OpenVMS queu-vD 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.T  C DIGITAL PostScript printers connected by serial lines or DECservers = and printers attached directly to the Ethernet are supported.g   Network Interface Controllersr  E Advanced Server supports the following Ethernet, FDDI, and Token Ringl network hardware devices:s  G o  For the TCP/IP transport, Advanced Server supports the network hard-rF    ware devices supported by the specific TCP/IP product. Refer to the  "                                 20 d  r  D    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-V    tact the vendor.s  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see%    the SPD for the following product:i  9    -  Compaq DECnet-Plus for OpenVMS Alpha (SPD 50.45.xx)e  E For information about what software versions of DECnet are supported,a see SOFTWARE REQUIREMENTS.  E o  For the NetBEUI transport, Advanced Server provides the same level D    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).   A Note: Advanced Server does not support the DEFZA FDDI controller.q   CLUSTER ENVIRONMENTq  D Advanced Server runs on members of OpenVMS Clusters. OpenVMS ClusterC configurations are fully described in the Software Product Descrip- 0 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-2, 7.3, or 7.3-1. Mixed-fD version clusters are supported if all cluster members upon which theD Advanced Server for OpenVMS runs are running OpenVMS Versions 7.2-2,C 7.3, or 7.3-1. The enhanced OpenVMS Registry components of Versions F 7.2-2, 7.3, and 7.3-1 are compatible with each other, but they are in-D compatible with the Registry components of earlier versions of Open-C VMS. Therefore, you cannot run Registry servers or clients (such as D the Advanced Server for OpenVMS) on both the earlier and later Open-F VMS systems at the same time. For more information, refer to the Open-> VMS Alpha release notes for the latest system you are running.    "                                 21 w     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. InOC a typical scenario, the server runs on only a few central nodes, toiD 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.l   SOFTWARE REQUIREMENTSS   Operating System  - o  OpenVMS Alpha Version 7.2-2, 7.3, or 7.3-1d  C For minimum hardware requirements of the operating system, refer toeJ 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/IPnG or DECnet network transport software might also be required by AdvanceduD Server, depending on the transport used by clients requiring connec-1 tions to the server, or for use of some features.a  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-pD arately. The following TCP/IP transports are compatible with the Ad- vanced Server:  F o  Compaq TCP/IP Services for OpenVMS. The versions supported for eachD    version of the OpenVMS operating system are indicated in Table 1,9    Compaq TCP/IP Services for OpenVMS Versions Supported.a  ; o  MultiNet for OpenVMS (from Process Software Corporation)h  . o  TCPware for OpenVMS (from Process Software)  "                                 22 o     D Note: Third-party TCP/IP products must include a PATHWORKS IP (PWIP)1 driver in order to work with the Advanced Server.e  C ___________________________________________________________________   C Table_1:_Compaq_TCP/IP_Services_for_OpenVMS_Versions_Supported_____p  # OpenVMS         TCP/IP Services forhC Version_________OpenVMS____________________________________________h   Alpha V7.3-1    V5.3   Alpha V7.3      V5.3 or V5.1  C Alpha_V7.2-2____V5.1_______________________________________________c  E The following DECnet products are compatible with the Advanced ServermC for OpenVMS. The versions supported for each version of the OpenVMStE operating system are indicated in Table 2, DECnet Versions Supported.p  ! o  Compaq DECnet-Plus for OpenVMSo   o  Compaq DECnet for OpenVMS  C ___________________________________________________________________i  C Table_2:_DECnet_Versions_Supported_________________________________                    DECnet, OpenVMS         for          DECnet-Plus forC Version_________OpenVMS______OpenVMS_______________________________w  " Alpha V7.3-1    7.3-1        7.3-1    Alpha V7.3      7.3          7.3  C Alpha_V7.2-2____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:   F o  PATHWORKS V5.0 for OpenVMS (LAN Manager). You can upgrade the PATH-D    WORKS V5.0 for OpenVMS (LAN Manager) server to PATHWORKS V6.1 for  "                                 23 s  n  C    OpenVMS (Advanced Server). Running the Advanced Server on a sys-iC    tem also running the PATHWORKS V5.0 for OpenVMS (LAN Manager) isPF    not possible or supported. You cannot continue to run the PATHWORKSE    for OpenVMS (LAN Manager) software, once the Advanced Server soft-ME    ware has been installed. The Advanced Server cannot coexist on theOD    same OpenVMS Cluster with the PATHWORKS for OpenVMS (LAN Manager)
    server.  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 OpenVMSHE    is not possible or supported. You cannot continue to run the PATH-gC    WORKS for OpenVMS (Advanced Server) once the Advanced Server foroE    OpenVMS software has been installed. The Advanced Server for Open-mD    VMS cannot coexist on the same OpenVMS Cluster with PATHWORKS for    OpenVMS (Advanced Server).   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 theirF own pace. A PATHWORKS for OpenVMS (LAN Manager) server can be upgradedD to act as a BDC, member server, or standalone server in a network inD which the PDC 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 (LANeE Manager) servers, or LAN Manager for OS/2 Servers. It can also act asoG a BDC for other Advanced Server for OpenVMS, PATHWORKS Advanced Server,s or Windows NT Server computers.t  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 andu mixed-mode domains.p          "                                 24 W  S   Client Softwares  D The following versions of client software are supported for use with Advanced Server for OpenVMS:  ' o  Windows NT workstation software V4.0e   o  Windows 2000R   o  Windows XP Professional  
 o  Windows 98r  
 o  Windows 95S   o  Windows for Workgroups V3.11a  5 o  Compaq PATHWORKS 32 Version 7.2 (see SPD 56.33.xx)    GROWTH CONSIDERATIONSS  E The minimum hardware and software requirements for any future versiongC of this product may be different from the requirements for the cur-u
 rent version.P                                "                                 25 w     C ___________________________________________________________________r  B PRODUCT NAME:  Compaq PATHWORKS V6.1 for OpenVMS (Advanced Server)   DESCRIPTIONr  G Compaq PATHWORKS for OpenVMS (Advanced Server), also known as the PATH-tD WORKS Advanced Server, is an OpenVMS layered application providing aC network operating system that is compatible with the Microsoft net-aJ working technology. In particular, PATHWORKS for OpenVMS (Advanced Server)G is based on the Windows NT Server, but it provides additional features.dE It enhances the Windows NT Server functionality by incorporating both F OpenVMS and Microsoft technology to deliver powerful features for net-C work administration and enhanced security. It combines the network- D ing strengths and rich application set of Windows NT with the provenD availability, reliability, scalability, and security of OpenVMS. TheD Advanced Server can operate independently or in cooperation with the Windows NT Server.  D As a server for workstations on a network, PATHWORKS Advanced ServerG provides file and print shares that enable a community of desktop users C to share computing resources efficiently. PATHWORKS Advanced ServerND 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-E dows 95, Windows 98, Windows 2000, Windows XP Professional, and Open-eE VMS users share printers connected to VAX computers, Alpha computers, E or OpenVMS Cluster systems, as well as network-based printers such asv 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.      "                                 26 I      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 NTr Server.s  D The major features of PATHWORKS Advanced Server are described in the following sections.n  
 File Servicesr  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.  C PATHWORKS Advanced Server lets users share OpenVMS files. PATHWORKSAD Advanced Server file shares are based on Microsoft's Advanced ServerD V3.0 SMB (Server Message Block) protocols. You can use discretionaryD access Windows NT controls on each file and directory to specify theC groups and users that can access files, to define the levels of ac-dG cess that each group or user is permitted, and to control auditing sup-rD ported by Windows NT-like security. Additional, optional security is3 provided by OpenVMS file and directory protections.o  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 records1 formats are allowed and supported on each volume:-   o  Sequential stream  8 o  Sequential fixed-length record (512 bytes per record)   o  Sequential undefinedi  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.s  "                                 27    u  E Multiple clients can concurrently access files stored on the server'scF disk through the file-access modes and byte-range locking support pro-# vided by PATHWORKS Advanced Server.   F Note: The Advanced Server does not support concurrent simultaneous ac-E cess to files by OpenVMS processes and the Advanced Server processes.aD To enable compatibility with legacy applications such as MS-DOS, the% Advanced Server automatically createssD 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.n   Print Shares  F PATHWORKS Advanced Server software lets DOS, Windows, Windows NT, Win-E dows 95, Windows 98, Windows 2000, Windows XP Professional, and Open-dE VMS users share printers connected to VAX computers, Alpha computers,tE or OpenVMS Cluster systems, as well as network-based printers such aseG LAT printers and PrintServers. Print shares are supported in local areaTF network (LAN) and wide area network (WAN) environments. PC clients canH print files from the DOS, Windows, Windows 95, Windows 98, Windows 2000,D Windows XP Professional, and Windows NT operating systems as well as from PC applications.o  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 createdSC 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 printingm2 to selected industry-standard PostScript printers.          "                                 28 r     3 Sharing of Network Resources by Heterogeneous Usersa  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. (ForH6 more information, 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 PATHWORKS Advanced Server todC be shared with traditional OpenVMS users. In addition, this featureo2 allows information to be shared among all clients.   Network Transports  E PATHWORKS Advanced Server supports TCP/IP, DECnet (Phase IV), DECnet-mH Plus (formerly known as DECnet/OSI), and NetBEUI network transport soft-G ware. One or more transport stacks can work concurrently on the server.h  G Both the TCP/IP and DECnet network transports are sold as separate Com-t+ paq products and require separate licenses.f  E NetBEUI transport software is included with PATHWORKS Advanced Server C software. Using NetBEUI transport software, LAN Manager clients canpG access the server in the LAN for file and print shares. NetBEUI is rec-cD ommended for use in small LAN-only environments of 50 nodes or less.C For information about supported network transport software, see theg section SOFTWARE REQUIREMENTS.   NetBIOS Interfacen  C PATHWORKS Advanced Server supports the NetBIOS interface in TCP/IP,aG DECnet, and NetBEUI networks, using multiple transport stacks on a sin-oC gle controller or on different network controllers. However, a Net-o+ BIOS programming interface is not provided.T  D NetBIOS support under TCP/IP includes both a p-node and a b-node RFCF 1001/1002 implementation. Therefore, the NetBIOS interface can be usedE under TCP/IP in both LAN and WAN environments. The PATHWORKS AdvancednE Server Configuration Manager utility allows you to select one or both > of the following methods for NetBIOS name resolution for WANs:  "                                 29 t  a   o  LMHOSTS filet  ' o  Windows Internet Name Service (WINS)n   o  DNS  C Note: Enabling DNS allows the server and clients to use a specifiednC 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 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, Versionr 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.m   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  E o  In Advanced Server Only mode, only the Advanced Server (Windows NTi,    Server style) security model is enforced.  C This mode is sufficient for most network environments. The AdvancedsE Server employs a user-level security model that provides precise con-nD 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. TheseDD features include support of discretionary access control permissionsC on individual files, directories, and resources and complete audit-v ing capabilities.p  E Like Windows NT Servers, Advanced Server does not support share-leveln7 security and operates in user-level security mode only.o  "                                 30 w  l  C o  In the Advanced Server and OpenVMS security mode, both the Open-r8    VMS and Advanced Server security models are enforced.  E Use of both security models is never necessary to control user accessdE 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- C vanced Server and OpenVMS security model results in the extra over- A head of validating both the Advanced Server and OpenVMS settings.a  F In addition, the Advanced Server supports external authentication (al-D lowing OpenVMS users to log in at the OpenVMS prompt using their do-G main user name and password) and password synchronization between Open- C VMS and Advanced Server systems, and it supports user account lock-  out.   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-bD 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-a ing large networks.   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-WC VMS (LAN Manager) servers, or LAN Manager for OS/2 servers. It alsomF 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-C mode and mixed-mode domains, in accord with the limitations imposedn1 by Microsoft on Windows NT V4-compatible servers.a  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 (Advancedu7 Server) and can be designated as either the PDC or BDC.o    "                                 31       D PATHWORKS Advanced Server provides support for wide area domains us-) ing one or both of the following methods:r   o  LMHOSTS fileo  E The presence of the LMHOSTS file on the PATHWORKS Advanced Server al- G lows NetLogon services and security database replication over wide arearC TCP/IP configurations. This file contains a list of nodes from geo-aE graphically dispersed sites synchronized by the PDC and accessible tosD clients in the server's domain. However, use of the LMHOSTS file forE replication over extreme distances or in networks with slow transmis-D sion speeds is not recommended.   ' o  WINS (Windows Internet Name Service)r  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-eD works, thus enabling WAN support for domain functions, NetLogon ser-) vices, and security database replication.o   o  DNS  C This allows the Advanced Server and clients to use a DNS server forbD 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.e   Trust Relationshipsa  F PATHWORKS Advanced Server supports trusts. Trust relationships can al-E low users from other domains to access resources in the local domain,sC and allows local domain users to access resources in other domains.    NetLogon Servicese  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.u    "                                 32 r  t  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- I cesses a request checks its copy of the domainwide user accounts database = for the user name and password supplied in the logon request.e   Network Browser Services  E PATHWORKS Advanced Server can act as a Master Browser in a Windows NTS network.   TimeSource Servicese  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.d   User Environment Managements  E Logon scripts can be used to configure MS-DOS and Windows workstationsC user environments by making network connections and starting appli-mC cations. User profiles can make workstations easier to use, as well 3 as control workstation access to network resources.V   Server Management and Control   G PATHWORKS Advanced Server can be managed from either the OpenVMS serverYE or a client workstation, using one of the following server management  interfaces:S  E o  PATHWORKS Advanced Server ADMINISTER command line interface, whichSD    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.iC    These tools, including Server Manager, User Manager for Domains,nF    and Event Viewer, allow you to administer PATHWORKS Advanced Server8    and Windows NT Server computers from network clients.  "                                 33 M  e  I o  Windows NT Server tools, which are available as part of the Windows NTS
    Server.  , Server management interfaces can be used to:  = o  Manage file and printer shares, user accounts, and groups.o  E o  Display and control server resources currently in use, such as ac- ,    tive sessions, connections, and services.  C o  View context-sensitive online help that provides command syntax,a:    options, and qualifiers for each menu item and command.  E PATHWORKS Advanced Server can be remotely administered from PATHWORKS D 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.s  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:   G o  The PATHWORKS Advanced Server Configuration Manager utility (a char-tD    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 benF    made to the OpenVMS SYSGEN parameters to support the running of theH    server are automatically performed by the Configuration Manager util-    ity.   E o  The PATHWORKS License Manager (a character-cell interface) to man-i$    age the PATHWORKS License Server.  # Windows 2000 and Windows XP Supportn   The Advanced Server supports:t  C o  Windows 2000 and Windows XP Professional clients. For Windows XPh/    support, check with Compaq software support.e  "                                 34 p  e  C o  Windows 2000 domain controllers in a Windows 2000 mixed-mode do-eG    main, when the Advanced Server is a backup domain controller or mem-iF    ber server; Windows 2000 domain controllers in a pure (native) Win-A    dows 2000 domain, when the Advanced Server is a member server.n  ' Integrating with Microsoft Environmentsp  F The Advanced Server provides numerous Windows NT integration features, such as:   o  Remote management from:  C    -  Network clients, using Windows NT server administration toolse7       that are provided for installation on the clientsl  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-yF    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  G o  Windows NT-compatible Server Message Block (SMB) file and print pro- 	    tocolsi  5 o  Connections from a wide variety of Windows clientsn   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 andaE extensive resource capacities by integrating multiple OpenVMS systems:1 that can be accessed using a single cluster name.d  "                                 35 A  n  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 pro-G vides higher availability. The PATHWORKS cluster alias name has a load-hE balancing feature that connects clients to the cluster member that is F the least loaded at the time the session is established. PATHWORKS Ad-G vanced Server includes a high-performance, clusterwide distributed datas; cache that provides scalability in a clustered environment.e  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-iE 5 disk volumes, a feature of OpenVMS Version 7.2 and later, for sharebD 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,l. 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 tohF 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-eE bination for both OpenVMS login and PATHWORKS Advanced Server networks logon.  C If external authentication is being used in an OpenVMS Cluster, allaF cluster members should be configured to process OpenVMS logon requestsE for network users. If one or more members do not support external au-dD thentication, user logins might result in unpredictable behavior. ToG ensure that external authentication works properly on the cluster, each.G node in the cluster should be at OpenVMS Alpha V7.2-2 or later or Open-  VMS VAX 7.2 or later.o  C For more information about external authentication for OpenVMS, re-rF fer to the Software Product Description for OpenVMS Alpha and VAX (SPD
 25.01.xx).      "                                 36 n     ! Integrating with OpenVMS Security   E PATHWORKS Advanced Server provides an extension to the Windows NT se-AF curity model by supporting OpenVMS security enforcement as an optional enhancement.   Alerter Service   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, forfC each, whether successful or unsuccessful attempts at specific oper-eG ations are to generate event messages. Security event messages are gen-nE erated based on the audit policy specified for the PATHWORKS Advancedt% 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 notC provided on PATHWORKS Advanced Servers. Therefore, automatic repli-oE cation of user files and directories on PATHWORKS Advanced Servers ist not supported.   Installation Utilities  C PATHWORKS Advanced Server is installed on OpenVMS systems using theeD 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.   C The installation procedure allows you to install PATHWORKS AdvancedPD Server with the integrated License Server or just the standalone Li-C cense Server, the external authentication images (except on OpenVMSo V6.2), or the Upgrade utility.  "                                 37 r  n   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired. C This product is no longer supported, and licenses to use this prod-  uct are no longer sold.m  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-  vanced Server.   License Management  E PATHWORKS Advanced Server offers license management for Client AccessoH 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 hosting': 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.  C A single copy of the PATHWORKS License Server software provides andiJ 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,xC to set alert levels, to set logging levels for licensing events, toPF enable or disable the License Server, and to revoke assigned licenses.E The PATHWORKS License Manager is also used to preallocate licenses tot  "                                 38    e  G specific "groups" (including the special, predefined server-based group, described later).e  E Each LAN needs only one active PATHWORKS License Server. (The LicensesE Server provided with PATHWORKS Advanced Server supports Client AccessC$ licenses for all supported clients.)  C The PATHWORKS License Registrar, which must be run on the same sys-oD tem as the file server, verifies the licenses for clients requestingG access to the server functions. Clients that can produce a valid ClientuF 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 validTH    client-based license, the PATHWORKS License Registrar software checksC    for the availability of a valid Client Access license being usedSC    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:x  E    -  If the PATHWORKS License Server was not configured for the sys-qG       tem where PATHWORKS Advanced Server is executing, then all ClientuE       Access licenses loaded into the local LMF database on that sys-a,       tem will be used in server-based mode.  C    -  If the PATHWORKS License Server was configured for the systemmC       where PATHWORKS Advanced Server is executing, then all ClientnE       Access licenses loaded into the local LMF database will, by de-l*       fault, be used in client-based mode.  G To allow some or all of these licenses to be used in server-based mode,eD 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.r  "                                 39 c  S  G Note: PATHWORKS Advanced Server allows you to simultaneously use ClientsD Access licenses in both client-based and server-based mode. However,E because clients using Client Access licenses in client-based mode are C already licensed to use the server software, they never consume ad-sG ditional Client Access licenses allocated for use in server-based mode.r  ! Accommodation of Retired Featureso  F The following features of PATHWORKS V5.0 for OpenVMS (LAN Manager) are= not provided in PATHWORKS V6.1 for OpenVMS (Advanced Server):a  C o  Standalone server role. PATHWORKS Advanced Server can be config-e(    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 for OpenVMS (LAN Manager) serverrF    on a separate system. Files held within shares on a FAT volume mustC    be migrated to PATHWORKS for OpenVMS (LAN Manager) shares before ,    you upgrade to PATHWORKS Advanced Server.  D o  Backward-compatibility mode. This mode is used to ease the migra-C    tion from PATHWORKS V4.x to PATHWORKS V5.0 for OpenVMS (LAN Man-.C    ager) . Make sure all clients making use of this connection for-II    mat are upgraded before the installation of PATHWORKS Advanced Server.m  E o  Remote Boot service. If clients depend on remote booting, you musteD    maintain the PATHWORKS for OpenVMS (LAN Manager) server on a sep-C    arate system. Transfer this function to another server that sup-v0    ports Remote Boot service before the upgrade.  D o  Share-level security. PATHWORKS Advanced Server manages access to-    all resources through user-level security.d  C o  LAN Manager and creator security mode. The server can be config-eF    ured for PATHWORKS Advanced Server Only security model or for PATH-4    WORKS Advanced Server and OpenVMS security model.  E o  PATHWORKS for OpenVMS (LAN Manager) Net command-line interface andiE    ADMINISTER/PATHWORKS character-cell interface. These features were D    replaced by the PATHWORKS Advanced Server ADMINISTER command-lineF    interface. The ADMINISTER command-line interface provides automatic  "                                 40 _  _  D    translation of a subset of Net commands that have ADMINISTER com-    mand equivalents.   LAN Manager Compatibility   I PATHWORKS Advanced Server maintains compatibility with LAN Manager client_G and server software. A PATHWORKS V5.0 for OpenVMS (LAN Manager) server:   2 o  Can be upgraded to a PATHWORKS Advanced Server.  C o  Can continue running PATHWORKS for OpenVMS (LAN Manager) and acthF    as a BDC, member server, or standalone server in a domain where theF    PDC is a PATHWORKS Advanced Server or a Windows NT Server computer.   HARDWARE REQUIREMENTSm  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-2, 7.3, and 7.3-1, and by OpenVMS VAX Version 6.2, 7.2, and 7.3,C are also supported by PATHWORKS V6.1 for OpenVMS (Advanced Server),_ except for the following:l   GPX II  A MicroVAX:   MicroVAX I, MicroVAX II, MicroVAX 2000, MicroVAX 31007             Model 40 and lower  ? VAX:        VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAXS             11/782, VAX 11/785  A VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXsta-i*             tion 4000 VLC, VAXstation 8000        "                                 41 W  S   Memory RequirementsM  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 MB)  % o  On VAX systems, a minimum of 64 MBa  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.n  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%E of the system memory and CPU time are dedicated to PATHWORKS Advancedc- Server, even though some work might use less.O   OPTIONAL HARDWAREe   PostScript Printersr  D PATHWORKS Advanced Server supports all PostScript printers supportedI by OpenVMS. Selected PostScript printers may optionally need the DECprintfD Supervisor for OpenVMS (DCPS) software to provide access through theE OpenVMS queuing system over TCP/IP or DECnet. Refer to the DCPS Soft-LG ware Product Description (SPD 44.15.xx) for a complete list of the DIG-i5 ITAL and other PostScript printers supported by DCPS.O  C DIGITAL PostScript printers connected by serial lines or DECserversm= and printers attached directly to the Ethernet are supported.D   Non-PostScript Printersa  D PATHWORKS Advanced Server also supports the following non-PostScript	 printers:e  "                                 42 o  p    + DIGITAL LA75 Companion          EPSON FX850o Printer , DIGITAL LA210                   EPSON FX1050. DIGITAL LA324                   IBM ProPrinter= DIGITAL LJ250 Companion         NEC SilentWriter II Model 290e
 Color PrinterP DIGITAL LN03 PLUSe   Network Interface Controllersu  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 the E    network hardware devices supported by the specific TCP/IP product.hC    Refer to the Software Product Description for Compaq TCP/IP Ser-dE    vices for OpenVMS (SPD 46.46.xx). For information on what software D    versions of Compaq TCP/IP for OpenVMS are supported, see the sec-G    tion SOFTWARE REQUIREMENTS. For information about other TCP/IP prod-     ucts, contact the vendor.  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)   7    -  Compaq DECnet-Plus for OpenVMS VAX (SPD 25.03.xx)   <    -  Compaq DECnet for OpenVMS VAX and Alpha (SPD 48.48.xx)  E For information about what software versions of DECnet are supported, & 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-iC    ating system. For more information, see the Software Product De-M6    scription for OpenVMS Alpha and VAX (SPD 25.01.xx).  D Note: PATHWORKS Advanced Server does not support the DEFZA FDDI con- troller.  "                                 43 h  i   CLUSTER ENVIRONMENTn  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-dE WORKS Advanced Server concurrently. In a typical scenario, the server C is run on only a few central nodes, to exploit the cluster's sharedn. 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,0 or a member server.i   SOFTWARE REQUIREMENTSr   Operating System  3 o  OpenVMS Alpha Version 6.2, 7.2-2, 7.3, and 7.3-1C  ( o  OpenVMS VAX Version 6.2, 7.2, and 7.3  C For minimum hardware requirements of the operating system, refer torJ 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 bypE PATHWORKS Advanced Server, depending on the transport used by clientswA requiring connections to the server, or for use of some features.         "                                 44 d  n  E When PATHWORKS Advanced Server is to be used in a TCP/IP environment,iE OpenVMS based TCP/IP software is required. This software must be pur- F chased separately. The following TCP/IP transports are compatible with the PATHWORKS Advanced Server:  & o  Compaq TCP/IP Services for OpenVMS.  E The versions supported for each version of the OpenVMS operating sys-AE tem are indicated in Table 3, Compaq TCP/IP Services for OpenVMS Ver-t sions Supported.  9 o  MultiNet for OpenVMS from Process Software Corporationi  8 o  TCPware for OpenVMS from Process Software Corporation  D Note: Third-party TCP/IP products must include a PATHWORKS IP (PWIP)1 driver in order to work with the Advanced Server.   C ___________________________________________________________________h  C Table_3:_Compaq_TCP/IP_Services_for_OpenVMS_Versions_Supported_____l  +                         TCP/IP Services forhC OpenVMS_Version_________OpenVMS____________________________________    Alpha V7.3-1            V5.3$ Alpha V7.3              V5.3 or V5.1 Alpha V7.2-2            5.1p Alpha V6.2              V4.2$ VAX V7.3                V5.3 or V5.1 VAX V7.2                5.1eC VAX_V6.2________________V4.2_______________________________________t  E The following DECnet and DECnet-Plus products are compatible with the E PATHWORKS Advanced Server. The versions supported for each version of F the OpenVMS operating system are indicated in Table 4, DECnet Versions
 Supported.  ! o  Compaq DECnet-Plus for OpenVMS   "                                 45 a  n   o  Compaq DECnet for OpenVMS  C ___________________________________________________________________e  C Table_4:_DECnet_Versions_Supported_________________________________r  :                         DECnet for         DECnet-Plus forC OpenVMS_Version_________OpenVMS____________OpenVMS_________________o  0 Alpha V7.3-1            7.3-1              7.3-1. Alpha V7.3              7.3                7.30 Alpha V7.2-2            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_____________________l   Other PATHWORKS Server Softwares  C The following PATHWORKS server products cannot run on the same sys-e4 tem as PATHWORKS V6.1 for OpenVMS (Advanced Server):  F o  PATHWORKS V5.0 for OpenVMS (LAN Manager). You can upgrade the PATH-D    WORKS V5.0 for OpenVMS (LAN Manager) server to PATHWORKS V6.1 forD    OpenVMS (Advanced Server). Running the PATHWORKS V6.1 for OpenVMSG    (Advanced Server) server on a system also running the PATHWORKS V5.0sE    for OpenVMS (LAN Manager) server is not possible or supported. You.G    cannot continue to run the PATHWORKS for OpenVMS (LAN Manager) soft-eH    ware, once the PATHWORKS Advanced Server software has been installed.E    PATHWORKS Advanced Server cannot coexist on the same OpenVMS Clus-W5    ter with PATHWORKS V5.0 for OpenVMS (LAN Manager).t  E o  PATHWORKS V6 for OpenVMS (Advanced Server). You can upgrade any ofeH    the previous PATHWORKS V6 for OpenVMS (Advanced Server) servers (V6.0G    through V6.0D) to PATHWORKS V6.1 for OpenVMS (Advanced Server). Run- E    ning any of these earlier servers on a system that is also runningrC    the PATHWORKS V6.1 for OpenVMS (Advanced Server) is not possiblefF    or supported. Once the PATHWORKS V6.1 for OpenVMS (Advanced Server)D    has been installed, you cannot continue to run an earlier version  "                                 46       C    of the server. PATHWORKS V6.1 for OpenVMS (Advanced Server) can-eH    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 LAN C Manager client and server software. LAN Manager users can add PATH-tC WORKS Advanced Server to an existing network and migrate to the newrC technology at their own pace. A PATHWORKS for OpenVMS (LAN Manager)eE server can be upgraded to PATHWORKS Advanced Server technology or actfC as a BDC, member server, or standalone server in a network in whichHG the PDC is a PATHWORKS Advanced Server or a Windows NT Server computer.(D PATHWORKS Advanced Server can be deployed as a PDC in a network com-C prising other PATHWORKS Advanced Servers, Windows NT Servers, PATH-hI WORKS for OpenVMS (LAN Manager) servers, or LAN Manager for OS/2 servers.tJ It can also act as a BDC for other PATHWORKS Advanced Server or Windows NTC Server computers. In addition, the Advanced Server can act as a BDC D in Windows 2000 mixed-mode domains, or as a member server in native-) mode and mixed-mode Windows 2000 domains.r  $ 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.    Client Softwares  D The following versions of client software are supported for use with PATHWORKS Advanced Server:  ' o  Windows NT workstation software V4.0    o  Windows 2000P   o  Windows XP Professional  
 o  Windows 981  
 o  Windows 95n  "                                 47    d   o  Windows for Workgroups V3.11e  ) o  Compaq PATHWORKS 32 V7.2, SPD 56.33.xxC   GROWTH CONSIDERATIONSi  E The minimum hardware and software requirements for any future versionSC of this product may be different from the requirements for the cur- 
 rent version.S                                                              "                                 48 a  c  C ___________________________________________________________________   D Licensing and Ordering Information:  Advanced Server V7.3A for Open-4 VMS and PATHWORKS V6.1 for OpenVMS (Advanced Server)   SOFTWARE LICENSING  E Both the the Advanced Server V7.3A for OpenVMS and PATHWORKS V6.1 for F OpenVMS (Advanced Server) products are licensed for use in exactly theC same way. Each product is purchased by licensing the clients or ap-IE plications that use the services provided by the product. There is nop additional fee.   F Though previously purchased licenses continue to be valid for use withF pre-V6.0 servers, only the new Client Access licenses can be purchased, when adding new clients to existing systems.  F The license required for clients to use Advanced Server file and printE services is referred to as a Client Access license (PAK Product Name:rF PWLMXXXCA07.03). (Note: COM for OpenVMS users do not require a licenseI to use the Advanced Server. Only clients using the file and print serverso require a license.)i  C Though there is only one license sold for any client using this Ad-c; vanced Server, this license can be used in one of two ways:t  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.    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 clientiE or seat. Once the right is assigned, the client system can access alloD systems that are running Advanced Server as well as all systems thatE are running any previous version of the file and print server. (Note: C In client-based mode, the PAK associated with the Client Access li-iF cense works only with PATHWORKS V5.0 for OpenVMS (LAN Manager) servers  "                                 49    n  C that have been upgraded to a minimum of V5.0F. Earlier revisions ofo- PATHWORKS V5.0x will not recognize this PAK.)   F Client-based licensing is typically used when a customer has more thanE one server and in systems where clients normally access more than oneeC server at the same time. Because only one license per client is re-iF quired regardless of how many servers are being accessed, client-basedD licensing mode can be more economical than server-based mode. In ad-F dition, because a client with a client-based license cannot be refusedD access to a server because of license limits, this mode also guaran-D tees that a particular system will always have access to one or more servers.  H Note: To use this licensing mode, a small licensing agent must be loadedF and enabled on each licensed client. The code for this licensing agentD is distributed with the Advanced Server and is also available on CD- ROM at a nominal fee.p   o  Server-based licensing mode  D When a license for Advanced Server is used in server-based licensingC mode, any client can access the server and make as many connectionsrC to file services and print shares as needed. (Note: In server-based G mode, the PAK associated with the Client Access license works only withSC PATHWORKS V5.0 for OpenVMS (LAN Manager) servers that have been up-eG graded to a minimum of V5.0F. Earlier revisions of PATHWORKS V5.0x will  not recognize or use this PAK.)s  E Server-based licensing works best in situations where all clients usedD or access only one server and there are enough licenses available onE each system for all clients to access their assigned server. (A "sys-o< tem" is defined as either a standalone system or a cluster.)  E (Note: When using server-based licenses to access file and print ser-sF vices in an OpenVMS Cluster environment, clients should connect to theI cluster using the Advanced Server cluster alias, if this option is avail- J able. Clients connecting in this way use one server-based license. ClientsD connecting directly to specific cluster members use one server-basedC license for each connection to a different cluster member. A client C can map multiple drives and printers from a single server while us-a# ing a single server-based license.)e  "                                 50 p  a  C The Advanced Server will allow up to "n" clients to access its ser- C vices concurrently, where "n" is the total number of licenses beingtH 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.K  C Though a server can have only "n" licenses available, any number ofgD clients can potentially access that server. The restriction is basedE only on the total number of clients that can connect to the server ats 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,lC the client will be denied access until one of the connected clientsd 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-vD tem, only the system on which the PAK is loaded can use the licensesD in server-based mode. (Note: PAKs must be loaded into a clusterwide, available LMF database.)  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:s  , http://www.compaq.com/products/software/info            "                                 51 c  s   ORDERING LICENSESa   General Information   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 oneaD 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 partrD numbers in Table 5, New License Part Numbers, to purchase the number# of Client Access licenses required.s  C ___________________________________________________________________   C Table_5:_New_License_Part_Numbers__________________________________e  C Part_Number___________Number_of_Licenses_per_PAK___________________e   QM-5SUAA-AB              1 QM-5SUAA-AC             10 QM-5SUAA-AD             25 QM-5SUAA-AE             50 QM-5SUAA-AF            100 QM-5SUAA-AG            250 QM-5SUAA-AH            500 QM-5SUAA-AJ           1000! QM-5SUAA-AK           Variable[1]hC ___________________________________________________________________ 7 [1]Equals total quantity ordered as a single line item.WC ___________________________________________________________________r   Upgrade Licenses  C Customers with licenses for previous versions of the file and printSE server that support the LAN Manager protocol are eligible to purchasetD Upgrade licenses to Advanced Server V7.3A for OpenVMS. Combined withC your original license, the Advanced Server Upgrade license provides E the right to use Advanced Server V7.3A for OpenVMS and PATHWORKS V6.1i  "                                 52       D for OpenVMS (Advanced Server). To be eligible to purchase an UpgradeE license, you must have proof-of-license for any version of one of the E licenses shown in Table 6, Previous-Version Licenses That Qualify forfG Upgrade Licenses. Table 7, Upgrade License Part Numbers, lists the partlI numbers for these Upgrade licenses. All the licenses listed are no longerPF sold but continue to be valid and grant the right to use the PATHWORKS) V5.0 for OpenVMS (LAN Manager) software.)h  C Note: Advanced Server V7.3 for OpenVMS and Advanced Server V7.2 foreF OpenVMS customers with a "right to new version contract" will be given a free upgrade license.s  C ___________________________________________________________________S  ? Table 6: Previous-Version Licenses That Qualify for Upgrade Li-cC _________censes____________________________________________________t  C License_Name_____________________________________Part_Numbers______n  > 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.x for OpenVMS (Advanced Server)     QM-A93AA-A[*]
 Client Accessi> Advanced Server V7.2x for OpenVMS Client         QM-5SUAA-A[*] AccessC ___________________________________________________________________e [*]Variable field C ___________________________________________________________________h          "                                 53 r  m  C ___________________________________________________________________i  C Table_7:_Upgrade_License_Part_Numbers______________________________   !                     Number of Li-eC Part_Number_________censes______________Number_of_Licenses_per_PAK_f  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 ___________________________________________________________________p7 [1]Equals total quantity ordered as a single line item.sC ___________________________________________________________________N    SOFTWARE MEDIA AND DOCUMENTATION  D Software media and documentation are available in the following for- mats:i      QA-A93AA-H8, CD-ROM media!    QA-A93AA-GZ, Documentation kitr  E In addition, Advanced Server V7.3A for OpenVMS and PATHWORKS V6.1 fornD 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  "                                 54 e  a  E This information is valid at time of release. Please contact your lo-c6 cal Compaq office for the most up-to-date information.   Service Licenses  D Service customers can order right-to-new version service licenses, aD media and documentation update service license, and a documentation- only update service license.  C o  Right-to-new version service licenses. Service customers can usesD    the part numbers listed in Table 8, Rights-to-New Version ServiceE    License Part Numbers, to order the indicated licenses granting theeC    right to use the latest version of the Advanced Server software.v  C ___________________________________________________________________   C Table_8:_Rights-to-New_Version_Service_License_Part_Numbers________n  !                     Number of Li-TC Part_Number_________censes______________Number_of_Licenses_per_PAK_t  , QT-5SUAA-TB            1                   1, QT-5SUAA-TC           10                  10, QT-5SUAA-TD           25                  25, QT-5SUAA-TE           50                  50, QT-5SUAA-TF          100                 100, QT-5SUAA-TG          250                 250, QT-5SUAA-TH          500                 5004 QT-5SUAA-TK            1                Variable [1]C ___________________________________________________________________A7 [1]Equals total quantity ordered as a single line item.uC ___________________________________________________________________r  C o  Media and documentation update service license. To order the up-sD    date service license for media and documentation, use part number    QT-A93AA-E8.h  F o  Documentation-only update service license. To order the update ser-D    vice license for documentation only, use part number QT-A93AA-KZ.  "                                 55    M   SOFTWARE PRODUCT SERVICESo  C A variety of service options are available including media and doc-tC umentation update service, rights-to-new-version service, and soft-.C ware telephone support and installation services. Ordering informa- E tion may vary depending on your geographical location. For specifics,o: contact your local sales office or account representative.   SOFTWARE WARRANTY   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.n  2  2002 Compaq Information Technologies Group, L.P.  E Compaq, the Compaq logo, Alpha, OpenVMS, Tru64, DECnet, VAX, VMS, andaI the DIGITAL logo are trademarks of Compaq Information Technologies Group,e( L.P. in the U.S. and/or other countries.  F Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft/ Corporation in the U.S. and/or other countries.sH Intel is a trademark of Intel Corporation in the U.S. and/or other coun- tries.D UNIX is a trademark of The Open Group in the U.S. and/or other coun- tries.  C All other product names mentioned herein may be trademarks of theirc respective companies.c  F Confidential computer software. Valid license from Compaq required forC possession, use, or copying. Consistent with FAR 12.211 and 12.212,eH Commercial Computer Software, Computer Software Documentation, and Tech-C nical Data for Commercial Items are licensed to the U.S. Governmento+ under vendor's standard commercial license.e          "                                 56 n  m  E Compaq shall not be liable for technical or editorial errors or omis-iD 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-OF ing herein should be construed as constituting an additional warranty.                                                                    "                                 57