 Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  DIGITAL PATHWORKS V1.0 for OpenVMS      SPD 41.47.08                 (NetWare)   DESCRIPTION   E DIGITAL PATHWORKS V1.0 for OpenVMS (NetWare[R]) is an OpenVMS layered C application that provides the functions of a NetWare V3.0 server in E a PC LAN environment. It is a member of the PATHWORKS family of prod- C ucts, which provides a framework for integrating personal computers C into an organization's total information system, allowing different C types of users to share information and network services across the  entire organization.  E The PATHWORKS family includes PC LAN server products running on Open- C VMS and DIGITAL UNIX[R] platforms, providing industry standard Net- D work Operating System (NOS) services that use protocols developed byD Novell[R], Microsoft[R], and Apple[R]. The PATHWORKS family also in-G cludes client products providing both client software for these servers E and enterprise-wide support capabilities such as wide area transports C (DECnet and TCP/IP) and applications such as Mail and Terminal Emu- G lation, allowing DOS, Windows[TM], Windows 95, Windows NT[TM], and Mac- F intosh[R] clients to participate as full peers in a widely distributed computing environment.   FEATURE OVERVIEW  D PATHWORKS for OpenVMS (NetWare) adds a new dimension to general pur-F pose OpenVMS systems. In addition to providing traditional support forD business, scientific, and engineering applications, this product al-E lows OpenVMS systems to appear to NetWare clients as Novell-certified  NetWare servers.    C                               DIGITAL                September 1997   C                                                         AE-PPMGJ-TH        > The major features of PATHWORKS for OpenVMS (NetWare) include:  G o  Novell-certified file and print services using Novell's NetWare Core '    Protocol and the IPX/SPX transports.   H o  Access to services provided by PATHWORKS for OpenVMS (NetWare) avail-E    able to PATHWORKS and other NetWare clients with appropriately li- G    censed components. (See the License Management section for details.)   D o  Files are stored on the server in native OpenVMS format. This al-G    lows information stored by the PCs using PATHWORKS for OpenVMS (Net- D    Ware) to be shared with traditional OpenVMS users. In particular,C    this feature allows the sharing of information between all PATH- 5    WORKS clients, even if they are not using NetWare.   C o  Printing support not only allows NetWare clients to use an Open- I    VMS system running PATHWORKS for OpenVMS (NetWare) to act as a generic G    NetWare Print Server, but this support also allows interactive Open- C    VMS users to direct jobs to remote, native NetWare print servers F    by simply directing their print jobs to local OpenVMS print queues.  D o  File and print services management using standard NetWare manage-F    ment utilities, such as FCONSOLE, PCONSOLE, and SYSCON. These func-E    tions, combined with other standard systems and network management F    utilities for OpenVMS, such as Remote System Management (RSM), pro-E    vide a powerful set of tools for total distributed systems manage-     ment.  F o  Either NetWare-only, or NetWare combined with OpenVMS security mod-C    els, can be applied in this environment, providing greater flex- -    ibility and added security to your system.   C o  A mail server is provided that works with the OpenVMS Mail util- C    ity and the PATHWORKS Mail client to provide clients with access 2    to enterprise-wide electronic mail over DECnet.  C o  A DECnet tunnel function for the IPX transport is provided. This C    function encapsulates IPX packets in DECnet packets, thereby al- E    lowing information sent over IPX to be transported anywhere within E    a DECnet network. This allows existing DECnet-based wide area net- F    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.  "                                  2       D o  New Novell Virtual Terminal (NVT2) support is provided, employingE    SPX as the new underlying transport. NVT2 support provided for DOS E    clients allows IPX-based terminal emulation software to be used on H    a PC for direct, interactive connections to the OpenVMS systems where0    PATHWORKS for OpenVMS (NetWare) is operating.  E o  NetWare (file and print) Application Programming Interfaces (APIs)     are provided.  D o  The host-based SCONSOLE Utility provides systems managers and ad-C    ministrators with a single menu-driven tool to configure and ad- D    minister OpenVMS-specific functions such as starting and stoppingC    the file server, the IPX/SPX transports, or the DECnet tunneling     function for IPX.  C o  License Management software, now capable of supporting PATHWORKS D    users of both NetWare and LAN Manager clients, provides the capa-
    bility to:   A    a. Distribute PATHWORKS client-based licenses across a network   E    b. Validate access by clients with PATHWORKS client-based licenses   I    c. Support client access using server-based licenses validated through B       the local OpenVMS License Management Facility (LMF) database  E Note that (a) and (b) are accomplished with PATHWORKS license manage-  ment software for the client.    FEATURE DETAILS    NetWare Volumes/File Services   C PATHWORKS for OpenVMS (NetWare) provides NetWare clients with a re- F mote file system that appears as a transparent extension of the client% system's local computing environment.   C PATHWORKS for OpenVMS (NetWare) services are based on Novell's Net- G Ware Core Protocols (NCPs) and have been certified by Novell as a fully 5 compliant implementation of Portable NetWare, V3.01B.   "                                  3       @ Three RMS file formats are allowed and supported on each volume:  	 o  Stream   8 o  Sequential fixed length record (512 bytes per record)  F o  Sequential fixed length record of a specified record size (1 to 32K    bytes per record)  C Included with PATHWORKS for OpenVMS (NetWare) is a feature called a E hybrid user. This feature allows users who are both interactive Open- E VMS users and users of PATHWORKS for OpenVMS (NetWare) to access both D their NetWare-created information and their interactive OpenVMS user, directory while logged in as a NetWare user.  D If you are identified as a hybrid user, a special volume called HOMEG is created when you log in. HOME points to your login directory in your E OpenVMS account. You can map drives to this HOME volume and/or to di- C rectories below it. You have access rights to all files in that di- A rectory just as if you were logged in to your account on OpenVMS.   D Multiple NetWare clients can concurrently access files stored on theG server's disk through the file access modes and byte-range locking sup- 8 port provided by the server as defined by Novell's NCPs.  D Through the use of the VMS Lock Manager, OpenVMS and PC applications can control file access.   Print Services  F PATHWORKS for OpenVMS (NetWare) software allows NetWare clients to ac-C cess printers used by interactive OpenVMS users and other PATHWORKS F clients that may not be using NetWare. These printers can be connectedI to the OpenVMS server, OpenVMS cluster, or LAT-supported terminal servers 	 in a LAN.   G The system administrator assigns a service name, called a NetWare print C queue, to an OpenVMS print queue and can define NetWare user access F to the print service. NetWare client software can redirect printer I/O< from a client printer port to a defined NetWare print queue.  "                                  4       G The system administrator creates, on the host, the physical and generic D queues and defines forms for selected DIGITAL and third-party print-D ers using standard OpenVMS commands. The administrator then uses theE PATHWORKS for OpenVMS (NetWare) SCONSOLE utility to associate NetWare C print queues with OpenVMS print queues. Refer to the Optional Hard-  ware section for details.   E Multiple NetWare print queues may be set up for the same printer. For F example, a landscape service and a portrait service may be created forG the same PrintServer 40 Plus printer. In addition, other printer queues H can be manually set to support additional DIGITAL and third-party print-% ers that are not listed in the menus.   I NetWare print queues and the NetWare print servers servicing those queues E may reside on different physical systems. Because PATHWORKS for Open- E VMS (NetWare) includes a NetWare-compliant PSERVER implementation, it C is compatible with many versions of Novell's print servers, includ-  ing:   o  NetWare 3.X (PSERVER.NLM)   o  NetWare 2.X (PSERVER.VAP)   o  Dedicated DOS (PSERVER.EXE)  C o  Network printers providing a NetWare compliant PSERVER implemen- 	    tation   
 o  Router VAP   ( o  NetWare for UNIX print server daemons  C Compatibility with NetWare for UNIX print server daemons means that C PATHWORKS for OpenVMS (NetWare) will interoperate with other Novell C Certified implementation of NetWare for UNIX provided by DIGITAL or  by other vendors.   F Any type of NetWare print server is capable of servicing NetWare printC queues located on any NetWare file server. To service NetWare print C queues associated with remote NetWare file servers, a PATHWORKS for C OpenVMS (NetWare) print server must be configured to attach to each   "                                  5       D NetWare file server associated with each NetWare print queue that it
 will service.   F Similarly, to be serviced by remote NetWare print servers, a PATHWORKSD for OpenVMS (NetWare) print queue would need to be configured to al- low this access.  I NetWare clients logged into a PATHWORKS for OpenVMS (NetWare) file server F can also access other NetWare print services available in the network,E either by attaching directly to the associated NetWare file server or  using the PCONSOLE utility.   E Interactive OpenVMS users can also queue print jobs to remote NetWare C print servers by simply queuing to normal OpenVMS print queues that F have been set up by PATHWORKS for OpenVMS (NetWare) to send print jobs+ to the desired remote NetWare print server.    Server Management and Control   D SCONSOLE, an OpenVMS Utility used with standard NetWare client util-D ities, provides the complete set of tools needed to manage the PATH-# WORKS for OpenVMS (NetWare) server.   E SCONSOLE is used to manage OpenVMS-specific functions related to this , product. In particular, SCONSOLE is used to:  8 o  Start and stop the server, in its entirety or in part  % o  Create, modify, and remove volumes   ; o  Associate NetWare print queues with OpenVMS print queues   " o  Modify server security settings   o  Add and delete hybrid users  ' o  Configure and tune server components   5 o  Display server specific statistics and information   "                                  6        Network Connectivity  
 o  IPX/SPX  D The PATHWORKS for OpenVMS (NetWare) software includes an OpenVMS im-C plementation of the two transport protocols used by Novell's native  NetWare products:   (    -  IPX (Internetwork Packet Exchange)  %    -  SPX (Sequenced Packet Exchange)   D IPX is delivered as a STREAMS driver in this product and is used forG all NetWare-related client/server functions. The IPX protocol is trans- : mitted as datagram packets between source and destination.  C SPX provides a layer above the IPX protocol that tracks IPX packets C to ensure that each packet is successfully received by its intended  destination.  * o  Novell Virtual Terminal (NVT2) Protocol  I NVT2 support consists of server software and software that must be loaded  on each client.   F On the PATHWORKS for OpenVMS (NetWare) server, an OpenVMS process pro-D vides Virtual Terminal services over SPX (using IPX). Each NVT2 con-C nection requires a corresponding SPX connection. Therefore, a maxi- 9 mum of 1000 concurrent NVT2 connections can be supported.   C The NVT2 software for DOS-based clients (TSR or VLM) redirects ter- E minal I/O through INT14 or INT6b interrupt modes, the interfaces used E by most terminal emulation applications. Note that the PATHWORKS V6.0 D for DOS and Windows SETHOST terminal emulation application also uses these interfaces.    o  IPX Tunneling Within DECnet  C PATHWORKS for OpenVMS (NetWare) includes the capability of connect- F ing one or more NetWare LANs using a DECnet WAN. The tunnel driver en-E capsulates IPX datagrams within DECnet packets transmitted across the E DECnet network to the tunnel partner and then de-encapsulates the IPX 1 datagram, routing it to its intended destination.   "                                  7       # Performance-Enhancing XQP+ Services   E PATHWORKS for OpenVMS (NetWare) includes a special release of the en- H hanced OpenVMS file system, known as XQP+ (eXtended QIO Processor Plus).C XQP+ is integral to OpenVMS V6.1 or later and is separately instal- C lable on VAX/VMS V5.5-2 and OpenVMS VAX V6.0 systems. XQP+ provides D improved concurrency using multithreading, which results in improved' performance for file system operations.   
 Mail Services   E The mail server component of PATHWORKS for OpenVMS (NetWare) provides G a service that is separate and distinct from the NetWare file and print C services. This mail server is based on the OpenVMS MAIL utility and D requires DECnet as its communications transport. It allows PATHWORKSD users, using the client PATHWORKS Mail software, to send and receiveE electronic mail messages without having to log in to the OpenVMS sys-  tem 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 F routes messages to the appropriate client when the user logs on to the server.   F The PATHWORKS for OpenVMS (NetWare) mail server provides the PATHWORKSG user with folders, distribution lists, and delivery capabilities. Also, C notification of new messages occurs both in real time (which may be ? optionally disabled) and upon log in to a network MAIL session.    Installation and Configuration  D PATHWORKS for OpenVMS (NetWare) shares code with, and is distributedC with, both PATHWORKS V5.0F for OpenVMS (LAN Manager) and with PATH- D WORKS V6.0 for OpenVMS (Advanced Server) (though still licensed sep-E arately). A single installation procedure is shared between PATHWORKS D for OpenVMS (NetWare) and PATHWORKS V5.0F for OpenVMS (LAN Manager).      "                                  8       E Another, different single installation procedure shared between PATH- D WORKS for OpenVMS (NetWare) and PATHWORKS V6.0 for OpenVMS (AdvancedD Server). Both procedures provide for the installation of one or bothD associated server products in a single step on an OpenVMS system us-G ing the standard VMSINSTAL procedure. An Installation Verification Pro- D cedure (IVP) is also included, which can be used to confirm that all, server software has been installed properly.  D DIGITAL recommends that a customer's first purchase of this softwareD product at each site include DIGITAL installation service. This ser-C vice provides implementation support for customers installing PATH- H WORKS for OpenVMS (NetWare) software and for the integration of PC work-D stations into the DIGITAL network. Contact your local DIGITAL repre-; sentative for information on the service options available.    License Management  E PATHWORKS for OpenVMS (NetWare) offers several license management ca- B pabilities related to both client-based and server-based licenses.  " o  Client-Based License Management  D PATHWORKS client licenses are provided as Product Authorization KeysD (PAKs) for the OpenVMS License Management Facility (LMF). These PAKsC must be loaded into an LMF database, using standard LMF procedures, E on an OpenVMS system that is acting as a PATHWORKS License Server.[1] C A single copy of the PATHWORKS License Server software can now pro- C vide and verify client-based licenses for clients using NetWare and C LAN Manager software. NetWare clients use the IPX transport to com-_C municate with a PATHWORKS License Server, while LAN Manager clientsD. use the DECnet, NetBEUI, or TCP/IP transports.   ____________________D  Although  the License Server can be active only on a single node inF   a cluster, if that node goes down for any reason, the License ServerH   will automatically activate itself on another node in the cluster that     is still running PATHWORKS.     "                                  9 g  i  E The PATHWORKS License Manager, which must execute on the same node asaD the License Server, provides a user interface that allows the systemC manager to monitor client license usage. The PATHWORKS License Man-uE ager is also used to preallocate licenses to specific groups of usersl' and to reclaim a license from a client.   E The PATHWORKS License Registrar, which executes on the same system asoC the file server, will "handshake" with clients requesting access tolD PATHWORKS for OpenVMS (NetWare) functions. Clients that can success-F fully "handshake" with the server and produce a valid client-based li-E cense will be allowed access to the services offered by the PATHWORKS  for OpenVMS (NetWare) server.M  " o  Server-Based License Management  D The PATHWORKS for OpenVMS (NetWare) server also allows client accessD based on a local server-based license. If a client requesting accessF to the server fails to produce a valid client-based license, the PATH-F WORKS License Registrar software checks the local LMF database for theE availability of a PATHWORKS for OpenVMS (NetWare) PC Concurrent (for- C merly known as FPS) license. If one is available, and the number of F concurrently connected clients allowed by the license has not been ex-* ceeded, the client will be allowed access.  D PATHWORKS for OpenVMS (NetWare) servers always allow you to use bothD client-based and server-based licenses, simultaneously. However, be-C cause clients that do have a valid client-based license are alreadyrC licensed to use the server software, they are never counted againstaF the fixed number of clients granted access by the server-based PC Con- current license.   RESTRICTIONS AND LIMITATIONS  E o  NetWare NLMs are not usable with a PATHWORKS for OpenVMS (NetWare)nE    server. NetWare NLMs are typically applications or utilities writ- E    ten specifically for an Intel platform using NetWare 3.x or for annF    Intel platform using NetWare 4.x as the host operating system. They1    are not easily portable to other environments.v    "                                 10 i  n   o  Portable NetWAre V3.01B  E PATHWORKS for OpenVMS (NetWare) is an implementation of Portable Net- D Ware V3.01B. As such, certain features currently available in NovellC NetWare 3.x, Intel-based servers are not included. Among these fea-m
 tures are:  E    -  The PATHWORKS for OpenVMS (NetWare) print server implementationOH       cannot be used with DOS-based clients configured with RPRINTER.EXED       or network-based printers that implement NetWare's RPRINT pro-       tocol.  @    -  Burst mode technology, or "packet burst", is not supported  C    -  Windows NT client software from Novell is not supported. How-(E       ever, Windows NT NetWare client software from Microsoft is sup-m
       ported.m  D o  The DOS utilities specific to PC hardware devices such as CHKDSK,F    FDISK, DISKCOPY, DISKCOMP, and FORMAT cannot be used with PATHWORKS    server volumes.  & o  Unsupported wire protocols include:  F    -  Ethernet using IEEE 802.3 (SNAP) frame type (used mainly by Mac-       intosh systems)e      -  Arcnet  D    -  Token Ring on VAX systems (Token Ring on Alpha systems is sup-       ported.)  5 o  The OpenVMS Spiralog file system is not supported.   C o  Though Novell's raw 802.3 Ethernet frame type is supported, somelD    usage restrictions will always apply, because it does not conformD    to the IEEE specifications. In particular, this frame type shouldC    not be used on any OpenVMS system using the DECnet-Plus protocol-E    (the default for OpenVMS V7.1 and later). See the product documen- %    tation for additional information.   D o  PATHWORKS for OpenVMS (NetWare) is not supported with OpenVMS VAX#    V6.0 or with OpenVMS Alpha V1.5.t  "                                 11 n  a  D o  The NetWare utility, Salvage, is not supported (incompatible with    the OpenVMS file system).  8 o  PATHWORKS for OpenVMS (NetWare) supports a maximum of  F    -  250 simultaneous users per OpenVMS node (an inherent NetWare 3.x       limitation)       -  250 NetWare volumesh  E    -  1000 SPX connections (each NVT2 session uses an SPX connection)t  C o  Though NetWare volumes may be dynamically marked for addition orpL    deletion, volumes are only added or deleted when the server is restarted.  A VARIANTS DELIVERED AND RELATIONSHIPS WITH OTHER PATHWORKS SERVERS   F Two slightly different versions of PATHWORKS for OpenVMS (NetWare) areC delivered with the distribution kits. Both sets of code provide the D exact same functions and capabilities; however, they are designed to# function in different environments.   ( o  PATHWORKS V1.0F for OpenVMS (NetWare)  C Delivered on the PATHWORKS V5.0F for OpenVMS distribution media andeH designed to coexist with PATHWORKS V5.0F for OpenVMS (LAN Manager) soft-F ware, it can be run on VAX and Alpha systems and with a number of dif-F ferent versions of OpenVMS either stand alone or coexisting with PATH-& WORKS V5.0F for OpenVMS (LAN Manager).  ) o  PATHWORKS V1.0G for OpenVMS (NetWare).   F Delivered on the PATHWORKS V6.0 for OpenVMS distribution media and de-C signed to coexist with PATHWORKS V6.0 for OpenVMS (Advanced Server) C software, it can be run only on Alpha systems with OpenVMS V7.1 ei-NC ther stand alone or coexisting with PATHWORKS V6.0 for OpenVMS (Ad-n vanced Server).e      "                                 12       D Though both V1.0F and V1.0G can be run stand alone and would deliverD identical services, V1.0F should normally be used, because the hard-F ware and software environments it supports include all those supported by V1.0G and and many more.r  ' PATHWORKS Server Combinations for V1.0Fn  C The following PATHWORKS server products can be run on the same sys-u- tem as PATHWORKS V1.0F for OpenVMS (NetWare):       PATHWORKS for VMS V4.x[1]/    PATHWORKS V5.0F for OpenVMS (LAN Manager)[1]e)    PATHWORKS V1.x for OpenVMS (Macintosh)   F The following PATHWORKS server products cannot be run on the same sys-- tem as PATHWORKS V1.0F for OpenVMS (NetWare):E  4    Any PATHWORKS V1.0x for OpenVMS (NetWare) product+    PATHWORKS V5.0 for OpenVMS (LAN Manager)m,    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),    PATHWORKS V5.0E for OpenVMS (LAN Manager)/    PATHWORKS V6.0 for OpenVMS (Advanced Server)h  C If you attempt to install PATHWORKS for OpenVMS (NetWare) on a sys-sG tem running any of the software listed, you will automatically be givenaA the option to upgrade related components to a compatible version.            ____________________F  PATHWORKS  for VMS V4.x and PATHWORKS V5.0F for OpenVMS (LAN Manager)  4   cannot be run on the same system at the same time.    "                                 13 t     ' PATHWORKS Server Combinations for V1.0Ge  C The following PATHWORKS server products can be run on the same sys-t- tem as PATHWORKS V1.0G for OpenVMS (NetWare):       PATHWORKS for VMS V4.x[1]2    PATHWORKS V6.0 for OpenVMS (Advanced Server)[1])    PATHWORKS V1.x for OpenVMS (Macintosh)f  F The following PATHWORKS server products cannot be run on the same sys-- tem as PATHWORKS V1.0G for OpenVMS (NetWare):   3    Any PATHWORKS V1.0x for OpenVMS (NetWare) servern7    Any PATHWORKS V5.0x for OpenVMS (LAN Manager) serverf  C If you attempt to install PATHWORKS for OpenVMS (NetWare) on a sys-eG tem running any of the software listed, you will automatically be giventA the option to upgrade related components to a compatible version.n   HARDWARE REQUIREMENTSo  C The following systems, components, and peripherals are supported asi
 specified:   Supported Processors  - o  For PATHWORKS V1.0F for OpenVMS (NetWare):a  C All VAX and Alpha processors supported by the version of OpenVMS int use are also supported.i         ____________________I  PATHWORKS  for VMS V4.x and PATHWORKS V6.0 for OpenVMS (Advanced Server)l  4   cannot be run on the same system at the same time.    "                                 14        Exceptions:r  C    ________________________________________________________________dC    MicroVAX________________VAXstation______________VAX_____________h  =    MicroVAX I              VAXstation I            VAX-11/725t=    MicroVAX II             VAXstation II           VAX-11/730d  =    MicroVAX 2000           VAXstation 2000         VAX-11/750r  >                            VAXstation 8000         VAX-11/780,C    ________________________________________________VAX-11/785______f  - o  For PATHWORKS V1.0G for OpenVMS (NetWare):K  / All Alpha processors supported by OpenVMS V7.1.r   Memory Requirementsl  D PATHWORKS for OpenVMS (NetWare) requires the following physical mem-F ory for proper installation, configuration, and execution of the soft- ware:u  - o  For PATHWORKS V1.0F for OpenVMS (NetWare):c  = 16 MBytes on VAX systems (24 MBytes if used with DECnet-Plus)e  - o  For PATHWORKS V1.0G for OpenVMS (NetWare):v   or  & PATHWORKS V1.0F for OpenVMS (NetWare):   64 MBytes on Alpha systems  E The memory requirements indicated are minimum requirements to installtD and run the server. Memory requirements can vary widely according toD the server CPU, the number of clients using the server and their ac-B tivities, and the other applications running on the server system.  D The recommended minimum is twice the memory of the absolute minimums
 specified.  "                                 15 ,  i   Disk Space Requirementst  D The following table provides the disk space requirements for the in-C stallation and configuration of PATHWORKS for OpenVMS (NetWare) ei-rD ther stand alone, with PATHWORKS V5.0F for OpenVMS (LAN Manager), orE with PATHWORKS V6.0 for OpenVMS (Advanced Server) software. Note thatoD each of the entries in this table may be directed to different disks? but, by default, all entries will be directed to the same disk.e  C These sizes are approximate; actual sizes may vary depending on the ? user's system environment, configuration, and software options.E  D You should also plan for additional, significant disk-space require-D ments once the product is in use, for items such as data files, vir-3 tual memory section files, log files, and so forth.r  C ___________________________________________________________________q? Installation/Configuration        VAX Systems     Alpha Systems C Requirements______________________(Blocks)________(Blocks)_________y  C Installation_Space_Requirements[1]_________________________________    Images and Command Files: 9     NetWare software only          20,000          36,000t9     with LAN Manager V5.0F         44,000          66,000  software9     with Advanced Server V6.0     N/A             141,000  software9   NetWare System Volume[2]         34,000          34,000c  C ___________________________________________________________________a  C Configuration_Space_Requirements___________________________________o   PATHWORKS server data files:C ___________________________________________________________________aB [1]These values represent the approximate permanent space required@ for product installation. Another 6000 blocks of temporary space3 is required during the actual installation process.p  @ [2]The NetWare SYS Volume contains the NetWare utilities used by NetWare clients.  "                                 16 s  e    C Installation/Configuration________VAX_Systems_____Alpha_Systems____nC Requirements______________________(Blocks)________(Blocks)_________o  C Configuration_Space_Requirements___________________________________s  9     NetWare software, only          6,000           6,000 9     with LAN Manager V5.0F         12,500          12,500r software9     with Advanced Server V6.0         N/A          77,500i software9 NetWare Configuration files,        1,000           1,000n etc.[3]i  C ___________________________________________________________________   C Totals_____________________________________________________________n  9     NetWare software, only         61,000          77,000t9     with LAN Manager V5.0F         91,500         113,500c software9     with Advanced Server V6.0         N/A         219,500d softwareC ___________________________________________________________________nC [3]These_files_are_typically_stored_on_the_OpenVMS_system_disk.____c   Network Interface Controllerso  H At least one network interface controller is required for use with PATH-A WORKS for OpenVMS (NetWare). The following devices are supported:n  1 o  All DIGITAL VAX and Alpha Ethernet controllerst  ' Supported Ethernet frame types include:A      -  Ethernet IIp  F    -  IEEE 802.3 (SAP). (Novell refers to this frame type as "802.2.")  ?    -  Raw 802.3. (Novell refers to this frame type as "802.3.") ;       (For more information, see the Restrictions section.)p  - o  All DIGITAL VAX and Alpha FDDI controllers   "                                 17 s  h  8 o  All DIGITAL Token Ring controllers for Alpha systems.  # Optional Hardware: DIGITAL Printersn  I All printers supported by the OpenVMS Operating System using print queuest6 are also supported by PATHWORKS for OpenVMS (NetWare).  C DIGITAL PostScript[R] printers require the use of DECprint Supervi-aE sor (DCPS) for OpenVMS V1.3. DCPS software is included with the PATH-lC WORKS for OpenVMS (NetWare) media, but the use of the DCPS softwares0 requires the purchase of an appropriate license.  C Refer to SPD 44.15.xx for DCPS licensing information and for a com-eG plete list of the DIGITAL and non-DIGITAL PostScript printers supportedr by DCPS.  C The NetWare Print Definition Files (.PDF) are provided for the fol-a lowing printers:   Colormate PS     LJ250   DEClaser 1100    LN03t DEClaser 1150    LN03 PLUS$ DEClaser 1152    LN03R ScriptPrinter DEClaser 2100    PrintServer 17n DEClaser 2100    PrintServer 20o plus% DEClaser 2150    Turbo PrintServer 20d DEClaser 2150    PrintServer 32V plus DEClaser 2200    PrintServer 40 % DEClaser 2200    Print Server 40 Plusd plus
 DEClaser 2250l
 DEClaser 2250  plus
 DEClaser 3200s      "                                 18 K       
 DEClaser 3250e   LA70 LA75	 LA75 Plus  LA210  LA310n LA324  LA424    OpenVMS CLUSTER ENVIRONMENT8  E The PATHWORKS for OpenVMS (NetWare) server provides for a common Net-eG Ware SYS volume across OpenVMS cluster members running the server. ThisaD means that a single bindery and trustee database is maintained clus- terwide.  D In addition, NetWare volumes can also be made available clusterwide.E A volume defined by SCONSOLE on one cluster member running the serveruC can also be configured so that it is available to all other clustervD servers. However, concurrent file sharing between servers running on+ different cluster members is not supported.r                                  "                                 19 p  i   SOFTWARE REQUIREMENTSt   Operating System SoftwareH  - o  For PATHWORKS V1.0F for OpenVMS (NetWare):t      -  For Alpha Systems:  9 OpenVMS Alpha Operating System V6.1, V6.2, V7.0, and V7.1       -  For VAX Systems:   VAX/VMS Operating System V5.5-2l=       OpenVMS VAX Operating System V6.1, V6.2, V7.0, and V7.1   - o  For PATHWORKS V1.0G for OpenVMS (NetWare):s  # OpenVMS Alpha Operating System V7.1r  C For minimum hardware requirements of the operating system, refer toeD the Software Product Descriptions for the OpenVMS VAX Operating Sys-I tem (SPD 25.01.xx) and the OpenVMS Alpha Operating System (SPD 41.87.xx).    OpenVMS Tailoringg  F For use with VAX/VMS V5.5-2 systems, the following OpenVMS classes are8 required for full functionality of this layered product:   o  OpenVMS Required Savesetp   o  Network Support   o  System Programming Support    o  Secure User's Environment   o  OPTL (Miscellaneous Files)   C For more information on OpenVMS classes and tailoring, refer to the I OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx)._  "                                 20 S  e   Network Transport Software   o  DECnet Software  H The DECnet network transport software is required by PATHWORKS for Open- VMS (NetWare):  8    -  When acting as a MAIL server for PATHWORKS clients  F    -  To optionally tunnel IPX packets between two OpenVMS systems us-       ing this softwarew  F    -  When the PATHWORKS License Server is configured to service PATH-1       WORKS clients using LAN Manager and DECnet.t  D The license to use DECnet software is usually bundled with your sys-, tem but may need to be purchased separately.  F Because the DECnet/IPX tunnel is a DECnet Phase IV implementation, itsD use on systems with DECnet-Plus installed requires the definition of network name synonyms.   o  TCP/IP Software  C TCP/IP network transport software is only required by PATHWORKS for-C OpenVMS (NetWare), if the PATHWORKS License Server is configured tol7 service PATHWORKS clients using LAN Manager and TCP/IP.b  C When TCP/IP software is used for this purpose, it must be purchasedeE separately. Please consult the Software Product Description for PATH-sG WORKS for OpenVMS (Advanced Server) and PATHWORKS for OpenVMS (LAN Man-t= ager), SPD 30.50.xx, for currently supported TCP/IP products.    Associated Client Software  D The following software products may be used on personal computers to7 access PATHWORKS for OpenVMS (NetWare) server software:r  < 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)w  "                                 21 d  h  I o  NetWare clients using the latest, supported version of Novell's clientlA    shell, NETX.EXE, that also support native NetWare 3.0 servers.   I o  NetWare clients using the latest, supported version of Novell's client @    VLM redirector, that also support native NetWare 3.0 servers.  H PATHWORKS for OpenVMS (NetWare) will appear as a NetWare for UNIX V3.01B1 server (or a NetWare V3.0 server) to all clients.O   GROWTH CONSIDERATIONSN  E The minimum hardware and software requirements for any future versionrC of this product may be different from the requirements for the cur-t
 rent version.   + SOFTWARE LICENSING AND ORDERING INFORMATIONa  F PATHWORKS for OpenVMS (NetWare) can be licensed in two different ways.  - o  Client-Based Licensing (Designated Access)s  C This product can be licensed for operation and access on any numberrE of supported platforms to provide services to clients assigned appro-t priate client-based licenses.h  C See the terms and conditions for Designated Access licenses on yoursg Product Authorizations Keys (PAKs) or on the Internet at http://www.digital.com/info/software-licensingrD for a description of the specific rights granted. See the ApplicableD Client-Based Licenses section later in this SPD for specific license names and ordering information.   ) o  Server-Based Licensing (PC Concurrent)   E A PATHWORKS PC Concurrent license for this product permits its use on D a single supported platform and allows access by clients that do not& have a PATHWORKS client-based license.        "                                 22    d  E See the terms and conditions for PC Concurrent licenses on your Prod-nc uct Authorizations Keys (PAKs) or on the Internet at http://www.digital.com/info/software-licensingeD for a description of the specific rights granted. See the ApplicableD Server-Based Licenses section later in this SPD for specific license names and ordering information.   E Note: Clients with client-based licenses for server access do not in- F terfere with the access of other clients that rely on server-based li-D censing for access to a particular server. The two licensing methods are designed to coexist.    Applicable Client-Based Licenses  * PATHWORKS V5.0 (NetWare) Designated Access   For new users, order:o      QM-2CMAA-AB, 1 user    QM-2CMAA-AC, 10 userS    QM-2CMAA-AD, 25 user     QM-2CMAA-AE, 50 useri    QM-2CMAA-AF, 100 user    QM-2CMAA-AG, 250 user    QM-2CMAA-AH, 500 user    QM-2CMAA-AJ, 1000 usern  F The PATHWORKS V5.0 (NetWare) Designated Access licenses also grant ac-= cess to the PATHWORKS V5.0 for DIGITAL UNIX (NetWare) server.   C See the terms and conditions for Designated Access licenses on yourtg Product Authorizations Keys (PAKs) or on the Internet at http://www.digital.com/info/software-licensingn1 for a description of the specific rights granted.c    Applicable Server-Based Licenses  3 PATHWORKS V1.0 for OpenVMS (NetWare) PC Concurrent:d   For new users, order:i      QM-0ENAA-AB, 10-userm  "                                 23 v  i      QM-0ENAA-AC, 25-userL    QM-0ENAA-AD, 50-userW    QM-0ENAA-AE, 100-user    QM-0ENAA-AF, 250-user  E See the terms and conditions for PC Concurrent licenses on your Prod-sc uct Authorizations Keys (PAKs) or on the Internet at http://www.digital.com/info/software-licensinga1 for a description of the specific rights granted.     Discontinued License Information  E The following client-based licenses are no longer sold. However, theyiF continue to be valid for accessing the PATHWORKS for OpenVMS (NetWare) server:   ; o  PATHWORKS for DOS and Windows (NetWare) CCS, QM-0EKAA-Axo  0 o  PATHWORKS for OS/2 (NetWare) CCS, QM-506AA-Ax    Software Media and Documentation  D Software media and documentation are available in the following for- mats:   )    TK50 streaming tape media, QA-A93AA-H5i    CDROM media, QA-A93AA-H8n!    Documentation kit, QA-A93AA-H8o  D In addition, PATHWORKS for OpenVMS (NetWare) software and documenta-" tion is included in the following:  C    DIGITAL OpenVMS Alpha Software Layered Products Library Package,r    QA-03XAA-H8E    DIGITAL OpenVMS VAX Software Layered Products Library Package, QA-     5G88A-H8a  F The above information is valid at time of release. Please contact yourC local DIGITAL sales representative for the most up-to-date informa-c tion.l  "                                 24 o  r   SOFTWARE PRODUCT SERVICESi  E A variety of service options are available from DIGITAL. For more in-hB formation, please contact your local DIGITAL sales representative.  B [R]  Apple, AppleShare, and Macintosh are registered trademarks of      Apple Computer, Inc.   B [R]  Microsoft is a registered trademark of Microsoft Corporation.  A [R]  NetWare and Novell are registered trademarks of Novell, Inc.)  A [R]  OSF/1 is a registered trademark of Open Software Foundation,R	      Inc.   @ [R]  PostScript is a registered trademark of Adobe Systems, Inc.  B [R]  UNIX is a registered trademark in the United States and otherA      countries, licensed exclusively through X/Open Company, Ltd.)  @ [TM] Windows and Windows NT are trademarks of Microsoft Corpora-
      tion.  B [TM] The DIGITAL logo, DEC, DEClaser, DECnet, DECprint, DECserver,@      DECwindows, DIGITAL, Internet, LAT, LA324, LN03, LN03 PLUS,A      MicroVAX, OpenVMS, PATHWORKS, PrintServer, ULTRIX, VAX, VAX-s@      11/750, VAX-11/780, VAX 8200, VAX 8250, VAX 8300, VAX 8350,=      VAX 8500, VAX 8530, VAX 8550, VAX 6000, VAX 9000, VAXft,)@      VAXcluster, VAXserver, VAXstation, VAXstation 4000 VLC, and9      VMS are trademarks of Digital Equipment Corporation.C  9 1997 Digital Equipment Corporation. All Rights Reserved.u                "                                 25