       %                               DIGITAL    Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  DIGITAL PATHWORKS V6.0A for OpenVMS     SPD 30.50.24 6                (Advanced Server) and DIGITAL PATHWORKS/                V5.0F1 for OpenVMS (LAN Manager)    INTRODUCTION  F This Software Product Description describes two separate products that' provide similar PC server capabilities:   0 o  PATHWORKS V6.0A for OpenVMS (Advanced Server)  - o  PATHWORKS V5.0F1 for OpenVMS (LAN Manager)   E Though similar, these products are based on different versions of the ? LAN Manager protocol and require different versions of OpenVMS.   H o  PATHWORKS V6.0A for OpenVMS (Advanced Server) is based on the currentC    networking technology available with Microsoft[R] Windows NT[TM] C    Servers. It requires OpenVMS V7.1 and will run on any VAX[TM] or +    Alpha system that supports OpenVMS V7.1.   E o  PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is based on LAN Manager D    V2.2 technology from Microsoft and is supported on both Alpha and5    VAX servers running a variety of OpenVMS versions.   F Both products are distributed in one package, and one license is valid for both products.  ; This Software Product Description (SPD) has three sections:   0 o  PATHWORKS V6.0A for OpenVMS (Advanced Server)  - o  PATHWORKS V5.0F1 for OpenVMS (LAN Manager)   . o  Software Licensing and Ordering information  C                                                      September 1998   C                                                         AE-RD64A-TE        C ___________________________________________________________________   D PRODUCT NAME:  DIGITAL PATHWORKS V6.0A for OpenVMS (Advanced Server)   DESCRIPTION   B DIGITAL[TM] PATHWORKS[TM] for OpenVMS[TM] (Advanced Server) is an G OpenVMS layered application that provides networking functions that are B compatible with the Windows NT Server - with additional features. H PATHWORKS 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 users C 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.  B PATHWORKS Advanced Server represents the newest generation of LAN H Manager systems technology. It enhances the LAN Manager functionality byE incorporating the latest Microsoft technology to deliver powerful new D features for network administration and enhanced security. PATHWORKSH Advanced Server can operate independently or in cooperation with systems# running Windows NT Server software.    FEATURES  I PATHWORKS Advanced Server adds a new dimension to general purpose OpenVMS C systems. In addition to providing traditional support for business, C scientific, and engineering applications, PATHWORKS Advanced Server F allows an OpenVMS system to appear to LAN Manager clients as a Windows
 NT Server.  D The major features of PATHWORKS Advanced Server are described in the following sections.         "                                  2       
 File Services   C PATHWORKS Advanced Server provides LAN Manager-based clients with a H remote file system that appears as a transparent extension of the client% system's local computing environment.   G PATHWORKS Advanced Server file shares are based on Microsoft's Advanced 1 Server V3.0 SMB (Server Message Block) protocols.   I Each file stored in a file service is stored as an OpenVMS file in Record C Management Services (RMS) format. Three types of RMS file or record 1 formats are allowed and supported on each volume:    o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefined   @ Files stored in a file service are accessible to PC clients, to F OpenVMS users, and to applications that can interpret the content and 9 organization of a file written by the client application.   D Multiple LAN Manager clients can concurrently access files stored on? the server's disk through the file access modes and byte-range  6 locking support provided by PATHWORKS Advanced Server.  G PATHWORKS Advanced Server lets network users share local OpenVMS files. D You can use discretionary access controls on each file and directoryD 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 C auditing supported by Windows NT-like security. Additional security 6 is provided by OpenVMS file and directory protections.   Print Shares  D PATHWORKS Advanced Server software lets DOS, Windows[R], Windows NT,E Windows 95[R], OS/2[R], and OpenVMS users share printers connected to C VAX computers, Alpha computers, or OpenVMS cluster systems, as well P as network-based printers such as LAT[TM] printers and DIGITAL PrintServers[TM].D Print shares are supported in local area network (LAN) and wide areaD network (WAN) environments. PC clients can print files from the DOS,  "                                  3       C OS/2, Windows, Windows 95, and Windows NT operating systems as well  as from PC applications.  G Multiple print shares can be defined for a single printer. For example, @ separate services can be created for landscape-mode printing andC portrait-mode printing. Similarly, separate services can be created D for DIGITAL mode and IBM[R] ProPrinter[R] mode printing for a single LA75[TM] printer.   E PATHWORKS Advanced Server supports the DECprint[TM] Supervisor (DCPS) K for OpenVMS product, which provides PostScript[R] and DEC[TM] ANSI printing 2 to selected industry-standard PostScript printers.  3 Sharing of Network Resources by Heterogeneous Users   A Services provided by PATHWORKS Advanced Server are accessible to  H PATHWORKS clients as well as to Microsoft clients. All clients using theG services of a PATHWORKS Advanced Server must be properly licensed. (For 6 more information, see the Software Licensing section.)  B Files are stored on the server in native OpenVMS RMS format. This G allows information stored by the PCs using PATHWORKS Advanced Server to C be shared with traditional OpenVMS users. In addition, this feature F allows information to be shared among all clients, including those notD based on PATHWORKS technology. Concurrent file access by host appli-2 cations or non-PATHWORKS clients is not supported.   Network Transport Support   I PATHWORKS Advanced Server supports DECnet[TM] (Phase IV), DECnet-Plus[TM] E (formerly known as DECnet/OSI), TCP/IP, and NetBEUI network transport C software. One or multiple transport stacks can work concurrently on  the server.   C The TCP/IP transport is sold as a separate DIGITAL product and must % include a PATHWORKS IP (PWIP) driver.         "                                  4       E NetBEUI transport software is included with PATHWORKS Advanced Server C software. Using NetBEUI transport software, LAN Manager clients can @ access the server in the LAN for file and print shares. See the C Software Requirements section for information on supported network   transport software.    NETBIOS[TM] Interface Support   C PATHWORKS Advanced Server supports the NETBIOS interface in DECnet, D TCP/IP, and NetBEUI networks. PATHWORKS Advanced Server uses NETBIOSE naming services and datagram services. However, a NETBIOS programming B interface is not provided. NETBIOS interface support includes the F support of multiple transport stacks on a single or different network  controllers.  D NETBIOS support under TCP/IP includes both a p-node and a b-node RFCG 1001/1002 implementation. Therefore, the NETBIOS interface is supported E under TCP/IP in both LAN and WAN environments. The PATHWORKS Advanced E Server Configuration Manager utility allows you to select one or both E of the following methods for NETBIOS name resolution for WAN support:    o  LMHosts file   1 o  Windows Internet Naming Services (WINS) Server    Flexible Security Models  C The PATHWORKS Advanced Server security model accommodates both the  I Advanced Server security model and the OpenVMS security model. The server C 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.   C PATHWORKS Advanced Server employs a user-level security model that  H provides precise control over access to shared resources, including diskC devices, directories, and printers. Control is based on a password  B assigned to each user account and the specific access permissions  defined for the resources.  "                                  5       E PATHWORKS Advanced Server incorporates enhanced features that provide H a high level of control over user and resource permissions and auditing.> These features include support of discretionary access control@ permissions on individual files, directories, and resources and  complete auditing capabilities.   C Like Windows NT Servers, PATHWORKS Advanced Server does not support C share-level security and operates in user-level security mode only.   ? o  In the Advanced Server and OpenVMS security model, both the  G    OpenVMS and Advanced Server security models are enforced. PATHWORKS  H    Advanced Server security is enhanced with OpenVMS security. Users whoC    require this additional security support can continue to protect -    their resources based on OpenVMS security.    Domain Support  C PATHWORKS Advanced Server allows the network to be subdivided into  F domains (administrative groups of servers and clients). Each PATHWORKS@ Advanced Server can be a member of a single domain. A PATHWORKS E Advanced Server can be a Primary Domain Controller (PDC) or a Backup  H Domain Controller (BDC). Domains are a convenient mechanism for control-@ ling user access to the network and for managing large networks.  G A PATHWORKS for DIGITAL UNIX[R] Advanced Server can be part of the same C domain as a PATHWORKS for OpenVMS Advanced Server and can be desig- ? nated as either the Primary Domain Controller or Backup Domain   Controller.   D PATHWORKS for OpenVMS Advanced Server provides support for wide area3 domains using one or both of the following methods:    o  LMHosts file   B The presence of the LMHosts file on the PATHWORKS Advanced Server I allows NetLogon services and security database replication over wide area ? TCP/IP configurations. This file contains a list of nodes from  B geographically dispersed sites synchronized by the Primary Domain I Controller and accessible to clients in the server's domain. However, use A of the LMHosts file for replication over extreme distances or in  : networks with slow transmission speeds is not recommended.  "                                  6       1 o  WINS (Windows Internet Naming Services) Server   C Support for WINS Servers allows PATHWORKS Advanced Server to act as C a WINS client; that is, to use the name registration and resolution D facilities available from a Microsoft WINS Server across routed wideD area TCP/IP networks, thus enabling WAN support from WINS for domain@ functions, NetLogon services, and security database replication.   Trust Relationships   D PATHWORKS Advanced Server supports trusts. Trust relationships allowD users from other domains to access resources in the local domain and8 local domain users to access resources in other domains.   NetLogon Services   E A single domain-wide logon lets a user access resources on any server A in a domain or on servers in other domains that trust the domain.   E The domain capabilities of PATHWORKS Advanced Server make it possible E for a user to issue a single logon request to gain access to multiple @ servers in a network. The NetLogon service forces the validationC of users' logon requests. The logon server that processes a 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  E PATHWORKS Advanced Server can act as a Master Browser in a Windows NT  network.   TimeSource Services   D DOS, Windows, and OS/2 clients can request date and time informationE from the PATHWORKS Advanced Server and set the local workstation date  and time to coincide with it.         "                                  7        User Environment Management   H Logon scripts can be used to configure MS-DOS[R] and Windows workstationJ user environments by making network connections and starting applications.I User profiles can make workstations easier to use, as well as controlling ( workstation access to network resources.   Server Management and Control   G PATHWORKS Advanced Server can be managed from either the OpenVMS server E or a client workstation, using one of the following server management  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 WindowsG    NT workstations, Windows 95 workstations, and Windows for Workgroups D    workstations. These tools, including Server Manager, User ManagerC    for Domains, and Event Viewer, allow you to administer PATHWORKS H    Advanced Server and Windows NT Server computers from network clients.  J o  Windows NT Server tools, which are available as part of the Windows NT 
    Server.  G o  PATHWORKS Advanced Server Configuration Manager utility (a character O    cell interface) to manage the local PATHWORKS Advanced Server configuration.   C o  PATHWORKS License Manager (a character cell interface) to manage      the PATHWORKS License Server.  * These management utilities can be used to:  < o  Manage file and printer shares, user accounts, and groups  B o  Display and control server resources currently in use, such as .    active sessions, connections, and services.  "                                  8       C o  View context-sensitive online help that provides command syntax, 9    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 ServerC can also be managed remotely from Windows NT Servers and PATHWORKS   Advanced Servers.   7 PATHWORKS Advanced Server Configuration Manager Utility   A The PATHWORKS Advanced Server Configuration Manager utility is a  O character 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, M the security model, the number of supported clients, the types of transports, < the type of WAN capabilities, and more. Any adjustments thatG need to be made to the OpenVMS SYSGEN parameters to support the running > of the server are automatically performed by the Configuration Manager utility.   Integrating with OpenVMS  C PATHWORKS Advanced Server encompasses many features of the OpenVMS  K operating System, including OpenVMS clusters and symmetric multiprocessing. @ OpenVMS cluster configurations provide failover availability andE extensive resource capacities by integrating multiple OpenVMS systems 1 that can be accessed using a single cluster name.   F PATHWORKS Advanced Server includes support for a transport-independentB PATHWORKS cluster alias NetBIOS name that allows multiple cluster E members to appear as a single server to the connecting clients. This  F support provides higher availability. The PATHWORKS cluster alias nameB has a load-balancing feature that connects clients to the cluster G member that is the least loaded at the time the session is established. C PATHWORKS Advanced Server includes a high performance, cluster-wide @ distributed data cache that provides scalability in a clustered  environment.  C PATHWORKS Advanced Server can run on both VAX and Alpha members of  3 homogeneous or mixed architecture OpenVMS clusters.   "                                  9       ( Integrating with External Authentication  C External authentication is an optional feature that allows OpenVMS _D systems to authenticate designated OpenVMS users with a PATHWORKS orF Windows NT username and password combination. You can set up external J authentication for any OpenVMS user, mapped to a PATHWORKS Advanced Server
 user account.t  G External authentication allows users to log on to the OpenVMS OperatingiE System using their PATHWORKS Advanced Server usernames and passwords.R= This feature is useful to OpenVMS system managers who want torA provide users with a single username and password combination to lA access both OpenVMS login and PATHWORKS Advanced Server. For morefD information about external authentication for OpenVMS, refer to the E OpenVMS Operating System Software Product Description (SPD 25.01.xx).q  ! Integrating with OpenVMS Securityy  B PATHWORKS Advanced Server provides an extension to the Windows NT H security model by supporting OpenVMS security enforcement as an optional enhancement.   Alerter Servicep  A PATHWORKS Advanced Server includes an Alerter Service that sends  A automatic alert messages to clients and users as specified in the  LANMAN.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, forn> each, whether successful or unsuccessful attempts at specific G operations are to generate event messages. Security event messages are 9I generated based on the audit policy specified for the Advanced Server and  for files and directories.   Replicator Service  ? Windows NT Servers provide user data replication across domain .G controllers using the Replicator service. The Replicator service is not[  "                                 10 a     H provided on PATHWORKS Advanced Servers. Therefore, automatic replicationM of user files and directories on PATHWORKS Advanced Servers is not supported.a   Installation Utilities  F PATHWORKS Advanced Server is installed on the OpenVMS system using theD standard VMSINSTAL procedure. An Installation Verification ProcedureD (IVP) is also included, which can be used to confirm that the server% software has been installed properly.K  C The installation procedure allows you to install PATHWORKS AdvancedaA Server with the integrated license server or just the standalone e license server.t   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.AC This product will no longer be supported, and licenses to use this lI product will no longer be sold. The code for this product continues to beeI distributed in the PATHWORKS V6.0A for OpenVMS (Advanced Server) softwaredA kit as a convenience for those who previously deployed it and whoe8 wish to continue to use it without support from DIGITAL.  D If you are running the PATHWORKS for OpenVMS (NetWare) server on the< same system with PATHWORKS Advanced Server, you must either:  G o  Upgrade the NetWare server as well as the PATHWORKS Advanced Server.eA    The NetWare server is upgraded automatically when you install W    PATHWORKS Advanced Server.   A o  Remove the NetWare server software from the system before you  %    install PATHWORKS Advanced Server.               "                                 11    a   Year 2000 Readys  D PATHWORKS Advanced Server has been tested to ensure that the product is Year 2000 ready.n   License Management  D PATHWORKS Advanced Server offers license management for client-basedC licenses (CCS, FPA, Designated Access, System, and CNS) and Client  I Access licenses, which can be used in either client-based or server-basede7 mode. (See the Software Licensing section for details.)h  I The license deliverables for PATHWORKS products are Product AuthorizationoB Keys (PAKs) that are then used with the OpenVMS License Management? Facility (LMF). These PAKs must be loaded into an LMF database,dC using standard LMF procedures, on an OpenVMS system that is hostingaA a PATHWORKS server or is acting as a PATHWORKS License Server.[1]n  ( 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 and C verifies client-based licenses or Client Access licenses being useda? in client-based mode by clients running LAN Manager protocols. sG PATHWORKS Advanced Server clients and PATHWORKS LAN Manager clients usee) the DECnet, TCP/IP, or NetBEUI transport.y  E The PATHWORKS License Manager, which executes on the same node as theaG License Server, provides a user interface that allows the administrator/@ to monitor client-based license usage, to manage license groups,C to set alert levels, to set logging levels for licensing events, tobF enable or disable the License Server, and to revoke assigned licenses.   ____________________C The  PATHWORKS License Server is active on only a single node in a sF cluster.  If that node goes down for any reason, the License Server isI automatically activated on another cluster node that is running PATHWORKSt Advanced Server.  "                                 12 a     E The PATHWORKS License Manager is also used to preallocate licenses to C specific "groups" (including the special, predefined "server-based"i> group described later) and to reclaim a license from a client.  E Each LAN needs only one active PATHWORKS License Server. (The LicenseAE Server provided with PATHWORKS Advanced Server can support every kindoD of PATHWORKS client-based license, as well as Client Access licenses for all supported clients.)a  E The PATHWORKS License Registrar, which executes on the same system asuD the file server, verifies the licenses for clients requesting accessA to the server functions. Clients that can produce a valid Client iA Access license are allowed access to the services offered by the p PATHWORKS Advanced Server.  C o  Server-based license management. PATHWORKS Advanced Server also  C    allows client access based on the availability of Client Access oF    licenses 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 usedcC    in server-based mode. If one is available, the client is allowedd
    access.  F Client Access licenses can be put into server-based mode in one of two ways:)  A    -  If the PATHWORKS License Server was not configured for the rJ       system where PATHWORKS Advanced Server is executing, then all ClientA       Access licenses loaded into the local LMF database on that O/       system 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 ClienteB       Access licenses loaded into the local LMF database will, by ,       default, be used in client-based mode.        "                                 13    r  G To allow some or all of these licenses to be used in server-based mode,SC use the PATHWORKS License Manager to allocate those licenses to the C special, predefined "server-based" group. Licenses available in the G server-based group will then be available for use in server-based mode.i  G Note: PATHWORKS Advanced Server allows you to simultaneously use Client D Access licenses in both client-based and server-based mode. However,E because clients using Client Access licenses in client-based mode arel@ already licensed to use the server software, they never consume I additional Client Access licenses allocated for use in server-based mode.n  ! Accommodation of Retired Features   E The following features of PATHWORKS V5.x for OpenVMS are not providedi in PATHWORKS V6.0A for OpenVMS:s  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 separatetD    system. Files held within shares on a FAT volume must be migratedC    to PATHWORKS LAN Manager shares before you upgrade to PATHWORKS c    Advanced Server.a  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 allrC    clients making use of this connection format are upgraded before 1    the installation of PATHWORKS Advanced Server.n  E o  Remote Boot service. If clients depend on remote booting, you must C    maintain the PATHWORKS LAN Manager server on a separate system. rF    Transfer this function to another server that supports Remote Boot     service before the upgrade.  D o  Share-level security. PATHWORKS Advanced Server manages access to-    all resources through user-level security.d      "                                 14 r  P  F o  LAN Manager and creator security mode. The server can be configuredE    for PATHWORKS Advanced Server Only security model or for PATHWORKS .    Advanced Server and OpenVMS security model.  L o  PATHWORKS LAN Manager Net command line interface and ADMINISTER/PATHWORKSJ    character cell interface. These features were replaced by the PATHWORKSD    Advanced Server ADMINISTER command line interface. The ADMINISTER;    command line interface provides automatic translation ofaE    a subset of Net commands that have ADMINISTER command equivalents.s  I PATHWORKS Advanced Server maintains compatibility with LAN Manager cliente4 and server software. A PATHWORKS LAN Manager server:  1 o  Can be upgraded to a PATHWORKS Advanced Servera  B o  Can continue running PATHWORKS LAN Manager and act as a Backup E    Domain Controller, member server, or standalone server in a domainoE    where the Primary Domain Controller is a PATHWORKS Advanced Servert#    or a Windows NT Server computer.p   HARDWARE REQUIREMENTS   A The following systems, components, and peripherals specified are u supported except as noted.                      "                                 15 d  r Processors Supported  D All VAX and Alpha processors supported by the OpenVMS V7.1 OperatingK System are also supported by PATHWORKS V6.0A for OpenVMS (Advanced Server),s except for the following:i   GPX II  A MicroVAX:   MicroVAX I, MicroVAX II, MicroVAX 2000, MicroVAX 3100e             Model 40 and lower  ? VAX:        VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAXi             11/782, VAX 11/785  : VAXstation: VAXstation I, VAXstation II, VAXstation 2000, 0             VAXstation 4000 VLC, VAXstation 8000   Memory Requirements   C PATHWORKS Advanced Server requires a minimum of physical memory forWC proper installation, configuration, and execution of the software, a  depending on the processor type:  ' o  On Alpha systems, a minimum of 64 MBe  % o  On VAX systems, a minimum of 64 MBi  @ Note: These memory requirements are a minimum requirement only. E Memory requirements can vary widely according to the server CPU, the iG number of clients using the server and their activities, and the numberiE and speed of the server's disks and the other applications running oni the server.r  F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires an D Alpha system with approximately 64 MB of memory. This means that 80%E of the system memory and CPU time are dedicated to PATHWORKS Advanced - Server, even though some work might use less.e  . Disk Space Requirements (Block Cluster Size=1)  E Table 1 provides the disk space requirements for the installation andhC configuration of PATHWORKS Advanced Server. By default, all entrieshD are directed to the same disk, but each can be directed to different disks.  "                                 16 a  p  H You should also plan for additional, significant disk-space requirements? for items such as data files, virtual memory section files, and 4 log files - after the product is started and in use.  C ___________________________________________________________________A  ; Table 1: Installation/Configuration Disk Space Requirements C ___________________________________________________________________   %                                 Alpha @ Item                            Systems              VAX SystemsC ___________________________________________________________________a  C Images and command files        148,500 blocks       130,500 blockso
             C PATHWORKS server data files      77,500 blocks        77,500 blockso  C Total                           226,000 blocks       208,000 blockssC ___________________________________________________________________n> Note: Sizes are approximate; actual sizes might vary depending= on the user's system environment, configuration, and softwarem options.C ___________________________________________________________________    OPTIONAL HARDWAREm   PostScript Printersh  D PATHWORKS Advanced Server supports all PostScript printers supportedE by DECprint Supervisor (DCPS) for OpenVMS V1.4. Refer to SPD 44.15.xxnF for a complete list of the DIGITAL and non-DIGITAL PostScript printers@ supported by DCPS. DECprint Supervisor software is included with PATHWORKS Advanced Server.  G DIGITAL PostScript printers connected by serial lines or DECservers[TM]W= and printers attached directly to the Ethernet are supported.o  D The right to use DCPS-Open software by the PATHWORKS Advanced Server< is granted by your license(s) for PATHWORKS Advanced Server.  "                                 17       A Note: A separate DCPS-Open license (order number QL-09MA*-AA) is  5 required for any other use of the DCPS-Open software.i   Non-PostScript Printers   D PATHWORKS Advanced Server also supports the following non-PostScript	 printers:l  . DIGITAL LA75 Companion          EPSON[R] FX850 Printers, DIGITAL LA210                   EPSON FX1050
 DIGITAL LA310 . DIGITAL LA324[TM]               IBM ProPrinter
 DIGITAL LA424p@ DIGITAL LJ250 Companion         NEC SilentWriter[R] II Model 290
 Color Printern DIGITAL LN03[TM] PLUSd   Network Interface Controllersr  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.KB    For DIGITAL TCP/IP Services for OpenVMS, refer to SPD 46.46.xx.  . For other TCP/IP products, contact the vendor.  D o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see'    the SPDs for the following products:   6    -  DECnet-Plus V7.1 for OpenVMS Alpha, SPD 50.45.xx  4    -  DECnet-Plus V7.1 for OpenVMS VAX, SPD 25.03.xx  9    -  DECnet for OpenVMS VAX and Alpha V7.1, SPD 48.48.xxu  D o  For the NetBEUI transport, PATHWORKS Advanced Server provides the>    same level of support for Ethernet and FDDI as the OpenVMS <    Operating System. For more information, see SPD 25.01.xx.  "                                 18 l  e  K Note: PATHWORKS Advanced Server does not support the DEFZA FDDI controller.o   CLUSTER ENVIRONMENTx  F PATHWORKS Advanced Server runs on members of OpenVMS clusters. OpenVMSA cluster configurations are fully described in the OpenVMS Clusterd4 Software Software Product Description (SPD 29.78.xx)  F PATHWORKS Advanced Server supports up to 31 server nodes in a cluster.D In other words, no more than 31 nodes in a cluster can run PATHWORKS? Advanced Server concurrently. In a typical scenario, the servereD is run on only a few central nodes - to exploit the cluster's shared. disks and high-speed interconnect environment.  C In a cluster, PATHWORKS Advanced Server supports simultaneous file fD access by all nodes running the server. A central event log, centralB Advanced Server accounts, and share databases are maintained in a D cluster. In a PATHWORKS Advanced Server domain, the OpenVMS cluster F represents a single domain member, whether it is acting as the Primary3 Domain Controller or as a Backup Domain Controller.t   SOFTWARE REQUIREMENTSl   Operating System  & o  OpenVMS Alpha Operating System V7.1  $ o  OpenVMS VAX Operating System V7.1  C For minimum hardware requirements of the operating system, refer to F the Software Product Description for the OpenVMS Operating System (SPD
 25.01.xx).   Network Transport Software  F PATHWORKS Advanced Server includes NetBEUI network transport software.C DECnet or TCP/IP network transport software may also be required bysB PATHWORKS for OpenVMS, depending on the transport used by clients A requiring connections to the server, or for use of some features.o  "                                 19 r     H The following DECnet and DECnet-Plus products are supported by PATHWORKS Advanced Server:  % o  DECnet-Plus V7.1 for OpenVMS Alphax  # o  DECnet-Plus V7.1 for OpenVMS VAXt  ( o  DECnet for OpenVMS VAX and Alpha V7.1  E When PATHWORKS Advanced Server is to be used in a TCP/IP environment,tA OpenVMS-based TCP/IP software is required. This software must be AG purchased separately. The following TCP/IP transports support PATHWORKSi Advanced Server:  1 o  DIGITAL TCP/IP Services for OpenVMS V4.1, V4.2f  < o  Process Software Corporation[TM] MultiNet[R] V4.0, Rev. B  ; o  Process Software Corporation TCPWARE[R] for OpenVMS V5.1o   Other PATHWORKS Server Softwaret  ? The following PATHWORKS server products cannot run on the same i$ system as PATHWORKS Advanced Server:  D o  PATHWORKS V5.x for OpenVMS. PATHWORKS V6.0A for OpenVMS (AdvancedI    Server) can be upgraded from the V5.x server. Running the V6.0A servere?    on a system also running the V5.x server is not possible or iC    supported. You cannot continue to run the PATHWORKS LAN Manager lL    software, once the PATHWORKS Advanced Server software has been installed.G    PATHWORKS Advanced Server cannot coexist on the same OpenVMS clustere    with PATHWORKS V5.x server.  D o  PATHWORKS V6.0 for OpenVMS. PATHWORKS V6.0A for OpenVMS (AdvancedI    Server) can be upgraded from the V6.0 server. Running the V6.0A servera?    on a system also running the V6.0 server is not possible or IG    supported. You cannot continue to run the PATHWORKS V6.0 for OpenVMSaC    (Advanced Server) software, once the PATHWORKS V6.0a for OpenVMS E    (Advanced Server) software has been installed. PATHWORKS V6.0A fors?    OpenVMS (Advanced Server) cannot coexist on the same OpenVMSW*    cluster with the PATHWORKS V6.0 server.  "                                 20    s  F PATHWORKS Advanced Server maintains full down-level compatibility withC LAN Manager client and server software. LAN Manager users can add aiC PATHWORKS Advanced Server to an existing network and migrate to therD new technology at their own pace. A PATHWORKS LAN Manager server canF be upgraded to PATHWORKS Advanced Server technology or act as a BackupC Domain Controller, member server, or standalone server in a networkeE in which the Primary Domain Controller is a PATHWORKS Advanced ServertB or a Windows NT Server computer. PATHWORKS Advanced Server can be E deployed as a Primary Domain Controller in a network comprising othervE PATHWORKS Advanced Servers, Windows NT Servers, DIGITAL PATHWORKS for F OpenVMS (LAN Manager) servers, or LAN Manager for OS/2 Servers. It canC also act as a Backup Domain Controller for other PATHWORKS AdvancedK& Server or Windows NT Server computers.   Client Softwaret  D The following versions of client software are supported for use with PATHWORKS Advanced Server:  9 o  Microsoft Windows NT workstation software V3.5 or V4.0e   o  Microsoft Windows 95c  ) o  Microsoft Windows for Workgroups V3.11i  " o  PATHWORKS 32 V7.1, SPD 56.33.xx  3 o  PATHWORKS V6.0 for DOS and Windows, SPD 55.07.xxi  ( o  PATHWORKS V5.1 for OS/2, SPD 55.24.xx   GROWTH CONSIDERATIONS   E The minimum hardware and software requirements for any future versioni? of this product may be different from the requirements for the   current version.        "                                 21    H  C ___________________________________________________________________   A PRODUCT NAME:  DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager)t   DESCRIPTIONa  A DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is an OpenVMS hB layered application that provides the functions of a Microsoft LANG Manager V2.2 server in a PC LAN environment - with additional features.tD It is a member of the PATHWORKS family of products, which provides aC framework for integrating personal computers into an organization'soB total information system, allowing users to share information and 0 network services across the entire organization.  E PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is functionally equivalenta2 to PATHWORKS for OpenVMS (LAN Manager) V5.0F-ECO1.  E Customers who have V5.0F-ECO1 installed do not need to install V5.0F1mD of the software. Likewise, installation of V5.0F1 precludes the need to install V5.0F-ECO1.  H The PATHWORKS family includes PC LAN server products running on OpenVMS,D DIGITAL UNIX, ULTRIX[TM], SCO[TM] UNIX, and OS/2 platforms providing> industry-standard Network operating system (NOS) services that? use Microsoft's LAN Manager protocol. The PATHWORKS family also H includes client software for these servers, include wide area transports? (such as DECnet and TCP/IP), and applications such as Mail and  C Terminal Emulation, allowing DOS, Windows, Windows NT, Windows 95, tC Windows for Workgroups, and OS/2 to participate as full peers in a d" distributed computing environment.   FEATURES  D PATHWORKS V5.0F1 for OpenVMS adds a new dimension to general purposeB OpenVMS systems. In addition to providing traditional support for G business, scientific, and engineering applications, this product allowslE an OpenVMS system to appear to LAN Manager clients as a Microsoft LANeC Manager server. PATHWORKS V5.0F for OpenVMS is an implementation of,- industry-standard Microsoft LAN Manager V2.2.c  "                                 22 a  a  C The major features of PATHWORKS V5.0F1 for OpenVMS are described inr the following sections.A  
 File ServicesS  D PATHWORKS V5.0F1 for OpenVMS provides LAN Manager-based clients withC a remote file system that appears as a transparent extension of thec, client system's local computing environment.  ? PATHWORKS for OpenVMS file shares are based on Microsoft's LAN t2 Manager V2.2 SMB (Server Message Block) protocols.  F Each file stored in a file service is stored as an OpenVMS file in RMS? format. Three types of RMS file/record formats are allowed and e supported on each volume:a   o  Sequential stream  8 o  Sequential fixed length record (512 bytes per record)   o  Sequential undefined   D Files stored in a file service are accessible to PC clients, OpenVMS> users, and to applications that can interpret the content and > organization of the file as written by the client application.  D Multiple LAN Manager clients can concurrently access files stored onF the server's disk through the file access modes and byte range locking1 support provided by the OpenVMS Operating System.e   Print Shares  @ PATHWORKS for OpenVMS software allows DOS, Windows, Windows NT, C Windows 95, OS/2, and OpenVMS users to share printers connected to  F Alpha, VAX, or VAXserver[TM] computers and to OpenVMS cluster systems,C as well as network-based printers such as LAT printers and DIGITAL aD Printservers. Print shares are supported in local area and wide areaE network environments. PC clients can print files from the DOS, OS/2, bI Windows, Windows 95, and Windows NT operating systems as well as from PC e
 applications.   "                                 23 e  n  G Multiple print shares may be defined for a single printer. For example,l@ separate services may be created for landscape-mode printing andC portrait-mode printing. Similarly, separate services may be createdeC for DIGITAL mode and IBM ProPrinter mode printing for a single LA75  printer.  D PATHWORKS V5.0F1 for OpenVMS includes the DECprint Supervisor (DCPS)A Open product, which provides PostScript and DEC ANSI printing to  / selected industry-standard PostScript printers.n  3 Sharing of Network Resources by Heterogeneous Usersl  F Services provided by PATHWORKS for OpenVMS are accessible to PATHWORKSF LAN Manager-based clients as well as to Microsoft LAN Manager clients.G All clients using the services of a PATHWORKS V5.0F1 for OpenVMS server F must be properly licensed. (See the Software Licensing section of thisH SPD.) Files are stored on the server in native OpenVMS Record Management@ Services (RMS) format. This allows information stored by the PCsH using PATHWORKS for OpenVMS to be shared with traditional OpenVMS users.C In addition, this feature allows information to be shared among all G PATHWORKS clients, including those not based on LAN Manager technology. > Concurrent file access by host applications or non-LAN Manager clients is not supported.o   Network Transport Supporto  F PATHWORKS V5.0F1 for OpenVMS supports DECnet, DECnet-Plus, TCP/IP, andD NetBEUI network transport software. One or multiple transport stacks$ can work concurrently on the server.  G The TCP/IP transport, which is sold as a separate product and available @ from various vendors, must include a PATHWORKS IP (PWIP) driver.  D NetBEUI transport software is included with the PATHWORKS V5.0F1 forG OpenVMS software. Using NetBEUI transport software, LAN Manager clientsnJ can access the server in the local area network for file and print shares.D See the Software Requirements section of this SPD for information on% supported network transport software.     "                                 24 a      NetBIOS Interface Supportt  F PATHWORKS V5.0F1 for OpenVMS supports the NetBIOS interface in DECnet,D TCP/IP, and NetBEUI networks. PATHWORKS for OpenVMS utilizes NetBIOSF naming services and datagram services. A NetBIOS programming interface< is not provided, however. NetBIOS interface support includesB the support of multiple transport stacks on a single or different G network controllers. NetBIOS support under TCP/IP includes a b-node RFCKD 1001/1002 implementation. This implies that the NetBIOS interface is? supported under TCP/IP in local area network environments only.s   Flexible Security Models  E The PATHWORKS V5.0F1 for OpenVMS security model accommodates both the5E LAN Manager security model and the OpenVMS security model. The serverdC may be configured to use the security implementation best suited toSE the environment. In "LAN Manager Only" mode, the LAN Manager securityPF model is enforced. In "LAN Manager and OpenVMS" mode, both the OpenVMSA and LAN Manager security models are enforced. In "LAN Manager and1H Creator" mode, OpenVMS security is applied to files not created by users of the PATHWORKS server.   Domain Support  E PATHWORKS V5.0F1 for OpenVMS allows the network to be subdivided intoqE administrative groups of servers and clients called domains. A domainmC is a group of servers and clients on a LAN and is the basic unit ofsE network administration. Each server running PATHWORKS for OpenVMS canmE be a member of a single domain. A PATHWORKS for OpenVMS server can besE a Primary Domain Controller, Backup Domain Controller, Member Server,eC or a Standalone Server, depending on the environment. Domains are aeD convenient mechanism for controlling user access to the network, and for managing large networks.  A PATHWORKS V5.0F1 for OpenVMS also provides support for wide area lE domains using the LMHosts file. This file's presence on the PATHWORKShF for OpenVMS (LAN Manager) server allows NET Logons and UAS replicationD over some wide area TCP/IP configurations. The LMHosts file containsH a list of nodes from geographically disperse sites that are synchronized: by the primary domain controller and accessible to clients  "                                 25 p     C in the server's domain. However, use of the LMHosts file for repli-nC cation over extreme distances or in networks with slow transmissionb speeds is not recommended.   Network Logon Services  E The domain capabilities of LAN Manager make it possible for a user toaH issue a single logon request in order to gain access to multiple serversF in a LAN. Running the netlogon service forces the validation of users'F logon requests. The logon server that processes the request checks itsC copy of the domain-wide user accounts database for the username ande' password supplied in the logon request._   LAN Manager V2.2 API Support  F PATHWORKS V5.0F1 for OpenVMS supports the LAN Manager V2.2 ApplicationH Programming Interfaces, with the exception of Named Pipes and Mailslots.B Note that LAN Manager APIs are not available to OpenVMS host-based> applications, but are available to PATHWORKS LAN Manager-basedI clients, non-PATHWORKS LAN Manager clients, and OS/2 LAN Manager servers.    Remote Boot Service   C The Remote Boot service included with PATHWORKS V5.0F1 for OpenVMS _H allows DOS and Windows workstations to start up using information storedC on the server's hard disk instead of on their own local hard disks.dD The PATHWORKS V5.0F1 for OpenVMS Remote Boot service is based on theA Microsoft LAN Manager Remote Boot service, which uses the Remote  F Program Load (RPL) protocol. Remote Boot is supported over NetBEUI on I Ethernet networks. PATHWORKS V5.0F1 for OpenVMS supports MOP (Maintenance D Operation Protocol) as a secondary loader for clients without an RPL ROM.  
 Mail Servicesn  C PATHWORKS V5.0F1 for OpenVMS includes a mail server component that IF allows clients to send and receive electronic mail. The mail server is      "                                 26 t  e  @ based on the OpenVMS MAIL-11 product and requires DECnet as its C communications transport. It allows users of PATHWORKS Mail client dG software to send and receive electronic mail messages without having toe4 log in to the OpenVMS system as an interactive user.  F A mail account may be established on the OpenVMS server for each user.F Mail can be sent to this account by other PATHWORKS Mail users as wellC as traditional users of OpenVMS mail software. The mail server then E routes messages to the appropriate client when the user logs onto the  server.A  F The PATHWORKS for OpenVMS mail server provides the PATHWORKS user withA folders, distribution lists, and delivery capabilities. Realtime AE notification of new messages can be optionally enabled by the client.d   Time and Date Services  D DOS, Windows, and OS/2 clients can request date and time informationE from the server system and set the local workstation date and time too coincide with them.u   PATHWORKS FAT File SystemP  D PATHWORKS V5.0F1 for OpenVMS includes the PATHWORKS FAT file system,D which is an alternative to, and designed to coexist with the OpenVMSE ODS-2 file system. It is based on the DOS File Allocation Table (FAT) B file system. PC files stored in the FAT file system are stored in G native DOS format in a container file on the server system. Features ofx& the PATHWORKS FAT file system include:  A o  Support for multiple readers and writers of the container filea  G o  Wide-area network access to files stored on the server in DOS format   I o  Improved performance on file and directory operations over the OpenVMS     ODS-2 file system  C The PATHWORKS FAT file system may be used as a migration path from tE existing PATHWORKS V4.x disk service container files. (See Accommoda-c tion of Retired Features.f  "                                 27 g  t   Server Management and Controlp  @ PATHWORKS V5.0F1 for OpenVMS supports several server management  interfaces:   7 o  A character cell utility called ADMINISTER/PATHWORKS.  A o  The LAN Manager NET ADMIN command line interface which may be SG    accessed from a terminal or terminal emulator, or from a LAN Managern>    client, including the PATHWORKS for DOS and Windows client.  ( The management utilities can be used to:  < o  Manage file and printer shares, user accounts, and groups  B o  Display and control server resources currently in use, such as -    active sessions, connections, and services   = o  View context-sensitive Help for each menu item and commandS   PATHWORKS Monitorn  E The PATHWORKS Monitor utility is a Windows-based application providedtA with the PATHWORKS V5.0F1 for OpenVMS server software. PATHWORKS  D Monitor collects data on server resource utilization and provides a / realtime graphical display of this information.    PATHWORKS Configuratione  C The PATHWORKS Configuration utility is an OpenVMS-based applicationDG that allows the user to modify the server's configuration. For example,r> the user can configure the data cache size, the security mode,C the number of supported clients and more. Any adjustments that needrG to be made to the OpenVMS SYSGEN parameters are automatically performedp by the Configuration utility.    Enhanced Cluster Support  I PATHWORKS V5.0F1 for OpenVMS includes support for a transport-independent B PATHWORKS cluster alias name service that allows multiple cluster ? members to appear as a single server to the connecting clients, F providing higher availability. The PATHWORKS cluster alias name has a H load balancing feature which connects clients to the cluster member that  "                                 28    r  E is the least loaded at the time the session is established. PATHWORKS/A V5.0F1 for OpenVMS also includes a high performance cluster-wide PH distributed data cache that provides scalability in a clustered environ-C ment. VAX clusters, Alpha clusters, and mixed-architecture clusters[. are supported by PATHWORKS V5.0F1 for OpenVMS.   Enhanced Performance from XQP+  G PATHWORKS V5.0F1 for OpenVMS includes a special release of the enhancedrF OpenVMS file system, known as XQP+ (eXtended QIO Processor Plus). XQP+F is separately installable to OpenVMS VAX V5.5-2. XQP+ is included withG OpenVMS VAX and Alpha V6.1 and later. When PATHWORKS V5.0F1 for OpenVMSiC detects the existence of the enhanced file system, it automaticallyl@ takes advantage of its improved concurrency, multithreading, andA directory caching features to provide better performance to file m system operations.   Installation Utilities  @ PATHWORKS V5.0F1 for OpenVMS is installed on the OpenVMS system E using the standard VMSINSTAL procedure. An Installation Verification VG Procedure (IVP) is also included, which can be used to confirm that the , server software has been installed properly.  G The installation procedure allows you to install the LAN Manager serverAD with the integrated license server, or just the standalone PATHWORKS License Server.   D DIGITAL recommends that a customer's first purchase of this softwareG product at each site include DIGITAL installation service. Contact your C local DIGITAL representative for information on the service options-
 available.                "                                 29 A  a   PATHWORKS NetWare Server  E The PATHWORKS for OpenVMS (NetWare) server software has been retired.hC This product will no longer be supported, and licenses to use this aI product will no longer be sold. The code for this product continues to ber@ distributed in this package as a convenience for those who have B previously deployed it and who wish to continue to use it without  support from DIGITAL.u   Security  D External authentication is an optional feature introduced in OpenVMSC V7.1 that enables OpenVMS systems to authenticate designated users rF using their LAN Manager domain using a single username/password combi-C nation. This feature is supported in PATHWORKS V5.0E and later. ForfC more information about external authentication for OpenVMS VAX, see 
 SPD 25.01.xx.r   Year 2000 Ready   E DIGITAL PATHWORKS V5.0F1 for OpenVMS (LAN Manager) has been tested tod+ ensure that the product is Year 2000 ready.o   License Management  A PATHWORKS for OpenVMS offers license management for client-based  E licenses (CCS, FPA, Designated Access, System, and CNS), server-basedOE licenses (FPS or PC Concurrent) and the Client Access licenses, whichxF can be used in either client-based or server-based mode. (See Software Licensing section for details.)t  I The license deliverables for PATHWORKS products are Product Authorization.B Keys (PAKs) that are then used with the OpenVMS License Management? Facility (LMF). These PAKs must be loaded into an LMF database,CC using standard LMF procedures, on an OpenVMS system that is hostingIA a PATHWORKS server or is acting as a PATHWORKS License Server.[2]O ____________________G [2] The  PATHWORKS License Server is active on only a single node in a eF cluster.  If that node goes down for any reason, the PATHWORKS LicenseI Server is automatically activated on another cluster node that is runningt
 PATHWORKS."                                 30 a  n  D o  Client-based license management. PATHWORKS for OpenVMS provides aD    facility called the PATHWORKS License Server that acts as a proxyJ    for client systems that require license keys stored in the LMF database    on an OpenVMS system.  C A single copy of the PATHWORKS License Server software provides andeC verifies client-based licenses or Client Access licenses being usedsB in client-based mode. PATHWORKS LAN Manager clients and PATHWORKS E Advanced Server clients use the DECnet, TCP/IP, or NetBEUI transport.S  E The PATHWORKS License Manager, which must execute on the same node assD 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, todF enable or disable the License Server, and to revoke assigned licenses.E The PATHWORKS License Manager is also used to preallocate licenses to C specific "groups" (including the special, predefined "server-based"r> group described later) and to reclaim a license from a client.  E Each LAN needs only one active PATHWORKS License Server. (The LicensecC Server provided with PATHWORKS V5.0F1 for OpenVMS (LAN Manager) caneG support every kind of PATHWORKS client-based license, as well as ClientA, Access licenses, and all supported clients.)  E The PATHWORKS License Registrar, which executes on the same system as D the file server, verifies the licenses for clients requesting accessF to the server functions. Clients that can produce a valid client-basedE license, or Client Access license, are allowed access to the services A offered by the PATHWORKS V5.0F1 for OpenVMS (LAN Manager) server.c  D o  Server-based license management. The PATHWORKS V5.0F1 for OpenVMSE    (LAN Manager) server also allows client access based on the avail-sD    ability of valid server-based licenses (either FPS and/or PC Con-E    current), and/or Client Access licenses being used in server-basedaC    mode in the local LMF database. If a client requesting access toeE    the server fails to produce a sufficient client-based license, theqC    PATHWORKS License Registrar software checks for the availabilityoF    of a valid server-based license or Client Access license being usedC    in server-based mode. If one is available the client is allowed c
    access.  "                                 31 l  c  F Client Access licenses can be put into server-based mode in one of two ways:n  G    o  If the PATHWORKS License Server was not configured for the systemrD       where PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is executing,?       then all Client Access licenses loaded into the local LMF @       database on that system will be used in server-based mode.  C    o  If the PATHWORKS License Server was configured for the systemDD       where PATHWORKS V5.0F1 for OpenVMS (LAN Manager) is executing,H       then all Client Access licenses loaded into the local LMF database5       will, by default, be used in client-based mode.y  G To allow some or all of these licenses to be used in server-based mode, D use the PATHWORKS License Manager and allocate those licenses to theC special, predefined group called the "server-based" group. LicensesdD available in the "server-based" group will then be available for use in server-based mode.I  E Note: PATHWORKS V5.0F1 for OpenVMS (LAN Manager) server allows you to B use both client-based and server-based licensing, simultaneously. F However, because clients using client-based licenses, or Client AccessE licenses in client-based mode, are already licensed to use the serversH software, they never consume additional server-based licenses, or ClientF Access licenses allocated for use in server-based mode, by a PATHWORKS( V5.0F1 for OpenVMS (LAN Manager) server.  ! Accommodation of Retired Features5  E The following features of PATHWORKS V4.x for OpenVMS are not providedc  in PATHWORKS V5.0F1 for OpenVMS:   o  File services over LAST   o  Disk services   o  Remote Boot over LAST  E If PATHWORKS V5.0F1 for OpenVMS is installed on a server system whichp? had been running V4.x of the product, some aspects of the V4.x tH environment related to the features listed above will be preserved. Disk  "                                 32    h  F services will remain intact and available to pre-V5.0F1 clients. LAST-C based Remote Boot services will also remain intact and available to  pre-V5.0F1 clients.p   HARDWARE REQUIREMENTS,  F The systems, components, and peripherals specified below are supported except as noted.   Processors Supported  E All VAX and Alpha processors that are supported by the version of theiF OpenVMS Operating System in use are also supported by PATHWORKS V5.0F18 for OpenVMS (LAN Manager) with the following exceptions:  2 MicroVAX:   MicroVAX I, MicroVAX II, MicroVAX 2000  ? VAX:        VAX-11/725, VAX-11/730, VAX 11/750, VAX 11/780, VAXc             11/782, VAX 11/785  I VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXstation 8000    Memory Requirementsr  D PATHWORKS V5.0F1 for OpenVMS requires the following minimum physicalC memory for proper installation, configuration, and execution of the 	 software:e  8    16 MB on VAX systems (24 MB if used with DECnet-Plus)      64 MB on Alpha systemsa  J Note that the memory requirements indicated above are minimum requirements? only, and that memory requirements can vary widely according to A the server CPU, the number of clients using the server and their tE activities, the number and speed of the server's disks and the other  # applications running on the server.     "                                 33 P     F For example, a typical configuration supporting a light workload (wordC processing or spreadsheet applications) for 50 PC users requires anAD Alpha system with approximately 64 MB of memory or a VAX system withA approximately 16 - 24 MB of memory. This assumes that 80% of the SG system memory and CPU time are dedicated to PATHWORKS, even though some  work loads may use less.  . Disk Space Requirements (Block Cluster Size=1)  E Table 2 provides the disk space requirements for the installation andm@ configuration of PATHWORKS V5.0F1 for OpenVMS (LAN Manager). By D default, all entries are directed to the same disk, but each can be  directed to different disks.  H You should also plan for additional, significant disk-space requirementsE after the product is started and in use for items such as data files, 6 virtual memory section files, log files, and so forth.  C ___________________________________________________________________o  ; Table 2: Installation/Configuration Disk Space RequirementsoC ___________________________________________________________________n  C Item                             VAX systems          Alpha systemsuC ___________________________________________________________________O  C Images and command files         40,000 blocks        60,000 blockss  C PATHWORKS server data files      12,500 blocks        12,500 blocksM  C ___________________________________________________________________ C Total                            52,500 blocks        72,500 blocks C ___________________________________________________________________e> Note: Sizes are approximate; actual sizes might vary depending= on the user's system environment, configuration, and softwareo options.C ___________________________________________________________________     "                                 34        OPTIONAL HARDWAREr   PostScript Printers   D PATHWORKS V5.0F1 for OpenVMS supports those PostScript printers thatE are supported by DECprint Supervisor (DCPS) for OpenVMS. Refer to SPDnF 44.15.xx for a complete list of the DIGITAL and non-DIGITAL PostScriptD printers supported by DCPS. DECprint Supervisor software is includedE with PATHWORKS V5.0F1 for OpenVMS. The right to use the DCPS softwareaG is granted by the DCPS Open license, which is included in the PATHWORKS B for OpenVMS (LAN Manager) PC Concurrent license, and the PATHWORKS< for DOS and Windows (LAN Manager) Designated Access license.                                                        "                                 35 s  u   Non-PostScript PrintersS  G PATHWORKS V5.0F1 for OpenVMS also supports the following non-PostScriptN	 printers:r  + DIGITAL LA75 Companion          EPSON FX850o Printer , DIGITAL LA210                   EPSON FX1050
 DIGITAL LA310W. DIGITAL LA324[TM]               IBM ProPrinter@ DIGITAL LA424                   NEC SilentWriter[R] II Model 290 DIGITAL LJ250 CompanionK
 Color Printere DIGITAL LN03[TM] PLUSe  D DIGITAL PostScript printers connected by serial lines or DECservers,= and printers attached directly to the Ethernet are supported.r   Network Interface Controllerst  A PATHWORKS for OpenVMS (LAN Manager) supports Ethernet, FDDI, and t7 Token Ring network hardware devices as described below:n  A o  For the TCP/IP transport, PATHWORKS for OpenVMS (LAN Manager)  I    supports the network hardware devices supported by the specific TCP/IPiI    product. For DIGITAL TCP/IP Services for OpenVMS, consult SPD 46.46.xxeC    (for Alpha systems) or SPD 25.A4.xx (for VAX systems). For other '    TCP/IP products, contact the vendor.   E o  For the DECnet transport using Ethernet, FDDI, or Token Ring, see:m  3    -  SPD 42.25.xx for DECnet for OpenVMS AXP, V6.1m  C    -  SPD 25.03.xx for DECnet/OSI V7.0 (or DECnet-Plus) for OpenVMSe       on VAX systems  I    -  SPD 50.45.xx for DECnet/OSI, V7.0 (or DECnet-Plus V7.1) for OpenVMS        Alphal  =    -  SPD 48.48.xx for DECnet for OpenVMS VAX and Alpha, V7.0s  "                                 36 u     B o  For the NetBEUI transport, PATHWORKS for OpenVMS (LAN Manager) B    provides the same level of support for Ethernet and FDDI as theE    OpenVMS operating system. For more information, see SPD 25.01.xx. nG    PATHWORKS V5.0F1 for OpenVMS (LAN Manager) does not support NetBEUI n"    over Token Ring on VAX systems.  G The PATHWORKS V5.0F1 for OpenVMS server does not support the DEFZA FDDI  controller.    CLUSTER ENVIRONMENT   G PATHWORKS V5.0F1 for OpenVMS (LAN Manager) supports all OpenVMS clusterH@ configurations. OpenVMS cluster configurations for Alpha systems@ are fully described in the OpenVMS Cluster Software for OpenVMS B Alpha Software Product Description (SPD 42.18.xx). OpenVMS clusterI configurations for VAX systems are fully described in the OpenVMS ClustertE Software for OpenVMS VAX Software Product Description (SPD 29.78.xx).   C PATHWORKS V5.0F1 for OpenVMS (LAN Manager) supports up to 31 server D nodes in cluster. In other words, no more than 31 nodes in a clusterC can run PATHWORKS V5.0F1 for OpenVMS (LAN Manager) concurrently. InhE a typical scenario, the server is run on only a few central nodes, toeK exploit the cluster's shared disks and high speed interconnect environment.n  B In a cluster, PATHWORKS V5.0F1 for OpenVMS (LAN Manager) supports I simultaneous file access by all nodes running the server. A central eventKG log and central LAN Manager accounts and share databases are maintained E in a cluster. In a LAN Manager domain, the OpenVMS cluster representsMC a single domain member, whether it is acting as the primary domain r, controller or as a backup domain controller.   SOFTWARE REQUIREMENTSi   Operating System   For Alpha Systems:  = o  OpenVMS Alpha Operating System V6.1, V6.2, V7.0, and V7.1.   "                                 37 n  r   For VAX Systems:  C o  OpenVMS VAX Operating System V5.5-2, V6.1, V6.2, V7.0, and V7.1.o  F For minimum hardware requirements of the operating system refer to theM Software Product Description for the OpenVMS Operating System (SPD 25.01.xx).s   OpenVMS Tailoringi  E For supported OpenVMS VAX V5.x systems, the following OpenVMS classesP< are required for full functionality of this layered product:   o  OpenVMS Required Saveseta  5 o  Network Support (required only for DECnet support)r   o  System Programming Supportt   o  Secure User's Environment   o  OPTL - Miscellaneous Filesr  C For more information on OpenVMS classes and tailoring, refer to theiI OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx).t   Network Transport Software  I PATHWORKS V5.0F1 for OpenVMS includes NetBEUI network transport software.r@ DECnet or TCP/IP network transport software may also be requiredD by PATHWORKS for OpenVMS, depending on the transport used by clientsA requiring connections to the server, or for use of some features.l  K The following versions of DECnet and DECnet-Plus are supported by PATHWORKSd V5.0F1 for OpenVMS:t   For Alpha Systems:  $ o  DECnet/OSI V6.3 for OpenVMS Alpha  $ o  DECnet/OSI V7.0 for OpenVMS Alpha  % o  DECnet-Plus V7.1 for OpenVMS Alpha   "                                 38    t   For VAX Systems:  " o  DECnet/OSI V6.3 for OpenVMS VAX  " o  DECnet/OSI V7.0 for OpenVMS VAX  # o  DECnet-Plus V7.1 for OpenVMS VAXc  H When PATHWORKS V5.0F1 for OpenVMS is to be used in a TCP/IP environment,@ OpenVMS-based TCP/IP software is required. This software must beG purchased separately. The following TCP/IP transports support PATHWORKSK V5.0F1 for OpenVMS:i  E o  DIGITAL TCP/IP Services for OpenVMS V4.0 (supported on OpenVMS for     VAX V5.5-2 only)o  E o  DIGITAL TCP/IP Services for OpenVMS V4.1 (supported on OpenVMS for     VAX V6.1 or later)M   o  MultiNet V3.5 rev A  < o  Process Software Corporation's TCPWARE for OpenVMS V5.0-4   Other PATHWORKS Server Softwareo  E The following PATHWORKS server products cannot run on the same systema. as PATHWORKS V5.0F1 for OpenVMS (LAN Manager):   o  PATHWORKS for OpenVMS V4.x.@    The PATHWORKS V5.0F1 for OpenVMS server can be installed and G    configured on a system running the V4.x server, but actually runninguD    the V5.0F1 server on a system also running the V4.x server is not    possible or supported.m  0 o  PATHWORKS V6.0A for OpenVMS (Advanced Server)A    The PATHWORKS V6.0A for OpenVMS software can be installed and nA    configured on a system running the V5.0F1 server, but actuallyaF    running the V5.0F1 server on a system also running the V6.0A serverB    is not possible or supported. An Upgrade utility provided with J    PATHWORKS V6.0A for OpenVMS allows server databases to be upgraded from    V5.0F1 to V6.0A.c  "                                 39        Client Software   D The following versions of client software are supported for use with PATHWORKS for OpenVMS:  @ o  Microsoft Windows NT workstation software V3.1, V3.5, or V4.0   o  Microsoft Windows 95r  ) o  Microsoft Windows for Workgroups V3.11i  " o  PATHWORKS 32 V7.1, SPD 56.33.xx  B o  PATHWORKS V6.0 for DOS and Windows (LAN Manager) (SPD 55.07.xx)  ) o  PATHWORKS for OS/2 V5.1 (SPD 55.24.xx)i  C o  LAN Manager V2.2 workstation software for DOS, Windows, and OS/2s   GROWTH CONSIDERATIONSo  E The minimum hardware and software requirements for any future versionn? of this product may be different from the requirements for the a current version.                                "                                 40    e  C ___________________________________________________________________5  G LICENSING AND ORDERING INFORMATION:  DIGITAL PATHWORKS V6.0A and V5.0F1a   SOFTWARE LICENSING  A PATHWORKS V6.0A for OpenVMS (Advanced Server)[3] is purchased by eG licensing the clients or applications that use the services provided by ( the product. There is no additional fee.  E The license that clients require to use the PATHWORKS Advanced ServereE software is referred to as a Client Access license (PAK Product Name:rE PWLMXXXCA06.00). Though there is only one license sold for any clienteC using this PATHWORKS server, this license can be used in one of twoe ways:s  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 PATHWORKS Advanced_F    Server is used in client-based licensing mode, the right to use theD    server is assigned electronically to a particular client or seat.   ____________________B All  previous versions of PATHWORKS for OpenVMS (Advanced Server),F including PATHWORKS V5.0F1 for OpenVMS (LAN Manager), are now licensedB for use in exactly the same way as PATHWORKS for OpenVMS (AdvancedC Server).  Though previously purchased licenses continue to be validtD for use with pre-V6 servers, only the new Client Access licenses may9 be purchased when adding new clients to existing systems.e  C In particular, all the licenses listed in Table 4, Previous VersionsA Licenses Qualifying for Upgrade Licenses, are no longer sold but  F continue to be valid and grant the right to use the PATHWORKS V5.0 for OpenVMS (LAN Manager) software.H    "                                 41 n  e  G    Once the right is assigned, the client system may access all systemshC    running PATHWORKS Advanced Server as well as all systems runningi4    any previous version of PATHWORKS for OpenVMS.[4]  A This mode of licensing PATHWORKS servers is normally used when a  F customer has more than one PATHWORKS server and where clients normallyF access more than one server at the same time. Because only one license@ per client is required regardless of how many servers are being I accessed, the client-based licensing mode can be more economical in thesec@ situations when compared to server-based mode (described later).  E Because a client with a client-based license cannot be refused accesssB to a server due to license limits, this mode of licensing is also F useful when you need to guarantee that a particular system will always# have access to one or more servers.   H Note: To use this licensing mode, a small licensing agent must be loadedF and enabled on each licensed client. The code for this licensing agentD is distributed with the PATHWORKS Advanced Server, is available free= on the Web, and is also available on CD-ROM at a nominal fee.   E o  Server-based licensing mode. When a license for PATHWORKS AdvancedoE    Server[5] is used in server-based licensing mode, the right to useb@    the server is assigned electronically to a particular server I    system running a copy of the software. Any client can then access thistH    server and make as many connections to file services and print shares
    as needed.e   ____________________H The  PAK associated with the Client Access license will work, in client-F based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversF that have been upgraded to a minimum of V5.0E. Prior revisions of this+ product will not recognize or use this PAK.l  H The  PAK associated with the Client Access license will work, in server-F based mode, only with PATHWORKS V5.0 for OpenVMS (LAN Manager) serversF that have been upgraded to a minimum of V5.0F. Prior revisions of this8 product will not recognize or use this PAK in this mode.  "                                 42 h  s  @ The PATHWORKS server will allow up to "n" clients to access its F services concurrently, where "n" is the total number of licenses beingJ used in server-based licensing mode. The server will not allow the "n+1st"E client to access its services, until one of the first "n" clients hase disconnected from the server.a  @ Note: Though a server may have only "n" licenses available, any H number of clients can potentially access that server. The restriction isH based only on the total number of clients that may connect to the server at one time.  D For example, if you have 100 licenses assigned to a PATHWORKS serverD in server-based licensing mode, then any 100 clients can make use ofE all services offered by the PATHWORKS server at one time. However, if C an additional client (the 101st) attempts to connect to the server,eC the client will be denied access until one of the connected clientsr disconnects from all services.  E Server-based licensing works best in situations where all clients use D or access only one server and there are enough licenses available on? each system for all clients to access their assigned server. A l? "system" is defined as either a standalone system or a cluster.n  @ Note: Customers can choose which mode to use and can change the C licensing mode, as their situation dictates, without contacting or p notifying DIGITAL.  ? Note also that any portion of multiple licenses delivered in a eG single PAK can be used in server-based mode, while the remainder can bewF 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.  D For complete terms and conditions related to Client Access licenses,@ refer to the back of your PAK for these licenses, or consult the4 DIGITAL Software Licensing InfoCenter on the Web at:  . http://www.digital.com/info/software-licensing    "                                 43 t      ORDERING INFORMATION   General Information5  D Unless otherwise noted, licenses related to each part number will beE delivered in a single PAK. Because each PAK can be loaded on only one D system, it is important to order your licenses in a manner that best fits your needs.   New or Additional Licenses  F For new or additional users of PATHWORKS for OpenVMS software, use the@ part numbers in Table 3 to purchase the number of Client Access I licenses required. When ordering, note that licenses related to each part F number will be delivered in a single PAK and any one PAK can be loaded on only one system  C ___________________________________________________________________   ! Table 3: New License Part NumbersnC ___________________________________________________________________n  0 Part Number           Number of Licenses per PAKC ___________________________________________________________________    QM-5SUAA-AB              1 QM-5SUAA-AC             10 QM-5SUAA-AD             25 QM-5SUAA-AE             50 QM-5SUAA-AF            100 QM-5SUAA-AG            250 QM-5SUAA-AH            500 QM-5SUAA-AJ           1000C ___________________________________________________________________2   Upgrade Licenses  C Customers with licenses for previous versions of PATHWORKS servers  D supporting the LAN Manager protocol are eligible to purchase UpgradeH licenses to PATHWORKS V6.0A for OpenVMS (Advanced Server). Combined withD your original license, the Upgrade license provides the right to use    "                                 44 l  t  A PATHWORKS V6.0A for OpenVMS (Advanced Server). To be eligible to fD purchase an Upgrade license, you must have proof-of-license for any G version of one of the licenses shown in Table 4. Table 5 lists the parth# numbers for these Upgrade licenses.i  C ____________________________________________________________________  B Table 4: Previous Version Licenses Qualifying for Upgrade LicensesC ____________________________________________________________________  B License Name                                          Part NumbersC ____________________________________________________________________  : CCS                                                   A[*]C PATHWORKS V5.x for OS/2 (LAN Manager) CCS             QM-YFWAA-A[*]eC PATHWORKS V5.0 (LAN Manager) FPA                      QM-2CLAA-A[*]_C PATHWORKS V5.0 (LAN Manager) Designated Access        QM-2CLAA-A[*] C PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS          QM-A93AA-A[*]_C PATHWORKS V5.0 for OpenVMS (LAN Manager) PC           QM-A93AA-A[*]m9 concurrent                                               mC ____________________________________________________________________ [*]Variable field_C ___________________________________________________________________                             "                                 45 K  5  C ___________________________________________________________________   % Table 5: Upgrade License Part Numbers.C ___________________________________________________________________I                       Number of B Part Number         Licenses            Number of Licenses per PAKC ___________________________________________________________________b  3 QM-5SUAA-CA            1                Variable[1]O, QM-5SUAA-CB            1                   1, QM-5SUAA-CC           10                  10, QM-5SUAA-CD           25                  25, QM-5SUAA-CE           50                  50, QM-5SUAA-CF          100                 100, QM-5SUAA-CG          250                 250, QM-5SUAA-CH          500                 500, QM-5SUAA-CJ         1000                1000C ___________________________________________________________________ 6 [1]Equals total quantity ordered as a single line itemC ___________________________________________________________________r    Software Media and Documentation  ? Software media and documentation are available in the followingc formats:      QA-A93AA-H8, CD-ROM media    QA-A93AA-H5, TK50 media!    QA-A93AA-GZ, Documentation kite  > In addition, PATHWORKS V6.0A for OpenVMS (Advanced Server) andE PATHWORKS V5.0F1 for OpenVMS (LAN Manager) software and documentationh are included in the following:  ?    QA-03XAA-H8, DIGITAL OpenVMS Alpha Software Layered Productsa    Library Package  E PATHWORKS V5.0F1 for OpenVMS (LAN Manager) software and documentationt are included in the following:  =    QA-5G88A-H8, DIGITAL OpenVMS VAX Software Layered Products5    Library Package  "                                 46 t     A This information is valid at time of release. Please contact yourT9 local DIGITAL office for the most up-to-date information.M   SOFTWARE PRODUCT SERVICES0  A A variety of service options are available from DIGITAL. For mores/ information, contact your local DIGITAL office.    SOFTWARE WARRANTY   > This software is provided by DIGITAL with a 90-day conformanceA warranty in accordance with the DIGITAL warranty terms applicableu to the license purchase.                                                      "                                 47 t  n    B [R]  Apple, Appleshare, and Macintosh are registered trademarks of      Apple Computer, Inc.W= [R]  AT&T is a registered trademark of American Telephone andn      Telegraph Corporation.y; [R]  EPSON is a registered trademark of Epson America, Inc.pI [R]  IBM, OS/2, and ProPrinter are registered trademarks of International0#      Business Machines Corporation. > [R]  Microsoft, MS-DOS, Windows, and Windows 95 are registered)      trademarks of Microsoft Corporation. > [TM] MultiNet and TCPWARE are registered trademarks of Process      Software Corporation.H [R]  PostScript is a registered trademark of Adobe Systems Incorporated.6 [TM] SCO is a trademark of Santa Cruz Operations, Inc.? [R]  SilentWriter is a registered trademark of NEC Corporation.eB [R]  UNIX is a registered trademark in the United States and otherA      countries, licensed exclusively through X/Open Company, Ltd.5; [TM] NetBIOS is a trademark of Micro Computer Systems, Inc.cD [TM] Process Software Corporation is a trademark of Process Software      Corporation.d8 [TM] Windows NT is a trademark of Microsoft Corporation.< [TM] DEC, DECnet, DECnet-Plus, DECprint, DECserver, DIGITAL,=      LA75, LA324, LAT, LN03, ManageWORKS, OpenVMS, PATHWORKS,a:      PrintServer, TK, ULTRIX, VAX, VAXserver, VMS, and theB      DIGITAL logo are trademarks of Digital Equipment Corporation.  < (c) 1998 Digital Equipment Corporation. All Rights Reserved.                        "                                 48                                                                                                                                                                                                                                                                                                                                                                                                                                                                    