       %                               DIGITAL    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 @ a PC LAN environment. It is a member of the PATHWORKS family of G products, 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.  G The PATHWORKS family includes PC LAN server products running on OpenVMS B and DIGITAL UNIX[R] platforms, providing industry standard Network? Operating System (NOS) services that use protocols developed by A Novell[R], Microsoft[R], and Apple[R]. The PATHWORKS family also  I includes client products providing both client software for these servers E and enterprise-wide support capabilities such as wide area transports ? (DECnet and TCP/IP) and applications such as Mail and Terminal  F Emulation, allowing DOS, Windows[TM], Windows 95, Windows NT[TM], and I Macintosh[R] clients to participate as full peers in a widely distributed  computing environment.   FEATURE OVERVIEW  @ PATHWORKS for OpenVMS (NetWare) adds a new dimension to general I purpose OpenVMS systems. In addition to providing traditional support for A business, scientific, and engineering applications, this product  G allows OpenVMS systems to appear to NetWare clients as Novell-certified  NetWare servers.  C                                                      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.   B o  Access to services provided by PATHWORKS for OpenVMS (NetWare) G    available to PATHWORKS and other NetWare clients with appropriately  I    licensed components. (See the License Management section for details.)   A o  Files are stored on the server in native OpenVMS format. This  D    allows information stored by the PCs using PATHWORKS for OpenVMS H    (NetWare) to be shared with traditional OpenVMS users. In particular,G    this feature allows the sharing of information between all PATHWORKS /    clients, even if they are not using NetWare.   E o  Printing support not only allows NetWare clients to use an OpenVMS E    system running PATHWORKS for OpenVMS (NetWare) to act as a generic I    NetWare Print Server, but this support also allows interactive OpenVMS ?    users to direct jobs to remote, native NetWare print servers F    by simply directing their print jobs to local OpenVMS print queues.  G o  File and print services management using standard NetWare management F    utilities, such as FCONSOLE, PCONSOLE, and SYSCON. These functions,>    combined with other standard systems and network managementI    utilities for OpenVMS, such as Remote System Management (RSM), provide D    a powerful set of tools for total distributed systems management.  I o  Either NetWare-only, or NetWare combined with OpenVMS security models, D    can be applied in this environment, providing greater flexibility%    and added security to your system.   > o  A mail server is provided that works with the OpenVMS Mail G    utility 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 @    function encapsulates IPX packets in DECnet packets, thereby G    allowing information sent over IPX to be transported anywhere within A    a DECnet network. This allows existing DECnet-based wide area  F    networks (WANs) to be used to transport IPX-based traffic from IPX @    local 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.  A o  The host-based SCONSOLE Utility provides systems managers and  B    administrators with a single menu-driven tool to configure and F    administer 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 ?    users of both NetWare and LAN Manager clients, provides the      capability 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  H Note that (a) and (b) are accomplished with PATHWORKS license management software for the client.   FEATURE DETAILS    NetWare Volumes/File Services   @ PATHWORKS for OpenVMS (NetWare) provides NetWare clients with a H remote file system that appears as a transparent extension of the client% system's local computing environment.   F PATHWORKS for OpenVMS (NetWare) services are based on Novell's NetWareB Core Protocols (NCPs) and have been certified by Novell as a fully5 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 @ hybrid user. This feature allows users who are both interactive I OpenVMS 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 B OpenVMS account. You can map drives to this HOME volume and/or to B directories below it. You have access rights to all files in that C directory just as if you were logged in to your account on OpenVMS.   D Multiple NetWare clients can concurrently access files stored on theB server's disk through the file access modes and byte-range locking; support 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  C PATHWORKS for OpenVMS (NetWare) software allows NetWare clients to  E access 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 F queues and defines forms for selected DIGITAL and third-party printers@ using standard OpenVMS commands. The administrator then uses theE PATHWORKS for OpenVMS (NetWare) SCONSOLE utility to associate NetWare > print queues with OpenVMS print queues. Refer to the Optional  Hardware section for details.   E Multiple NetWare print queues may be set up for the same printer. FortF example, a landscape service and a portrait service may be created forG the same PrintServer 40 Plus printer. In addition, other printer queues J can be manually set to support additional DIGITAL and third-party printers! that are not listed in the menus.W  I NetWare print queues and the NetWare print servers servicing those queuesNG may reside on different physical systems. Because PATHWORKS for OpenVMSOA (NetWare) includes a NetWare-compliant PSERVER implementation, itgF is compatible with many versions of Novell's print servers, including:   o  NetWare 3.X (PSERVER.NLM)   o  NetWare 2.X (PSERVER.VAP)   o  Dedicated DOS (PSERVER.EXE)  H o  Network printers providing a NetWare compliant PSERVER implementation  
 o  Router VAP   ( o  NetWare for UNIX print server daemons  C Compatibility with NetWare for UNIX print server daemons means thatdC PATHWORKS for OpenVMS (NetWare) will interoperate with other NovellmC Certified implementation of NetWare for UNIX provided by DIGITAL oro by other vendors.n  F Any type of NetWare print server is capable of servicing NetWare printC queues located on any NetWare file server. To service NetWare printoC queues associated with remote NetWare file servers, a PATHWORKS fortC OpenVMS (NetWare) print server must be configured to attach to each   "                                  5 W     D NetWare file server associated with each NetWare print queue that it
 will service.m  F Similarly, to be serviced by remote NetWare print servers, a PATHWORKSA for OpenVMS (NetWare) print queue would need to be configured to e allow 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 orr using the PCONSOLE utility.N  E Interactive OpenVMS users can also queue print jobs to remote NetWareeC print servers by simply queuing to normal OpenVMS print queues thatcF have been set up by PATHWORKS for OpenVMS (NetWare) to send print jobs+ to the desired remote NetWare print server.h   Server Management and Controlp  ? SCONSOLE, an OpenVMS Utility used with standard NetWare client lC utilities, provides the complete set of tools needed to manage the w' PATHWORKS for OpenVMS (NetWare) server.H  E SCONSOLE is used to manage OpenVMS-specific functions related to thise, 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 queuesn  " o  Modify server security settings   o  Add and delete hybrid users  ' o  Configure and tune server componentsp  5 o  Display server specific statistics and informationj  "                                  6 r      Network Connectivity  
 o  IPX/SPX  A The PATHWORKS for OpenVMS (NetWare) software includes an OpenVMS mE implementation of the two transport protocols used by Novell's native  NetWare products:N  (    -  IPX (Internetwork Packet Exchange)  %    -  SPX (Sequenced Packet Exchange)   D IPX is delivered as a STREAMS driver in this product and is used forA all NetWare-related client/server functions. The IPX protocol is n? transmitted as datagram packets between source and destination.c  C SPX provides a layer above the IPX protocol that tracks IPX packetsrC to ensure that each packet is successfully received by its intendedv destination.  * o  Novell Virtual Terminal (NVT2) Protocol  I NVT2 support consists of server software and software that must be loadedi on each client.c  B On the PATHWORKS for OpenVMS (NetWare) server, an OpenVMS process C provides Virtual Terminal services over SPX (using IPX). Each NVT2 pA connection requires a corresponding SPX connection. Therefore, a p= maximum of 1000 concurrent NVT2 connections can be supported.n  ? The NVT2 software for DOS-based clients (TSR or VLM) redirects oH terminal I/O through INT14 or INT6b interrupt modes, the interfaces usedE by most terminal emulation applications. Note that the PATHWORKS V6.0 D for DOS and Windows SETHOST terminal emulation application also uses these interfaces.n   o  IPX Tunneling Within DECnet  E PATHWORKS for OpenVMS (NetWare) includes the capability of connecting ? one or more NetWare LANs using a DECnet WAN. The tunnel driver eG encapsulates 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.i  "                                  7 a  n  # Performance-Enhancing XQP+ Servicesl  B PATHWORKS for OpenVMS (NetWare) includes a special release of the J enhanced OpenVMS file system, known as XQP+ (eXtended QIO Processor Plus).C XQP+ is integral to OpenVMS V6.1 or later and is separately instal-eD lable on VAX/VMS V5.5-2 and OpenVMS VAX V6.0 systems. XQP+ provides E improved concurrency using multithreading, which results in improved u' performance for file system operations.   
 Mail Servicesb  E The mail server component of PATHWORKS for OpenVMS (NetWare) providescG 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 andoD requires DECnet as its communications transport. It allows PATHWORKSD users, using the client PATHWORKS Mail software, to send and receiveA electronic mail messages without having to log in to the OpenVMS n 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 thenyF 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,gC notification of new messages occurs both in real time (which may be ? optionally disabled) and upon log in to a network MAIL session.l   Installation and Configuration  D PATHWORKS for OpenVMS (NetWare) shares code with, and is distributed> with, both PATHWORKS V5.0F for OpenVMS (LAN Manager) and with D PATHWORKS V6.0 for OpenVMS (Advanced Server) (though still licensed H separately). A single installation procedure is shared between PATHWORKSD for OpenVMS (NetWare) and PATHWORKS V5.0F for OpenVMS (LAN Manager).      "                                  8 p  t  @ Another, different single installation procedure shared between H PATHWORKS for OpenVMS (NetWare) and PATHWORKS V6.0 for OpenVMS (AdvancedD Server). Both procedures provide for the installation of one or bothA associated server products in a single step on an OpenVMS system rD using the standard VMSINSTAL procedure. An Installation VerificationG Procedure (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 software@ product at each site include DIGITAL installation service. This A service provides implementation support for customers installing  G PATHWORKS for OpenVMS (NetWare) software and for the integration of PC pB workstations into the DIGITAL network. Contact your local DIGITAL @ representative for information on the service options available.   License Management  B PATHWORKS for OpenVMS (NetWare) offers several license management D capabilities 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,sE on an OpenVMS system that is acting as a PATHWORKS License Server.[1]d? A single copy of the PATHWORKS License Server software can now eF provide and verify client-based licenses for clients using NetWare and? LAN Manager software. NetWare clients use the IPX transport to  F communicate with a PATHWORKS License Server, while LAN Manager clients. use the DECnet, NetBEUI, or TCP/IP transports.   ____________________G [1] Although  the License Server can be active only on a single node in D a cluster, if that node goes down for any reason, the License ServerF will automatically activate itself on another node in the cluster that is still running PATHWORKS.i    "                                  9    s  E The PATHWORKS License Manager, which must execute on the same node aseD the License Server, provides a user interface that allows the systemF manager to monitor client license usage. The PATHWORKS License Manager@ is also used to preallocate licenses to specific groups of users' and to reclaim a license from a client.r  E The PATHWORKS License Registrar, which executes on the same system asIC the file server, will "handshake" with clients requesting access toeD PATHWORKS for OpenVMS (NetWare) functions. Clients that can success-C fully "handshake" with the server and produce a valid client-based XG license will be allowed access to the services offered by the PATHWORKS  for OpenVMS (NetWare) server.N  " 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 accessA to the server fails to produce a valid client-based license, the  J PATHWORKS License Registrar software checks the local LMF database for the@ availability of a PATHWORKS for OpenVMS (NetWare) PC Concurrent G (formerly known as FPS) license. If one is available, and the number ofuC concurrently connected clients allowed by the license has not been e, exceeded, the client will be allowed access.  D PATHWORKS for OpenVMS (NetWare) servers always allow you to use bothA client-based and server-based licenses, simultaneously. However, tE because clients that do have a valid client-based license are alreadyMC licensed to use the server software, they are never counted againstyB the fixed number of clients granted access by the server-based PC  Concurrent license.p   RESTRICTIONS AND LIMITATIONS  E o  NetWare NLMs are not usable with a PATHWORKS for OpenVMS (NetWare) G    server. NetWare NLMs are typically applications or utilities writtentA    specifically for an Intel platform using NetWare 3.x or for antF    Intel platform using NetWare 4.x as the host operating system. They1    are not easily portable to other environments.r    "                                 10        o  Portable NetWAre V3.01B  A PATHWORKS for OpenVMS (NetWare) is an implementation of Portable  G NetWare V3.01B. As such, certain features currently available in Novell ? NetWare 3.x, Intel-based servers are not included. Among these C
 features are:n  E    -  The PATHWORKS for OpenVMS (NetWare) print server implementationtH       cannot be used with DOS-based clients configured with RPRINTER.EXE@       or network-based printers that implement NetWare's RPRINT        protocol.m  @    -  Burst mode technology, or "packet burst", is not supported  ?    -  Windows NT client software from Novell is not supported. )D       However, Windows NT NetWare client software from Microsoft is        supported.  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:  B    -  Ethernet using IEEE 802.3 (SNAP) frame type (used mainly by        Macintosh systems)      -  Arcnet  K    -  Token Ring on VAX systems (Token Ring on Alpha systems is supported.)   5 o  The OpenVMS Spiralog file system is not supported.t  C o  Though Novell's raw 802.3 Ethernet frame type is supported, some D    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-I%    tation for additional information.e  D o  PATHWORKS for OpenVMS (NetWare) is not supported with OpenVMS VAX#    V6.0 or with OpenVMS Alpha V1.5.i  "                                 11 i  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)a      -  250 NetWare volumesn  E    -  1000 SPX connections (each NVT2 session uses an SPX connection)   C o  Though NetWare volumes may be dynamically marked for addition or L    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.i  ( o  PATHWORKS V1.0F for OpenVMS (NetWare)  C Delivered on the PATHWORKS V5.0F for OpenVMS distribution media andfB designed to coexist with PATHWORKS V5.0F for OpenVMS (LAN Manager)F software, it can be run on VAX and Alpha systems and with a number of D different versions of OpenVMS either stand alone or coexisting with * PATHWORKS V5.0F for OpenVMS (LAN Manager).  ) o  PATHWORKS V1.0G for OpenVMS (NetWare).e  C Delivered on the PATHWORKS V6.0 for OpenVMS distribution media and eE designed to coexist with PATHWORKS V6.0 for OpenVMS (Advanced Server)a@ software, it can be run only on Alpha systems with OpenVMS V7.1 @ either stand alone or coexisting with PATHWORKS V6.0 for OpenVMS (Advanced Server).      "                                 12 s  e  D Though both V1.0F and V1.0G can be run stand alone and would deliver? identical services, V1.0F should normally be used, because the RJ hardware and software environments it supports include all those supported by V1.0G and and many more.s  ' PATHWORKS Server Combinations for V1.0Fp  ? The following PATHWORKS server products can be run on the same n0 system as PATHWORKS V1.0F for OpenVMS (NetWare):      PATHWORKS for VMS V4.x[1]/    PATHWORKS V5.0F for OpenVMS (LAN Manager)[1]r)    PATHWORKS V1.x for OpenVMS (Macintosh)   B The following PATHWORKS server products cannot be run on the same 0 system as PATHWORKS V1.0F for OpenVMS (NetWare):  4    Any PATHWORKS V1.0x for OpenVMS (NetWare) product+    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),    PATHWORKS V5.0E for OpenVMS (LAN Manager)/    PATHWORKS V6.0 for OpenVMS (Advanced Server)g  ? If you attempt to install PATHWORKS for OpenVMS (NetWare) on a uJ system running any of the software listed, you will automatically be givenA the option to upgrade related components to a compatible version.p           ____________________I [1] PATHWORKS  for VMS V4.x and PATHWORKS V5.0F for OpenVMS (LAN Manager)u2 cannot be run on the same system at the same time.    "                                 13 n  l  ' PATHWORKS Server Combinations for V1.0Gt  ? The following PATHWORKS server products can be run on the same  0 system 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)c  B The following PATHWORKS server products cannot be run on the same 0 system as PATHWORKS V1.0G for OpenVMS (NetWare):  3    Any PATHWORKS V1.0x for OpenVMS (NetWare) serverc7    Any PATHWORKS V5.0x for OpenVMS (LAN Manager) serverg  ? If you attempt to install PATHWORKS for OpenVMS (NetWare) on a sJ system running any of the software listed, you will automatically be givenA the option to upgrade related components to a compatible version.n   HARDWARE REQUIREMENTSw  C The following systems, components, and peripherals are supported asa
 specified:   Supported Processors  - o  For PATHWORKS V1.0F for OpenVMS (NetWare):h  C All VAX and Alpha processors supported by the version of OpenVMS in  use are also supported.o         ____________________L [1] PATHWORKS  for VMS V4.x and PATHWORKS V6.0 for OpenVMS (Advanced Server)2 cannot be run on the same system at the same time.    "                                 14 t  f   Exceptions:e  C    ________________________________________________________________ 6    MicroVAX                VAXstation              VAXC    ________________________________________________________________v  =    MicroVAX I              VAXstation I            VAX-11/725c=    MicroVAX II             VAXstation II           VAX-11/730d  =    MicroVAX 2000           VAXstation 2000         VAX-11/750a  >                            VAXstation 8000         VAX-11/780,=                                                    VAX-11/785nC    ________________________________________________________________t  - o  For PATHWORKS V1.0G for OpenVMS (NetWare):   / All Alpha processors supported by OpenVMS V7.1.e   Memory Requirementsl  @ PATHWORKS for OpenVMS (NetWare) requires the following physical D memory for proper installation, configuration, and execution of the 	 software:o  - o  For PATHWORKS V1.0F for OpenVMS (NetWare):e  = 16 MBytes on VAX systems (24 MBytes if used with DECnet-Plus)   - o  For PATHWORKS V1.0G for OpenVMS (NetWare):i   or  & PATHWORKS V1.0F for OpenVMS (NetWare):   64 MBytes on Alpha systems  E The memory requirements indicated are minimum requirements to install D and run the server. Memory requirements can vary widely according toA the server CPU, the number of clients using the server and their iD activities, and the other applications running on the server system.  D The recommended minimum is twice the memory of the absolute minimums
 specified.  "                                 15    e   Disk Space Requirementst  A The following table provides the disk space requirements for the hA installation and configuration of PATHWORKS for OpenVMS (NetWare)rF either stand alone, with PATHWORKS V5.0F for OpenVMS (LAN Manager), orE with PATHWORKS V6.0 for OpenVMS (Advanced Server) software. Note that D 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.t  C These sizes are approximate; actual sizes may vary depending on ther? user's system environment, configuration, and software options.b  H You should also plan for additional, significant disk-space requirementsA once the product is in use, for items such as data files, virtuala. memory section files, log files, and so forth.  C ___________________________________________________________________I? Installation/Configuration        VAX Systems     Alpha Systemsn: Requirements                      (Blocks)        (Blocks)C ___________________________________________________________________d  " Installation Space Requirements[1]C ___________________________________________________________________    Images and Command Files:   9     NetWare software only          20,000          36,000o  9     with LAN Manager V5.0F         44,000          66,000s     software  9     with Advanced Server V6.0     N/A             141,000D     software  9   NetWare System Volume[2]         34,000          34,000KC ___________________________________________________________________oB [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.   @ [2]The NetWare SYS Volume contains the NetWare utilities used by NetWare clients.  "                                 16 e  s  C ___________________________________________________________________n? Installation/Configuration        VAX Systems     Alpha Systemss: Requirements                      (Blocks)        (Blocks)C ___________________________________________________________________h  C Configuration_Space_Requirements___________________________________tC ___________________________________________________________________)   PATHWORKS server data files:  9     NetWare software, only          6,000           6,000   9     with LAN Manager V5.0F         12,500          12,500i     software  9     with Advanced Server V6.0         N/A          77,500W     software  9     NetWare Configuration files,    1,000           1,000u     etc.[3]V  C ___________________________________________________________________r   TotalsC ___________________________________________________________________i  9     NetWare software, only         61,000          77,000o  9     with LAN Manager V5.0F         91,500         113,500d     software  9     with Advanced Server V6.0         N/A         219,500      softwareC ___________________________________________________________________S? [3]These files are typically stored on the OpenVMS system disk.fC ___________________________________________________________________h   Network Interface Controllersi  C At least one network interface controller is required for use with eE PATHWORKS for OpenVMS (NetWare). The following devices are supported:i  1 o  All DIGITAL VAX and Alpha Ethernet controllers   ' Supported Ethernet frame types include:d      -  Ethernet IIt  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.")R;       (For more information, see the Restrictions section.)S  "                                 17 e  e  - o  All DIGITAL VAX and Alpha FDDI controllers   8 o  All DIGITAL Token Ring controllers for Alpha systems.  # Optional Hardware: DIGITAL Printersa  I All printers supported by the OpenVMS Operating System using print queues 6 are also supported by PATHWORKS for OpenVMS (NetWare).  C DIGITAL PostScript[R] printers require the use of DECprint Supervi-e@ sor (DCPS) for OpenVMS V1.3. DCPS software is included with the G PATHWORKS for OpenVMS (NetWare) media, but the use of the DCPS softwarea0 requires the purchase of an appropriate license.  ? Refer to SPD 44.15.xx for DCPS licensing information and for a oJ complete list of the DIGITAL and non-DIGITAL PostScript printers supported by DCPS.                                          "                                 18    n  I The NetWare Print Definition Files (.PDF) are provided for the following t	 printers:y   Colormate PS     LJ250   DEClaser 1100    LN03  DEClaser 1150    LN03 PLUS$ DEClaser 1152    LN03R ScriptPrinter DEClaser 2100    PrintServer 17  DEClaser 2100    PrintServer 20  plus% DEClaser 2150    Turbo PrintServer 20  DEClaser 2150    PrintServer 32O plus DEClaser 2200    PrintServer 40D% DEClaser 2200    Print Server 40 PlusS plus
 DEClaser 2250A
 DEClaser 2250P plus
 DEClaser 3200n
 DEClaser 3250e   LA70 LA75	 LA75 Plust LA210l LA310O LA324  LA424    OpenVMS CLUSTER ENVIRONMENTg  A The PATHWORKS for OpenVMS (NetWare) server provides for a common iJ NetWare SYS volume across OpenVMS cluster members running the server. ThisK means that a single bindery and trustee database is maintained clusterwide.L          "                                 19       D In addition, NetWare volumes can also be made available clusterwide.E A volume defined by SCONSOLE on one cluster member running the servertC can also be configured so that it is available to all other clustertD servers. However, concurrent file sharing between servers running on+ different cluster members is not supported.p   SOFTWARE REQUIREMENTS    Operating System Softwareo  - o  For PATHWORKS V1.0F for OpenVMS (NetWare):O      -  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-2f=       OpenVMS VAX Operating System V6.1, V6.2, V7.0, and V7.1   - o  For PATHWORKS V1.0G for OpenVMS (NetWare):l  # OpenVMS Alpha Operating System V7.1   C For minimum hardware requirements of the operating system, refer toE@ the Software Product Descriptions for the OpenVMS VAX Operating L System (SPD 25.01.xx) and the OpenVMS Alpha Operating System (SPD 41.87.xx).   OpenVMS Tailoring   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 SavesetH   o  Network Support   o  System Programming Support    o  Secure User's Environment  "                                 20        o  OPTL (Miscellaneous Files)_  C For more information on OpenVMS classes and tailoring, refer to theAI OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx)._   Network Transport Software   o  DECnet Software  C The DECnet network transport software is required by PATHWORKS for   OpenVMS (NetWare):  8    -  When acting as a MAIL server for PATHWORKS clients  C    -  To optionally tunnel IPX packets between two OpenVMS systems         using this software   A    -  When the PATHWORKS License Server is configured to service _5       PATHWORKS clients using LAN Manager and DECnet._  @ The license to use DECnet software is usually bundled with your / system but may need to be purchased separately.R  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 foriC OpenVMS (NetWare), if the PATHWORKS License Server is configured to 7 service PATHWORKS clients using LAN Manager and TCP/IP.   C When TCP/IP software is used for this purpose, it must be purchasedr@ separately. Please consult the Software Product Description for G PATHWORKS for OpenVMS (Advanced Server) and PATHWORKS for OpenVMS (LAN e@ Manager), SPD 30.50.xx, for currently supported TCP/IP products.      "                                 21 u  s   Associated Client Software  D The following software products may be used on personal computers to7 access PATHWORKS for OpenVMS (NetWare) server software:s  < 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)i  I o  NetWare clients using the latest, supported version of Novell's clientTA    shell, NETX.EXE, that also support native NetWare 3.0 servers.h  I o  NetWare clients using the latest, supported version of Novell's clienta@    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.    GROWTH CONSIDERATIONSa  E The minimum hardware and software requirements for any future versione? of this product may be different from the requirements for the o current version.  + SOFTWARE LICENSING AND ORDERING INFORMATION_  F PATHWORKS for OpenVMS (NetWare) can be licensed in two different ways.  - o  Client-Based Licensing (Designated Access)   C This product can be licensed for operation and access on any number_E of supported platforms to provide services to clients assigned appro-_ priate client-based licenses._  C See the terms and conditions for Designated Access licenses on youre9 Product Authorizations Keys (PAKs) or on the Internet at  . http://www.digital.com/info/software-licensingD 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._    "                                 22 _  _  ) o  Server-Based Licensing (PC Concurrent)m  E A PATHWORKS PC Concurrent license for this product permits its use onkD a single supported platform and allows access by clients that do not& have a PATHWORKS client-based license.  G See the terms and conditions for PC Concurrent licenses on your Product 1 Authorizations Keys (PAKs) or on the Internet at _. http://www.digital.com/info/software-licensingD 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._  B Note: Clients with client-based licenses for server access do not E interfere with the access of other clients that rely on server-based _F licensing 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:       QM-2CMAA-AB, 1 user    QM-2CMAA-AC, 10 usera    QM-2CMAA-AD, 25 userr    QM-2CMAA-AE, 50 user     QM-2CMAA-AF, 100 user    QM-2CMAA-AG, 250 user    QM-2CMAA-AH, 500 user    QM-2CMAA-AJ, 1000 usera  C The PATHWORKS V5.0 (NetWare) Designated Access licenses also grant i? access to the PATHWORKS V5.0 for DIGITAL UNIX (NetWare) server.   C See the terms and conditions for Designated Access licenses on youre9 Product Authorizations Keys (PAKs) or on the Internet at 0. http://www.digital.com/info/software-licensing1 for a description of the specific rights granted.l        "                                 23 i  f    Applicable Server-Based Licenses  3 PATHWORKS V1.0 for OpenVMS (NetWare) PC Concurrent:    For new users, order:o      QM-0ENAA-AB, 10-userl    QM-0ENAA-AC, 25-useri    QM-0ENAA-AD, 50-userM    QM-0ENAA-AE, 100-user    QM-0ENAA-AF, 250-user  G See the terms and conditions for PC Concurrent licenses on your Productf1 Authorizations Keys (PAKs) or on the Internet at  . http://www.digital.com/info/software-licensing1 for a description of the specific rights granted.     Discontinued License Information  E The following client-based licenses are no longer sold. However, they F continue to be valid for accessing the PATHWORKS for OpenVMS (NetWare) server:   ; o  PATHWORKS for DOS and Windows (NetWare) CCS, QM-0EKAA-Axp  0 o  PATHWORKS for OS/2 (NetWare) CCS, QM-506AA-Ax    Software Media and Documentation  H Software media and documentation are available in the following formats:  )    TK50 streaming tape media, QA-A93AA-H5e    CDROM media, QA-A93AA-H8e!    Documentation kit, QA-A93AA-H8   G In addition, PATHWORKS for OpenVMS (NetWare) software and documentationt is included in the following:e  C    DIGITAL OpenVMS Alpha Software Layered Products Library Package,     QA-03XAA-H8  "                                 24    t  M    DIGITAL OpenVMS VAX Software Layered Products Library Package, QA-5G88A-H8   F The above information is valid at time of release. Please contact yourG local DIGITAL sales representative for the most up-to-date information.t   SOFTWARE PRODUCT SERVICES   B A variety of service options are available from DIGITAL. For more D information, please contact your local DIGITAL sales representative.  B [R]  Apple, AppleShare, and Macintosh are registered trademarks of      Apple Computer, Inc.t  B [R]  Microsoft is a registered trademark of Microsoft Corporation.  A [R]  NetWare and Novell are registered trademarks of Novell, Inc.l  A [R]  OSF/1 is a registered trademark of Open Software Foundation, 	      Inc.2  @ [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.d  D [TM] Windows and Windows NT are trademarks of Microsoft Corporation.  8 [TM] The DIGITAL logo, DEC, DEClaser, DECnet, DECprint, @      DECserver, DECwindows, DIGITAL, Internet, LAT, LA324, LN03,B      LN03 PLUS, MicroVAX, OpenVMS, PATHWORKS, PrintServer, ULTRIX,?      VAX, VAX-11/750, VAX-11/780, VAX 8200, VAX 8250, VAX 8300,H@      VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 6000, VAX 9000,>      VAXft, VAXcluster, VAXserver, VAXstation, VAXstation 4000B      VLC, and VMS are trademarks of Digital Equipment Corporation.  9 1997 Digital Equipment Corporation. All Rights Reserved.r  "                                 25