       $                               Compaq   Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq Advanced Server V7.2A            SPD 30.50.27 #                for OpenVMS          5                and Compaq PATHWORKS V6.0C for OpenVMS    INTRODUCTION  F This Software Product Description describes two separate products that' provide similar PC server capabilities:   . o  Compaq Advanced Server V7.2A for OpenVMS[R]  C Advanced Server V7.2A for OpenVMS requires OpenVMS Operating System  for Alpha[R] V7.2 or V7.2-1.  7 o  Compaq PATHWORKS V6.0C for OpenVMS (Advanced Server)   D PATHWORKS V6.0C for OpenVMS (Advanced Server) requires OpenVMS Oper-D ating System for Alpha and VAX[R] V6.2, V7.1, or V7.2 or OpenVMS Op-  erating System for Alpha V7.2-1.  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.2A for OpenVMS   7 o  Compaq PATHWORKS V6.0C for OpenVMS (Advanced Server)   . o  Software Licensing and Ordering Information  C                                                        October 1999   C                                                         AE-RD64D-TE        C ___________________________________________________________________   7 PRODUCT NAME:  Compaq Advanced Server V7.2A for OpenVMS    DESCRIPTION   D Compaq[R] Advanced Server for OpenVMS is an OpenVMS layered applica-D tion that provides networking functions that are compatible with theF Windows NT[R] Server - with additional features. Advanced Server soft-D ware is based on Windows NT Server source code from Microsoft[R] and AT&T[R].  G Advanced Server software is based on PATHWORKS V6 for OpenVMS (Advanced F Server) software - with new capabilities to support the Windows NT in-C tegration features introduced with OpenVMS Operating System for Al- C pha V7.2. These capabilities provide a tighter integration with the E OpenVMS Operating System V7.2 and include support for the ODS-5 based C Enhanced File Specifications - including long names and deep direc- F tories, support for the OpenVMS Registry (based on the Windows NT reg-E istry), and COM capabilities that deliver enhanced integration of the E Windows NT and OpenVMS environments. (The ODS-2 file system will con-  tinue to be supported.)   C As a server for workstations on a network, the Advanced Server pro- D vides file and print shares that enable a community of desktop usersC to share computing resources efficiently. Advanced Server can func- C tion as a simple file and print server for a small, isolated commu- F nity of users or as the foundation of a large network distributed over a wide geographical area.   F Advanced Server software lets DOS, Windows[R], Windows NT, Windows 95,F Windows 98, OS/2[R], and OpenVMS users share printers connected to Al-C pha computers or OpenVMS cluster systems - as well as network-based / printers such as LAT printers and PrintServers.             "                                  2       D Advanced Server represents the Windows NT Server systems technology.D It enhances the Windows NT Server functionality by incorporating Mi-D crosoft technology to deliver powerful features for network adminis-C tration and enhanced security. Advanced Server can operate indepen- E dently or in cooperation with systems running Windows NT Server soft-  ware.    FEATURES  E Advanced Server adds an additional dimension to general purpose Open- C VMS systems. In addition to providing traditional support for busi- C ness, scientific, and engineering applications, Advanced Server al- E lows an OpenVMS Operating System to appear to PC clients as a Windows 
 NT Server.  C The major features of the Advanced Server are described in the fol-  lowing sections.  
 File Services   C Advanced Server provides clients with a remote file system that ap- E pears as a transparent extension of the client system's local comput-  ing environment.  D Advanced Server file shares are based on Microsoft's Advanced Server* V3.0 SMB (Server Message Block) protocols.  I Each file stored in a file service is stored as an OpenVMS file in Record C Management Services (RMS) format. Three types of RMS file or record 1 formats are allowed and supported on each volume:    o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefined   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.   "                                  3       E Multiple clients can concurrently access files stored on the server's F disk through the file access modes and byte-range locking support pro- vided by Advanced Server.   C Advanced Server lets users share OpenVMS files. You can use discre- F tionary Windows NT access controls on each file and directory to spec-D ify the groups and users that can access files, to define the levelsE of access that each group or user is permitted, and to control audit- C ing supported by Windows NT-like security. Additional, optional se- = curity is provided by OpenVMS file and directory protections.    Print Shares  F Advanced Server software lets DOS, Windows[R], Windows NT, Windows 95,F Windows 98, OS/2[R], and OpenVMS users share printers connected to Al-C pha computers or OpenVMS cluster systems - as well as network-based E printers such as LAT printers and PrintServers. Print shares are sup- D ported in local area network (LAN) and wide area network (WAN) envi-F ronments. PC clients can print files from the DOS, OS/2, Windows, Win-E dows 95, Windows 98, and Windows NT 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 D for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer.   C Advanced Server supports the DECprint Supervisor for OpenVMS (DCPS) G product, which provides PostScript[R] and DEC ANSI printing to selected & industry-standard PostScript printers.  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 Ad-C vanced Server must be properly licensed. (For more information, see   the SOFTWARE LICENSING section.)    "                                  4       E Files are stored on the server in native OpenVMS RMS format. This al- E lows information stored by the PCs using Advanced Server to be shared D with traditional OpenVMS users. In addition, this feature allows in-) formation to be shared among all clients.    Network Transport Support   F Advanced Server for OpenVMS supports DECnet (Phase IV) and DECnet-PlusE (formerly known as DECnet/OSI) transport software as supported by the C OpenVMS Operating System V7.2. Advanced Server also supports TCP/IP D and NetBEUI network transport software. One or more transport stacks$ can work concurrently on the server.  D Both the TCP/IP and DECnet transports are sold as separate Compaq[R]F products (require a separate license). The TCP/IP product must include> a PATHWORKS IP driver (PWIP) to work with the Advanced Server.  E NetBEUI transport software is included with Advanced Server software. F Using NetBEUI transport software, clients can access the server in theD LAN for file and print shares. See the SOFTWARE REQUIREMENTS section8 for information on supported network transport software.   NetBIOS[TM] Interface Support   E Advanced Server supports the NetBIOS interface in DECnet, TCP/IP, and H NetBEUI networks. Advanced Server uses NetBIOS naming services and data-C gram services. However, a NetBIOS programming interface is not pro- H vided. NetBIOS interface support includes the support of multiple trans-9 port stacks on a single or different network controllers._  D NetBIOS support under TCP/IP includes both a p-node and a b-node RFCG 1001/1002 implementation. Therefore, the NetBIOS interface is supportedOG under TCP/IP in both LAN and WAN environments. The Advanced Server Con- G figuration Manager utility allows you to select one or both of the fol-e; lowing methods for NetBIOS name resolution for WAN support:    o  LMHosts filer  & o  Windows Internet Name Server (WINS)  "                                  5 a  g   Flexible Security Models  G As an option, the Advanced Server security model can implement the Win-AF dows NT security model with the OpenVMS security model. The server canC be configured to use the security implementation best suited to thet environment.                                                                    "                                  6 t  h  H o  In Advanced Server Only mode, only the Advanced Server security model    is enforced.s  F Advanced Server employs a user-level security model that provides pre-E cise control over access to shared resources, including disk devices, E directories, and printers. Control is based on a password assigned to E each user account and the specific access permissions defined for the 
 resources.  H Advanced Server incorporates enhanced features that provide a high levelF of control over user and resource permissions and auditing. These fea-D tures include support of discretionary access control permissions onF individual files, directories, and resources and complete auditing ca- pabilities.s  E Like Windows NT Servers, Advanced Server does not support share-level-7 security and operates in user-level security mode only.   D o  In the Advanced Server and OpenVMS security model, both the Open-H    VMS and Advanced Server security models are enforced. Advanced ServerD    for OpenVMS security is enhanced with OpenVMS security. Users whoC    require this additional security support can continue to protectl-    their resources based on OpenVMS security.t   Domain Support  E Advanced Server allows the network to be subdivided into domains (ad-aC ministrative groups of servers and clients). Advanced Server can berD a member of a single domain. Advanced Server can be a Primary DomainC Controller (PDC) or a Backup Domain Controller (BDC). Domains are anC convenient mechanism for controlling user access to the network and  for managing large networks.  I Advanced Server for UNIX[R], as well as any Windows NT compatible server, C can be part of the same domain with Advanced Server for OpenVMS andsC can be designated as either the Primary Domain Controller or Backup  Domain Controller.      "                                  7 m     C Advanced Server for OpenVMS provides support for wide area networksr+ using one or both of the following methods:e   o  LMHosts file,  C The presence of the LMHosts file on Advanced Server allows NetLogonuE services and security database replication over wide area TCP/IP con-sC figurations. This file contains a list of nodes from geographically E dispersed sites synchronized by the Primary Domain Controller and ac- G cessible to clients in the server's domain. However, use of the LMHoststD file for replication over extreme distances or in networks with slow' transmission speeds is not recommended.u  & o  WINS (Windows Internet Name Server)  E Support for WINS allows Advanced Server to act as a WINS client; thataD is, to use the name registration and resolution facilities availableC from a Microsoft WINS across routed wide area TCP/IP networks, thuspG enabling WAN support from WINS for domain functions, NetLogon services, " and security database replication.   Trust RelationshipsS  D Advanced Server supports trusts. Trust relationships can allow usersE from other domains to access resources in the local domain and/or lo- 6 cal domain users to access resources in other domains.   NetLogon Services   E A single domain-wide logon lets a user access resources on any servereA in a domain or on servers in other domains that trust the domain..  F The domain capabilities of Advanced Server make it possible for a userC to issue a single logon request to authenticate the user for accessiF to multiple servers in a network. The NetLogon service forces the val-C idation of users' logon requests. The logon server that processes a E request checks its copy of the domain-wide user accounts database for 8 the username and password supplied in the logon request.   Network Browser Services  D Advanced Server can act as a Master Browser in a Windows NT network.  "                                  8    t   TimeSource Servicesn  D DOS, Windows, and OS/2 clients can request date and time informationC from Advanced Server and set the local workstation date and time tos coincide with it.e   User Environment Managemente  E Logon scripts can be used to configure MS-DOS[R] and Windows worksta- E tion user environments by making network connections and starting ap- F plications. User profiles can make workstations easier to use, as well7 as controlling workstation access to network resources.    Server Management and Controlr  I Advanced Server can be managed from either the OpenVMS server or a client-E workstation, using one of the following server management interfaces:   C o  The Advanced Server ADMINISTER command line interface, which cantC    be accessed from a terminal or terminal emulator. It conforms toR    standard DCL command syntax.r  D o  Windows NT Server administration tools, which are included in theC    Advanced Server software kit to be installed on Windows NT work-nG    stations, Windows 95 workstations, Windows 98 workstations, and Win-oG    dows for Workgroups workstations. These tools, including Server Man-WE    ager, User Manager for Domains, and Event Viewer, allow you to ad-wE    minister Advanced Server and Windows NT Server computers from net-f    work clients.  C o  Windows NT Server tools, which are available as part of the Win-p    dows NT 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-D,    tive sessions, connections, and services.  C o  View context-sensitive online help that provides command syntax,u9    options, and qualifiers for each menu item and commands  "                                  9 s  o  C Advanced Server can be remotely administered from PATHWORKS and Mi-sE crosoft Windows client workstations. Advanced Server can also be man-rD aged remotely from Windows NT Server, Advanced Server, and PATHWORKS Advanced Server 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:  F o  The Advanced Server Configuration Manager utility (a character cell@    interface) to manage the local Advanced Server configuration.  E o  The License Manager (a character cell interface) to manage the Li-e    cense Server.  D o  The Advanced Server Parameter Management utility (PWRK$REGUTL) to*    manage server configuration parameters.  - Advanced Server Configuration Manager Utility   E The Advanced Server Configuration Manager utility is a character cellnE user interface that allows the user to set up and modify the server'saG configuration. For example, the user can configure the data cache size,uH the security model, the number of supported clients, the types of trans-C ports, the type of WAN capabilities, and more. Any adjustments thataD need to be made to the OpenVMS SYSGEN parameters to support the run-C ning of the server are automatically performed by the Configurations Manager utility.   Integrating with OpenVMS  G Advanced Server encompasses many features of the OpenVMS Operating Sys-pD tem, including OpenVMS clusters and symmetric multiprocessing. Open-C VMS cluster configurations provide failover availability and exten-.E sive resource capacities by integrating multiple OpenVMS systems thati, can be accessed using a single cluster name.  D Advanced Server includes support for a transport-independent clusterD alias NetBIOS name that allows multiple cluster members to appear asG a single server to the connecting clients. This support provides higherOF availability. The cluster alias name has a load-balancing feature that  "                                 10    s  F connects clients to the cluster member that is the least loaded at theE time the session is established. Advanced Server includes a high per-eE formance, cluster-wide distributed data cache that provides scalabil-r ity in a clustered environment.d  G Advanced Server can run on OpenVMS Operating System for Alpha V7.2 mem-lD bers of homogeneous or mixed architecture OpenVMS clusters. AdvancedE Server supports the use of ODS-2 disk volumes and ODS-5 disk volumes, D a feature of OpenVMS V7.2, for share and file access by clients. TheE new ODS-5 based Enhanced File Specifications provide support for longl names.  ( Integrating with External Authentication  C External authentication is an optional feature that allows users to E log on to the OpenVMS Operating System using their PATHWORKS AdvancedcF Server usernames and passwords. This feature is useful to OpenVMS sys-F tem managers who want to provide users with a single username and passE word combination for both OpenVMS login and PATHWORKS Advanced Server  network logon.  C For more information about external authentication for OpenVMS, re- D fer to the Software Product Description for OpenVMS Operating System! for Alpha and VAX (SPD 25.01.xx).,  ! Integrating with OpenVMS Securityc  F Advanced Server provides an extension to the Windows NT security modelF by supporting OpenVMS security enforcement as an optional enhancement.  ! Integrating with OpenVMS Registryp  F Advanced Server provides network users with access to the OpenVMS Reg-D istry. Advanced Server also stores its own configuration data in theC OpenVMS Registry. The server configuration parameters are automati-rE cally migrated from the LANMAN.INI file to the OpenVMS Registry, whenMD a PATHWORKS Advanced Server is upgraded to Advanced Server V7.2A forD OpenVMS. Advanced Server provides the PWRK$REGUTL utility for manag-G ing server configuration parameters in the OpenVMS Registry. The server   "                                 11 r  D  F parameters in the OpenVMS Registry can also be viewed and managed from# a Windows NT based registry editor.    Alerter Servicea  F Advanced Server includes an Alerter Service that sends automatic alertH messages to clients and users as specified in the Advanced Server Alert-0 Names parameter setting in the OpenVMS Registry.   Event Log ServiceC  D Event logs provide valuable information about server activities. TheE administrator can select from several event types and can select, forwC each, whether successful or unsuccessful attempts at specific oper- G ations are to generate event messages. Security event messages are gen-oF erated based on the audit policy specified for Advanced Server and for files and directories.   Replicator Service  C Windows NT Servers provide user data replication across domain con-hD 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.s   Installation Utilities  F Advanced Server is installed on the OpenVMS Operating System using theD standard VMSINSTAL procedure. An Installation Verification ProcedureD (IVP) is also included, which can be used to confirm that the server% software has been installed properly.b  E The installation procedure allows you to install Advanced Server with C the integrated license server or just the standalone license serverr& or the external authentication images.   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.uC This product is no longer supported, and licenses to use this prod-  uct are no longer sold.l  "                                 12 e  n  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.   YEAR 2000 Readye  C This product is Year 2000 Ready. Any code or bug fixes checked intoeF patch kits for PATHWORKS LAN Manager V5.0F1, PATHWORKS Advanced ServerD V6.0A and V6.0B, Advanced Server V7.2 and later versions of Advanced? Server are also reviewed and certified for Year 2000 readiness.v  E Year 2000 Ready is defined: "Year 2000 Ready" products are defined byrC Compaq as products capable of accurately processing, providing, andeE /or receiving date data from, into, and between the twentieth and theiG twenty-first centuries and the years 1999 and 2000, including leap year F calculations, when used in accordance with the associated product doc-F umentation and provided that all hardware, firmware, and software usedF in combination with such products properly exchange accurate date data with the products.  C For additional information, visit the Brand area on the Compaq YearnN 2000 Ready web site located at http://www.compaq.com/year2000/warranties.html.  C To ensure that this product is Year 2000 Ready, the following test-oD ing process/methods were used: An investigation team performed a re-E view of all source code for modules containing time-related and date-oC related data fields. These modules were identified and reviewed foroD Year 2000 readiness. Testing was performed on any functionality thatC had date and time dependencies during the following Year 2000 tran-W sitions:  ' o  December 31, 1999 to January 1, 2000s  ) o  February 28, 2000 to February 29, 2000   % o  February 29, 2000 to March 1, 2000   C The following functionality was tested to verify reliability and toe< correct results during the transitions mentioned previously:   o  Process and service startup  "                                 13 t  s  8 o  Domain controller synchronization and user validation   o  User account management   o  Timesource services   o  File and printt  ) o  Event and log file creation and accesss   o  License managemente  C To ensure that this product interoperates properly with other hard-aC ware and software, the following testing process/methods were used:oC During the File and Print testing, Microsoft Windows NT 4.0 and Mi-mD crosoft Windows 95 clients were used to test interoperability duringD the transitions. Microsoft DOS clients were used to verify the Time- source services.   License Management  E Advanced Server offers license management for Client Access licenses,dC which can be used in either client-based or server-based mode. (Seer  SOFTWARE LICENSING for details.)  C The license deliverables for Advanced Server are Product Authoriza-rD 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 ise= hosting Advanced Server or an Advanced Server license server.e  ( The two types of license management are:  E o  Client-based license management. Advanced Server provides a facil-dE    ity called Advanced Server license server that acts as a proxy fortF    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 Clientu0 Access licenses being used in client-based mode.  "                                 14    W  G The Advanced Server License Manager, which must be run on the same nodeeD as the license server, provides a user interface that allows the ad-D ministrator to monitor client-based license usage, to manage licenseH groups, to set alert levels, to set logging levels for licensing events,C to enable or disable the license server, and to revoke assigned li-uD censes. The Advanced Server License Manager is also used to preallo-E cate licenses to specific "groups" (including the special, predefinedO$ server-based group described later).  C Each LAN needs only one active Advanced Server license server. (ThetC license server provided with Advanced Server supports Client Access $ 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 byl Advanced Server.  F o  Server-based license management. Advanced Server also allows clientD    access based on the availability of Client Access licenses in theF    local LMF database being used in server-based mode. If a client re-F    questing access to the server fails to produce a valid client-basedE    license, the Advanced Server License Registrar software checks forrJ    the availability of a valid Client Access license being used in server-A    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: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-s,       tem will be used in server-based mode.  G    -  If the Advanced Server license server was configured for the sys- D       tem where Advanced Server is executing, then all Client AccessC       licenses loaded into the local LMF database will, by default,m#       be used in client-based mode.   "                                 15 d  c  G To allow some or all of these licenses to be used in server-based mode,tF use the Advanced Server License Manager to allocate a portion of thoseI licenses to the special, predefined "server-based group". Licenses avail-cH able in the server-based group will then be available for use in server- based mode.   D Note: Advanced Server allows you to simultaneously use Client AccessE licenses in both client-based and server-based mode. However, becausewE clients using Client Access licenses in client-based mode are alreadyfI licensed to use the server software, they never consume additional Clientn7 Access licenses allocated for use in server-based mode..  
 Compatibility   C Advanced Server maintains compatibility with LAN Manager client andeH server software. Advanced Server also maintains compatibility with PATH-$ WORKS for OpenVMS (Advanced Server).  2 A PATHWORKS V5.x for OpenVMS (LAN Manager) server:  ) o  Can be upgraded to Advanced Server.[1]e  E o  Can continue running PATHWORKS LAN Manager and act as a Backup Do-VC    main Controller, member server, or standalone server in a domainoF    where the Primary Domain Controller is an Advanced Server or a Win-    dows NT Server computer.t   HARDWARE REQUIREMENTSc  D The following systems, components, and peripherals are supported ex- cept as noted.   Processors Supported  C All Alpha processors supported by the OpenVMS Operating System V7.2e2 are also supported by Advanced Server for OpenVMS.   ____________________E  You  can upgrade PATHWORKS V5 for OpenVMS (LAN Manager) to PATHWORKStG   V6 for OpenVMS (Advanced Server), then upgrade PATHWORKS V6 for Open-d  =   VMS (Advanced Server) to Advanced Server V7.2A for OpenVMS.e  "                                 16 t  s   Memory Requirementsi  D Advanced Server requires a minimum of physical memory for proper in-C stallation, configuration, and execution of the software, dependinge on the processor type:  ' o  On Alpha systems, a minimum of 64 MB   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 onM the server.e  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%G of the system memory and CPU time are dedicated to the Advanced Server,u% even though some work might use less.f   OPTIONAL HARDWARE    PostScript Printersr  F Advanced Server supports all PostScript printers supported by DECprintD Supervisor for OpenVMS (DCPS) V1.7. Refer to SPD 44.15.xx for a com-I plete list of the DIGITAL PostScript printers and other PostScript print-e ers supported by DCPS.  C DIGITAL PostScript printers connected by serial lines or DECservers0= and printers attached directly to the Ethernet are supported.    Network Interface Controllersu  E Advanced Server supports the following Ethernet, FDDI, and Token Ringn network hardware devices:   G o  For the TCP/IP transport, Advanced Server supports the network hard-aF    ware devices supported by the specific TCP/IP product. Refer to theE    Software Product Description for DIGITAL TCP/IP Services for Open-s    VMS, (SPD 46.46.xx).u  "                                 17 t  a  . For other TCP/IP products, contact the vendor.  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see%    the SPD for the following product:r  =    -  Compaq DECnet-Plus V7.2 for OpenVMS Alpha, SPD 50.45.xxh  E o  For the NetBEUI transport, Advanced Server provides the same levelpC    of support for Ethernet and FDDI as the OpenVMS Operating Systeme=    for Alpha and VAX. For more information, see SPD 25.01.xx.i  A Note: Advanced Server does not support the DEFZA FDDI controller.    CLUSTER ENVIRONMENT   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)  E Advanced Server supports up to 31 server nodes in a cluster. In otherlF words, no more than 31 nodes in a cluster can run Advanced Server con-F currently. In a typical scenario, the server is run on only a few cen-E tral nodes - to exploit the cluster's shared disks and high-speed in-i terconnect environment.a  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 domainC member, whether it is acting as the Primary Domain Controller or as  a Backup Domain Controller.i   SOFTWARE REQUIREMENTSh   Operating System  4 o  OpenVMS Operating System for Alpha V7.2 or V7.2-1      "                                 18 r     C For minimum hardware requirements of the operating system, refer toeE the Software Product Description for OpenVMS Operating System for Al-G pha and VAX, SPD 25.01.xx.   Network Transport Software  C Advanced Server includes NetBEUI network transport software. DECnettG or TCP/IP network transport software might also be required by AdvanceddD Server, depending on the transport used by clients requiring connec-1 tions to the server, or for use of some features.r  B The following DECnet-Plus product is supported by Advanced Server:  6 o  Compaq DECnet-Plus V7.2 or V7.2-1 for OpenVMS Alpha  C When Advanced Server is to be used in a TCP/IP environment, OpenVMSrG based TCP/IP software is required. This software must be purchased sep-tA arately. The following TCP/IP transports support Advanced Server:i  4 o  DIGITAL TCP/IP Services for OpenVMS V5.0 or V5.0A  ; o  Process Software Corporation[TM] MultiNet[R] for OpenVMS.  6 o  Process Software Corporation TCPWARE[R] for OpenVMS   PATHWORKS Software  H Advanced Server for OpenVMS cannot run on the same system as other PATH-3 WORKS server products; specifically, this includes:m  C o  PATHWORKS V5.0 for OpenVMS (LAN Manager). Advanced Server cannoteF    be upgraded from the PATHWORKS LAN Manager V5.0 server. Running Ad-C    vanced Server on a system also running the PATHWORKS LAN ManageraC    V5.0 server is not possible or supported. You cannot continue tooF    run the PATHWORKS LAN Manager software, once the PATHWORKS AdvancedC    Server software has been installed. Advanced Server cannot coex-rF    ist on the same OpenVMS cluster with the PATHWORKS LAN Manager V5.0
    server.    "                                 19 s     E o  PATHWORKS V6.0C for OpenVMS (Advanced Server). Advanced Server canyD    be upgraded from PATHWORKS Advanced Server V6.0, V6.0A, V6.0B, orH    V6.0C. Running PATHWORKS Advanced Server V6.0, V6.0A, V6.0B, or V6.0CC    on a system also running Advanced Server is not possible or sup-aE    ported. You cannot continue to run PATHWORKS Advanced Server V6.0,oF    V6.0A, V6.0B, or V6.0C, once the Advanced Server V7.2A software hasC    been installed. Advanced Server cannot coexist on the same Open-ID    VMS cluster with PATHWORKS V6.0, V6.0A, V6.0B, or V6.0C for Open-    VMS (Advanced Server).e  C Advanced Server maintains down-level compatibility with LAN ManageraH client and server software. LAN Manager users can add an Advanced ServerE to an existing network and migrate to the new technology at their owncG pace. A PATHWORKS LAN Manager server can be upgraded to act as a Backup D Domain Controller, member server, or stand-alone server in a networkF in which the Primary Domain Controller is an Advanced Server or a Win- dows NT Server computer.  E The Advanced Server can be deployed as a Primary Domain Controller inrG a network comprising other Advanced Server servers, Windows NT Servers,dD PATHWORKS for OpenVMS (Advanced Server) servers, PATHWORKS for Open-G VMS (LAN Manager) servers, or LAN Manager for OS/2 Servers. It can alsoyF act as a Backup Domain Controller for other Advanced Server, PATHWORKS0 Advanced Server, or Windows NT Server computers.   Client Softwaree  D The following versions of client software are supported for use with PATHWORKS Advanced Server:  9 o  Microsoft Windows NT workstation software V3.5 or V4.0i   o  Microsoft Windows 95    o  Microsoft Windows 98n  ) o  Microsoft Windows for Workgroups V3.11   + o  DIGITAL PATHWORKS 32 V7.1A, SPD 56.33.xxn  4 o  PATHWORKS V6.0A for DOS and Windows, SPD 55.07.xx  "                                 20    e   GROWTH CONSIDERATIONSi  E The minimum hardware and software requirements for any future versionwC of this product may be different from the requirements for the cur- 
 rent version.e                                                                      "                                 21 v  s  C ___________________________________________________________________   C PRODUCT NAME:  Compaq PATHWORKS V6.0C for OpenVMS (Advanced Server)a   DESCRIPTION   C Compaq[TM] PATHWORKS[R] for OpenVMS (Advanced Server) is an OpenVMSAD layered application that provides networking functions that are com-D patible with the Windows NT Server - with additional features. PATH-D WORKS Advanced Server is based on Windows NT Server source code from Microsoft and AT&T[R].  D As a server for workstations on a network, PATHWORKS Advanced ServerG provides file and print shares that enable a community of desktop userssC to share computing resources efficiently. PATHWORKS Advanced Server D can function as a simple file and print server for a small, isolatedF community of users or as the foundation of a large network distributed over a wide geographical area.  D PATHWORKS Advanced Server software lets DOS, Windows[R], Windows NT,F Windows 95, Windows 98, OS/2[R], and OpenVMS users share printers con-E nected to VAX computers, Alpha computers, or OpenVMS cluster systems,rH as well as network-based printers such as LAT printers and PrintServers.  D PATHWORKS Advanced Server represents LAN Manager systems technology.D It enhances the LAN Manager functionality by incorporating MicrosoftF technology to deliver powerful features for network administration andF enhanced security. PATHWORKS Advanced Server can operate independentlyB or in cooperation with systems running Windows NT Server software.   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 AdvancedC Server allows an OpenVMS system to appear to LAN Manager clients asv a Windows NT Server.      "                                 22 H  W  D The major features of PATHWORKS Advanced Server are described in the following sections.   
 File Servicess  C PATHWORKS Advanced Server provides LAN Manager-based clients with atH remote file system that appears as a transparent extension of the client% system's local computing environment.i  G PATHWORKS Advanced Server file shares are based on Microsoft's Advancedt1 Server V3.0 SMB (Server Message Block) protocols.f  I Each file stored in a file service is stored as an OpenVMS file in RecorddC Management Services (RMS) format. Three types of RMS file or recordr1 formats are allowed and supported on each volume:w   o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefined   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-o7 ganization of a file written by the client application.r  D Multiple LAN Manager clients can concurrently access files stored onD the server's disk through the file access modes and byte-range lock-2 ing support provided by PATHWORKS Advanced Server.  E PATHWORKS Advanced Server lets users share OpenVMS files. You can use C discretionary access Windows NT controls on each file and directoryeD to specify the groups and users that can access files, to define theE levels of access that each group or user is permitted, and to control.D auditing supported by Windows NT-like security. Additional, optional? security is provided by OpenVMS file and directory protections.)   Print Shares  D PATHWORKS Advanced Server software lets DOS, Windows[R], Windows NT,F Windows 95, Windows 98, OS/2[R], and OpenVMS users share printers con-E nected to VAX computers, Alpha computers, or OpenVMS cluster systems,-  "                                 23 d  g  H as well as network-based printers such as LAT printers and PrintServers.D Print shares are supported in local area network (LAN) and wide areaD network (WAN) environments. PC clients can print files from the DOS,D OS/2, Windows, Windows 95, Windows 98, and Windows NT operating sys-% tems 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 andmC portrait-mode printing. Similarly, separate services can be created D for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer.g  D PATHWORKS Advanced Server supports the DECprint Supervisor for Open-D VMS (DCPS) product, which provides PostScript[R] and DEC ANSI print-6 ing to selected industry-standard PostScript printers.  3 Sharing of Network Resources by Heterogeneous Userst  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. (Ford6 more information, see the SOFTWARE LICENSING section.)  E Files are stored on the server in native OpenVMS RMS format. This al-nE lows information stored by the PCs using PATHWORKS Advanced Server toeC be shared with traditional OpenVMS users. In addition, this featurev2 allows information to be shared among all clients.   Network Transport Supporte  G PATHWORKS Advanced Server supports DECnet (Phase IV), DECnet-Plus (for- G merly known as DECnet/OSI), TCP/IP, and NetBEUI network transport soft-eG ware. One or more transport stacks can work concurrently on the server.p  G Both the TCP/IP and DECnet network transports are sold as separate Com-NF paq products (require a separate license). The TCP/IP product must in-E clude a PATHWORKS IP (PWIP) driver in order to work with the Advancedu Server.     "                                 24 o  o  E NetBEUI transport software is included with PATHWORKS Advanced ServernC software. Using NetBEUI transport software, LAN Manager clients caneE access the server in the LAN for file and print shares. See the SOFT-cE WARE REQUIREMENTS section for information on supported network trans-  port software.   NetBIOS[TM] Interface Support.  C PATHWORKS Advanced Server supports the NetBIOS interface in DECnet,fD TCP/IP, and NetBEUI networks. PATHWORKS Advanced Server uses NetBIOSE naming services and datagram services. However, a NetBIOS programmingmF interface is not provided. NetBIOS interface support includes the sup-G port of multiple transport stacks on a single or different network con-o	 trollers.c  D NetBIOS support under TCP/IP includes both a p-node and a b-node RFCG 1001/1002 implementation. Therefore, the NetBIOS interface is supported0E under TCP/IP in both LAN and WAN environments. The PATHWORKS AdvancedcE Server Configuration Manager utility allows you to select one or bothaE of the following methods for NetBIOS name resolution for WAN support:    o  LMHosts filed  & o  Windows Internet Name Server (WINS)   Flexible Security Models  E As an option, the PATHWORKS Advanced Server security model can imple-eC ment the Windows NT security model with the OpenVMS security model.mD The server can be configured to use the security implementation best suited to the environment.  H o  In Advanced Server Only mode, only the Advanced Server security model    is enforced.s  G PATHWORKS Advanced Server employs a user-level security model that pro-rE vides precise control over access to shared resources, including diskSF devices, directories, and printers. Control is based on a password as-C signed to each user account and the specific access permissions de-t fined for the resources.  "                                 25 r  r  E PATHWORKS Advanced Server incorporates enhanced features that provideoE a high level of control over user and resource permissions and audit- C ing. These features include support of discretionary access control D permissions on individual files, directories, and resources and com- plete auditing capabilities.  C Like Windows NT Servers, PATHWORKS Advanced Server does not supportIC share-level security and operates in user-level security mode only.   D o  In the PATHWORKS Advanced Server and OpenVMS security model, bothD    the OpenVMS and PATHWORKS Advanced Server security models are en-D    forced. PATHWORKS Advanced Server security is enhanced with Open-C    VMS security. Users who require this additional security support E    can continue to protect their resources based on OpenVMS security.    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-KF vanced Server can be a Primary Domain Controller (PDC) or a Backup Do-F main Controller (BDC). Domains are a convenient mechanism for control-@ ling user access to the network and for managing large networks.  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 (AdvancedfE Server) and can be designated as either the Primary Domain Controllere or Backup Domain Controller.  D PATHWORKS Advanced Server provides support for wide area domains us-) ing one or both of the following methods:    o  LMHosts filee  E The presence of the LMHosts file on the PATHWORKS Advanced Server al- G lows NetLogon services and security database replication over wide areaAC TCP/IP configurations. This file contains a list of nodes from geo-LC graphically dispersed sites synchronized by the Primary Domain Con-lF troller and accessible to clients in the server's domain. However, useE of the LMHosts file for replication over extreme distances or in net-e7 works with slow transmission speeds is not recommended.s  "                                 26    E  1 o  Windows Internet Naming Services (WINS) Serverl  C Support for WINS Servers allows PATHWORKS Advanced Server to act asiC a WINS client; that is, to use the name registration and resolutionlD facilities available from a Microsoft WINS Server across routed wideD area TCP/IP networks, thus enabling WAN support from WINS for domain@ functions, NetLogon services, and security database replication.   Trust Relationshipsc  F PATHWORKS Advanced Server supports trusts. Trust relationships can al-D low users from other domains to access resources in the local domain? and/or local domain users to access resources in other domains.l   NetLogon Servicesn  E A single domain-wide logon lets a user access resources on any serverAA in a domain or on servers in other domains that trust the domain.h  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 usermH for access to multiple servers in a network. The NetLogon service forcesC the validation of users' logon requests. The logon server that pro-tJ cesses a request checks its copy of the domain-wide user accounts database< for the username and password supplied in the logon request.   Network Browser Services  E PATHWORKS Advanced Server can act as a Master Browser in a Windows NTg network.   TimeSource Servicess  D DOS, Windows, and OS/2 clients can request date and time informationE from the PATHWORKS Advanced Server and set the local workstation dateA and time to coincide with it.e        "                                 27 n      User Environment Managementa  E Logon scripts can be used to configure MS-DOS[R] and Windows worksta-iE tion user environments by making network connections and starting ap-eF plications. User profiles can make workstations easier to use, as well7 as controlling workstation access to network resources.d   Server Management and Control   G PATHWORKS Advanced Server can be managed from either the OpenVMS serverNE or a client workstation, using one of the following server managemento interfaces:   E o  PATHWORKS Advanced Server ADMINISTER command line interface, which D    can be accessed from a terminal or terminal emulator. It conforms"    to standard DCL command syntax.  D o  Windows NT Server administration tools, which are included in theD    PATHWORKS Advanced Server software kit to be installed on WindowsE    NT workstations, Windows 95 workstations, Windows 98 workstations, I    and Windows for Workgroups workstations. These tools, including ServernD    Manager, User Manager for Domains, and Event Viewer, allow you toE    administer PATHWORKS Advanced Server and Windows NT Server comput-,    ers from network clients.  C o  Windows NT Server tools, which are available as part of the Win-g    dows NT 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-c,    tive sessions, connections, and services.  C o  View context-sensitive online help that provides command syntax,v9    options, and qualifiers for each menu item and commandr  E PATHWORKS Advanced Server can be remotely administered from PATHWORKSrD and Microsoft Windows client workstations. PATHWORKS Advanced ServerF can also be managed remotely from Windows NT Servers and PATHWORKS Ad- vanced Server systems.  "                                 28 g  T  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:A  C o  PATHWORKS Advanced Server Configuration Manager utility (a char- F    acter cell interface) to manage the local PATHWORKS Advanced Server    configuration.   C o  PATHWORKS License Manager (a character cell interface) to manageI     the PATHWORKS license server.  7 PATHWORKS Advanced Server Configuration Manager Utilityl  F The PATHWORKS Advanced Server Configuration Manager utility is a char-K acter cell interface that allows the user to set up and modify the server's G configuration. For example, the user can configure the data cache size,dH the security model, the number of supported clients, the types of trans-C ports, the type of WAN capabilities, and more. Any adjustments thateD need to be made to the OpenVMS SYSGEN parameters to support the run-C ning of the server are automatically performed by the ConfigurationA Manager utility.   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 andiE extensive resource capacities by integrating multiple OpenVMS systemse1 that can be accessed using a single cluster name.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 sup-C port provides higher availability. The PATHWORKS cluster alias namemF has a load-balancing feature that connects clients to the cluster mem-D ber that is the least loaded at the time the session is established.C PATHWORKS Advanced Server includes a high performance, cluster-widepC distributed data cache that provides scalability in a clustered en-d
 vironment.  "                                 29 y  p  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-iD 5 disk volumes, a feature of OpenVMS V7.2, for share and file accessE by clients. However, PATHWORKS V6.0C Advanced Server for OpenVMS does F not support the features of ODS-5 devices; instead, it treats the ODS- 5 device as an ODS-2 device.  ( Integrating with External Authentication  C External authentication is an optional feature that allows users to G log on to an OpenVMS system using their PATHWORKS Advanced Server user-.F names and passwords. This feature is useful to OpenVMS system managersC who want to provide users with a single username and pass word com- E bination for both OpenVMS login and PATHWORKS Advanced Server networke logon.  H Note that external authentication is supported on OpenVMS V7.1 or later.C If external authentication is being used in an OpenVMS Cluster, allmF cluster members should be configured to process OpenVMS logon requestsE for network users. If one or more members do not support external au-hD thentication, user logins might result in unpredictable behavior. ToG ensure that external authentication works properly on the cluster, eachi7 node in the cluster should be at OpenVMS V7.1 or later.s  C For more information about external authentication for OpenVMS, re- 7 fer to the Software Product Description (SPD 25.01.xx).   ! Integrating with OpenVMS SecurityH  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.O  "                                 30 a  e   Event Log Service   D Event logs provide valuable information about server activities. TheE administrator can select from several event types and can select, forrC each, whether successful or unsuccessful attempts at specific oper-oG ations are to generate event messages. Security event messages are gen-eE erated based on the audit policy specified for the PATHWORKS Advancedu% Server and for files and directories.o   Replicator Service  C Windows NT Servers provide user data replication across domain con- D trollers using the Replicator service. The Replicator service is notC provided on PATHWORKS Advanced Servers. Therefore, automatic repli-kE cation of user files and directories on PATHWORKS Advanced Servers is  not supported.   Installation Utilities  C PATHWORKS Advanced Server is installed on OpenVMS systems using thewD 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 AdvanceduD Server with the integrated license server or just the standalone li-F cense server, the external authentication images, or the Upgrade util- ity.   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.iC This product is no longer supported, and licenses to use this prod-  uct are no longer sold.g  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.  "                                 31 s      YEAR 2000 Readinesse  C This product is Year 2000 Ready. Any code or bug fixes checked intoeF patch kits for PATHWORKS LAN Manager V5.0F1, PATHWORKS Advanced ServerG V6.0A, and later versions of Advanced Server are also reviewed and cer-i tified for Year 2000 readiness.r  E Year 2000 Ready is defined: "Year 2000 Ready" products are defined byeC Compaq as products capable of accurately processing, providing, and E /or receiving date data from, into, and between the twentieth and theRG twenty-first centuries and the years 1999 and 2000, including leap yeariF calculations, when used in accordance with the associated product doc-F umentation and provided that all hardware, firmware, and software usedF in combination with such products properly exchange accurate date data with the products.  C For additional information, visit the Brand area on the Compaq YearaN 2000 Ready web site located at http://www.compaq.com/year2000/warranties.html.  C To ensure that this product is Year 2000 Ready, the following test-hD ing process/methods were used: An investigation team performed a re-E view of all source code for modules containing time-related and date-AC related data fields. These modules were identified and reviewed foreD Year 2000 readiness. Testing was performed on any functionality thatC had date and time dependencies during the following Year 2000 tran-e sitions:  ' o  December 31, 1999 to January 1, 2000o  ) o  February 28, 2000 to February 29, 2000   % o  February 29, 2000 to March 1, 2000t  C The following functionality was tested to verify reliability and tou< correct results during the transitions mentioned previously:   o  Process and service startup  8 o  Domain controller synchronization and user validation   o  User account management   o  Timesource services  "                                 32 n      o  File and print   ) o  Event and log file creation and access    o  License managementt  C To ensure that this product interoperates properly with other hard-eC ware and software, the following testing process/methods were used:,C During the File and Print testing, Microsoft Windows NT 4.0 and Mi- D crosoft Windows 95 clients were used to test interoperability duringD the transitions. Microsoft DOS clients were used to verify the Time- source services.   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.1 (See the SOFTWARE LICENSING section for details.)K  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 hostingl: 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 andeJ 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,nC to set alert levels, to set logging levels for licensing events, tofF enable or disable the license server, and to revoke assigned licenses.E The PATHWORKS License Manager is also used to preallocate licenses to   "                                 33 o  e  G specific "groups" (including the special, predefined server-based groupu described later).e  E Each LAN needs only one active PATHWORKS license server. (The LicensedE Server provided with PATHWORKS Advanced Server supports Client Accesss$ licenses for all supported clients.)  C The PATHWORKS License Registrar, which must be run on the same sys-bD tem as the file server, verifies the licenses for clients requestingG access to the server functions. Clients that can produce a valid ClientaF 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 valideH    client-based license, the PATHWORKS License Registrar software checksC    for the availability of a valid Client Access license being usedyC    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:d  E    -  If the PATHWORKS license server was not configured for the sys-tG       tem where PATHWORKS Advanced Server is executing, then all ClientsE       Access licenses loaded into the local LMF database on that sys-T,       tem will be used in server-based mode.  C    -  If the PATHWORKS license server was configured for the system C       where PATHWORKS Advanced Server is executing, then all ClientrE       Access licenses loaded into the local LMF database will, by de- *       fault, be used in client-based mode.  G To allow some or all of these licenses to be used in server-based mode,rD use the PATHWORKS License Manager to allocate a portion of those li-G censes to the special, predefined "server-based" group. Licenses avail-eH able in the server-based group will then be available for use in server- based mode.o  "                                 34    u  G Note: PATHWORKS Advanced Server allows you to simultaneously use ClienthD Access licenses in both client-based and server-based mode. However,E because clients using Client Access licenses in client-based mode areaC already licensed to use the server software, they never consume ad-lG ditional Client Access licenses allocated for use in server-based mode.   ! Accommodation of Retired Featuresc  F The following features of PATHWORKS V5.0 for OpenVMS (LAN Manager) are> not provided in PATHWORKS V6.0x for OpenVMS (Advanced Server):  D o  Standalone and member server roles. PATHWORKS Advanced Server can:    be configured as a Primary or Backup Domain Controller.  D o  FAT volumes. To continue to provide FAT volume access to clients,C    you must maintain the PATHWORKS LAN Manager server on a separateiD    system. Files held within shares on a FAT volume must be migratedF    to PATHWORKS LAN Manager shares before you upgrade to PATHWORKS Ad-    vanced Server.r  D o  Backward compatibility mode. This mode is used to ease the migra-C    tion from PATHWORKS V4.x to PATHWORKS LAN Manager. Make sure allgC    clients making use of this connection format are upgraded beforeA1    the installation of PATHWORKS Advanced Server.i  E o  Remote Boot service. If clients depend on remote booting, you must I    maintain the PATHWORKS LAN Manager server on a separate system. Trans-iE    fer this function to another server that supports Remote Boot ser-n    vice before the upgrade.o  D o  Share-level security. PATHWORKS Advanced Server manages access to-    all resources through user-level security.   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.  L o  PATHWORKS LAN Manager Net command line interface and ADMINISTER/PATHWORKSF    character cell interface. These features were replaced by the PATH-C    WORKS Advanced Server ADMINISTER command line interface. The AD-fD    MINISTER command line interface provides automatic translation ofE    a subset of Net commands that have ADMINISTER command equivalents.e  "                                 35 o  n  
 Compatibilityd  I PATHWORKS Advanced Server maintains compatibility with LAN Manager client G and server software. A PATHWORKS V5.0 for OpenVMS (LAN Manager) server:k  1 o  Can be upgraded to a PATHWORKS Advanced Server,  E o  Can continue running PATHWORKS LAN Manager and act as a Backup Do-aC    main Controller, member server, or standalone server in a domain2E    where the Primary Domain Controller is a PATHWORKS Advanced Serverq#    or a Windows NT Server computer.o   HARDWARE REQUIREMENTS   D The following systems, components, and peripherals are supported ex- cept as noted.   Processors Supported  F All VAX and Alpha processors supported by OpenVMS Operating System forH Alpha and VAX V6.2, V7.1, and V7.2 are also supported by PATHWORKS V6.0C8 for OpenVMS (Advanced Server), except for the following:   GPX II  A MicroVAX:   MicroVAX I, MicroVAX II, MicroVAX 2000, MicroVAX 3100l             Model 40 and lower  ? VAX:        VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAXo             11/782, VAX 11/785  A VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXsta-e*             tion 4000 VLC, VAXstation 8000   Memory Requirementsd  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   "                                 36    l  % o  On VAX systems, a minimum of 64 MBc  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 ona the server.m  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires an2D Alpha system with approximately 64 MB of memory. This means that 80%E of the system memory and CPU time are dedicated to PATHWORKS Advancede- Server, even though some work might use less.w   OPTIONAL HARDWAREs   PostScript Printersr  D PATHWORKS Advanced Server supports all PostScript printers supportedE by DECprint Supervisor for OpenVMS (DCPS) V1.7. Refer to SPD 44.15.xxuE for a complete list of the DIGITAL and other PostScript printers sup-m ported by DCPS.e  C DIGITAL PostScript printers connected by serial lines or DECserversn= and printers attached directly to the Ethernet are supported.e   Non-PostScript Printerss  D PATHWORKS Advanced Server also supports the following non-PostScript	 printers:a  . DIGITAL LA75 Companion          EPSON[R] FX850 Printery, DIGITAL LA210                   EPSON FX1050. DIGITAL LA324[TM]               IBM ProPrinter@ DIGITAL LJ250 Companion         NEC SilentWriter[R] II Model 290
 Color PrinterS DIGITAL LN03[TM] PLUSl    "                                 37 S  c   Network Interface Controllersl  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 theyE    network hardware devices supported by the specific TCP/IP product.eD    Refer to the Software Product Description for DIGITAL TCP/IP Ser-$    vices for OpenVMS (SPD 46.46.xx).  . For other TCP/IP products, contact the vendor.  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see'    the SPDs for the following products:i  G    -  Compaq DECnet-Plus V7.2 or V7.2-1 for OpenVMS Alpha, SPD 50.45.xx   E    -  Compaq DECnet-Plus V7.2 or V7.2-1 for OpenVMS VAX, SPD 25.03.xxe  J    -  Compaq DECnet for OpenVMS VAX and Alpha V7.2 or V7.2-1, SPD 48.48.xx  D o  For the NetBEUI transport, PATHWORKS Advanced Server provides theC    same level of support for Ethernet and FDDI as the OpenVMS Oper- 8    ating System. For more information, see SPD 25.01.xx.  D Note: PATHWORKS Advanced Server does not support the DEFZA FDDI con- troller.   CLUSTER ENVIRONMENTW  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)h  C PATHWORKS Advanced Server supports up to 31 server nodes in a clus- E ter. In other words, no more than 31 nodes in a cluster can run PATH-vE WORKS Advanced Server concurrently. In a typical scenario, the server D is run on only a few central nodes - to exploit the cluster's shared. disks and high-speed interconnect environment.  "                                 38    C  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-rD ter. In a PATHWORKS Advanced Server domain, the OpenVMS cluster rep-C resents a single domain member, whether it is acting as the Primaryl3 Domain Controller or as a Backup Domain Controller.s   SOFTWARE REQUIREMENTSa   Operating System  B o  OpenVMS Operating System for Alpha V6.2, V7.1, V7.2, and V7.2-1  8 o  OpenVMS Operating System for VAX V6.2, V7.1, and V7.2  C For minimum hardware requirements of the operating system, refer toaE the Software Product Description for OpenVMS Operating System for Al-d pha and VAX (SPD 25.01.xx).l   Network Transport Software  F PATHWORKS Advanced Server includes NetBEUI network transport software.E DECnet or TCP/IP network transport software might also be required bylE PATHWORKS Advanced Server, depending on the transport used by clients A requiring connections to the server, or for use of some features.   D The following DECnet and DECnet-Plus products are supported by PATH- WORKS Advanced Server:  > o  Compaq DECnet-Plus V7.1, V7.2, and V7.2-1 for OpenVMS Alpha  < o  Compaq DECnet-Plus V7.1, V7.2, and V7.2-1 for OpenVMS VAX  0 o  DECnet for OpenVMS VAX and Alpha V7.1 or V7.2  E When PATHWORKS Advanced Server is to be used in a TCP/IP environment,sE OpenVMS based TCP/IP software is required. This software must be pur- D chased separately. The following TCP/IP transports support PATHWORKS Advanced Server:  F o  DIGITAL TCP/IP Services for OpenVMS V4.2 for OpenVMS Operating Sys-    tem V6.2   "                                 39 d  o  F o  DIGITAL TCP/IP Services for OpenVMS V5.0 for OpenVMS Operating Sys-    tem V7.1a  E o  DIGITAL TCP/IP Services for OpenVMS V5.0 and V5.0A for OpenVMS Op- )    erating System V7.1, V7.2, and V7.2-1.T  ; o  Process Software Corporation[TM] MultiNet[R] for OpenVMSc  6 o  Process Software Corporation TCPWARE[R] for OpenVMS   Other PATHWORKS Server Software,  C The following PATHWORKS server products cannot run on the same sys- 5 tem as PATHWORKS V6.0C for OpenVMS (Advanced Server):t  F o  PATHWORKS V5.0 for OpenVMS (LAN Manager). PATHWORKS V6.0C for Open-D    VMS (Advanced Server) can be upgraded from the PATHWORKS LAN Man-G    ager V5.0 server. Running the PATHWORKS Advanced Server V6.0C serverSD    on a system also running the PATHWORKS LAN Manager V5.0 server isF    not possible or supported. You cannot continue to run the PATHWORKSD    LAN Manager software, once the PATHWORKS Advanced Server softwareF    has been installed. PATHWORKS Advanced Server cannot coexist on the?    same OpenVMS cluster with PATHWORKS LAN Manager V5.0 server.p  D o  PATHWORKS V6.0B for OpenVMS (Advanced Server). PATHWORKS AdvancedF    Server V6.0C can be upgraded from the V6.0, V6.0A, or V6.0B server.D    Running the V6.0, V6.0A, or V6.0B server on a system also runningE    the V6.0C server is not possible or supported. You cannot continuenC    to run the PATHWORKS Advanced Server V6.0, V6.0A, or V6.0B soft-sC    ware, once the PATHWORKS Advanced Server V6.0C software has been C    installed. PATHWORKS Advanced Server V6.0C cannot coexist on the G    same OpenVMS cluster with the PATHWORKS Advanced Server V6.0, V6.0A,i    or V6.0B.  E PATHWORKS Advanced Server maintains down-level compatibility with LANoC Manager client and server software. LAN Manager users can add PATH-lC WORKS Advanced Server to an existing network and migrate to the newdC technology at their own pace. A PATHWORKS LAN Manager server can berC upgraded to PATHWORKS Advanced Server technology or act as a BackupgD Domain Controller, member server, or stand-alone server in a networkE in which the Primary Domain Controller is a PATHWORKS Advanced Server   "                                 40 n  o  E or a Windows NT Server computer. PATHWORKS Advanced Server can be de-OC ployed as a Primary Domain Controller in a network comprising otherEC PATHWORKS Advanced Servers, Windows NT Servers, PATHWORKS for Open-aG VMS (LAN Manager) servers, or LAN Manager for OS/2 Servers. It can alsolE act as a Backup Domain Controller for other PATHWORKS Advanced Server  or Windows NT Server computers.p   Client SoftwareV  D The following versions of client software are supported for use with PATHWORKS Advanced Server:  9 o  Microsoft Windows NT workstation software V3.5 or V4.0    o  Microsoft Windows 95    o  Microsoft Windows 98   ) o  Microsoft Windows for Workgroups V3.11   + o  DIGITAL PATHWORKS 32 V7.1A, SPD 56.33.xxi  4 o  PATHWORKS V6.0A for DOS and Windows, SPD 55.07.xx   GROWTH CONSIDERATIONSe  E The minimum hardware and software requirements for any future versionsC of this product may be different from the requirements for the cur-f
 rent version.d                      "                                 41 m  m  C ___________________________________________________________________   D Licensing and Ordering Information:  Advanced Server V7.2A for Open-5 VMS and PATHWORKS V6.0C for OpenVMS (Advanced Server)    SOFTWARE LICENSING  J Advanced Server V7.2A for OpenVMS[2] is purchased by licensing the clientsD or applications that use the services provided by the product. There is no additional fee.e  F The license required for clients to use Advanced Server file and printH services[3] is referred to as a Client Access license (PAK Product Name:F PWLMXXXCA06.00 for V6.0C or PWLMXXXCA07.02 for either V6.0C or V7.2A).C Though there is only one license sold for any client using this Ad-e; vanced Server, this license can be used in one of two ways:L  2 o  Client-based mode (also known as per-seat mode)  F o  Server-based mode (also known as per-server or concurrent use mode)  H These two different licensing modes are described in the following text.  E o  Client-Based Licensing Mode. When a license for Advanced Server isAC    used in client-based licensing mode, the right to use the serverrF    is assigned electronically to a particular client or seat. Once the   ____________________F  PATHWORKS  V6.0C for OpenVMS (Advanced Server) is licensed for use inE   exactly the same way as Advanced Server V7.2A for OpenVMS (AdvancedAE   Server).  Though previously purchased licenses continue to be valid F   for use with pre-V6 servers, only the new Client Access licenses can;   be purchased when adding new clients to existing systems.   C In particular, all the licenses listed in Table 2, Previous VersionHG   Licenses Qualifying for Upgrade Licenses, are no longer sold but con-iE   tinue to be valid and grant the right to use the PATHWORKS V5.0 forA  !   OpenVMS (LAN Manager) software.oF  COM  for OpenVMS users will not require a license to use the AdvancedE   Server.  Only clients using the file and print servers will requiref     a license.  "                                 42 c  a  C    right is assigned, the client system can access all systems run-TC    ning Advanced Server as well as all systems running any previousp,    version of the file and print server. [4]  C This mode of licensing Advanced Server is normally used when a cus- E tomer has more than one server and where clients normally access more2E than one server at the same time. Because only one license per clientaJ is required regardless of how many servers are being accessed, the client-D based licensing mode can be more economical in these situations when0 compared to server-based mode (described later).  E Because a client with a client-based license cannot be refused accessKF to a server due to license limits, this mode of licensing is also use-C ful when you need to guarantee that a particular system will alwaysi# have access to one or more servers.P  H Note: To use this licensing mode, a small licensing agent must be loadedF and enabled on each licensed client. The code for this licensing agentF is distributed with the Advanced Server, is available free on the Web,1 and is also available on CD-ROM at a nominal fee.x  F o  Server-based licensing mode. When a license for Advanced Server [5]E    is used in server-based licensing mode, any client can then accessKE    the server and make as many connections to file services and printn    shares as needed.       ____________________I  The  PAK associated with the Client Access license will work, in client-.H   based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversH   that have been upgraded to a minimum of V5.0F. Prior revisions of this  -   product will not recognize or use this PAK.AI  The  PAK associated with the Client Access license will work, in server-hH   based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversH   that have been upgraded to a minimum of V5.0F. Prior revisions of this  :   product will not recognize or use this PAK in this mode.  "                                 43 D  .  C The Advanced Server will allow up to "n" clients to access its ser-lC vices concurrently, where "n" is the total number of licenses beingaJ used in server-based licensing mode. The server will not allow the "n+1st"E client to access its services, until one of the first "n" clients hasr disconnected from the server.s  D Note: Though a server can have only "n" licenses available, any num-E ber of clients can potentially access that server. The restriction is2C based only on the total number of clients that might connect to thef server at one time.D  D For example, if you have 100 licenses assigned to an Advanced ServerD in server-based licensing mode, then any 100 clients can make use ofD all services offered by the Advanced Server at one time. However, ifC an additional client (the 101st) attempts to connect to the server, C the client will be denied access until one of the connected clients- disconnects from all services.  E Server-based licensing works best in situations where all clients use.D or access only one server and there are enough licenses available onD each system for all clients to access their assigned server. A "sys-> tem" is defined as either a standalone system or a cluster.[6]  D Note: Customers can choose which mode to use or to use a combinationE of both modes. They can change the licensing mode, as their situatione1 dictates, without contacting or notifying Compaq.P   ____________________D  When  using server-based licenses for access to file and print ser-D   vices in an OpenVMS cluster environment, clients should connect toE   the cluster using the Advanced Server cluster alias, if this optionAG   is available.  Clients connecting using the alias consume one server-AF   based license.  Clients connecting directly to specific cluster mem-E   bers consume one server-based license for each connection to a dif-d   ferent cluster member.  H A client can map multiple drives and printers from a single server while  *   consuming a single server-based license.  "                                 44 e  S  C Note also that any portion of multiple licenses delivered in a sin- D gle PAK can be used in server-based mode, while the remainder can beF used in client-based mode. Because a PAK can be legally loaded on onlyF one system, it is only the system where the PAK is loaded that can use% the licenses in server-based mode.[7]   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:T  . http://www.digital.com/info/software-licensing   ORDERING INFORMATION   General Informationv  D Unless otherwise noted, licenses related to each part number will beE delivered in a single PAK. Because each PAK can be loaded on only 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 parteC numbers in Table 1 to purchase the number of Client Access licenses E required. When ordering, note that licenses related to each part num- C ber will be delivered in a single PAK and any one PAK can be loadede on only one system               ____________________  B  PAKs  must be loaded into a cluster-wide, available LMF database.    "                                 45 N  n  C ___________________________________________________________________B  C Table_1:_New_License_Part_Numbers__________________________________s  C Part_Number___________Number_of_Licenses_per_PAK___________________    QM-5SUAA-AB              1 QM-5SUAA-AC             10 QM-5SUAA-AD             25 QM-5SUAA-AE             50 QM-5SUAA-AF            100 QM-5SUAA-AG            250 QM-5SUAA-AH            500C QM-5SUAA-AJ___________1000_________________________________________,   Upgrade Licenses  C Customers with licenses for previous versions of the file and printIC server supporting the LAN Manager protocol are eligible to purchase D Upgrade licenses to Advanced Server V7.2A for OpenVMS. Combined withC your original license, the Advanced Server Upgrade license provides F the right to use Advanced Server V7.2A for OpenVMS and PATHWORKS V6.0CD for OpenVMS (Advanced Server). To be eligible to purchase an UpgradeE license, you must have proof-of-license for any version of one of theeC licenses shown in Table 2. Table 3 lists the part numbers for thesei Upgrade licenses.n                            "                                 46       C ___________________________________________________________________n  C Table_2:_Previous_Version_Licenses_Qualifying_for_Upgrade_Licenses_   C License_Name__________________________________________Part_Numbers_   ? PATHWORKS V5.x for DOS and Windows (LAN Manager)      QM-0TLAA-e: CCS                                                   A[*]? PATHWORKS V5.x for OS/2 (LAN Manager) CCS             QM-YFWAA- :                                                       A[*]? PATHWORKS V5.0 (LAN Manager) FPA                      QM-2CLAA-f:                                                       A[*]? PATHWORKS V5.0 (LAN Manager) Designated Access        QM-2CLAA-v:                                                       A[*]? PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS          QM-A93AA-l:                                                       A[*]? PATHWORKS V5.0 for OpenVMS (LAN Manager) PC Con-      QM-A93AA-c: current                                               A[*]? PATHWORKS V6.0 for OpenVMS (Advanced Server)          QM-A93AA-o: Client Access                                         A[*]C ___________________________________________________________________s [*]Variable fieldnC ___________________________________________________________________                                   "                                 47    u  C ___________________________________________________________________p  C Table_3:_Upgrade_License_Part_Numbers______________________________e  !                     Number of Li-vC Part_Number_________censes______________Number_of_Licenses_per_PAK_   3 QM-5SUAA-CA            1                Variable[1]a, 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 ___________________________________________________________________a6 [1]Equals total quantity ordered as a single line itemC ___________________________________________________________________     Software Media and Documentation  ? Software media and documentation are available in the followinga formats:      QA-A93AA-H8, CD-ROM media!    QA-A93AA-GZ, Documentation kit-  B In addition, Advanced Server V7.2A for OpenVMS and PATHWORKS V6.0C@ for OpenVMS (Advanced Server) software and documentation are in- cluded in the following:  ?    QA-03XAA-H8, OpenVMS Alpha Software Layered Products Libraryd
    Package  @ PATHWORKS V6.0C for OpenVMS (Advanced Server) software and docu-( mentation are included in the following:  =    QA-5G88A-H8, OpenVMS VAX Software Layered Products Libraryh
    Package  "                                 48 e  r  A This information is valid at time of release. Please contact your 8 local Compaq office for the most up-to-date information.   SOFTWARE PRODUCT SERVICES_  @ A variety of service options are available from Compaq. For more. information, contact your local Compaq office.   SOFTWARE WARRANTYe  = This software is provided by Compaq with a 90-day conformancem@ warranty in accordance with the Compaq warranty terms applicable to the license purchase.  B [R]  Compaq, the Compaq logo, DIGITAL, OpenVMS, PATHWORKS, and VAX<      are registered in the U.S. Patent and Trademark Office.A [R]  Macintosh is a registered trademarks of Apple Computer, Inc.r= [R]  AT&T is a registered trademark of American Telephone andK      Telegraph Company. ; [R]  EPSON is a registered trademark of Epson America, Inc.lB [R]  IBM, OS/2, and ProPrinter are registered trademarks of Inter-,      national Business Machines Corporation.> [R]  Microsoft, MS-DOS, Windows, and Windows NT are registered)      trademarks of Microsoft Corporation.,A [R]  PostScript is a registered trademark of Adobe Systems Incor-v
      porated.h? [R]  SilentWriter is a registered trademark of NEC Corporation. < [R]  UNIX is a registered trademark of The Open Group in the'      United States and other countries.lA [TM] MultiNet, Process Software Corporation, and TCPWARE are reg-l8      istered trademarks of Process Software Corporation.6 [TM] SCO is a trademark of Santa Cruz Operations, Inc.; [TM] NetBIOS is a trademark of Micro Computer Systems, Inc.t  :  1999 Digital Equipment Corporation. All Rights Reserved.          "                                 49