DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: PATHWORKS V1.0E for OpenVMS SPD 41.47.05 (NetWare) DESCRIPTION PATHWORKS V1.0E for OpenVMS (NetWare[R]) is an OpenVMS layered appli- cation that provides the functions of a NetWare V3.x server in a PC LAN environment. It is a member of the PATHWORKS family of products, which provides a framework for integrating personal computers into an organization's total information system, allowing different types of users to share information and network services across the entire or- ganization. The PATHWORKS family includes PC LAN server products running on Open- VMS, Digital UNIX[R], ULTRIX, SCO[TM] UNIX, and OS/2[R] platforms pro- viding industry standard Network Operating System (NOS) services that use Novell[R]'s NetWare, Microsoft[R]'s LAN Manager, and Apple[R]'s AppleShare[R] protocols. The PATHWORKS family also includes client prod- ucts providing both client software for these servers and enterprisewide support capabilities such as wide area transports (DECnet and TCP/IP) and applications such as Mail and Terminal Emulation, allowing DOS, Windows[TM], Windows 95, Windows NT[TM], OS/2, and Macintosh[R] clients to participate as full peers in a widely-distributed computing envi- ronment. December 1996 AE-PPMGF-TH Features - Overview PATHWORKS for OpenVMS (NetWare) adds a new dimension to general pur- pose OpenVMS systems. In addition to providing traditional support for business, scientific, and engineering applications, this product al- lows OpenVMS systems to appear to NetWare clients as Novell-certified NetWare servers. The major features of PATHWORKS V1.0E for OpenVMS (NetWare) include: o Novell-certified file and print services using Novell's NetWare Core Protocol and the IPX/SPX transports. o Access to services provided by PATHWORKS V1.0E for OpenVMS (Net- Ware) available to PATHWORKS and other NetWare clients (with ap- propriately licensed components, see License Management section for details). o Files are stored on the server in native OpenVMS format. This al- lows information stored by the PCs using PATHWORKS V1.0E for Open- VMS (NetWare) to be shared with traditional OpenVMS users. In par- ticular, this feature allows the sharing of information between all PATHWORKS clients, even if they are not using NetWare. o Printing support not only allows NetWare clients to use an Open- VMS system running PATHWORKS V1.0E for OpenVMS (NetWare) to act as a generic NetWare Print Server, but this support also allows in- teractive OpenVMS users to direct jobs to remote, native NetWare print servers by simply directing their print jobs to local Open- VMS print queues. o File and print services management using standard NetWare manage- ment utilities, such as FCONSOLE, PCONSOLE, and SYSCON. These func- tions, combined with other standard systems and network management utilities for OpenVMS, such as Remote System Management (RSM), pro- vide a powerful set of tools for total distributed systems manage- ment. o Either NetWare-only, or NetWare combined with OpenVMS security mod- els can be applied in this environment, providing greater flexi- bility and added security to your system. 2 o A mail server is provided that works in conjunction with the Open- VMS Mail utility and the PATHWORKS Mail client to provide clients with access to enterprisewide electronic mail over DECnet. o A DECnet tunnel-function for the IPX transport is provided. This function encapsulates IPX packets in DECnet packets, thereby al- lowing information sent over IPX to be transported anywhere within a DECnet network. This allows existing DECnet-based wide area net- works (WANs) to be used to transport IPX-based traffic from IPX lo- cal area networks (LANs) on one side of the WAN to another. o New Novell Virtual Terminal (NVT2) support is provided, employing SPX as the new underlying transport. NVT2 support provided for DOS clients allows IPX-based terminal emulation software to be used on a PC for direct, interactive connections to the OpenVMS systems where PATHWORKS V1.0E for OpenVMS (NetWare) is operating. o NetWare (file and print) Application Programming Interfaces (APIs) are provided o The host-based SCONSOLE Utility provides systems managers and ad- ministrators with a single menu-driven tool to configure and ad- minister OpenVMS-specific functions such as starting and stopping the file server, the IPX/SPX transports, or the DECnet tunneling function for IPX. o License Management software, now capable of supporting PATHWORKS users of both NetWare and LAN Manager clients, provides the capa- bility to: a. Distribute PATHWORKS client-based licenses across a network b. Validate access by clients with PATHWORKS client-based licenses c. Support client access using server-based licenses validated through the local OpenVMS License Management Facility (LMF) database Note that (a) and (b) above are accomplished in conjunction with PATH- WORKS license management software for the client. 3 Feature Details o NetWare Volumes/File Services PATHWORKS V1.0E for OpenVMS (NetWare) provides NetWare clients with a remote file system that appears as a transparent extension of the client system's local computing environment. PATHWORKS V1.0E for OpenVMS (NetWare) services are based on Novell's NCP (NetWare Core Protocol) protocols and have been certified by Nov- ell as a fully compliant implementation of Portable NetWare, V3.01B. There are three types of RMS file formats allowed and supported on each volume: . Stream . Sequential Fixed Length Record (512 bytes/record) . Sequential Fixed Length Record of a specified record size (1 to 32K bytes/record) Included with PATHWORKS V1.0E for OpenVMS (NetWare) is a feature called a hybrid user. This feature allows users who are both interactive Open- VMS users and users of PATHWORKS V1.0E for OpenVMS (NetWare) to ac- cess both their NetWare created information and their interactive Open- VMS user directory while logged in as a NetWare user. If you are identified as a hybrid user, a special volume called HOME is created when you log in. HOME points to your login directory of your OpenVMS account. You can map drives to this HOME volume and/or to di- rectories below it. You have access rights to all files in that di- rectory just as if you were logged in to your account on OpenVMS. Multiple NetWare clients can concurrently access files stored on the server's disk through the file access modes and byte-range locking sup- port provided by the server as defined by Novell's NCP protocol. Through the use of the VMS Lock Manager, OpenVMS and PC-based appli- cations can control file access. o Print Services 4 PATHWORKS V1.0E for OpenVMS (NetWare) software allows NetWare clients to access printers also used by interactive OpenVMS users and other PATHWORKS clients that may not be using NetWare. These printers can be connected to the OpenVMS server, OpenVMS cluster, or LAT-supported terminal servers in a LAN. The system administrator assigns a service name, called a NetWare print queue, to an OpenVMS print queue, and can define NetWare user access to the print service. NetWare client software can redirect printer I/O from a client printer port to a defined NetWare print queue. The system administrator creates, on the host, the physical and generic queues and defines forms for selected Digital and third-party print- ers using standard OpenVMS commands. The administrator then uses the PATHWORKS V1.0E for OpenVMS (NetWare) SCONSOLE utility to associate NetWare print queues with OpenVMS print queues. Refer to the Optional Hardware section for details. Multiple NetWare print queues may be set up for the same printer. For example, a landscape service and a portrait service may be created for the same PrintServer 40 Plus printer. In addition, other printer queues can be manually set to support additional Digital and third-party print- ers that are not listed in the menus. NetWare print queues and the NetWare print servers servicing those queues may reside on different physical systems. Because PATHWORKS for Open- VMS (NetWare) includes a NetWare-compliant PSERVER implementation, it is compatible with all versions of Novell's print servers, including: . NetWare 3.X (PSERVER.NLM) . NetWare 2.X (PSERVER.VAP) . Dedicated DOS (PSERVER.EXE) . Network printers providing a NetWare compliant PSERVER imple- mentation . Router VAP . NetWare for UNIX print server daemons 5 Note that compatibility with "NetWare for UNIX print server daemons" means that PATHWORKS V1.0E for OpenVMS (NetWare) will interoperate with any other Novell Certified implementation of NetWare for UNIX provided by Digital or by other vendors. Any type of NetWare print server is capable of servicing NetWare print queues located on any NetWare file server. In order to service Net- Ware print queues associated with remote NetWare file servers, a PATH- WORKS V1.0E for OpenVMS (NetWare) print server must be configured to attach to each NetWare file server associated with each NetWare print queue that it will service. Similarly, in order to be serviced by remote NetWare print servers, a PATHWORKS V1.0E for OpenVMS (NetWare) print queue would need to be configured to allow this access. NetWare clients that are logged into a PATHWORKS V1.0E for OpenVMS (Net- Ware) file server can also access other NetWare print services avail- able in the network, either by attaching directly to the associated NetWare file server or using the PCONSOLE utility. Interactive OpenVMS users can also queue print jobs to remote Net- Ware print servers by simply queuing their to normal OpenVMS print queues that have been set up by PATHWORKS V1.0E for OpenVMS (Net- Ware) to send print jobs to the desired remote NetWare print server. 6 o Server Management and Control SCONSOLE, an OpenVMS Utility used in conjunction with standard Net- Ware client utilities, provides the complete set of tools needed to manage the PATHWORKS V1.0E for OpenVMS (NetWare) server. SCONSOLE is used to manage OpenVMS-specific functions related to this product. In particular, SCONSOLE is used to: . Start and stop the server, in its entirety or in part . Create, modify, and remove volumes . Associate NetWare print queues with OpenVMS print queues . Modify server security settings . Add and delete hybrid users . Configure and tune server components . Display server specific statistics and information o Network Connectivity - IPX/SPX The PATHWORKS V1.0E for OpenVMS (NetWare) software includes an Open- VMS implementation of the two transport protocols used by Novell's na- tive NetWare products: . IPX - Internetwork Packet Exchange . SPX - Sequenced Packet Exchange IPX is delivered as a STREAMS driver in this product and is used for all NetWare related client/server functions. The IPX protocol is trans- mitted as datagram packets between source and destination. SPX provides a layer above the IPX protocol that tracks IPX packets to ensure that each packet is successfully received by its intended destination. - Novell Virtual Terminal (NVT2) Protocol NVT2 support consists of server software and software that must be loaded on each client. 7 On the PATHWORKS V1.0E for OpenVMS (NetWare) server, an OpenVMS pro- cess provides Virtual Terminal services over SPX (using IPX). Each NVT2 connection requires a corresponding SPX connection. Therefore, a max- imum of 1,000 concurrent NVT2 connections can be supported. The NVT2 software for DOS-based clients (TSR or VLM) redirects ter- minal I/O through INT14 or INT6b interrupt modes, the interfaces used by most terminal emulation applications. Note that the PATHWORKS V5.x for DOS and Windows SETHOST terminal emulation application also uses these interfaces. - IPX Tunneling within DECnet PATHWORKS V1.0E for OpenVMS (NetWare) includes a capability of con- necting one or more NetWare LANs using a DECnet WAN. The tunnel driver encapsulates IPX datagrams within DECnet packets transmitted across the DECnet network to the tunnel partner and then de-encapsulates the IPX datagram, routing it to its intended destination. o Performance-Enhancing XQP+ Services PATHWORKS V1.0E for OpenVMS (NetWare) includes a special release of the enhanced OpenVMS file system, known as XQP+ (eXtended QIO Proces- sor Plus). XQP+ is integral to OpenVMS V6.1, or greater, and is sep- arately installable on VAX/VMS V5.5-2 and OpenVMS VAX V6.0 systems. XQP+ provides improved concurrency using multi-threading, which results in improved performance for file system operations. o Mail Services The mail server component of PATHWORKS V1.0E for OpenVMS (NetWare) pro- vides a service that is separate and distinct from the NetWare file and print services. This mail server is based on the OpenVMS MAIL util- ity and requires DECnet as its communications transport. It allows PATH- WORKS users, using the client PATHWORKS Mail software, to send and re- ceive electronic mail messages without having to log in to the Open- VMS system as an interactive user. 8 A mail account may be established on the OpenVMS server for each user. Mail can be sent to this account by other PATHWORKS Mail users as well as traditional users of OpenVMS mail software. The mail server then routes messages to the appropriate client when the user logs onto the server. The PATHWORKS V1.0E for OpenVMS (NetWare) mail server provides the PATH- WORKS user with folders, distribution lists, and delivery capabili- ties. Also, notification of new messages occurs both in realtime (which may be optionally disabled) and upon log in to a network MAIL session. o Installation and Configuration PATHWORKS V1.0E for OpenVMS (NetWare) and PATHWORKS V5.0E for Open- VMS (LAN Manager) software are now distributed together (though still licensed separately_) in a single media and documentation kit. There is a single installation procedure that is shared between the two prod- ucts that provides for the installation of one or both server prod- ucts in a single step on an OpenVMS system using the standard VMSIN- STAL procedure. An Installation Verification Procedure (IVP) is also included, which can be used to confirm that all server software has been installed properly. Digital recommends that a customer's first purchase of this software product at each site include Digital installation service. This ser- vice provides implementation support for customers installing PATH- WORKS V1.0E for OpenVMS (NetWare) software and for the integration of DOS workstations into the Digital network. Contact your local Digi- tal representative for information on the service options available. o License Management PATHWORKS V1.0E for OpenVMS (NetWare) offers several license manage- ment capabilities related to both client-based and server-based li- censes. - Client-based License Management 9 PATHWORKS client licenses are provided as Product Authorization Keys (PAKs) for the OpenVMS or Digital UNIX License Management Facility (LMF). These PAKs must be loaded into an LMF database, using standard LMF pro- cedures, on an OpenVMS or Digital UNIX system that is acting as a PATH- WORKS License Server [1]. A single copy of the PATHWORKS License Server software can now provide and verify client-based licenses for clients using NetWare and LAN Manager software. NetWare clients use the IPX transport to communicate with a PATHWORKS License Server, while LAN Manager clients use the DECnet, NetBEUI, or TCP/IP transports. The PATHWORKS License Manager, which must execute on the same node as the license server, provides a user interface that allows the system manager to monitor client license usage. The PATHWORKS License Man- ager is also used to pre-allocate licenses to specific groups of users and to reclaim a license from a client. The PATHWORKS License Registrar, which executes on the same system as the file server, will "handshake" with clients requesting access to PATHWORKS V1.0E for OpenVMS (NetWare) functions. Clients that can suc- cessfully "handshake" with the server and produce a valid client-based license will be allowed access to the services offered by the PATH- WORKS V1.0E for OpenVMS (NetWare) server. - Server-based License Management The PATHWORKS V1.0E for OpenVMS (NetWare) server also allows client access based on a local server-based license. If a client requesting access to the server fails to produce a valid client-based license, the PATHWORKS License Registrar software checks the local LMF database for the availability of a PATHWORKS V1.0E for OpenVMS (NetWare) FPS license. If one is available, and the number of concurrently-connected clients allowed by the license has not been exceeded, the client will be allowed access. ____________________ Note that, although the license server can be active only on a sin- gle node in a cluster, if that node goes down for any reason, the li- cense server will automatically activate itself on another node in the cluster that is still running PATHWORKS. 10 Note that PATHWORKS V1.0E for OpenVMS (NetWare) servers always allow you to use both client-based and server-based licenses, simultaneously. However, since clients that do have a valid client-based license are already licensed to use the server software, they are never counted against the fixed number of clients granted access by the server-based FPS license. 11 Restrictions and Limitations o NetWare NLMs are not usable with a PATHWORKS V1.0E for OpenVMS (Net- Ware) server. NetWare NLMs are typically applications or utilities written specifically for an Intel platform using NetWare 3.x or for an Intel platform using NetWare 4.x as the host operating system and are not easily portable to other environments. o Version 3.01B PATHWORKS V1.0E for OpenVMS (NetWare) is an implementation of Portable NetWare, V3.01B. As such, certain features currently available in Nov- ell NetWare 3.x Intel-based servers are not included. Among these fea- tures are: - The PATHWORKS V1.0E for OpenVMS (NetWare) print server imple- mentation cannot be used in conjunction with DOS based clients configured with RPRINTER.EXE or network based printers that im- plement NetWare's RPRINT protocol. - Burst mode technology, or "packet burst", is not supported o The DOS utilities specific to PC hardware devices such as CHKDSK, FDISK, DISKCOPY, DISKCOMP and FORMAT cannot be used with PATHWORKS server volumes. o Unsupported wire protocols include: - Ethernet using IEEE 802.3 (SNAP) frame-type (used mainly by Mac- intosh systems) - Arcnet - Token Ring on VAX systems (Token Ring on Alpha systems is sup- ported) o The OpenVMS Spiralog file system is not supported. o Though Novell's raw 802.3 Ethernet frame-type is supported, because it does not conform to the IEEE specifications, some usage restric- tions will always apply. In particular, this frame-type should not be used on any OpenVMS using the DECnet/OSI protocol (the default 12 for OpenVMS V7.1 and later). See product documentation for addi- tional info. o PATHWORKS V1.0E for OpenVMS (NetWare) is not supported with Open- VMS VAX, Version 6.0, or with OpenVMS AXP, Version 1.5. o The NetWare utility Salvage is not supported (incompatible with the OpenVMS file system). o PATHWORKS V1.0E for OpenVMS (NetWare) supports a maximum of - 250 simultaneous users per OpenVMS node (an inherent NetWare 3.x limitation). - 250 NetWare volumes. - 1,000 SPX connections (each NVT2 session uses an SPX connection). o Though NetWare volumes may be dynamically marked for addition or deletion, volumes are only added or deleted when the server is restarted. HARDWARE REQUIREMENTS The following systems, components, and peripherals are supported as specified below: Supported Processors All VAX and Alpha processors that are supported by the version of Open- VMS in use are also supported by PATHWORKS V1.0E for OpenVMS (NetWare), with the following exceptions : MicroVAX: MicroVAX I, MicroVAX II, MicroVAX 2000 VAXstation:VAXstation I, VAXstation II, VAXstation 2000, VAXstation 8000 13 VAX: VAX-11/725, VAX-11/730, VAX-11/750 VAX-11/780, VAX-11 /785 Memory Requirements PATHWORKS V1.0E for OpenVMS (NetWare) requires the following physi- cal memory for proper installation, configuration, and execution of the software: 16 MBytes on VAX systems (24 MBytes if used with DECnet/OSI) 64 MBytes on Alpha systems Note that the memory requirements indicated above are minimum require- ments to install and run the server. Memory requirements can vary widely according to the server CPU, the number of clients using the server and their activities, and the other applications running on the server system. The recommended minimum is twice memory of the absolute minimums spec- ified above. Disk Space Requirements The following table provides the disk space requirements for the in- stallation and configuration of PATHWORKS V1.0E for OpenVMS (NetWare) either stand-alone or with PATHWORKS V5.0E for OpenVMS (LAN Manager) software. Note that each of the four entries in this table may be di- rected to different disks, but, by default, all entries will be di- rected to the same disk. 14 Installation/Configuration_________________________________________ Requirements____________________VAX_systems____Alpha_systems_______ Installation Space Require- ments[1]: Images and command files: NetWare software, only 20,000 32,000 blocks blocks with LAN Manager 44,000 66,000 blocks software blocks NetWare System Volume[2] 34,000 34,000 blocks blocks Configuration Space Require- ments: PATHWORKS server data files: NetWare software, only 6,000 6,000 blocks blocks with LAN Manager 12,500 12,500 blocks software blocks NetWare Configuration files, 1,000 1,000 blocks etc.[3] blocks Totals: NetWare software, only 61,000 73,000 blocks blocks with LAN Manager 91,500 113,500 blocks software blocks ___________________________________________________________________ [1]Note: These values represent the approximate permanent space required for product installation. Another 6,000 blocks of tempo- rary space is required during the actual installation process. [2]The NetWare SYS Volume contains the NetWare utilities used by NetWare clients. [3]These_files_are_typically_stored_on_the_OpenVMS_system_disk.____ These sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. 15 You should also plan for additional, significant disk-space require- ments once the product is in use, for items such as data files, vir- tual memory section files, log files, and so forth. Network Interface Controllers At least one network interface controller is required for use with PATH- WORKS V1.0E for OpenVMS (NetWare). The following devices are supported: o All Digital VAX and Alpha Ethernet controllers Supported Ethernet frame-types include: - Ethernet_II - IEEE 802.3 (SAP) (Note: Novell refers to this frame-type as "802.2") - Raw 802.3 (Note: Novell refers to this frame-type as "802.3") (See restrictions in "Restrictions" section) o All Digital VAX and Alpha FDDI controllers o All Digital Token Ring controllers for Alpha systems. Optional Hardware Digital Printers All printers supported by the OpenVMS Operating System using print queues are also supported by PATHWORKS V1.0E for OpenVMS (NetWare). Note that Digital PostScript[R] printers require the use of DECprint Supervisor (DCPS) for OpenVMS. DCPS software is included with the PATH- WORKS V1.0E for OpenVMS (NetWare) media, but the use of the DCPS soft- ware requires the purchase of an appropriate license. Refer to SPD 44.15.xx for DCPS licensing information and for a com- plete list of the Digital and non-Digital PostScript printers supported by DCPS. 16 The NetWare Print Definition Files (.PDF) are provided for the fol- lowing printers: . Colormate PS . DEClaser 1100 . DEClaser 1150 . DEClaser 1152 . DEClaser 2100 . DEClaser 2100 plus . DEClaser 2150 . DEClaser 2150 plus . DEClaser 2200 . DEClaser 2200 plus . DEClaser 2250 . DEClaser 2250 plus . DEClaser 3200 . DEClaser 3250 . LA70 . LA75 . LA75 Plus . LA210 . LA310 . LA324 . LA424 . LJ250 . LN03 . LN03 PLUS . LN03R ScriptPrinter . PrintServer 17 . PrintServer 20 . turbo PrintServer 20 . PrintServer 32 17 . PrintServer 40 . PrintServer 40 Plus CLUSTER ENVIRONMENT The PATHWORKS V1.0E for OpenVMS (NetWare) server provides for a com- mon NetWare SYS volume across cluster members running the server. This means that a single bindery and trustee database is maintained clus- terwide. In addition, NetWare volumes can also be made available clusterwide. A volume, defined via SCONSOLE on one cluster member running the server, can also be configured so that it is available to all other cluster servers. However, concurrent file sharing between servers running on different cluster members is not supported. SOFTWARE REQUIREMENTS Operating System Software For Alpha Systems: o OpenVMS Alpha Operating System V6.1, V6.2, V7.0 and V7.1 For VAX Systems: o VAX/VMS Operating System V5.5-2 o OpenVMS VAX Operating System V6.1, V6.2, V7.0, and V7.1 For minimum hardware requirements of the operating system refer to the Software Product Descriptions for the OpenVMS VAX operating system (SPD 25.01.xx) and the OpenVMS AXP operating system (SPD 41.87.xx). OpenVMS Tailoring For use with VAX/VMS V5.5-2 systems, the following OpenVMS classes are required for full functionality of this layered product: . OpenVMS Required Saveset . Network Support 18 . System Programming Support . Secure User's Environment . OPTL - Miscellaneous Files For more information on OpenVMS classes and tailoring, refer to the OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx). Network Transport Software o DECnet Software The DECnet network transport software is required by PATHWORKS V1.0E for OpenVMS (NetWare): - when acting as a MAIL server for PATHWORKS clients - to optionally tunnel IPX packets between two OpenVMS systems us- ing this software - when the PATHWORKS License Server is configured to service PATH- WORKS clients using LAN_Manager and DECnet The license to use DECnet software is usually bundled with your sys- tem, but may need to be purchased separately. Note that because the DECnet/IPX tunnel is a DECnet Phase IV imple- mentation, its use on systems with DECnet/OSI installed requires the definition of network name synonyms. o TCP/IP Software TCP/IP network transport software is only required by PATHWORKS V1.0E for OpenVMS (NetWare) if the PATHWORKS License Server is configured to service PATHWORKS clients using LAN_Manager and TCP/IP. When TCP/IP software is used for this purpose, it must be purchased separately. The following TCP/IP transports are known to work with the PATHWORKS License Server: . TCP/IP Services for OpenVMS V4.1 from Digital Equipment Cor- poration . Multinet[TM] V3.5 rev A from TGV[R], Inc. . TCPware[R] for OpenVMS V5.0-4 from Process Software Corpora- tion[R] 19 . PathWay V1.1 from The Wollongong Group, Inc. Associated PATHWORKS Server Software PATHWORKS V1.0E for OpenVMS (NetWare) and PATHWORKS V5.0E for Open- VMS (LAN Manager) now share some components. As a result, certain com- binations of PATHWORKS server software cannot be run on the same ma- chine at the same time. The following PATHWORKS server products can be run on the same sys- tem as PATHWORKS V1.0E for OpenVMS (NetWare): PATHWORKS for VMS, V4.x[1] PATHWORKS V5.0E for OpenVMS (LAN Manager)[1] PATHWORKS V1.x for OpenVMS (Macintosh) The following PATHWORKS server products cannot be run on the same sys- tem as PATHWORKS V1.0E for OpenVMS (NetWare): PATHWORKS V1.0 for OpenVMS (NetWare) PATHWORKS V1.0C for OpenVMS (NetWare) PATHWORKS V5.0 for OpenVMS (LAN Manager) PATHWORKS V5.0A for OpenVMS (LAN Manager) PATHWORKS V5.0B for OpenVMS (LAN Manager) PATHWORKS V5.0C for OpenVMS (LAN Manager) PATHWORKS V5.0D for OpenVMS (LAN Manager) Note that if you attempt to install PATHWORKS V1.0E for OpenVMS (Net- Ware) on a system running any of the software listed above, you will automatically be given the option to upgrade related components to a compatible version. Associated Client Software ____________________ Note that PATHWORKS for VMS, V4.x and PATHWORKS V5.0E for OpenVMS (LAN Manager) cannot be run on the same system at the same time 20 The following software products may be used on personal computers to access PATHWORKS for OpenVMS (NetWare) server software: o PATHWORKS V6.0 or V5.x for DOS and Windows (SPD 55.07.xx) o PATHWORKS V5.1 for OS/2 (SPD 55.24.xx) o NetWare clients using the latest, supported version of Novell's client shell, NETX.EXE. o NetWare clients using the latest, supported version of Novell's client VLM redirector. Note that PATHWORKS V1.0E for OpenVMS (NetWare) will appear as a Net- Ware for UNIX V3.01B server (or a NetWare V3.0 server) to all clients. GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements for the cur- rent version. SOFTWARE LICENSING AND ORDERING INFORMATION PATHWORKS V1.0E for OpenVMS (NetWare) can be licensed in two differ- ent ways. 1. Client-based licensing (CCS or FPA) This product can be licensed for operation and access on any number of supported platforms to provide services to clients assigned appro- priate client-based licenses. See the attached PATHWORKS license terms and conditions for CCS (Sec- tion 1) and FPA (Section 2) licenses for a description of the specific rights granted, and the Applicable Client-based Licenses section be- low for specific license names and ordering information. 2. Server-based licensing (FPS) 21 A PATHWORKS FPS license for this product permits its use on a single supported platform and allows access by clients that do not have a PATH- WORKS client-based license. See the attached PATHWORKS License terms and conditions for FPS (Sec- tion 4) licenses for a description of the specific rights granted, and the Applicable Server-based Licenses section below for specific li- cense names and ordering information. Note: Clients with client-based licenses for server access do not in- terfere with the access of other clients that rely on server-based li- censing for access to a particular server. The two licensing methods are designed to coexist. Applicable Client-based Licenses o PATHWORKS V6.0 for DOS and Windows (NetWare) CCS For new users, order: QM-0EKAA-AA (variable number of licenses per PAK) QM-0EKAA-A*[1] (fixed number of licenses per PAK) Please refer to the specific terms in the attached "Digital License Agreement for PATHWORKS Programs" for a description of the rights as- sociated with PATHWORKS V6.0 for DOS and Windows (NetWare) CCS licenses. o PATHWORKS V5.1 for OS/2 (NetWare) CCS For new users, order: QM-506AA-AA (variable number of licenses per PAK) QM-506AA-A*[1] (fixed number of licenses per PAK) Please refer to the specific terms in the attached "Digital License Agreement for PATHWORKS Programs" for a description of the rights as- sociated with PATHWORKS V5.1 for OS/2 (NetWare) CCS licenses. ____________________ Reference current price lists for available part numbers 22 o PATHWORKS V5.0 (NetWare) FPA For new users, order: QM-2CMAA-AA (variable number of licenses per PAK) QM-2CMAA-A*[1] (fixed number of licenses per PAK) Please refer to the specific terms in the attached "Digital License Agreement for PATHWORKS Programs" for a description of the rights as- sociated with PATHWORKS V5.0 (NetWare) FPA licenses. Applicable Server-based Licenses o PATHWORKS V1.0 for OpenVMS (NetWare) FPS: For new users, order: QM-0ENAA-AB, 10-user QM-0ENAA-AC, 25-user QM-0ENAA-AD, 50-user QM-0ENAA-AE, 100-user QM-0ENAA-AF, 250-user Please refer to the specific terms in the attached "Digital License Agreement for PATHWORKS Programs" for a description of the rights as- sociated with PATHWORKS V1.0 for OpenVMS (NetWare) FPS licenses. Software Media and Documentation Software media and documentation is available in the following for- mats: QA-A93AA-H5 (TK50 streaming tape; for VAX systems) QA-A93AA-H8 (CDROM; for VAX and AXP systems) In addition, PATHWORKS V1.0E for OpenVMS (NetWare) software and doc- umentation is included in the following: QA-03XAA-H8 (Digital CDROM Software Library for OpenVMS AXP) 23 QA-VWJ8A-A8 (OpenVMS VAX Consolidated Distribution) The above information is valid at time of release. Please contact your local Digital sales representative for the most up-to-date informa- tion. SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. For more in- formation, please contact your local Digital sales representative. [R] Apple, AppleShare, and Macintosh are registered trademarks of Apple Computer, Inc. [R] Microsoft is a registered trademark of Microsoft Corporation. [R] NetWare and Novell are registered trademarks of Novell, Inc. [R] OSF/1 is a registered trademark of Open Software Foundation, Inc. [R] OS/2 is a registered trademark of International Business Ma- chines Corporation. [R] PostScript is a registered trademark of Adobe Systems, Inc. [R] TCPware and Process Software Corporation are registered trade- marks of Process Software Corporation [R] TGV is a registered trademark of TGV, Inc. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. [TM]MultiNet is a trademark of TGV, Inc. [TM]SCO is a trademark of Santa Cruz Operations, Inc. [TM]Windows and Windows NT are trademarks of Microsoft Corporation. 24 [TM]The DIGITAL Logo, DEC, DEClaser, DECnet, DECprint, DECserver, DECwindows, Digital, Internet, LAT, LA324, LN03, LN03 PLUS, MicroVAX, OpenVMS, PATHWORKS, PrintServer, ULTRIX, VAX, VAX-11 /750, VAX-11/780, VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 6000, VAX 9000, VAXft, VAXclus- ter, VAXserver, VAXstation, VAXstation 4000 VLC, and VMS are trademarks of Digital Equipment Corporation. ©1996 Digital Equipment Corporation. All Rights Reserved. 25 DIGITAL LICENSE AGREEMENT for PATHWORKS Programs STOP! IMPORTANT - CAREFULLY READ THE DIGITAL LICENSE AGREEMENT BEFORE PRO- CEEDING. IF YOU DO NOT AGREE TO ITS TERMS, PLEASE RETURN THE LICENSE AGREEMENT AND ALL ACCOMPANYING MATERIALS WITHOUT FURTHER OPENING OR USING THEM. RETURN THEM TO THE SUPPLIER FROM WHICH YOU OBTAINED THEM FOR A FULL REFUND. FURTHER OPENING OR USE OF THE MATERIALS INDICATES YOUR ACCEPTANCE OF THE TERMS OF THE LICENSE AGREEMENT. A Product Authorization Key constitutes proof of license, and is re- quired to permit use of the Software in accordance with these terms. 26 LICENSE TERMS PATHWORKS_CCS_Licenses: A. License: PATHWORKS V6.0 for DOS and Windows[R] (LAN Manager) CCS or License: PATHWORKS V6.0 for DOS and Windows (LAN Manager) CCS- UPGRADE [*] When you purchase either of the above licenses you may use the fol- lowing programs ("Software") under the terms in Section 1 and all terms provided in Additional Terms below. Client Programs: PATHWORKS V6.0 for DOS and Windows PATHWORKS X.25 (DOS), any version PATHWORKS ISDN[R] (DOS), any version PATHWORKS for DOS (NetWare[R] Coexistence), any version PATHWORKS Remote for DOS and Windows, any version Server Programs: PATHWORKS V5.0 for OpenVMS (LAN Manager) PATHWORKS for ULTRIX, V1.3 PATHWORKS V6.1 for Digital UNIX[R] (Advanced Server) PATHWORKS for SCO[TM] UNIX, V1.1 ____________________ See special terms for UPGRADE licenses in the GRANT section under Ad- ditional Terms below. 27 B. License: PATHWORKS V4.1 for Windows NT[TM] (LAN Manager) CCS When you purchase the above license you may use the following programs ("Software") under the terms in Section 1 and all terms provided in Additional Terms below. Client Program: PATHWORKS V4.1 for Windows NT Server Programs: PATHWORKS V5.0 for OpenVMS (LAN Manager) PATHWORKS for ULTRIX, V1.3 PATHWORKS V6.1 for Digital UNIX (Advanced Server) PATHWORKS for SCO UNIX, V1.1 C. License: PATHWORKS V5.1 for OS/2[R] (LAN Manager) CCS or License: PATHWORKS V5.1 for OS/2 (LAN Manager) CCS-UPGRADE [*] When you purchase either of the above licenses you may use the fol- lowing programs ("Software") under the terms in Section 1 and all terms provided in Additional Terms below. Client Program: PATHWORKS V5.1 for OS/2 Server Programs: PATHWORKS V5.0 for OpenVMS (LAN Manager) PATHWORKS for ULTRIX, V1.3 PATHWORKS V6.1 for Digital UNIX (Advanced Server) PATHWORKS for SCO UNIX, V1.1 ____________________ See special terms for UPGRADE licenses in the GRANT section under Ad- ditional Terms below. 28 D. License: PATHWORKS V6.0 for DOS and Windows (NetWare) CCS or License: PATHWORKS V6.0 for DOS and Windows (NetWare) CCS-UPGRADE [*] When you purchase either of the above licenses you may use the fol- lowing programs ("Software") under the terms in Section 1 and all terms provided in Additional Terms below. Client Programs: PATHWORKS V6.0 for DOS and Windows PATHWORKS X.25 (DOS), any version PATHWORKS ISDN (DOS), any version PATHWORKS for DOS (NetWare Coexistence), any version PATHWORKS Remote for DOS and Windows, any version Server Programs: PATHWORKS V1.0 for OpenVMS (NetWare) PATHWORKS V5.0 for Digital UNIX (NetWare) E. License: PATHWORKS V5.1 for OS/2 (NetWare) CCS When you purchase the above license you may use the following programs ("Software") under the terms in Section 1 and all terms provided in Additional Terms below. Client Programs: PATHWORKS V5.1 for OS/2 Server Programs: PATHWORKS V1.0 for OpenVMS (NetWare) PATHWORKS V5.0 for Digital UNIX (NetWare) ____________________ See special terms for UPGRADE licenses in the GRANT section under Ad- ditional Terms below. 29 F. License: PATHWORKS V1.3 for Macintosh[R] CCS When you purchase the above license you may use the following programs ("Software") under the terms in Section 1 and all terms provided in Additional Terms below. Client Program: PATHWORKS V1.3 for Macintosh Server Programs: PATHWORKS V1.3 for OpenVMS (Macintosh) Section 1 Terms For purposes of these terms a client computer ("Licensed Client") is a computer that has been assigned one of these licenses by the PATHWORKS license server. The number of Licensed Clients may not exceed the Quantity specified in the associated Product Authoriza- tion Key. You may copy and use the client Software identified above only on a Licensed Client. You may copy, access, and use the server Software iden- tified above on any number of server systems, provided that this ac- cess is only by Licensed Clients. 30 PATHWORKS_FPA_Licenses: A. License: PATHWORKS V5.0 (LAN Manager) FPA When you purchase the above license you may use the following programs ("Software") under the terms in Section 2 and all terms provided in Additional Terms below. Server Programs: PATHWORKS V5.0 for OpenVMS (LAN Manager) PATHWORKS for ULTRIX, V1.3 PATHWORKS V6.1 for Digital UNIX (Advanced Server) PATHWORKS for SCO UNIX, V1.1 B. License: PATHWORKS V5.0 (NetWare) FPA When you purchase the above license, or if you have a PATHWORKS V1.0 (NetWare) FPA license, you may use the following programs ("Software") under the terms in Section 2 and all terms provided in Additional Terms below. Server Programs: PATHWORKS V1.0 for OpenVMS (NetWare) PATHWORKS V5.0 for Digital UNIX (NetWare) C. License: PATHWORKS V1.3 (Macintosh) FPA When you purchase the above license, or if you have a PATHWORKS V1.2 (Macintosh) FPA license, you may use the following programs ("Soft- ware") under the terms in Section 2 and all terms provided in Addi- tional Terms below. Server Programs: PATHWORKS V1.3 for OpenVMS (Macintosh) 31 Section 2 Terms For purposes of these terms a client computer ("Licensed Client") is a computer that has been assigned one of these licenses by the PATHWORKS license server. The number of Licensed Clients may not exceed the Quantity specified in the associated Product Authoriza- tion Key. You may copy, access, and use the server Software identified above on any number of server systems, provided that this access is only by Li- censed Clients. 32 PATHWORKS_CNS_Licenses: A. License: PATHWORKS V6.0 for DOS and Windows CNS or License: PATHWORKS V6.0 for DOS and Windows CNS-UPGRADE [*] When you purchase either of the above licenses you may use the fol- lowing programs ("Software") under the terms in Section 3 and all terms provided in Additional Terms below. Programs: PATHWORKS V6.0 for DOS and Windows PATHWORKS X.25 (DOS), any version PATHWORKS ISDN (DOS), any version PATHWORKS for DOS (NetWare Coexistence), any version PATHWORKS Remote for DOS and Windows, any version B. License: PATHWORKS V4.1 for Windows NT CNS When you purchase the above license you may use the following program ("Software") under the terms in Section 3 and all terms provided in Additional Terms below. Program: PATHWORKS V4.1 for Windows NT C. License: PATHWORKS V5.1 for OS/2 CNS or License: PATHWORKS V5.1 for OS/2 CNS-UPGRADE [*] ____________________ See special terms for UPGRADE licenses in the GRANT section under Ad- ditional Terms below. 33 When you purchase either of the above licenses you may use the fol- lowing programs ("Software") under the terms in Section 3 and all terms provided in Additional Terms below. Program: PATHWORKS V5.1 for OS/2 34 D. License: PATHWORKS V1.3 for Macintosh CNS When you purchase the above license you may use the following program ("Software") under the terms in Section 3 and all terms provided in Additional Terms below. Program: PATHWORKS V1.3 for Macintosh Section 3 Terms You may copy and use the Software identified above on the number of computers specified in Quantity on the associated Product Au- thorization Key. 35 PATHWORKS_FPS_Licenses: A. License: PATHWORKS V1.0 for OpenVMS (NetWare) FPS When you purchase the above license you may use the following program ("Software") under the terms in Section 4 and all terms provided in Additional Terms below. Server Program: PATHWORKS V1.0 for OpenVMS (NetWare) B. License: PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS When you purchase the above license you may use the following program ("Software") under the terms in Section 4 and all terms provided in Additional Terms below. Server Program: PATHWORKS V5.0 for OpenVMS (LAN Manager) C. License: PATHWORKS V5.0 for Digital UNIX (LAN Manager) FPS When you purchase the above license you may use the following program ("Software") under the terms in Section 4 and all terms provided in Additional Terms below. Server Program: PATHWORKS V6.1 for Digital UNIX (Advanced Server) D. License: PATHWORKS V5.0 for Digital UNIX (NetWare) FPS 36 When you purchase the above license you may use the following program ("Software") under the terms in Section 4 and all terms provided in Additional Terms below. Server Program: PATHWORKS V5.0 for Digital UNIX (NetWare) 37 Section 4 Terms You may copy, access, and use the server Software identified above on a single server system, provided that the number of client com- puters accessing and using the server Software at any one time does not exceed the Quantity specified on the associated Product Autho- rization Key. 38 ADDITIONAL TERMS 1. GRANT Digital Equipment Corporation ("DIGITAL") grants you the right to use the version(s) of the Software specified above or any prior version of the Software. UPGRADE LICENSES ARE VALID ONLY IF YOU ARE ALSO LICENSED FOR A PRIOR VERSION OF THE SOFTWARE FOR THE SAME QUANTITY OF COMPUTERS AS SPEC- IFIED ABOVE. Prior versions of the software may only be used on the same computer(s) as the upgraded Software. You must register and load the associated Product Authorization Key before you use the Software. Each PAK must be registered and loaded in only one license management data base. You may copy the Software onto a network server for the sole purpose of distributing the Software to the specified quantity of computers. You may make archival or back-up copies of the Software. You may permanently transfer your rights to use the Software, the Soft- ware itself including prior versions of the Software, the Product Au- thorization Key(s) for this version and all prior versions, and the accompanying documentation including a copy of this License Agreement and License Agreement(s) for prior versions, provided you retain no copies of the Software, updates, documentation, or Product Authoriza- tion Key(s), and the recipient agrees to the terms of this License Agree- ment. 2. COPYRIGHT The Software is owned by DIGITAL and its suppliers and is protected by copyright laws and international treaties. Your use of the Soft- ware and associated documentation is subject to the applicable copy- right laws and the express rights and restrictions of this License Agree- ment. 39 3. RESTRICTIONS You may not rent, lease, or otherwise transfer the Software except as expressly authorized in this License Agreement. You may not remove any copyright, trademark or other proprietary no- tices from the Software or the media. You may not reverse engineer, decompile, or disassemble the Software, except to the extent Digital cannot prohibit such acts by law. 40 LIMITED WARRANTY DIGITAL warrants that the Software will perform substantially as de- scribed in the documentation accompanying the Software for a period of ninety (90) days from delivery. ANY IMPLIED WARRANTIES OF MERCHANTABIL- ITY OR FITNESS FOR A PARTICULAR PURPOSE ARE LIMITED TO NINETY (90) DAYS. EXCLUSIVE REMEDY. DIGITAL's and its suppliers' entire liability and your exclusive remedy for Software which does not conform to DIGITAL's Limited Warranty shall be, at DIGITAL's option, either (1) repair or replacement of the nonconforming Software, or (2) refund of your pur- chase price. This warranty and remedy are subject to your returning the non-conforming Software during the warranty period to DIGITAL in the country in which you obtained the Software. DISCLAIMER OF WARRANTIES. THE ABOVE WARRANTIES ARE YOUR EXCLUSIVE WAR- RANTIES AND NO OTHER WARRANTY, EXPRESS OR IMPLIED, WILL APPLY. DIG- ITAL does not warrant that the operation of the Software will be un- interrupted or error free. This warranty gives you specific legal rights, and you may also have other rights which vary from state to state. Some states do not al- low limitations on how long an implied warranty lasts, so the above limitation may not apply to you. ALLOCATION OF LIABILITY DIGITAL'S AND ITS SUPPLIERS' TOTAL LIABILITY TO YOU FOR ANY CAUSE WHAT- SOEVER SHALL BE LIMITED TO THE PURCHASE PRICE YOU PAID FOR THE PROD- UCT. THIS LIMITATION WILL APPLY REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT OR TORT, INCLUDING WITHOUT LIMITATION NEGLIGENCE. THE FORE- GOING LIMITATION DOES NOT APPLY TO DAMAGES RESULTING FROM PERSONAL IN- JURY CAUSED BY DIGITAL'S NEGLIGENCE. IN NO EVENT WILL DIGITAL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES RESULTING FROM LOSS OF DATA OR USE, LOST PROFITS, OR ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES. 41 Some jurisdictions do not allow the exclusion or limitation of inci- dental or consequential damages, so the above limitation or exclusion may not apply to you. U.S. GOVERNMENT RESTRICTED RIGHTS The Software and documentation are provided with "RESTRICTED RIGHTS". Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227- 7013, or FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Contractor/manufacturer is Digital Equipment Corporation. 42 GENERAL You are responsible for compliance with all applicable export or re- export control laws and regulations if you export the Software. This Agreement is governed by and is to be construed under the laws of the Commonwealth of Massachusetts. The 1980 United Nations Conven- tion on Contracts for International Sale of Goods will not apply. If you have any questions concerning this Agreement, please contact your local DIGITAL sales office or write to: DIGITAL EQUIPMENT COR- PORATION, 111 Powdermill Road, Maynard, MA 01754-1418. [R] ISDN is a registered trademark of Fujitsu Network Switching of America. [R] Macintosh is a registered trademark of Apple Computer, Inc. [R] NetWare is a registered trademark of Novell, Inc. [R] OS/2 is a registered trademark of International Business Ma- chines Corporation. [R] OSF/1 is a registered trademark of Open Software Foundation, Inc. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. [R] Windows is a registered trademark of Microsoft Corporation. [TM] SCO is a trademark of Santa Cruz Operations, Inc. [TM] Windows NT is a trademark of Microsoft Corporation. [TM] The DIGITAL Logo, Alpha, DEC, Digital, OpenVMS, PATHWORKS, and ULTRIX are trademarks of Digital Equipment Corporation. ©1996 Digital Equipment Corporation. All Rights Reserved. 43