  	  Software   Product  Description  D  ___________________________________________________________________  N  PRODUCT NAME: Distributed Computing Environment (DCE) V1.3      SPD: 43.05.03                for OpenVMS    DESCRIPTION  F  The Distributed Computing Environment for OpenVMS product family pro-E  vides a set of the distributed computing functionality specified for F  the Open Software Foundation[TM]'s (OSF[R]) Distributed Computing En-G  vironment (DCE) as well as tools for application developers. With DCE, G  the OSF has established a standard set of services and interfaces that F  facilitate the creation, use, and maintenance of client-server appli-E  cations. The DCE for OpenVMS serves as the basis for an open comput- G  ing environment where networks of multivendor systems appear as a sin- D  gle system to the user. Since DCE makes the underlying networks andG  operating systems transparent, application developers can easily build E  portable, interoperable client-server applications. Users can locate F  and share information safely and easily across the entire enterprise.D  The DCE for OpenVMS supplies system managers with a set of tools toH  consistently manage the entire distributed computing environment, whileI  also assuring the integrity of the enterprise. The DCE for OpenVMS prod- E  uct family supports both the OpenVMS[TM] VAX[TM] and OpenVMS[TM] Al-   pha Operating Systems.   E  The functionality provided in the DCE for OpenVMS product family in-   cludes:  I  o  DCE Remote Procedure Call (RPC): Used to create and run client-server E     applications, the RPC allows direct calls to remote systems as if $     they were local procedure calls.  E  o  DCE Distributed Time Service (DTS): Synchronizes time on individ- 3     ual nodes in a distributed network environment.   G  o  DCE Security Service: Provides secure communications and access via .     authorization and authentication services.  D                                DIGITAL                 February 1995  D                                                          AE-PSYVD-TE       H  o  DCE Cell Directory Service (CDS): Provides location-independent nam-     ing for resources.  E  o  Global Directory Agent (GDA): The Global Directory Agent provides F     a means of linking multiple CDS namespaces via either X.500 or the*     Internet Domain[R] Name Server (BIND).  E  o  The Interface Definition Language (IDL) compiler: IDL is the lan- 0     guage used to define remote procedure calls.  =  o  Tools and utilities that help manage the DCE environment.   D  The DCE Threads Service which provides user-context multiprocessingC  functionality is provided as part of the OpenVMS Operating System.   D  The DCE for OpenVMS product family currently consists of eight sep-H  arate products, four on OpenVMS VAX, and four on OpenVMS Alpha, to pro-D  vide customers with maximum flexibility for configuring a DCE envi-0  ronment, known as a DCE cell. The products are:  D  o  DCE Runtime Services for OpenVMS, which is required for all sys-D     tems participating in the DCE cell. The DCE Runtime Services kitF     includes DCE client functions as well as DCE administration tools.  F  o  DCE Application Developers' Kit for OpenVMS, which is required forI     developers of distributed applications, but optional for other users. E     The DCE Application Developers' Kit provides programmers with all E     the DCE API's and the Interface Definition Language (IDL). IDL is F     an easy-to-use, ANSI C-based language for writing remote procedure
     calls.  D  o  DCE Cell Directory Server, at least one of which is required forF     each DCE cell. The DCE CDS Server is a central repository contain-D     ing information about the location of resources in the DCE cell.G     It allows access to resources by a single name, regardless of phys-      ical location.  G  o  DCE Security Server, at least one of which is required for each DCE E     cell. The DCE Security Server protects resources from illegal ac- I     cess and provides secure communications within and between DCE cells.   #                                   2        D  The DCE for OpenVMS V1.3 product family is an implementation of OSFC  DCE V1.0.3 adapted and enhanced for OpenVMS. Enhancements include:   G  o  DCE for OpenVMS provides simplified installation and configuration.   D  o  Integrated Login. This settable feature enables DCE login to oc-H     cur automatically when a user logs in to a standard interactive ses-D     sion. At the OpenVMS username and password prompts, the user en-D     ters either his OpenVMS username and password or his DCE accountH     name and password. If valid, the user is logged in to both the Open-A     VMS system and the DCE cell in a single integrated operation.   D  o  IMPORT and EXPORT utilities to move accounts to and from the DCE"     Registry and OpenVMS's SYSUAF.  F  o  The DCE IDL compiler for OpenVMS supports DEC C++, and FORTRAN, as     well as C.  E  o  The DCE IDL has been extended to support a number of C++ language D     syntax features that provide a distributed object framework. TheD     DCE RPC runtime environment now supports DEC C++ bindings to re-     mote objects.   D  o  IDL development templates are provided to help with the develop-%     ment of client-server interfaces.   6  o  A conversion utility for DEC RPC V1.0 programs[1].  F  o  A PC name server proxy agent, a feature which enables systems run-1     ning Microsoft[R] RPC to obtain CDS bindings.   D  The DCE for OpenVMS also includes two utilities that complement the4  DCE core services, NSedit, and The Resource Broker.  F  o  NSedit. NSedit is a Motif based graphical tool which enables usersD     to navigate, manipulate, and peruse the CDS name space much moreD     effectively and efficiently than when using the CDS command line     interface.    ____________________   7  DEC   RPC conversion utility is available on VAX only.   #                                   3        H  o  The Resource Broker. The Resource Broker is a graphical utility thatF     dynamically provides you with the location of the best resource orD     service available across the network, based on user-defined cri-J     teria. The Resource Broker allows you to optimize the resources withinG     your distributed environment by not only finding all instances that D     satisfy your application's resource needs, but also by providingD     you with a list of those instances sorted in the order that bestE     satisfies your application needs. The Resource Broker may also be A     used to monitor the state of DCE services across the network.     PRODUCT OPTIONS  D  The DCE for OpenVMS product family currently consists of eight sep-@  arate products, four on OpenVMS VAX, and four on OpenVMS Alpha:  ,  1. DCE Runtime Services Kit for OpenVMS VAX.  2. DCE Runtime Services Kit for OpenVMS Alpha  E  This is a fully integrated set of services that provide applications G  with the essential capabilities required to use DCE's distributed ser- H  vices. The DCE Runtime Services makes the following DCE features avail-"  able to distributed applications:  @  o  Remote Procedure Call Runtime API and Library that includes:       -  Access to DCE RPC  A     -  Use of the DCE Cell Directory Service for locating servers   5     -  Use of DCE Security Service for authentication   E     -  RPC event logging monitor to assist in debugging client-server         applications   .  o  Distributed Time Service (Client & Server)  2  o  Integrated Login, including IMPORT and EXPORT.    o  Administrative tools  
  o  NSedit  #                                   4        :  o  PC proxy agent for communication with Microsoft[R] RPC    o  The Resource Broker   D  A group of DCE systems that work together and are administered as aG  unit is called a cell. Every system within a DCE cell must run the DCE   Runtime Services kit.  I  RPC supports the client-server model that characterizes many distributed G  applications. The DCE Runtime Services kit provides such client-server E  applications the ability to interoperate over DECnet, TCP/IP and UDP D  /IP network protocols on the OpenVMS operating system. See the sec-:  tion titled SOFTWARE REQUIREMENTS for additional details.  E  The right-to-use the DCE Runtime Services for OpenVMS is included as E  part of the OpenVMS Operating System license. See the section titledE2  SOFTWARE LICENSING for more detailed information.  3  3. DCE Application Developers' Kit for OpenVMS VAXe5  4. DCE Application Developers' Kit for OpenVMS Alphas  H  The DCE Application Developers' Kit for OpenVMS includes tools requiredD  for the development of distributed applications using remote proce-  dure calls (RPC). It includes:t    o  IDL RPC stub compileri  &  o  Time provider source code routines    o  Sample applicationss  5  o  All public DCE application programming interfacese    o  IDL development templatesa    o  UUIDGEN   H  Support for the X Directory Service (XDS) API and Generic Security Ser-F  vice API (GSSAPI) is also included in the DCE Application Developers'  Kit.,  F  The DCE Runtime Services for OpenVMS is a prerequisite for use of the=  DCE Application Developers' Kit and must be installed first.e  #                                   5r i  a  -  5. DCE Cell Directory Server for OpenVMS VAX /  6. DCE Cell Directory Server for OpenVMS Alphas  G  The DCE Cell Directory Server provides a consistent mechanism for nam-mF  ing and locating users, applications, files, and systems within a DCEI  cell. The DCE CDS Server also includes the Global Directory Agent (GDA).uD  The Global Directory Agent provides a means of linking multiple CDS:  namespaces via the Internet Domain[R] Name Server (BIND).  E  The DCE Runtime Services kit is required on each system in the cell.rF  Users must install the Runtime Services Kit before installing the DCED  CDS Server. Similarly, the DCE CDS Server requires the installation=  of the DCE Security Server on a system in the same DCE cell.s  '  7. DCE Security Server for OpenVMS VAXn)  8. DCE Security Server for OpenVMS Alpha   F  The DCE Security Server allows users controlled access to informationF  in a distributed computing environment safely and confidentially. The>  DCE Security Server accomplishes this through three services:  H  o  DCE Authentication Service allows users and resources to prove theirF     identity to each other. The DCE Authentication Service is based onG     Kerberos, which requires that all users and resources possess a se-e
     cret key.g  E  o  DCE Authorization Service verifies operations that users may per-dF     form on resources. A DCE Registry Service contains a list of validE     users. An Access Control List (ACL) associated with each resourcesG     determines valid users, through the Registry Service, and the types %     of operations a user may perform.   D  o  DCE Data Integrity Service protects network data from tampering.E     Cryptographic checksums automatically generated by RPC enable DCEiF     to determine whether data has been modified or corrupted in trans-     mission.        #                                   6s q  e  E  The DCE Runtime Services kit is required on each system in the cell.eF  Users must install the Runtime Services Kit before installing the DCEE  Security Server. Similarly, the DCE Security Server requires the in- C  stallation of the DCE CDS Server on a system in the same DCE cell.l    OSF CERTIFICATION  F  Digital certifies that the DCE for OpenVMS conforms to the OSF[R] Ap-D  plication Environment Specification/Distributed Computing (AES/DC),D  and has successfully been certified using the OSF[R] DCE ValidationD  Test Suite. Digital further certifies that each copy of the DCE forE  OpenVMS meets the requirements as specified in the OSF CertificationtE  and Trademark Policy, and contains all the mandatory OSF[R] DCE cer-e   tification modules as required.    CONFORMANCE TO STANDARDS   D  The OSF DCE is based on several de facto and de jure standards, in-	  cluding:f    o  POSIX 1003.4a draft Threads   +  o  POSIX 1003.6 draft Access Control Listsc  D  o  OSF DCE is compatible with the Network Time Protocol (NTP) stan-	     dardsn    HARDWARE REQUIREMENTS                        #                                   7. r  c    Alpha Processors Supportedf  .  Alpha:      Digital 2100 Server Model A500MP,.              Digital 2100 Server Model A600MP,2              DEC 3000 Model 400 Alpha Workstation,-              DEC 3000 Model 400 Alpha Server, 2              DEC 3000 Model 500 Alpha Workstation,-              DEC 3000 Model 500 Alpha Server, 2              DEC 3000 Model 600 Alpha Workstation,-              DEC 3000 Model 600 Alpha Server,s1              DEC 3000 Model 800 Alpha Workstationd  ,              DEC 4000 Model 610 Alpha System  ,              DEC 7000 Model 610 Alpha System  -              DEC 10000 Model 610 Alpha Systemd    VAX Processors Supportedo              VAXft Model 110,e            VAXft Model 310,             VAXft Model 410,r            VAXft Model 610,d            VAXft Model 612    VAX:      VAX 4000 Model 100,            VAX 4000 Model 200,            VAX 4000 Model 300,            VAX 4000 Model 400,            VAX 4000 Model 500,            VAX 4000 Model 600C  %            VAX 6000 Model 200 Series, %            VAX 6000 Model 300 Series,v%            VAX 6000 Model 400 Series,t        #                                   8r n  i    %            VAX 6000 Model 500 Series, $            VAX 6000 Model 600 Series  $            VAX 7000 Model 600 Series  (            VAX 8200, VAX 8250, VAX 8300,(            VAX 8350, VAX 8500, VAX 8530,(            VAX 8550, VAX 8600, VAX 8650,(            VAX 8700, VAX 8800, VAX 8810,'            VAX 8820, VAX 8830, VAX 8840a              VAX 9000 Model 110,            VAX 9000 Model 210,%            VAX 9000 Model 300 Series,e$            VAX 9000 Model 400 Series  %            VAX 10000 Model 600 Series               VAX-11/750,!            VAX-11/780, VAX-11/785a  &  MicroVAX: MicroVAX II, MicroVAX 2000,&            MicroVAX 3100 Model 10/10E,&            MicroVAX 3100 Model 20/20E,"            MicroVAX 3100 Model 30,"            MicroVAX 3100 Model 40,"            MicroVAX 3100 Model 80,"            MicroVAX 3100 Model 90,(            MicroVAX 3300, MicroVAX 3400,(            MicroVAX 3500, MicroVAX 3600,'            MicroVAX 3800, MicroVAX 3900n  +  VAXstation:VAXstation II, VAXstation 2000, $            VAXstation 3100 Model 30,$            VAXstation 3100 Model 38,        #                                   9o r  a    $            VAXstation 3100 Model 40,$            VAXstation 3100 Model 48,$            VAXstation 3100 Model 76,,            VAXstation 3200, VAXstation 3500,+            VAXstation 3520, VAXstation 3540r  $            VAXstation 4000 Model 60,$            VAXstation 4000 Model 90,            VAXstation 4000 VLC  ;  VAXserver: VAXserver 3100, VAXserver 3300, VAXserver 3400,f:            VAXserver 3500, VAXserver 3600, VAXserver 3602,)            VAXserver 3800, VAXserver 3900s  $            VAXserver 4000 Model 200,$            VAXserver 4000 Model 300,#            VAXserver 4000 Model 500D  $            VAXserver 6000 Model 210,$            VAXserver 6000 Model 220,$            VAXserver 6000 Model 310,$            VAXserver 6000 Model 320,$            VAXserver 6000 Model 410,$            VAXserver 6000 Model 420,$            VAXserver 6000 Model 510,$            VAXserver 6000 Model 520,$            VAXserver 6000 Model 610,$            VAXserver 6000 Model 620,#            VAXserver 6000 Model 630r    Processors Not Supported   &  MicroVAX I, VAXstation I, VAX-11/725,(  VAX-11/782, VAXstation 8000, VAX-11/730    Processor Restrictions:      #                                  10i w     E  A TK50 Tape Drive is required for standalone MicroVAX 2000 and VAXs-h  tation 2000 systems.e  3  Disk Space Requirements ( Block Cluster Size = 1):m    For Alpha Alpha Systems  )  Disk space required for    36,000 blockso  DCE Runtime installation:)  Disk space required        32,000 blocksi  for DCE Runtime use
  (permanent):   )  Disk space required for    48,000 blocksh  DCE ADK installationt  (includes DCE Runtime):)  Disk space required for    42,000 blocks   DCE ADK (includes DCE  Runtime) use (permanent):    For VAX Systems  )  Disk space required for    22,000 blocksC  DCE Runtime installation:)  Disk space required        18,000 blockse  for DCE Runtime use
  (permanent):n  )  Disk space required for    36,000 blockse  DCE ADK installationC  (includes DCE Runtime):)  Disk space required for    30,000 blockse  DCE ADK (includes DCE  Runtime) use (permanent):            #                                  11e r     F  The CDS Server and Security Server images are automatically installedG  as part of the DCE Runtime Services but must be enabled by Product Au-o  thorization Keys (PAKS).   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'st9  system environment, configuration, and software options.     CLUSTER ENVIRONMENT  D  This layered product is fully supported when installed on any valid=  and licensed VAXcluster* configuration without restrictions.   I  *  VAXcluster configurations are fully described in the VAXcluster Soft- F     ware Product Description (29.78.xx) and include SEE, Ethernet, and&     Mixed Interconnect configurations.    SOFTWARE REQUIREMENTS  E  OpenVMS Operating System V5.5-2, V6.0, V6.1 (VAX) or V1.5, V6.1 (Al-i  pha).  D  TCP/IP is required to establish a DCE cell. DECnet may also be usedE  in conjunction with TCP/IP for application communication, but TCP/IPGH  is required for communication between DCE cell members by DCE services.H  DECnet only environments are only supported for applications using justD  the RPC, and are not configuring their environment into a DCE cell.  D  The DCE for OpenVMS supports Digital's TCP/IP Services for OpenVMS.E  It is also designed to work with other vendors TCP(UDP)/IP products.SC  Contact your TCP vendor to see if it supports the DCE for OpenVMS.o  G  The DCE for OpenVMS will communicate over DECnet Phase IV or over DEC-r(  net/OSI (also known as DECnet Phase V).            #                                  12o n  a    OPTIONAL SOFTWARE    VAX C  DEC C  C++  DEC Fortran for OpenVMS  DEC X.500 Directory Service   Language-Sensitive Editor (LSE)  Module Management System (MMS)   OpenVMS POSIX    GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version of D  this product may be different from the requirements for the current	  version.i    DISTRIBUTION MEDIAe  0  TK50 Streaming Tape (VAX), CD-ROM (VAX & Alpha)  H  This product is NOT available as part of the OpenVMS Consolidated Soft-D  ware Distribution CD-ROM. The software documentation for this prod-E  uct is NOT available as part of the OpenVMS Online Documentation Li-   brary CD-ROM.    ORDERING INFORMATIONt    For Alpha Systems  (  DCE Runtime Services for OpenVMS Alpha:  .  Software License: N/A. See SOFTWARE LICENSING  Software Media: QA-24CAA-H8$  Software Documentation: QA-01RAA-GZ'  Software Product Services: QA-24CA*-**   3  DCE Application Developers' Kit for OpenVMS Alpha:q    #                                  13s s  n    Software License: QL-24CA9-AA  Software Media: QA-24CAA-H8$  Software Documentation: QA-01SAA-GZ'  Software Product Services: QT-24CA*-**f  -  DCE Cell Directory Server for OpenVMS Alpha:e    Software License: QL-24EA9-AA  Software Media: QA-24CAA-H8$  Software Documentation: QA-01RAA-GZ'  Software Product Services: QT-24EA*-**r  '  DCE Security Server for OpenVMS Alpha:s    Software License: QL-24GA9-AA  Software Media: QA-24CAA-H8$  Software Documentation: QA-01RAA-GZ'  Software Product Services: QT-24GA*-**r    For VAX Systems  &  DCE Runtime Services for OpenVMS VAX:  .  Software License: N/A. See SOFTWARE LICENSING+  Software Media: QA-01RAA-H5 or QA-24CAA-H8 $  Software Documentation: QA-01RAA-GZ'  Software Product Services: QT-01RA*-**e  1  DCE Application Developers' Kit for OpenVMS VAX:     Software License: QL-01SA9-AA+  Software Media: QA-01RAA-H5 or QA-24CAA-H8s$  Software Documentation: QA-01SAA-GZ'  Software Product Services: QT-01SA*-**   +  DCE Cell Directory Server for OpenVMS VAX:     Software License: QL-24DA9-AA+  Software Media: QA-01RAA-H5 or QA-24CAA-H8 $  Software Documentation: QA-01RAA-GZ'  Software Product Services: QT-24DA*-**0  #                                  14l    k  %  DCE Security Server for OpenVMS VAX:     Software License: QL-24FA9-AA+  Software Media: QA-01RAA-H5 or QA-24CAA-H8 $  Software Documentation: QA-01RAA-GZ'  Software Product Services: QT-24FA*-**t  G  *  Denotes variant fields. For additional information on available li-0E     censes, services, and media, refer to the appropriate price book.   E  Media Notes: Media kit QA-24CAA-H8 contains binaries for all OpenVMSCD  DCE products (VAX & Alpha). Media kit QA-01RAA-H5 contains binariesD  for all OpenVMS DCE VAX kits (i.e. DCE Runtime for OpenVMS VAX, DCEF  Application Developers' Kit for OpenVMS VAX, DCE CDS for OpenVMS VAX,*  and DCE Security Server for OpenVMS VAX.)  F  Documentation Notes: Documentation kits are the same for both the VAXD  and Alpha platforms. QA-01RAA-GZ contains documentation for the DCEI  Runtime Services, DCE CDS Server, and DCE Security Server for both plat-0F  forms. QA-01SAA-GZ contains the documentation for the DCE Application$  Developers' Kit for both platforms.  F  QA-01SAA-GZ is comprised of all the documentation in QA-01RAA-GZ plus7  three additional books on DCE application development.V    SOFTWARE LICENSING8  D  The right-to-use the DCE Runtime Services for OpenVMS (VAX & Alpha)D  products are licensed with the OpenVMS Operating System at no addi-D  tional cost. However, media and documentation must be ordered sepa-  rately.  G  The DCE Runtime Services for OpenVMS is technically controlled for ex-0H  port under U.S. Department of Commerce, Export Regulations, ECCN 5D11A.E  A U.S. Individual Validated License may be required for sale to cus- D  tomers in, or from, certain foreign countries. Please refer to yourF  Digital Sales Representative or Digital Export Administrator in coun-+  try of destination for further assistance.o    #                                  151 M  l  E  This software is furnished under the licensing provisions of Digital D  Equipment Corporation's Standard Terms and Conditions. For more in-E  formation about Digital's licensing terms and policies, contact your,  local Digital office.  %  License Management Facility Support:   F  The DCE Application Developers' kit supports the OpenVMS License Man-  agement Facility.  D  License units for this product are allocated on an Unlimited System  Use basis.a  F  For more information on the License Management Facility, refer to theE  OpenVMS Operating System Software Product Description (SPD 25.01.xx) H  or the License Management Facility manual of the OpenVMS Operating Sys-  tem documentation set.X    SOFTWARE PRODUCT SERVICES  H  A variety of service options and consulting services are available fromB  Digital. For more information, contact your local Digital office.    SOFTWARE WARRANTY  H  Warranty for this software product is provided by Digital with the pur-G  chase of a license for the product as defined in the Software Warranty0  Addendum of this SPD.  ;   1995 Digital Equipment Corporation. All rights reserved.,  A  [R] OSF and OSF/1 are registered trademarks of the Open Softwaree      Foundation, Inc.e  B  [R] Microsoft is a registered trademark of Microsoft Corporation.  B  [TM] Open Software Foundation is a trademark of the Open Software      Foundation, Inc./  A  [TM] The DIGITAL Logo, DECstation, DECsystem, Digital, MicroVAX,i@      OpenVMS, PATHWORKS, ULTRIX, VAX, VAXserver, VAXstation, and9      VMS are trademarks of Digital Equipment Corporation.A  #                                  16p