DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: DEC DATATRIEVE Version 7.1 for OpenVMS VAX Systems SPD 24.44.30 DESCRIPTION DEC[TM] DATATRIEVE[TM] for OpenVMS[TM] VAX[TM] systems is a query, re- port, and data management tool for the OpenVMS Operating System. It provides a uniform access method for data stored by RMS[TM], Oracle Rdb[TM], and Oracle CODASYL DBMS[TM] files on OpenVMS and data residing in other databases accessible by the DEC DB Integrator Gateway products. Us- ing DEC DATATRIEVE, a novice or experienced user can retrieve or mod- ify data without considering the underlying storage method or phys- ical location. Modes of Operation DEC DATATRIEVE presents information in several different formats. In- formation can be displayed using simple defaults or can be reported on through a more flexible report writer. Information can be displayed on a terminal or workstation, printed on a hard-copy device, or writ- ten to a file. Information can also be presented graphically with user- defined VAX FMS[TM] and VAX TDMS forms, as well as with DECforms[TM]. Graphics output is ReGIS[TM]; it can be managed by devices or convert- ers accepting ReGIS. DEC DATATRIEVE also provides an efficient way to access information stored on other VAX, Alpha or PDP[TM]-11 systems linked by DECnet[TM]. DEC DATATRIEVE can be used interactively to retrieve, modify, store, or delete data using a simple set of commands. Frequently used com- binations of commands can be stored as named procedures and invoked January 1996 AE-PVM0D-TE by name. Programs written in other DEC languages can call DEC DATA- TRIEVE, allowing them to be independent of underlying data storage meth- ods and physical location. A DECwindows[TM] Motif[R] interface to DEC DATATRIEVE is provided. This allows the user to perform a subset of the DEC DATATRIEVE functions using menu bars, scroll bars, pop-up menus, pull-down menus, and but- tons. The user can also use a navigator to browse through the dictio- nary directories, select objects, and execute commands on them directly from pop-up menus. Data Dictionary DEC DATATRIEVE is dictionary driven. DEC DATATRIEVE Version 7.1 has removed the dependencies from Oracle CDD/Repository by supporting a new textfile dictionary in addition to Oracle CDD/Repository. DEC DATA- TRIEVE Version 7.1 provides the following two independent dictionary alternatives: o Data Dictionary using Oracle CDD/Repository for OpenVMS. o DEC DATATRIEVE Textfile-based dictionary. Data Dictionary using Oracle CDD/Repository for OpenVMS Using this dictionary, data descriptions are stored in and retrieved from Oracle CDD/Repository for OpenVMS. DEC DATATRIEVE includes com- mands to store, examine, modify, and delete definitions in the dic- tionary and can use definitions stored by other layered products, such as the Oracle CODASYL DBMS schema definitions or the Oracle Rdb for OpenVMS database definitions. DATATRIEVE requires the Oracle/CDD Repos- itory in order to manage the Oracle CODASYL DBMS databases. DEC DATATRIEVE fully supports CDO format dictionaries, including the ability to access shareable fields. Pieces tracking is also supported for these entities. DEC DATATRIEVE includes full support for DMU for- mat dictionaries as well. Textfile-based Dictionary 2 If Oracle CDD/Repository is present on the system, you can select, at installation time, whether to link DEC DATATRIEVE with Oracle CDD/Repository or not. When Oracle CDD/Repository is linked to DEC DATATRIEVE, its use can dynamically be disabled and enabled at run-time by using the SET CDD and SET NO CDD commands. When Oracle CDD/Repository is not linked to DEC DATATRIEVE, the alternative textfile dictionary is enabled. The new textfile dictionary stores the DEC DATATRIEVE object defini- tions as text in text files. Oracle CDD/Repository object definitions can be extracted and rede- fined as files in the new dictionary system. Text file definitions can- not be shared with compilers and database systems, but can be accessed and manipulated by applications and OpenVMS utilities. Temporary Definition of Objects DEC DATATRIEVE Version 7.1 extends the use the DECLARE command to de- fine DEC DATATRIEVE objects. Such objects are temporary (time scope is within a DEC DATATRIEVE session) and do not depend on any dictio- nary system, as they are stored in memory. Protection - Protection with Oracle CDD/Repository When DEC DATATRIEVE accesses data through data definitions stored by Oracle CDD/Repository for OpenVMS, protection provided by Oracle CDD/Repository applies. An Access Control List associated with an object definition specifies which types of access are granted to the definition itself, and to the defined data. Standard OpenVMS Access Elements can be used based on usernames, UICs, and identifiers. Access rights for termi- nals can be specified also. - Protection with the DATATRIEVE resident dictionary using text files Text file definitions are subject to the OpenVMS ACL protections, and must be defined and managed by the programmer, using the appropriate DATATRIEVE or OpenVMS commands. - Protection with in-memory temporary object definitions 3 In-memory temporary object definitions do not use any protection mech- anisms, and bypass those definitions defined by either Oracle CDD/Repository or the textfile dictionary. Remote Data Access DEC DATATRIEVE provides access to data on remote systems in two ways as follows: o Takes advantage of the remote data access functionality transpar- ently provided by the individual data base management systems (for example, RMS remote files, Oracle Rdb remote databases) according to their rules. o Requests a DATATRIEVE server to start on the remote system (Open- VMS Alpha and VAX systems or PDP-11) to manage the data definitions and process data remotely. Most operations are performed on the server node and only selected data is exchanged between the requester and the server systems. To work in this way, a DATATRIEVE system (DEC DATATRIEVE or DATATRIEVE-11) must be installed on the server node. For the Nonprogrammer DEC DATATRIEVE provides the novice user with a tutorial mode called GUIDE Mode. DEC DATATRIEVE offers ADT (Application Design Tool) for the more ex- perienced user who wants to define data structures. ADT takes the user step-by-step through the definition of a domain based on an RMS data file. If DEC DATATRIEVE is used on the same information by experienced and novice users, the novice user can use the full power of the language by invoking procedures designed by the more experienced user. For the Programmer DEC DATATRIEVE is a highly structured language that provides automatic access optimization, data type conversion, and data validation. Loop- ing and control structures, such as IF THEN ELSE, BEGIN END, REPEAT, 4 WHILE, CHOICE and FOR (each record) can be combined and nested to cre- ate complex, powerful procedures. DEC DATATRIEVE responds to programming errors with clear, explicit er- ror messages. The user can issue an EDIT command to invoke a text ed- itor with an erroneous statement as input text, correct the mistake, and resubmit the command. This editor can be either EDT, TPU, or DEC Language-Sensitive Editor (LSE) and is controlled by a user logical name assignment. Data Definition DEC DATATRIEVE stores the fixed attributes of each record in the record definition. In addition to COBOL-like attributes, DEC DATATRIEVE al- lows validation criteria, fields whose values are computed at run-time, missing value expressions, and default values. DEC DATATRIEVE supports most data types used by DEC Fortran[TM], COBOL, VAX PL/I, DEC C, and DEC BASIC[TM]. DEC DATATRIEVE also supports Vary- ing String and Segmented String data types in DEC Oracle Rdb for Open- VMS databases. 5 Views A VIEW is an alternative description of data. It can be used to al- low a user access to a subset of the data items in a record. It can restrict a user by including only some of the data items in a record, or it can combine data items from several files. Information can be linked through common values (or set linkages in Oracle CODASYL DBMS) to produce complex hierarchical structures. Using a predefined VIEW, a user can access and display data from several files at once with the same commands used on a single file. Data accessed through a VIEW can be printed and modified, but data cannot be stored or erased using a VIEW. Call Interface DEC DATATRIEVE provides a client/server API. The DATATRIEVE Client li- braries for OpenVMS and Windows[TM] systems are supplied with the kit of the DATATRIEVE product for OpenVMS systems, and can be copied freely to Client systems. DEC DATATRIEVE can be accessed from the following programs: o Programs linked with DEC DATATRIEVE, residing on the same node and process space where DEC DATATRIEVE resides, and written in high- level languages such as DEC Fortran, DEC C, COBOL, DEC BASIC, DEC Pascal[TM], and VAX PL/I. o Programs linked with a DEC DATATRIEVE client library, residing on different nodes or platforms, and written in Visual C++[R], Visual Basic[R] or OpenVMS program languages. DEC DATATRIEVE automatically converts data from its storage format to the format expected by the program. DEC DATATRIEVE Client for Windows[TM] The DEC DATATRIEVE Client/Server architecture allows existing DEC DATA- TRIEVE users to downsize and distribute their applications and inter- active DEC DATATRIEVE operations. The DEC DATATRIEVE Client for Windows is separately packaged. 6 DEC DATATRIEVE Client for Windows is an application which provides a user-friendly graphical interface on personal computers running Mi- crosoft[R] Windows to perform DEC DATATRIEVE operations on a connected server. The DEC DATATRIEVE Client for Windows offers a graphical user inter- face that permits users to: o Browse through the dictionary from a Windows desktop. o Access, modify, and execute their existing DEC DATATRIEVE proce- dures and dictionary objects. o Access the DEC DATATRIEVE language for interactive queries using a query editor. o Operate on data: display, modify, and store. o Interoperate (data import/export) with other PC applications. DEC DATATRIEVE Client for Windows Version 1.1 contains the following new features, that permit users to: o Use a query-by-example mechanism in the Query Editor. A query can be specified by providing constraints on field values and simple links between fields, without using the graphical query editor. o Define DEC DATATRIEVE objects using specific dialog boxes that guide the creation of the objects themselves. o Use plots. DEC DATATRIEVE Client for Windows PLOT statements pro- duce graphic results in the client environment. o Use Client/Server TCP/IP transport in addition to DECnet. Storage Methods DEC DATATRIEVE uses a single, consistent syntax to provide full ac- cess to information stored in RMS for OpenVMS sequential or indexed files (RMS relative files are supported for queries only), Oracle CO- DASYL DBMS, and Oracle Rdb databases. DEC DATATRIEVE can also provide access to information stored in certain IBM[R] mainframe databases through 7 the use of DEC DB Integrator Gateway for DB2[TM], as well as infor- mation stored in ORACLE[R] databases through DEC DB Integrator Gate- way for ORACLE, and SYBASE[R] databases through DEC DB Integrator Gate- way for SYBASE. Data from all these sources can be combined into a sin- gle VIEW. If access to a Oracle CODASYL DBMS database involves explicit set walk- ing or if records must be manually connected or disconnected from sets, the user can employ DEC DATATRIEVE language features that are specific to Oracle CODASYL DBMS access. However, if the user employs VIEWS or implicit set walking, DEC DATATRIEVE can access information in Ora- cle CODASYL DBMS databases using the same syntax used for data from an RMS file or Oracle Rdb. Report Generation The DEC DATATRIEVE REPORT statement can produce simple formatted re- ports without formatting statements. It also allows the user to over- ride the default format when more complex reports are required. Re- ports can either be page-based, printable documents, or table-based formatted data that can be input by a spreadsheet. Column headers and, in page-based reports, page headers containing ti- tle, date, and page numbers are produced automatically. Simple state- ments (AT TOP, AT BOTTOM) create page headers and trailers for con- trol breaks, page breaks or a report summary. DEC DATATRIEVE provides all of its statistical functions and value expressions within the RE- PORT statement. Reports can be output in a variety of output formats: table reports are produced in DTIF format, and page-based reports in DDIF, PostScript[R] and Text formats. Usage of DDIF and PostScript allows a variety of text attributes (size, font types, rendition) to be applied to any part of the report to obtain a boardroom-quality output. These attributes, and other printing characteristics such as page size and orientation, can be selected from DEC DATATRIEVE through simple statements without re- quiring the use of a graphical terminal. Simple character-cell based reports are also available, using the Text format. Using the CDA[TM] 8 converter library, DTIF and DDIF reports can be converted to a vari- ety of output formats, allowing interoperability with a number of pop- ular applications. The Report Writer provides two layout tools: a grid printout of the CDA report layout with placement of rows and columns, including those with varying font types, and graphical printout of the layout page, with placement of the different report objects (such as header, footer, body) Reports can be generated from data stored in RMS files, Oracle CODA- SYL DBMS and Oracle Rdb databases. Reports can also be generated from other databases accessed through the use of the appropriate DEC DB In- tegrator Gateways or DEC DATATRIEVE VIEWS that combine any of these databases without any change in the syntax of the REPORT statement. Graphics DEC DATATRIEVE includes a number of predefined plots invoked with a single command that takes standard record selection expressions as ar- guments and creates bar, pie, line, and scattered point plots of the information selected. Plots can be displayed on Digital Equipment Cor- poration Graphics terminals such as the VT340 (refer to the OPTIONAL HARDWARE section for a list of specific supported terminals). Hard copy can be obtained from terminals by attaching a Digital device which sup- ports the SIXEL protocol (for example, LA50, LA75). For users with DECwin- dows, graphics can be displayed in DECterm windows. The DATATRIEVE Client V1.1 for Windows can display, process, modify, print plots created by the plot statement, and export the plot using the clipboard to other applications. Printing to postscript printers is also supported. Compatibility DEC DATATRIEVE for OpenVMS VAX systems and DEC DATATRIEVE for Open- VMS Alpha systems are highly compatible, with the exception of the sup- port for floating point definitions, typical of the Alpha platform. 9 DEC DATATRIEVE is largely upward compatible from DATATRIEVE-11. DATATRIEVE-11 provides a utility that extracts the contents of a DATATRIEVE-11 dic- tionary in a format to be entered into Oracle CDD/Repository for Open- VMS. Some syntactic and semantic differences do exist between DATATRIEVE-11 and DEC DATATRIEVE. Procedures copied with the EXTRACT utility can re- quire modification. DEC DATATRIEVE for OpenVMS VAX systems and DEC DATATRIEVE for Open- VMS Alpha systems are highly compatible, with the exception of the sup- port for floating point definitions typical of the Alpha platform. SOURCE CODE INFORMATION The following source code modules are provided with binary, single- use license options on all magnetic distribution media: o Function definitions o Text definitions o Macro library for function and text definitions o Message text o Sample callable DEC DATATRIEVE programs in Fortran, C, BASIC, and Visual BASIC o DEC DATATRIEVE dictionary object definitions: - Plots - Domains - Records - Procedures - Tables o Language INCLUDE files for the DEC DATATRIEVE Access Block (used by Callable DEC DATATRIEVE) o Language INCLUDE files for literal values, external symbols and rou- tine entry point definitions 10 o Language TEMPLATE file for use with DEC Language-Sensitive Editor (LSE) This source code is provided on an "as is" basis without any warranty of any kind, either express or implied. HARDWARE REQUIREMENTS Processors Supported VAXft[TM] Models 110, 310, 410, 610, 612 Systems: VAX Systems VAXserver[TM] 3100, VAXserver 3300, VAXserver /Servers: 3400, VAXserver 3500, VAXserver 3600, VAXserver 3602, VAXserver 3800, VAXserver 3900 VAXserver 4000 Model 50, VAXserver 4000 Model 100 Series, VAXserver 4000 Model 200 Series, VAXserver 4000 Model 300 Series, VAXserver 4000 Model 400 Series, VAXserver 4000 Model 500 Series, VAXserver 4000 Model 600 Series, VAXserver 4000 Model 700 Series VAX 6000 Model 200 Series, VAX 6000 Model 300 Series, VAX 6000 Model 400 Series, VAX 6000 Model 500 Series, VAX 6000 Model 600 Series VAX 7000 Model 600 Series, VAX 7000 Model 700 Series VAX 8000 Model 200 Series, 11 VAX 8000 Model 300 Series, VAX 8000 Model 500 Series, VAX 8000 Model 600 Series, VAX 8000 Model 700 Series, VAX 8000 Model 800 Series, VAX 8000 Model 900 Series VAX 9000 Model 110, VAX 9000 Model 210, VAX 9000 Model 300 Series, VAX 9000 Model 400 Series VAX-11/730, VAX-11/750, VAX-11/780, VAX-11/785 MicroVAX[TM]MicroVAX II[TM], 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 3300, MicroVAX 3400, MicroVAX 3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900 VAXstation[TVAXstation II, VAXstation 2000, VAXstation 3100 Model 30, VAXstation 3100 Model 38, VAXstation 3100 Model 40, VAXstation 3100 Model 48, VAXstation 3100 Model 76, VAXstation 3200, VAXstation 3500, VAXstation 3520, VAXstation 3540 VAXstation 4000 Model 60, VAXstation 4000 VLC Processors Not Supported 12 MicroVAX I[TM], VAXstation I, VAX-11/725, VAX-11/782, VAXstation 8000 Processor Restrictions: A TK50 Tape Drive is required for standalone MicroVAX 2000 and VAXs- tation 2000 systems. Other Hardware Required: Mass storage with a minimum of 25,000 disk blocks for DEC DATATRIEVE system software for VAX Systems. Disk Space Requirements (Block Cluster Size = 1): Disk space required for 18,000 blocks installation: (15.3 Mbytes) Disk space required for 20,000 blocks use (permanent): (10.2 Mbytes) These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. Memory Requirements for DECwindows Support: The minimum supported memory for this application running in a stan- dalone DECwindows environment with both the client and server execut- ing on that same system is 8M bytes. The performance and memory usage of DECwindows applications are par- ticularly sensitive to system configuration. Less memory may be re- quired on the client system (the system where the software is installed and executed) if the server (the component that displays the appli- cation) resides on another system. More memory may be required on a system with several applications running, or where it may be desir- able to improve the performance of an application. 13 OPTIONAL HARDWARE Any device supported by the prerequisite software. Graphics can be displayed on VT125, VT240, VT241, VT330, and VT340 ter- minals only. For users with DECwindows, graphics can be displayed in DECterm windows. CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VAXcluster[TM]* configuration without restrictions. The HARDWARE REQUIREMENTS section of this product's Software Product De- scription details any special hardware required by this product. * V5.x VAXcluster configurations are fully described in the VAXclus- ter Software Product Description (29.78.xx) and include CI, Eth- ernet, and Mixed Interconnect configurations. SOFTWARE REQUIREMENTS For Systems Using Terminals (No DECwindows Interface): o OpenVMS VAX Operating System Version 5.3 or higher. For Fullname support OpenVMS VAX Version 6.1 is required. For Workstations Running VWS: o OpenVMS VAX Operating System Version 5.3 or higher. For Fullname support OpenVMS VAX Version 6.1 is required. o OpenVMS Workstation Software V4.1 - V4.2 For Workstations Running DECwindows Motif: o OpenVMS VAX Operating System Version 5.3 or higher (and necessary components of DECwindows Motif for OpenVMS). For Fullname support OpenVMS VAX Version 6.1 is required. 14 The following information concerns CDA output (PostScript, DDIF, DTIF): o For systems running DECwindows Motif: CDA output is provided by the converter libraries which are bundled with DECwindows Motif itself. o For systems using terminals: the prerequisite software CDA Run-time Services must be installed. This product may run in either of the following ways: o Stand-alone execution - running the X11 display server and the client application on the same machine. o Remote execution - running the X11 display server and the client application on different machines. OpenVMS DECwindows is part of the OpenVMS VAX Operating System but must be installed separately. Installation of OpenVMS DECwindows gives users the option to install any or all of the following three components: o OpenVMS DECwindows Compute Server (Base kit; includes run-time sup- port) o OpenVMS DECwindows Device Support o OpenVMS DECwindows Programming Support For stand-alone execution, the following DECwindows component must be installed on the machine: o OpenVMS DECwindows Compute Server For remote execution, the following DECwindows component must be in- stalled on the machine: Server Machine o OpenVMS DECwindows Compute Server (Base kit; includes run-time sup- port) 15 Client Machine o OpenVMS DECwindows Compute Server (Base kit; includes run-time sup- port) OpenVMS Tailoring The following OpenVMS classes are required for full functionality of this layered product: o OpenVMS Required Saveset o Network Support o Programming Support o System Programming Support o Utilities For more information on OpenVMS classes and tailoring, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.xx). OPTIONAL SOFTWARE o DECwindows Motif V1.1 or higher o Oracle CDD/Repository for OpenVMS Version 5.0 or higher o VAX Rdb/ELN[TM] V2.1 or higher o Oracle CODASYL DBMS V4.2 or higher (for this option, the instal- lation of the Oracle CDD/Repository is a prerequisite) o DECforms V1.3 or higher o VAX FMS V2.3 or higher o VAX Language-Sensitive Editor V1.3 for character cell terminals. VAX Language-Sensitive Editor/Source Code Analyzer V3.1 for work- stations running DECwindows o Oracle Rdb/VMS V4.0B or higher o VAX TDMS V1.9 or higher 16 o DEC DB Integrator Gateway for DB2 V1.0 or higher o DEC DB Integrator Gateway for ORACLE V1.0 or higher o DEC DB Integrator Gateway for SYBASE V1.0 or higher o CDA Run-time Services for OpenVMS V1.0 o DECnet/OSI for OpenVMS VAX Version 5.7 or higher for Fullname sup- port. o In order to use the DATATRIEVE Client for Windows with the DATA- TRIEVE server, the following software is required by the Client: * Microsoft Windows Version 3.1 or higher, or Microsoft Windows 95[R], or Microsoft Windows NT[TM]. * A compiler or interpreter that can access DLL libraries (only required for the DEC DATATRIEVE Call Interface). The following software has been tested to support DECnet connections: * On the Server: - DECnet Extensions Version 5.4 for OpenVMS VAX or DECnet Version 6.0 or higher for OpenVMS VAX. * On the Client: - PATHWORKS[TM] Version 5.0A or higher for Windows V3.1 and V3.11. The following software has been tested to support TCP/IP connections: * On the Server: - DEC TCP/IP Services for OpenVMS V3.2 - TGV MultiNet[R] V3.3 * On the Client: - PATHWORKS Version 5.0A or higher for Windows V3.1 and V3.11. - TCP/IP for Windows 95 17 - TCP/IP for Windows V3.11 - TCP/IP for Windows NT V3.5 - Trumpet V2.1 Rev F Certain versions of these products depend upon a specific version of the operating system. Please refer to the Software Product Descrip- tion of the product in question to determine which version is required. GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA 9-track 1600 BPI Magtape, TK50 Streaming Tape This product is also available as part of the OpenVMS VAX Consolidated Software Distribution on CD-ROM. The software documentation for this product is also available as part of the OpenVMS VAX Online Documentation Library on CD-ROM. ORDERING INFORMATION Unlimited Use Software Licenses: QL-898A*-** Software Media: QA-898A*-** Software Documentation: QA-898AA-GZ Software Product Services: QT-898A*-** Concurrent Use Software License: QL-898A*-3* Personal Use 18 Software License: QL-898A*-2* * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. SOFTWARE LICENSING This software is furnished under the licensing provisions of Digital Equipment Corporation's Standard Terms and Conditions. For more in- formation about Digital's licensing terms and policies, contact your local Digital office. License Management Facility Support: This layered product supports the OpenVMS License Management Facil- ity. License units for this product are allocated on an Unlimited System Use plus Personal Use and Concurrent Use basis. This layered product offers a Personal Use license. Each Personal Use license allows one identified individual to use the layered product. This layered product offers a Concurrent Use license. Each Concurrent Use license allows any one individual at a time to use the layered prod- uct. For more information on the License Management Facility, refer to the OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx) or the OpenVMS VAX Operating System documentation. For more information about Digital's licensing terms and policies, con- tact your local Digital office. 19 SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. For more in- formation, contact your local Digital office. SOFTWARE WARRANTY Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the SOFTWARE LICENS- ING section of this SPD. © 1996 Digital Equipment Corporation. All rights reserved. [TM] DB2 is a trademark of International Business Machines Corpo- ration. [R] IBM is a registered trademark of International Business Ma- chines Corporation. [R] Microsoft, MS, Visual Basic, Visual C++, Windows, and Windows 95 are registered trademarks of Microsoft Corporation. [R] MultiNet is a registered trademark of TGV, Inc. [R] Motif is a registered trademark of Open Software Foundation, Inc. [R] ORACLE is a registered trademark of Oracle Corp. [TM] Oracle CDD/Repository, Oracle CODASYL DBMS, Oracle Expert, Oracle Rdb and Oracle TRACE are trademarks of Oracle Corpora- tion. [R] PostScript is a registered trademark of Adobe Systems Corp. [TM] Windows NT is a trademark of Microsoft Corporation. [TM] CDA, DATATRIEVE, DEC, DEC BASIC, DEC Fortran, DECforms, DEC- net, DECwindows, FMS, MicroVAX, MicroVAX I, MicroVAX II, OpenVMS, PATHWORKS, PDP, ReGIS, VAX, VAX 6000, VAX Pascal, VAX Rdb/ELN, VAXft, VAXstation, VMS RMS, and the DIGITAL logo are trademarks of Digital Equipment Corporation. 20