     	  Software   Product  Description  D  ___________________________________________________________________  D  PRODUCT NAME:  PATHWORKS V1.3 for OpenVMS (Macintosh)  SPD 35.09.03    1  DESCRIPTION   E  PATHWORKS[TM] V1.3 for OpenVMS[TM] (Macintosh[R]) is a member of the G  PATHWORKS family of software products that provides Macintosh network- F  ing and network operating systems (NOS) integration in local and wideD  area networks. PATHWORKS integrates the broadest set of PCs, Macin-E  tosh's servers, NOSs, network transports, and protocols and provides E  the foundation for client-server applications and corporate informa-   tion exchanges.G  PATHWORKS provides a framework for integrating personal computers into F  an organization's total information system so that different types ofF  users can share information, large system resources, and network ser-&  vices across the entire organization.  E  PATHWORKS for OpenVMS (Macintosh) allows VAX[TM] and Alpha computers D  running the OpenVMS operating system to offer file, print, and mailD  to Macintosh clients. By using a VAX or Alpha server system, Macin-F  tosh users can share applications, data, printers, and resources, ac-D  cess information from remote systems on the network, and apply thatD  information in Macintosh applications. This product is described in"  the Software Product Description.  K  PATHWORKS for Macintosh - Macintosh software that allows Macintosh clients G  to access file, print, and mail on OpenVMS, or file and print services E  on RISC/ULTRIX[TM] systems. This software also includes applications E  for terminal emulation, X display services, TCP/IP utilities, client D  front end management, DECnet[TM], and mail. This product is used inG  conjunction with PATHWORKS for OpenVMS (Macintosh) and is required for H  Macintosh client access to these OpenVMS-based services (SPD 31.53.xx).H  This product is used in conjunction with DEC OSF/1[R] Alpha or Pacer[R]G  for ULTRIX and is required for Macintosh client access to RISC/UNIX[R]   /ULTRIX-based services.    2  Features  F  PATHWORKS for OpenVMS (Macintosh) provides the following features and  capabilities:    o  DECshare File Services    o  DECshare Print Services   #  o  Network-based server management     o  Mail for Macintosh server     o  AppleTalk[R] for OpenVMS  D                                DIGITAL                  January 1995  D                                                          AE-PJBDD-TE       )  o  AppleTalk-to-DECnet transport gateway       Server Software  G  PATHWORKS for OpenVMS (Macintosh) provides the Macintosh user with the +  following features of the server software:   D  o  DECshare File Services - The Macintosh user is provided with ac-E     cess to remote OpenVMS file systems as a transparent extension of E     the client's local disk facilities. Macintosh files are stored on D     the VAX and Alpha systems and accessed as if they were stored onF     the user's local disk. DECshare file services are based on the Ap-G     pleTalk for OpenVMS (V3.2) network transport and are compliant with 4     the Apple[R] Filing Protocol (AFP), Version 2.1.  D     DECshare file services assign the Macintosh type and creator at-D     tributes to files that were not created on a Macintosh. The cre-D     ator and type determine the icon that is displayed on the Macin-H     tosh desktop. When a Macintosh user selects a file that was not cre-G     ated using the Macintosh, DECshare assigns a type and creator based E     on the file's extension through a lookup table. This table may be 9     modified to tailor the server to site-specific needs.   G     Each Macintosh file stored on the file server is stored as an Open- E     VMS file in RMS Sequential file format. These Macintosh files are G     accessible to OpenVMS users and applications that can interpret the D     content and organization of a file written by a Macintosh appli-     cation.   D     The file server can read all RMS file types that can be read se-E     quentially, allowing Macintosh applications to read files written D     by an OpenVMS application. Each read issued by the Macintosh ap-H     plication results in the presentation to the application of the next/     n bytes contained sequentially in the file.   F     AFP byte-range locking is supported for Macintosh applications ac-4     cessing files provided through the file service.  E     System administrators can create file services that appear in any G     one of the local AppleTalk zones which provides flexibility in your H     environment. System administrators can also limit the number of con-D     nections to a file server volume and set a timeout value for in-I     active connections to a file server. The file server can detect unau- =     thorized intrusions using the OpenVMS Intrusion database.   E  o  DECshare Print Services - Remote printers appear to the Macintosh E     user as a transparent extension of the client's local facilities. D     Macintosh users can access OpenVMS print queues to print to bothD     Apple LaserWriter[R] and Digital PostScript[R] printers. The Ap-F     ple LaserWriter can be accessable to VMS users via a LocalTalk[R]-F     to-Ethernet router, a direct Ethernet connection (for those Laser-E     Writer printers that support this), a terminal server (LAT) port, @     or directly connected to a serial port on the server system.  #                                   2        G     The system administrator assigns a service name to the print queue. F     The Macintosh users select the printer from the Chooser as they doG     local printers. Then the printer I/O is directed to the defined and $     selected DECshare print service.  F     DECshare print services include support for the DECshare Receiver,H     which handles print requests from the Macintosh. The Receiver storesE     the PostScript data it receives from the Macintosh in a temporary E     OpenVMS file before sending the data to the OpenVMS print queuing D     system. System administrators can choose to disable the ReceiverG     so thatMacintosh users cannot print to a specific LaserWriter. Sys- D     tem administrators can also hide a LaserWriter from the Chooser,F     so that users who want to print to a specific printer are required0     to print through the DECshare print service.  E     DECshare print services also support the DECshare print symbiont, F     which transfers data from VAX and Alpha systems to an Apple Laser-E     Writer printer. The DECshare symbiont also converts an ASCII file D     submitted by an OpenVMS user to PostScript data before transfer-D     ring the data to the printer. The symbiont does not support fullD     ANSI conversion. DECshare uses the DECprint Printing Services to2     transfer data to a Digital PostScript printer.  J     The MSA$MANAGER utility is used to create print services. Print queuesD     for Digital's printers must be previously defined on the OpenVMSF     system. LaserWriter queues using the DECshare symbiont are created     by the MSA$MANAGER utility.   H  o  Server Management and Control - When a server offers a file resourceE     for use, the system administrator can associate an Access Control 7     List, which specifies privileges assigned to users.   D     While the software may be running on more than one node of a VM-F     Scluster[TM], each Macintosh Volume served can only be served fromG     a single file server in the cluster. As a result, there is no clus- %     ter fail-over of a served volume.   E     An administrator's utility (MSA$MANAGER) is provided to allow the H     system administrator to add and remove services, and show resources.F     The system administrator can also manage a remote server using the     SET REMOTE command.   E     A second administrator's utility (ATK$MANAGER) is provided to al- E     low the system administrator to set up and maintain AppleTalk for 7     OpenVMS and the AppleTalk/DECnet transport gateway.   D  o  PATHWORKS Mail SERVER- The mail server included in PATHWORKS forH     OpenVMS (Macintosh) provides Macintosh and PC clients with the abil-D     ity to send and receive electronic mail messages. A mail accountE     must be established on the OpenVMS server for each client, unless H     an account already exists. Mail can be sent to this account by otherG     Macintosh clients as well as users of any mail system that can com- H     municate with OpenVMS mail software.The mail server then routes mes-J     sages to the appropriate client when the client logs in to the server.  #                                   3        G     The PATHWORKS for OpenVMS (Macintosh) mail server provides the Mac- D     intosh user with folders, distribution lists, and delivery capa-D     bilities. Notification of new messages occurs when the MacintoshH     user logs in to a network session and the PATHWORKS Listener is run-     ning on the client.       Network Connectivity   F  AppleTalk for OpenVMS Version 3.2 is an implementation of Apple's Ap-F  pleTalk Networking protocols and interface libraries for OpenVMS sys-D  tems. AppleTalk for OpenVMS allows an OpenVMS system to communicateD  with an AppleTalk network. The DECshare file and print services useE  this network transport. The AppleTalk for OpenVMS protocol stack in- D  cludes support for the following protocols: ADSP, AELAP, AARP, AEP,L  NBP, ZIP, RTMP (full set), ATP, ASP (server only), PAP (client and server).D  The ASP client and the AFP protocols are not implemented in the Ap-$  pleTalk for OpenVMS protocol stack.  E  AppleTalk for OpenVMS, Version 3.2 supports AppleTalk Phase 2 proto- E  cols. Only Macintosh computers connected to Phase 2 networks can ac- +  cess services using AppleTalk for OpenVMS.   F  AppleTalk for OpenVMS also allows routing, or tunneling, through DEC-H  net. When tunneling, AppleTalk packets are encapsulated in DECnet pack-G  ets so that the AppleTalk network can be extended, and Macintosh users E  can access remote AppleTalk networks and servers as if they were lo-   cal.   G  The router provides AppleTalk Internet routing, zone management, rout- D  ing table maintenance, and name-binding broadcast request handling.E  When routing, or tunneling, datalink speeds below 56 kilobits/second_G  are not recommended and speeds below 19.2 kilobits/second are not sup-eF  ported. The datalink speed must be capable of handling DECnet and Ap-F  pleTalk traffic (including all protocol overhead) without congestion.F  That is, there must be sufficient bandwidth to maintain reliable com-
  munications.e  E  AppleTalk/DECnet Gateway, which is OpenVMS software, connects a Mac-tE  intosh with a DECnet service on any DECnet node. As a result, Macin-sD  tosh users who have only AppleTalk connectivity but no DECnet resi-F  dent software can participate in task-to-task applications. MacintoshH  applications that are written to take advantage of the AppleTalk/DECnetD  gateway can participate in AppleTalk/DECnet task-to-task communica-H  tions. The gateway provides bi-directional conversion between AppleTalkD  ADSP and DECnet NSP protocols. The gateway supports up to 1000 con-G  nections from client applications- provided that sufficient system CPUrF  and memory resources are available. Significant system tuning will beG  necessary if the number of sessions is raised appreciably from the de- 
  fault of 32.a    Restrictions and Limitations       #                                   4f a  n  F  Because PATHWORKS for OpenVMS (Macintosh) uses AppleTalk Phase 2 pro-G  tocols, services provided by PATHWORKS for OpenVMS (Macintosh) serversaE  will only be accessible to Macintoshes that are connected to Phase 2oD  networks. Phase 1 networks can co-exist with Phase 2, provided thatE  Phase 1 to Phase 2 transition router is suitably placed somewhere ineE  the network. Use of Phase 1 protocols anywhere in the network is noti/  recommended due to the increased network load.H  H  While AFP byte range locking is supported among Macintosh clients, onlyI  file locking is supported with other types of clients (DOS and OS/2)[R].c  G  For a serially connected LaserWriter, the following characters in font D  families are not available: Ctrl-C, Ctrl-D, Ctrl-Q, Ctrl-S, Ctrl-T.F  These characters are used by the PostScript interpreter for handshak-I  ing purposes. Attempts to print these characters result in a space char-sF  acter. This restriction does not apply to AppleTalk printers directly$  connected on Ethernet or LocalTalk.  F  The PATHWORKS Mail server restricts folder names to 39 characters. IfF  a user creates a folder with more than 39 characters in the name, the,  name is truncated after the 39th character.  F  The DECshare implementation of AFP V2.1 does not support Blank Access,  Privileges or the AFP Cat Search functions.    3  SOFTWARE REQUIREMENTSs  ;  For Systems Using Terminals (No DECwindows[TM] Interface):u  9  o  OpenVMS VAX Operating System V5.5-2 - V6.1 or greatert  1  o  OpenVMS Alpha Operating System 6.1 or greaterl  %  For Workstations Running DECwindows:   9  o  OpenVMS VAX Operating System V5.5-2 - V6.1 or greatert  1  o  OpenVMS Alpha Operating System 6.1 or greaterr  '  o  DECWindows/Motif[R] V1.1 or greaterl    OpenVMS Tailoring  E  For OpenVMS V5.x systems, the following OpenVMS classes are requiredt  for full functionality:    o  OpenVMS Required Saveset    o  Network Supporta    o  System Programming    o  Secure User's Environment   D  For more information on OpenVMS classes and tailoring, refer to theJ  OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx).  #                                   5e c  o  E  For printers listed in the Optional Digital Hardware section of thisoH  SPD, appropriate supporting software (such as DECprint[R] Printing Ser-'  vices V4.1, SPD 32.41.xx) is required.h  D  AppleTalk tunneling and the AppleTalk/DECnet gateway require DECnetF  or DECnet/OSI for OpenVMS VAX V5.5. For DECnet/OSI support, the Open-F  VMS node must have a Phase IV compatible name in the back translation  table.n    4  HARDWARE REQUIREMENTSt  F  PATHWORKS for OpenVMS (Macintosh) has been tested on a number of sup-F  ported configurations. If a customer problem with PATHWORKS for Open-H  VMS (Macintosh) is reproduced by the customer on one of these supportedE  configurations, Digital will work the problem to resolution on thesetG  supported configurations. If the customer problem cannot be reproduced D  by the customer on one of these supported configurations, it is the5  responsibility of the customer to resolve the issue.f  F  PATHWORKS supports all VAX and Alpha systems, components, and periph-D  erals that are supported by the versions of OpenVMS that are listed5  as supported in the OpenVMS SPD's for VAX and Alpha.s    Processors Not Supported   .  o  MicroVAX[TM] I, MicroVAX II, MicroVAX 2000  E  o  VAXstationMicroVAX[TM] I, VAXstation II, VAXstation 2000, VAXsta-l
     tion 8000t  &  o  VAX-11/725, VAX-11/730, VAX 11/782    Other Hardware Requirements  D  The VAX or Alpha system must be connected to the same AppleTalk In-2  ternet or DECnet network as the Macintosh client.  G  A minimum of 1 MB of available free list memory is required to install D  and run the server process. Depending on client print and file ser-G  vice workload, up to 1 MB of additional memory should be allocated foraF  every 5 Macintosh clients. Ten percent of total memory should be leftE  in free list. In the above case, virtual memory (pagefile space) re-e/  quired is 4 megabytes per 5 Macintosh clients.r  D  PATHWORKS for OpenVMS (Macintosh) supports all valid Digital VAX orE  Alpha Ethernet or FDDI controllers. Refer to the OpenVMS VAX Operat-iH  ing System (SPD 25.01.xx) for more information about these controllers.E  LocalTalk connections are not supported by the VAX or Alpha hardwareeD  and Token Ring connections are not supported by PATHWORKS for Open-G  VMS (Macintosh). The use of some external routers to connect LocalTalkrI  or TokenTalk Macintosh networks to Ethernet is supported. Refer to PATH-t9  WORKS for Macintosh (SPD 31.56.xx) for more information.M      #                                   6M r     2  Disk Space Requirements (Block Cluster Size = 1):
  eightpointss   9  Disk space required for    20,800 blocks (10,400 Kbytes)i  VAX installation 9  Disk space required for    24,600 blocks (12,300 Kbytes)h  Alpha installationa8  Disk space required for    18,300 blocks (9,150 Kbytes)  VAX use (permanent)9  Disk space required for    22,100 blocks (11,050 Kbytes)e  Alpha use (permanent)  F  These counts refer to the disk space required on the system disk. TheE  sizes are approximate; actual sizes may vary depending on the user'seF  system environment, configuration, and software options. These counts*  include the OpenVMS server software only.    5  Optional Apple Hardwareu  H  The following hardware options may be added to the configurations (sub-E  ject to the limitations of the system chosen) described in the HARD-$  WARE REQUIREMENTS sections.  D  PATHWORKS for OpenVMS (Macintosh) supports the following Apple Com-!  puter PostScript laser printers:     o  LaserWriter Plus    o  LaserWriter II NTb    o  LaserWriter II NTX    o  LaserWriter IIf     o  LaserWriter IIgn    o  LaserWriter Pro 600 and 630s    o  LaserWriter Select 360    6  Optional Digital Hardwareo  D  PATHWORKS for OpenVMS (Macintosh) supports the following PostScript  Digital printers:    o  PrintServer[TM] 40 Plus     o  PrintServer 40    o  PrintServer 32    o  PrintServer 20 Turbo    o  PrintServer 20    o  ColorMate PS    o  LN03R ScriptPrinter[TM]A    o  DEClaser[TM] 1150l  #                                   7u         o  DEClaser 1152s    o  DEClaser 2150)    o  DEClaser 2250     o  DEClaser 3250n    o  DECcolorwriter 1000s    o  DEClaser 3500o    o  DEClaser 3500m    7  CLUSTER ENVIRONMENTa  F  While the software may be running on more than one node of a VMSclus-H  ter, each Macintosh Volume served can be served only from a single fileH  server on a single system in the cluster. As a result, there is no sup-/  port for cluster fail-over of a served volume.O    8  GROWTH CONSIDERATIONSv  E  The minimum hardware/software requirements for any future version ofaD  this product may be different from the requirements for the current	  version.s    9  DISTRIBUTION MEDIA  )  TK50 Tape Cartridge, CD-ROM, or MAG Tapeh    10  SOFTWARE LICENSINGc  '  PATHWORKS V1.3 for OpenVMS (Macintosh)i#  Client based Licensing (CCS & FPA)e  D  This product may be licensed for operation and access on any numberG  of supported platforms when appropriate client-based licenses are pur-e7  chased for clients using the services of this product..  D  The PATHWORKS for Macintosh license gives the user the right to useG  the client software on a single Macintosh CPU and to use the PATHWORKShD  for OpenVMS (Macintosh) server software on one or more VAX or AlphaE  systems, or the Pacer for ULTRIX server software on one or more RISC )  /ULTRIX systems, or DEC OSF/1 for Alpha.i  E  See the attached PATHWORKS license terms and conditions for Combina-kK  tion Client Server ("CCS". in section 1) and File and Print Access ("FPA",kI  in section 2) licenses for a description of the specific rights granted.r$  See below for ordering information.  I  A license must be obtained in advance for each Macintosh system on whichuG  the PATHWORKS for Macintosh client software is installed or from which D  the PATHWORKS for OpenVMS (Macintosh), Pacer for ULTRIX, or DEC OSF   /1 Alpha services are accessed.  #                                   8v .  T    11  ORDERING INFORMATIONt  F  Use of the PATHWORKS V1.3 for OpenVMS (Macintosh) software may be li-B  censed on a per-client basis, using the licenses described below.  $  o  PATHWORKS V1.3 for Macintosh CCS+        (One required per Macintosh client.)   1        QM-YPH9A-AA (multiple licenses per PAK[1])f+        QM-YPH9A-A1 (single license per PAK)   B  For existing users, the following upgrade licenses are available:  +  o  QM-YPH9B-AA (multiple licenses per PAK)t  (  o  QM-YPH9B-A1 (single license per PAK)  $  o  PATHWORKS V1.3 for Macintosh FPA+        (One required per Macintosh client.)e  .        QM-OEAAA-AA (multiple licenses per PAK)+        QM-OEAAA-A1 (single license per PAK)n    Media and Documentation  %  Media and Documentation: QA-YPCAA-H*n     (Minimum of one required.)  Programmer's Documentation:     QA-YPCAC-GZ (Optional.)l    Documentation  E  Server Administration documentation includes the Introduction to theaE  AppleTalk Network System, Server Installation Guide, Server Adminis-e=  trator's Guide, and Server Administrator's Reference Manual.n  E  Programmers' documentation includes the Programmer's Guide, Program-nG  mer's Reference, DECnet for Macintosh Programmer's Reference, Program-e  mer's ReadMe.  F  Note: The availability of these software product options and servicesF  may vary by country. Customers should contact their local Digital of-&  fice for information on availability.    12  SOFTWARE PRODUCT SERVICES  F  A variety of service options are available from Digital. For more in-.  formation, contact your local Digital office.      ____________________a  -  PAK   stands for "Product Authorization Key"u    #                                   9i    l  
  eightpointssd  ?  [R] OSF/1 and Motif are registered trademarks of Open SoftwareS     Foundation, Inc.  ?  [R] Microsoft, MS-DOS, and NT are registered trademarks of Mi-b     crosoft Corporation.  A  [R] OS/2 is a registered trademark of International Business Ma-      chines Corporation.   3  [R] Pacer is a registered trademark of Pacer, Inc.l  ?  [R] PostScript is a registered trademark of Adobe Systems Inc.   @  [R] Apple, AppleTalk, LaserWriter, LocalTalk, Macintosh and To-=     kenTalk are registered trademarks of Apple Computer, Inc.i  B  [R] UNIX is a registered trademark licensed exclusively by X/Open     Company, Ltd.s  C  [TM]The DIGITAL logo, DEC, DECnet, DECprint, DEClaser, DECwindows,t>     Digital, LN03 ScriptPrinter, MicroVAX, OpenVMS, PATHWORKS,A     PrintServer, TK, ULTRIX, VAX, VAXstation, and VMS, are trade-s+     marks of Digital Equipment Corporation.                                                             #                                  10a r  n  :  1995 Digital Equipment Corporation. All Rights Reserved.      1                    DIGITAL LICENSE AGREEMENTS fori+                          PATHWORKS ProgramsA                %                                 STOP!r  E  IMPORTANT - CAREFULLY READ THE DIGITAL LICENSE AGREEMENT BEFORE PRO-yE  CEEDING. IF YOU DO NOT AGREE TO ITS TERMS, PLEASE RETURN THE LICENSEsD  AGREEMENT AND ALL ACCOMPANYING MATERIALS WITHOUT FURTHER OPENING ORE  USING THEM. RETURN THEM TO THE SUPPLIER FROM WHICH YOU OBTAINED THEMeE  FOR A FULL REFUND. FURTHER OPENING OR USE OF THE MATERIALS INDICATESu7  YOUR ACCEPTANCE OF THE TERMS OF THE LICENSE AGREEMENT.c  E  A Product Authorization Key constitutes proof of license, and is re-DE  quired to permit use of the Software in accordance with these terms.                                                             #                                  11n E  n        )                             LICENSE TERMS         PATHWORKS_CCS_Licenses:    D     A. License: PATHWORKS V5.1 for DOS and Windows[TM] (LAN Manager)
        CCS  G  When you purchase the above license you may use the following programssD  ("Software") under the terms in Section 1 and all terms provided in  Additional Terms below.             Client Programs:  /              PATHWORKS V5.1 for DOS and Windowsm.              PATHWORKS X.25 (DOS), any version1              PATHWORKS ISDN[R] (DOS), any versiontD              PATHWORKS for DOS (NetWare[R] Coexistence), any version>              PATHWORKS Remote for DOS and Windows, any version             Server Programs:  5              PATHWORKS V5.0 for OpenVMS (LAN Manager)e'              PATHWORKS for ULTRIX, V1.3d0              PATHWORKS V5.0 for DEC OSF/1[R] AXP0              PATHWORKS for SCO[TM] UNIX[R], V1.1  C     B. License: PATHWORKS V4.1 for Windows NT[TM] (LAN Manager) CCSh  G  When you purchase the above license you may use the following programsQD  ("Software") under the terms in Section 1 and all terms provided in  Additional Terms below.             Client Program:r  *              PATHWORKS V4.1 for Windows NT             Server Programs:  5              PATHWORKS V5.0 for OpenVMS (LAN Manager)l'              PATHWORKS for ULTRIX, V1.3t-              PATHWORKS V5.0 for DEC OSF/1 AXPo)              PATHWORKS for SCO UNIX, V1.1r              #                                  12e r  o  <     C. License: PATHWORKS V5.0 for OS/2[R] (LAN Manager) CCS  G  When you purchase the above license you may use the following programs D  ("Software") under the terms in Section 1 and all terms provided in  Additional Terms below.             Client Program:o  $              PATHWORKS V5.0 for OS/2             Server Programs:  5              PATHWORKS V5.0 for OpenVMS (LAN Manager) '              PATHWORKS for ULTRIX, V1.35-              PATHWORKS V5.0 for DEC OSF/1 AXPu)              PATHWORKS for SCO UNIX, V1.1e  @     D. License: PATHWORKS V5.1 for DOS and Windows (NetWare) CCS  G  When you purchase the above license you may use the following programs D  ("Software") under the terms in Section 1 and all terms provided in  Additional Terms below.             Client Programs:  /              PATHWORKS V5.1 for DOS and Windowsc.              PATHWORKS X.25 (DOS), any version.              PATHWORKS ISDN (DOS), any versionA              PATHWORKS for DOS (NetWare Coexistence), any versionc>              PATHWORKS Remote for DOS and Windows, any version             Server Programs:  1              PATHWORKS V1.0 for OpenVMS (NetWare) 7              PATHWORKS V5.0 for DEC OSF/1 AXP (NetWare)t                                        #                                  13     A  3     E. License: PATHWORKS V1.3 for Macintosh[R] CCSp  G  When you purchase the above license you may use the following programsuD  ("Software") under the terms in Section 1 and all terms provided in  Additional Terms below.             Client Program:(  )              PATHWORKS V1.3 for Macintosh              Server Programs:  3              PATHWORKS V1.3 for OpenVMS (Macintosh) )              PACER for DEC OSF/1 AXP V2.6e"              PACER for ULTRIX V2.5  +                             Section 1 Termsr  E     For purposes of these terms a client computer ("Licensed Client")cE     is a computer that has been assigned one of these licenses by theDD     PATHWORKS license server. The number of Licensed Clients may notF     exceed the Quantity specified in the associated Product Authoriza-
     tion Key.s  D  You may copy and use the client Software identified above only on aI  Licensed Client. You may copy, access, and use the server Software iden-uE  tified above on any number of server systems, provided that this ac- "  cess is only by Licensed Clients.                                                      #                                  14b i  h    PATHWORKS_FPA_Licenses:    0     A. License: PATHWORKS V5.0 (LAN Manager) FPA  G  When you purchase the above license you may use the following programseD  ("Software") under the terms in Section 2 and all terms provided in  Additional Terms below.             Server Programs:  5              PATHWORKS V5.0 for OpenVMS (LAN Manager)6'              PATHWORKS for ULTRIX, V1.3S-              PATHWORKS V5.0 for DEC OSF/1 AXP )              PATHWORKS for SCO UNIX, V1.1S    ,     B. License: PATHWORKS V5.0 (NetWare) FPA  E  When you purchase the above license, or if you have a PATHWORKS V1.0oG  (NetWare) FPA license, you may use the following programs ("Software") H  under the terms in Section 2 and all terms provided in Additional Terms  below.)             Server Programs:  1              PATHWORKS V1.0 for OpenVMS (NetWare)l7              PATHWORKS V5.0 for DEC OSF/1 AXP (NetWare)N  .     C. License: PATHWORKS V1.3 (Macintosh) FPA  E  When you purchase the above license, or if you have a PATHWORKS V1.2vD  (Macintosh) FPA license, you may use the following programs ("Soft-D  ware") under the terms in Section 2 and all terms provided in Addi-  tional Terms below.             Server Programs:  3              PATHWORKS V1.3 for OpenVMS (Macintosh)i)              PACER for DEC OSF/1 AXP V2.6 "              PACER for ULTRIX V2.5                            #                                  15M r  G        +                             Section 2 Terms   E     For purposes of these terms a client computer ("Licensed Client")rE     is a computer that has been assigned one of these licenses by therD     PATHWORKS license server. The number of Licensed Clients may notF     exceed the Quantity specified in the associated Product Authoriza-
     tion Key.n  F  You may copy, access, and use the server Software identified above onG  any number of server systems, provided that this access is only by Li-a  censed Clients.                                                                                  #                                  16r p  i    PATHWORKS_CNS_Licenses:    6     A. License: PATHWORKS V5.1 for DOS and Windows CNS  G  When you purchase the above license you may use the following programsoD  ("Software") under the terms in Section 3 and all terms provided in  Additional Terms below.             Programs:s  /              PATHWORKS V5.1 for DOS and Windowso.              PATHWORKS X.25 (DOS), any version.              PATHWORKS ISDN (DOS), any versionA              PATHWORKS for DOS (NetWare Coexistence), any version >              PATHWORKS Remote for DOS and Windows, any version  1     B. License: PATHWORKS V4.1 for Windows NT CNSA  F  When you purchase the above license you may use the following programD  ("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.0 for OS/2 CNS(  F  When you purchase the above license you may use the following programD  ("Software") under the terms in Section 3 and all terms provided in  Additional Terms below.             Program:  $              PATHWORKS V5.0 for OS/2                                      #                                  17c e  e      0     D. License: PATHWORKS V1.3 for Macintosh CNS  F  When you purchase the above license you may use the following programD  ("Software") under the terms in Section 3 and all terms provided in  Additional Terms below.             Program:  )              PATHWORKS V1.3 for Macintoshc    +                             Section 3 Termsn  D     You may copy and use the Software identified above on the numberD     of computers specified in Quantity on the associated Product Au-     thorization Key.                                                                          #                                  18e a  b    PATHWORKS_FPS_Licenses:    8     A. License: PATHWORKS V1.0 for OpenVMS (NetWare) FPS  F  When you purchase the above license you may use the following programD  ("Software") under the terms in Section 4 and all terms provided in  Additional Terms below.             Server Program:t  1              PATHWORKS V1.0 for OpenVMS (NetWare)_  <     B. License: PATHWORKS V5.0 for OpenVMS (LAN Manager) FPS  F  When you purchase the above license you may use the following programD  ("Software") under the terms in Section 4 and all terms provided in  Additional Terms below.             Server Program:r  5              PATHWORKS V5.0 for OpenVMS (LAN Manager)s  B     C. License: PATHWORKS V5.0 for DEC OSF/1 AXP (LAN Manager) FPS  F  When you purchase the above license you may use the following programD  ("Software") under the terms in Section 4 and all terms provided in  Additional Terms below.             Server Program:T  ;              PATHWORKS V5.0 for DEC OSF/1 AXP (LAN Manager)c  >     D. License: PATHWORKS V5.0 for DEC OSF/1 AXP (NetWare) FPS  F  When you purchase the above license you may use the following programD  ("Software") under the terms in Section 4 and all terms provided in  Additional Terms below.             Server Program:A  7              PATHWORKS V5.0 for DEC OSF/1 AXP (NetWare)e                          #                                  19          +                             Section 4 Termsn  F     You may copy, access, and use the server Software identified aboveF     on a single server system, provided that the number of client com-G     puters accessing and using the server Software at any one time doesPF     not exceed the Quantity specified on the associated Product Autho-     rization Key.Y                                                                                              #                                  20I T  .        *                           ADDITIONAL TERMS  	  1. GRANTA  F  Digital Equipment Corporation ("DIGITAL") grants you the right to useD  the version(s) of the Software specified above or any prior version  of the Software.t  D  You must register and load the associated Product Authorization KeyD  before you use the Software. Each PAK must be registered and loaded*  in only one license management data base.  E  You may copy the Software onto a network server for the sole purposeME  of distributing the Software to the specified quantity of computers.f9  You may make archival or back-up copies of the Software.o  H  You may permanently transfer your rights to use the Software, the Soft-E  ware itself including any updates to the specified version(s) of the F  Software, the accompanying documentation including the original Prod-E  uct Authorization Key, and a copy of this License Agreement provided D  you retain no copies of the Software, documentation, or Product Au-G  thorization Key, and the recipient agrees to the terms of this LicenseS  Agreement.O  
  2. COPYRIGHTy  D  The Software is owned by DIGITAL and its suppliers and is protectedD  by copyright laws and international treaties. Your use of the Soft-E  ware and associated documentation is subject to the applicable copy-fJ  right laws and the express rights and restrictions of this License Agree-  ment.    3. RESTRICTIONS  F  You may not rent, lease, or otherwise transfer the Software except as0  expressly authorized in this License Agreement.  E  You may not remove any copyright, trademark or other proprietary no- &  tices from the Software or the media.  F  You may not reverse engineer, decompile, or disassemble the Software.G  However, in some jurisdictions the law permits reverse engineering forP4  interoperability purposes under certain conditions.                  #                                  21        *                           LIMITED WARRANTY  E  DIGITAL warrants that the Software will perform substantially as de-nD  scribed in the documentation accompanying the Software for a periodK  of ninety (90) days from delivery. Any implied warranties of merchantabil- I  ity or fitness for a particular purpose are limited to ninety (90) days.r  D  EXCLUSIVE REMEDY. DIGITAL's and its suppliers' entire liability andG  your exclusive remedy for Software which does not conform to DIGITAL'sEE  Limited Warranty shall be, at DIGITAL's option, either (1) repair ornE  replacment of the nonconforming Software, or (2) refund of your pur-aD  chase price. This warranty and remedy are subject to your returningE  the non-conforming Software during the warranty period to DIGITAL ine0  the country in which you obtained the Software.  G  DISCLAIMER OF WARRANTIES. THE ABOVE WARRANTIES ARE YOUR EXCLUSIVE WAR-SD  RANTIES AND NO OTHER WARRANTY, EXPRESS OR IMPLIED, WILL APPLY. DIG-E  ITAL does not warrant that the operation of the Software will be un-   interrupted or error free.n  E  This warranty gives you specific legal rights. In some jurisdictionsW6  other or additional rights are granted to you by law.  .                        ALLOCATION OF LIABILITY  H  DIGITAL'S AND ITS SUPPLIERS' TOTAL LIABILITY TO YOU FOR ANY CAUSE WHAT-E  SOEVER SHALL BE LIMITED TO THE PURCHASE PRICE YOU PAID FOR THE PROD-eJ  UCT. THIS LIMITATION WILL APPLY REGARDLESS OF THE FORM OF ACTION, WHETHERH  IN CONTRACT OR TORT, INCLUDING WITHOUT LIMITATION NEGLIGENCE. THE FORE-G  GOING LIMITATION DOES NOT APPLY TO DAMAGES RESULTING FROM PERSONAL IN-s%  JURY CAUSED BY DIGITAL'S NEGLIGENCE.   D  IN NO EVENT WILL DIGITAL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGESD  RESULTING FROM LOSS OF DATA OR USE, LOST PROFITS, OR ANY INCIDENTAL  OR CONSEQUENTIAL DAMAGES.  E  Some jurisdictions do not allow the exclusion or limitation of inci-iF  dental or consequential damages, so the above limitation or exclusion  may not apply to you.    3                   U.S. GOVERNMENT RESTRICTED RIGHTS   F  The Software and documentation are provided with "RESTRICTED RIGHTS".E  Use, duplication, or disclosure by the U.S. Government is subject tooG  restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-wE  7013, or FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable.t:  Contractor/manufacturer is Digital Equipment Corporation.              #                                  22        &                                GENERAL  E  You are responsible for compliance with all applicable export or re-e@  export control laws and regulations if you export the Software.  D  This Agreement is governed by and is to be construed under the laws&  of the Commonwealth of Massachusetts.  D  If you have any questions concerning this Agreement, please contactD  your local DIGITAL sales office or write to: DIGITAL EQUIPMENT COR-7  PORATION, 111 Powdermill Road, Maynard, MA 01754-1418.I  
  eightpointss   C  [R] ISDN is a registered trademark of Fujitsu Network Switching ofe
      America.   @  [R] Macintosh is a registered trademark of Apple Computer, Inc.  6  [R] NetWare is a registered trademark of Novell, Inc.  A  [R] OS/2 is a registered trademark of International Business Ma-       chines Corporation.  A  [R] OSF/1 is a registered trademark of Open Software Foundation,S	      Inc.E  @  [R] UNIX is a registered trademark licensed exclusively through      X/Open Company, Ltd.t  7  [TM] SCO is a trademark of Santa Cruz Operations, Inc.t  A  [TM] Windows and Windows NT are trademarks of Microsoft Corpora- 
      tion.  D  [TM] The DIGITAL Logo, DEC, Digital, OpenVMS, PATHWORKS, and ULTRIX5      are trademarks of Digital Equipment Corporation.V  :  1995 Digital Equipment Corporation. All Rights Reserved.                                #                                  23 