      Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  DECdfs for OpenVMS                      SPD 28.78.07                 Version 2.3-1   DESCRIPTION   H DECdfs for OpenVMS is a DECnet for OpenVMS and DECnet-Plus layered prod-D uct that provides OpenVMS users with the ability to use remote Open-D VMS VAX and OpenVMS Alpha disks as if they were directly attached to the local OpenVMS system.   F DECdfs software provides users and applications with transparent, highE performance file access while using fewer CPU resources than standard / DECnet for OpenVMS and DECnet-Plus file access.   D Systems running DECdfs software can act as "servers" or "clients" orE both. DECdfs servers make file resources available to systems running E DECdfs client software. DECdfs clients are able to use file resources D of systems running DECdfs server software. The file resources acces-D sible through DECdfs can range in scope from a master file directoryE and all of its subordinate directories and files on a disk volume, to D an individual file. The DECdfs server software assigns a unique name to the resource to be shared.   G In configurations where DECdns (Distributed Name Service) is supported, E the DECdfs server registers the resource name with DECdns. In config- F urations where DECdns is not supported, the DECdfs client must includeH the resource location name when issuing the command to use the resource.  F DECdfs software uses DECdns on OpenVMS VAX configurations running DEC-C net for OpenVMS or DECnet-Plus, and on OpenVMS Alpha configurations E running DECnet-Plus. In order for DECdfs to use DECdns, there must be D at least one DECdns server in the network. DECdns allows the name of  C                                                          April 2001        C the resource to be independent of its physical location on the net- D work. DECdfs systems throughout the network can continue accessing a2 resource even if the resource location is changed.  D DECdns is not available on OpenVMS Alpha configurations running DEC-C net, but these configurations can use DECdfs by specifying the node # name where the resource is located.   E The DECdfs client uses the resource by means of the DFS$CONTROL MOUNT E command. This command specifies the DECdns name by which the resource H was registered, enables communication between the client and the server,C and creates a pseudo-device on the client system. The pseudo-device F makes the remote resource appear to the client system as a local disk.G Users can then perform operations on the pseudo-device, and DECdfs han- / dles all of the network access and translation.    Features  9 The features of DECdfs for OpenVMS Version 2.3-1 include:   * o  High performance access to remote disks  E o  Applications require no modifications to use remote disks, because     the disks appear to be local   H o  Fewer CPU resources used than standard DECnet for OpenVMS and DECnet-    Plus file access   D o  Supports all OpenVMS file types, including Extended File Specifi-
    cations  2 o  Supports the following OpenVMS file operations:      -  Shared access (read)  %    -  Exclusive access (read & write)   H    -  All OpenVMS directory operations, including the creation and dele-       tion of directories       -  Virtual I/O       -  Mapped I/O  "                                  2       I o  Transparent access to most of the standard OpenVMS DCL commands (those G    commands which neither manipulate identifiers nor use logical, phys-     ical or write-shared I/O)  E o  Operates in any DECnet for OpenVMS, DECnet-Plus, or DECnet over IP C    environment; both Local Area Networks and Wide Area Networks are     supported  D o  Uses DECdns, if present, to provide location-independent data ac-    cess   D o  File security provided through standard OpenVMS proxy mechanisms.<    The system manager on the server controls all file access  H o  Optional end-to-end checksum provided to guard against network faults  G o  The DECdfs Management utility allows the user to control DECdfs com- ;    ponents and to display statistical and error information   E o  Supports 64-bit addresses for I/O buffers on OpenVMS Alpha Version     7.0 and later   Restrictions  0 o  Files opened for write are opened exclusively   o  Logical I/O is not supported   $ o  Installed files are not supported  E o  The use of ACLs (Access Control Lists) on DECdfs client devices is J    not supported. ACLs on served files are not visible to a DECdfs client.   HARDWARE REQUIREMENTS    Processors Supported  D DECdfs for OpenVMS Version 2.3-1 is supported on all systems runningC the versions of the OpenVMS operating system that are listed in the   section "SOFTWARE REQUIREMENTS".   Memory Requirements   C DECdfs for OpenVMS Version 2.3-1 will run properly with the minimum   "                                  3       C physical memory required by the OpenVMS operating system and DECnet D for OpenVMS (Phase IV) or DECnet/OSI or DECnet-Plus (Phase V). ReferF to the Software Product Descriptions for those products for memory re- quirements.    CLUSTER ENVIRONMENT   C This layered product is fully supported when installed on any valid D and licensed OpenVMS Cluster configuration. The OpenVMS Cluster con-C figurations are fully described in the Software Product Description , for OpenVMS Cluster Software (SPD 29.78.xx).   SOFTWARE REQUIREMENTS   # The following software is required:   A o  One of the following versions of the OpenVMS operating system:   1    -  OpenVMS Alpha Version 6.2, 7.1, 7.2, or 7.3   D    -  OpenVMS VAX Version 5.5-2 (DECnet for OpenVMS only), 6.2, 7.1,       7.2, or 7.3   2 o  One of the following network software products:      -  DECnet for OpenVMS      -  DECnet/OSI for OpenVMS      -  DECnet-Plus for OpenVMS    OpenVMS Tailoring   D The following OpenVMS classes are required for full functionality of this layered product:    o  OpenVMS Required Saveset       "                                  4        o  Network Support  C For more information on OpenVMS classes and tailoring, refer to the E OpenVMS Operating System Software Product Description (SPD 25.01.xx).    DISK SPACE REQUIREMENTS   C To install DECdfs for OpenVMS Version 2.3-1, you need the following  free space on your system disk:   / o  4000 free blocks for an OpenVMS Alpha system   - o  1500 free blocks for an OpenVMS VAX system   D This size is approximate; the actual size may vary depending on your8 system environment, configuration, and software options.   GROWTH CONSIDERATIONS   E The minimum hardware and software requirements for any future version C of this product may be different from the requirements for the cur- 
 rent version.    ORDERING INFORMATION  D The software media and documentation ship on the layered product CD-E ROM that is included in the OpenVMS Version 7.3 kit. DECdfs for Open- E VMS Version 2.3-1 software and documentation are also included in the E OpenVMS Software Product Library and the OpenVMS Online Documentation  Library, respectively.                    "                                  5        SOFTWARE LICENSING  E A license is required for each OpenVMS system on which the DECdfs for E OpenVMS software is to be installed and executed. A DECdfs license is  required on:  E o  Each server node that registers available directories or files for #    access and use by DECdfs clients   C o  Each client node that accesses and uses the directories or files     on a DECdfs server   D Each OpenVMS system may be licensed to use the full functionality ofE DECdfs or the client functionality only. A full functionality license C grants the right to use both the client capabilities and the server 
 capabilities.   3 The following table lists the appropriate licenses.   C ___________________________________________________________________ !                    Full Function- C System_____________ality______________Client_Only__________________   1 OpenVMS Alpha      QL-37YA*-AA        QL-37ZA*-AA   C OpenVMS_VAX________QL-VEQA*-AA________QL-381A*-AA__________________   E This software is furnished only under a license. For more information D about Compaq's licensing terms and policies, contact your local Com- paq office.   # License Management Facility Support   C This layered product supports the OpenVMS License Management Facil- C ity. License units for this product are allocated on a CPU-capacity  basis.  E For more information on the License Management Facility, refer to the D OpenVMS Operating System Software Product Description (SPD 25.01.xx)  "                                  6       2 or the OpenVMS Operating System documentation set.  E For more information on Compaq's licensing policies, contact your lo-  cal Compaq office.   SOFTWARE PRODUCT SERVICES   D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   YEAR 2000 READINESS   C This product is capable of accurately processing, providing, and/or I receiving date data from, into, and between the twentieth and the twenty- F first centuries, and the years 1999 and 2000, including leap year cal-C culations, when used in accordance with the associated product doc- G umentation, and provided that all hardware, firmware, and software used D in combination with the product properly exchange accurate date data with the product.    SOFTWARE WARRANTY   F This software is provided by Compaq with a 90-day comformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.   A [TM] Alpha, Compaq, DECnet, Digital, OpenVMS, VAX, and the Compaq 8      logo are trademarks of Compaq Computer Corporation.  7 2001 Compaq Computer Corporation. All rights reserved.                     "                                  7                                                                                       "                                  8