       $                               Compaq   Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  DECset Release 12.2A for OpenVMS VAX Systems     SPD  27.07.21   DESCRIPTION   D DECset for OpenVMS VAX Systems is an integrated programming tool setH that supports software developers' coding, debugging, testing, and main- tenance activities.   A DECset for OpenVMS VAX Systems contains the following components:   D o  DIGITAL Language-Sensitive Editor/Source Code Analyzer (LSE/SCA),'    Version 4.5, for OpenVMS VAX Systems   = o  DIGITAL Test Manager, Version 3.8, for OpenVMS VAX Systems   D o  DIGITAL Performance and Coverage Analyzer (PCA), Version 4.5, for    OpenVMS VAX Systems  E o  DIGITAL Code Management System (CMS), Version 3.9, for OpenVMS VAX 
    Systems  C o  DIGITAL Module Management System (MMS), Version 3.2, for OpenVMS     VAX Systems  C The components of the DECset tool set can be used in either a work- F station or character-cell terminal environment. All components includeE both DECwindows Motif[R] for OpenVMS VAX and command-line interfaces.   C In addition to these six tools, DECset also provides an Environment E Manager (ENVMGR), which provides a single mechanism for tailoring the E execution environment for a set of DECset tools. DECset also provides C the program design facility, a set of features in LSE, SCA, and the   C                                                         August 1999        C compilers that aid in the detailed program design phase of software  development.  ) DECset for OpenVMS VAX Systems Components   - DIGITAL Language-Sensitive Editor/Source Code ! Analyzer for OpenVMS VAX Systems:    Language-Sensitive Editor   C The Language-Sensitive Editor (LSE) is a multilanguage programmer's C editor. Language-specific templates and online language help assist C both new and experienced programmers in developing programs faster. D With LSE, users can efficiently edit, compile, review diagnostic in-D formation from compilations, and correct compile time errors withoutH exiting the editor. LSE also enables users to customize and extend their editing environment.  D Programmers can perform low-level program designs with LSE by embed-G ding pseudocode in source code. Users can also view source code at var- D ious levels of detail by replacing a sequence of source lines with a single overview line.   C LSE provides an interface via callable routines, as well as through C the LSE command-line interface and the DECwindows Motif for OpenVMS  VAX interface.  E The following VAX compilers fully support LSE; the language templates  are included with LSE:  
    DEC Ada    DEC BASIC    DEC C
    DEC C++    VAX COBOL    DIGITAL Fortran
    DEC PASCAL     VAX BLISS-32     VAX C    VAX MACRO  "                                  2           VAX PL/1   G The following VAX products partially support LSE (refer to product SPDs ? for more details); the templates are included with the product:       DIGITAL ACMS (SPD 25.50.xx)     DEC DATATRIEVE (SPD 24.44.xx)  E Note: Certain LSE features are not available when using language pre- 2 processors, such as those supplied for Oracle Rdb.  C LSE works in concert with CMS, SCA, and the VAX Debugger to provide G a highly interactive, online environment that facilitates the NAVIGATE- C EDIT-COMPILE-DEBUG portion of the program development cycle. DECset C users can directly reserve and replace files from CMS while in LSE, C go to the exact source code location in LSE from the SCA, and go to < the exact source code location in LSE from the VAX Debugger.   Source Code Analyzer  D The Source Code Analyzer (SCA) aids programmers in understanding theE complexities of software systems. Since it allows users to analyze an D entire system, as opposed to individual modules, and helps users un-D derstand unfamiliar systems, SCA is extremely useful during both the3 implementation and maintenance phases of a project.   D SCA provides navigation capabilities to assist users in locating andG viewing components of their source code. SCA accomplishes this by stor- D ing compiler-generated information about a set of source files in anH SCA library. SCA then allows users to perform queries about their source code in the following ways:   G o  Using a name browser to locate all items that match a search string.   C o  Specifying a cross-reference query to find how and where program     symbols are used.  F o  Specifying a call graph query to graphically display call relation-    ships between routines.  "                                  3       F o  Specifying a data structure query to graphically display the struc-F    ture of data types in the source code or to find symbols of a given    type.  C After users have a query result, they can use the go-to-source fea- ? ture to navigate to locations of interest in their source code.   H SCA also provides static analysis capabilities to assist users in check-& ing consistent use of program symbols.  C SCA provides an interface via callable routines, as well as through C the SCA command-line interface and the DECwindows Motif for OpenVMS G VAX interface. The following VAX compilers generate information to pop-  ulate an SCA library:   
    DEC Ada    DEC BASIC    DEC C    VAX C    VAX COBOL    DIGITAL Fortran
    DEC PASCAL     VAX BLISS-32     VAX MACRO    VAX PL/1   E Note: SCA is not available when using language preprocessors, such as  those supplied for Oracle Rdb.  D The following VAX compilers also generate pseudocode and specializedH comment processing information so SCA can produce design reports, cross-# reference and analysis information:   
    DEC Ada    DEC BASIC    VAX C    VAX COBOL    DIGITAL Fortran
    DEC PASCAL     VAX BLISS-32   "                                  4           VAX PL/1   - DIGITAL Language-Sensitive Editor/Source Code G Analyzer for OpenVMS VAX Systems is a component of the DECset for Open- D VMS VAX Systems product and is also available separately. Please re-4 fer to the ORDERING INFORMATION section of this SPD.  , DIGITAL Test Manager for OpenVMS VAX Systems  F The DIGITAL Test Manager for OpenVMS VAX Systems is a regression test-I ing tool that automates the creation and maintenance of regression tests. F It also automatically compares test run results with expected test re-F sults. The DIGITAL Test Manager provides users with flexibility in or-D ganizing tests, selecting tests for execution, and verifying and re-> viewing test results. With the DIGITAL Test Manager users can:  , o  Test batch and command-line applications.  I o  Test interactive applications that input and output text to character- ?    cell terminals (DEC and ANSI CRT) with single display plane.    o  Create and record tests.   , o  Group tests into meaningful combinations.  E o  Execute specific tests, groups of tests, or combinations of groups     of tests.  D o  Compare the results of the executed tests with benchmark test re-"    sults to determine differences.  # o  View test results interactively.    o  Update benchmarks as needed.   F o  Filter test results to ignore output that is expected to change for    each test execution.   F The DIGITAL Test Manager enables users to store software test descrip-@ tions and related files in CMS libraries for storage efficiency.  "                                  5       D The DIGITAL Test Manager provides an interface through callable rou- tines, as well as through the D DIGITAL Test Manager command-line interface and the DECwindows Motif for OpenVMS VAX interface.  F The DIGITAL Test Manager for OpenVMS VAX Systems is a component of theH DECset for OpenVMS VAX Systems product and is also available separately.= Please refer to the ORDERING INFORMATION section of this SPD.   A DIGITAL Performance and Coverage Analyzer for OpenVMS VAX Systems   C The DIGITAL Performance and Coverage Analyzer (PCA) for OpenVMS VAX F Systems helps users pinpoint execution bottlenecks in application pro-F grams. PCA can also identify which parts of an application are not ex-D ecuted by a given set of test data. PCA has two components: the Col-C lector, which gathers performance or test coverage data on the run-_C ning user program; and the Analyzer, which later processes and dis-oD plays the collected data. The Analyzer graphically presents informa-H tion in four types of charts: histograms, tables, annotated source list- ings, and call trees.d  D PCA does not analyze operating system performance or aid in hardware resource planning.  E PCA can gather and report on the following types of performance data:r   o  Call stacks   o  CPU sampling data   o  Event markers   o  PC sampling dataT   o  Page fault data   o  System services datat   o  Input/Output data   o  Exact execution counts(   o  Test coverage data   "                                  6 a  e   o  Ada tasking datai  . Additional PCA features include the following:  7 o  Traversing commands to sift through performance data   E o  Screen mode to display different types of data in separate windowst  C o  Multiple data kinds allowing the display of different categoriesn5    of performance data in the same histogram or tablea  F o  Acceptable noncoverage indicating portions of code that are accept-"    ably noncovered to the Analyzer  - o  Filtering to analyze only a subset of dataa  C With PCA, users can analyze applications written in any of the fol-l lowing OpenVMS languages:e  
    DEC Ada    DEC BASIC    DEC C
    DEC C++    VAX COBOL    DIGITAL Fortran
    DEC PASCAL     VAX BLISS-32u    VAX PL/1   D PCA works in concert with LSE and the DIGITAL Test Manager. From theE character-cell version of PCA, users can communicate with LSE and canAE examine source code. When used with the DIGITAL Test Manager, PCA cane3 evaluate the code coverage of a user's test system.n  H PCA provides a command-line interface and the DECwindows Motif for Open- VMS VAX interface.  D DIGITAL Performance and Coverage Analyzer for OpenVMS VAX Systems is a component of theH DECset for OpenVMS VAX Systems product and is also available separately.= Please refer to the ORDERING INFORMATION section of this SPD.w  "                                  7 l  u  6 DIGITAL Code Management System for OpenVMS VAX Systems  E The DIGITAL Code Management System (CMS) for OpenVMS VAX Systems pro-iD vides an efficient method for storing project files and tracking allK changes to those files. Code management is especially important to projectse> that have long life spans or several versions of the software.  C CMS stores any kind of RMS file, including documents; plans; speci-dF fications; status reports; source code files; object files; executableG images; sixel files; or other records, and keeps these files in projectCE libraries. CMS also stores history information. As a project evolves,rE CMS tracks changes to the library by storing only the changes made to C a file. Not only does this reduce the amount of disk space used forAD storing multiple versions of files, but it also allows CMS to recon-F struct any previous version of a file and to identify the changes madeD between any two versions. In addition to storing successive changes,C CMS maintains a record of who is currently working on a library el-h0 ement and a historical record of library access.   With CMS, users can:  & o  Support multiple project libraries.  , o  Retrieve previous generations (versions).  * o  Delete, purge, or collapse generations.  E o  Obtain a report of file modifications, including when, why, and byr"    whom the modification was made.  F o  Determine the origin of each line of a file, either as an annotated&    listing or as comments in the file.  # o  Manage concurrent modifications.z  , o  Merge separately developed modifications.  5 o  Combine related files together as a class (group).e  C o  Relate the generation of one element to the corresponding gener-iE    ations of other elements for purposes of freezing baselines or re-A1    leases and for organizing ongoing development.n  "                                  8       G o  Interface via callable routines, as well as through the CMS command-oE    line interface and the DECwindows Motif for OpenVMS VAX interface.p  H o  Through the use of CMS access control lists, fine tune security mech-D    anisms applied to CMS libraries, and provide a means of notifica-    tion about library events.a  D CMS can act as a project's central repository, by storing and track-C ing source-code files, object code, documentation, and a variety ofmC files generated by other tools. CMS can store files for MMS and thepC DIGITAL Test Manager. LSE and DIGITAL Test Manager users can access ? CMS elements directly from within LSE and DIGITAL Test Manager.   I The DIGITAL Code Management System provides an interface through callableoG routines, as well as through the command-line interface and the DECwin-e% dows Motif for OpenVMS VAX interface.t  E DIGITAL Code Management System for OpenVMS VAX Systems is a componentoC of the DECset for OpenVMS VAX Systems product and is also availablesD separately. Please refer to the ORDERING INFORMATION section of this SPD.  9 DIGITAL Module Management System for OpenVMS VAX Systems:d  D DIGITAL Module Management System (MMS) for OpenVMS VAX Systems auto-C mates and simplifies the building of software applications, whetherCE they are simple programs of only one or two files or complex programsnF consisting of many source files, message files, and documentation. MMSG can optimize the build process by rebuilding only those components (anduF their dependencies) in a system that have changed since the system wasD last built. In this way, MMS eliminates the steps of recompiling andC linking modules that have not changed. MMS can automatically gener- D ate description files. Once users create a description file contain-H ing the rules describing the relationships among the components of theirH application and the MMS commands to build the application, MMS can build2 both small or large systems with a single command.  H MMS provides a command-line interface and the DECwindows Motif for Open- VMS VAX interface.  "                                  9 P     D DIGITAL Module Management System for OpenVMS VAX Systems is a compo- nent of the DECset forD OpenVMS VAX Systems product and is also available separately. Please6 refer to the ORDERING INFORMATION section of this SPD.   HARDWARE REQUIREMENTSi   Processors Supported:t   VAXft:    VAXft 3000 Processorss   VAX:      VAX 4000 Model 50 (           VAX 4000 Model 100, 100A, 105A           VAX 4000 Model 200           VAX 4000 Model 300(           VAX 4000 Model 500, 500A, 505A"           VAX 4000 Model 600, 600A#           VAX 4000 Model 700A, 705At  +           VAX 6000 Model 210, 220, 230, 240l0           VAX 6000 Model 310, 320, 330, 340, 3605           VAX 6000 Model 410, 420, 430, 440, 450, 460s5           VAX 6000 Model 510, 520, 530, 540, 550, 560 5           VAX 6000 Model 610, 620, 630, 640, 650, 660o  5           VAX 7000 Model 610, 620, 630, 640, 650, 660w5           VAX 7000 Model 710, 720, 730, 740, 750, 760e5           VAX 7000 Model 810, 820, 830, 840, 850, 860              VAX 8200, VAX 8250           VAX 8300, VAX 8350           VAX 8530, VAX 8550           VAX 8600, VAX 8650           VAX 8700&           VAX 8800, VAX 8810, VAX 8820           VAX 8830, VAX 8840        "                                 10 c       &           VAX 8842, VAX 8974, VAX 8978  #           VAX 9000 Model 110, 110VPn#           VAX 9000 Model 210, 210VPe#           VAX 9000 Model 310, 310VPe#           VAX 9000 Model 320, 320VP #           VAX 9000 Model 330, 330VP #           VAX 9000 Model 340, 340VPr#           VAX 9000 Model 410, 410VPn#           VAX 9000 Model 420, 420VPe#           VAX 9000 Model 430, 430VPr#           VAX 9000 Model 440, 440VPI  6           VAX 10000 Model 610, 620, 630, 640, 650, 660   MicroVAX: MicroVAX IIp           MicroVAX 2000   5           MicroVAX 3100 Model 10/10E, 20/20E, 30, 40,M8           MicroVAX 3100 Model 80, 85, 88, 90, 95, 96, 98&           MicroVAX 3200, MicroVAX 3300&           MicroVAX 3400, MicroVAX 3500&           MicroVAX 3600, MicroVAX 3800           MicroVAX 3900p  1 VAXstation: VAXstation II/GPX, VAXstation II/QVSSr             VAXstation 2000n             VAXstation 2000/GPXa             VAXstation 2000/MFBd  4             VAXstation 3100 Model 30, 38, 40, 48, 760             VAXstation 3100/GPX Model 38, 48, 760             VAXstation 3100/SPX Model 38, 48, 76             VAXstation 3200n,             VAXstation 3500, VAXstation 3520        "                                 11 h  a                 VAXstation 3540o  5             VAXstation 4000 Model 60, 90, 95, 96, VLC   1 VAXserver:  VAXserver 3100 Model 10, 10E, 20, 20E &             VAXserver 3200, 3300, 3400,             VAXserver 3500, 3600, 3800, 3900  8             VAXserver 4000 Model 200, 300, 400, 500, 600  )             VAXserver 6000 Model 210, 220t)             VAXserver 6000 Model 310, 320o)             VAXserver 6000 Model 410, 420t)             VAXserver 6000 Model 510, 520t    VAXserver:  VAXserver 8200, 8250              VAXserver 8300, 8350              VAXserver 8530, 8550              VAXserver 8600, 8650             VAXserver 87002             VAXserver 8800, 8810, 8820, 8830, 8840   Processors Not Supported:e  
 MicroVAX I VAXstation I VAXstation 8000  VAX-11/725, VAX-11/730 VAX-11/750, VAX-11/751" VAX-11/780, VAX-11/782, VAX-11/785   Processor Restrictions:t  D A TK50 Tape Drive is required for standalone MicroVAX 2000 and VAXs- tation 2000 systems.  	 TerminalsG    "                                 12 3     C Character-cell interfaces for DECset are supported on the followingg
 terminals:   o  VT1xx   o  VT2xx   o  VT3xx   o  VT4xx   o  VT5xx   o  ANSI CRTx  1 Disk Space Requirements (Block Cluster Size = 1):n  F Each component of DECset for OpenVMS VAX Systems can be installed sep-D arately. Each component requires the following disk space for a suc- cessful installation:   C ___________________________________________________________________ B                    Space required     Space required for use (per-C COMPONENT__________to_install_________manent)______________________i  3 LSE:               40,000 blocks      23,000 blocks 3                    (20.5M bytes)      (12.0M bytes)V  3 SCA:               13,000 blocks      10,000 blocksf2                    (6.7M bytes)       (5.1M bytes)  2 DIGITAL Test       15,000 blocks      5,500 blocks Manager:2                    (7.7M bytes)       (2.6M bytes)  2 PCA:               12,000 blocks      9,000 blocks2                    (6.1M bytes)       (4.6M bytes)  2 MMS:               4,000 blocks       1,500 blocks2                    (2.0M bytes)       (1.0M bytes)  "                                 13 d  a    C ___________________Space_required_____Space_required_for_use_(per-_rC COMPONENT__________to_install_________manent)______________________s  2 CMS:               10,000 blocks      4,000 blocks2                    (5.1M bytes)       (2.0M bytes)  2 ENVMGR:            2,500 blocks       1,000 blocksC ___________________(1.3M_bytes)_______(0.5M_bytes)_________________h  C Requirements for installation of all DECset for OpenVMS VAX SystemssD components, including Language-Sensitive Editor support for all lan-* guages, requires the following disk space:  C ___________________________________________________________________cB                    Space required     Space required for use (per-C COMPONENT__________to_install_________manent)______________________m  3 ALL COMPONENTS:    87,800 blocks      48,600 blocks C ___________________(45.3M_bytes)______(24.9M_bytes)________________i  C These counts refer to the maximum disk space required on the system C disk. The sizes are approximate; actual sizes may vary depending onoC the user's system environment, configuration, and software options.e  D The minimum supported memory for this application running in a stan-E dalone DECwindows Motif[R] for OpenVMS VAX environment, with both theA: client and server executing on that same system, is 32 MB.  D The performance and memory usage of DECwindows Motif for OpenVMS VAXE applications are particularly sensitive to system configuration. LessEE memory may be required on the DECwindows Motif for OpenVMS VAX client C system (the system where the software is installed and executed) ifCC the server (the component that displays the application) resides on D another system. More memory may be required on a system with severalE applications running or where it may be desirable to improve the per-r formance of an application.o      "                                 14 h      CLUSTER ENVIRONMENTS  C This layered product is fully supported when installed on any validmF and licensed VMScluster* configuration without restrictions. The HARD-F WARE REQUIREMENTS sections of this product's Software Product Descrip-: tion detail any special hardware required by this product.  H *  VAXcluster configurations are fully described in the VAXcluster Soft-D    ware Product Description (SPD 29.78.xx) and include CI, Ethernet,)    and Mixed Interconnect configurations.e   SOFTWARE REQUIREMENTSF  E For Systems Using Terminals (Without DECwindows Motif for OpenVMS VAXe Interface):e  : o  OpenVMS VAX Operating System, Version 5.5-2-Version 7.1  5 For Systems Running DECwindows Motif for OpenVMS VAX:w  : o  OpenVMS VAX Operating System, Version 5.5-2-Version 7.1  0 o  DECwindows Motif for OpenVMS VAX, Version 1.2   OPTIONAL SOFTWAREs  D Certain versions of these products depend upon a specific version ofE the operating system. Please refer to the SPD of the product in ques-h- tion to determine which version is necessary.t  % o  DEC Ada Version 3.4 (SPD 26.60.xx)f  ' o  DEC BASIC Version 3.8 (SPD 25.36.xx)   # o  DEC C Version 5.6 (SPD 25.38.xx)r  % o  DEC C++ Version 5.6 (SPD 37.39.xx)a  ' o  VAX COBOL Version 5.4 (SPD 25.04.xx)e  ) o  DIGITAL Fortran Version 6.5 (25.16.xx)o  ( o  DEC PASCAL Version 5.6 (SPD 25.11.xx)  "                                 15 i     & o  VAX PL/1 Version 3.5 (SPD 25.30.xx)   GROWTH CONSIDERATIONSa  D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the currente version.   Year 2000 ReadyS    This product is Year 2000 Ready.D "Year 2000 Ready" products are defined by Compaq as products capableE of accurately processing, providing, and/or receiving date data from, F into and between the twentieth and the twenty-first centuries, and theC years 1999 and 2000, including leap year calculations, when used inlF accordance with the associated product documentation and provided thatG all hardware, firmware and software used in combination with such prod-6< ucts properly exchange accurate date data with the products.  C For additional information visit the DIGITAL Brand area on Compaq's0# Year 2000 Ready web site located at40 http://www.compaq.com/year2000/warranties3.html.   DISTRIBUTION MEDIA  - 9-track 1600 BPI Magtape, TK50 Streaming Tape6  C The software binaries and documentation are also available on vari-  ous CD-ROM distributions:d  G o  OpenVMS VAX Software Layered Products Library-This offering includes4C    the OpenVMS VAX Layered Product software binaries. (QA-5FW8A-A8)   F o  OpenVMS VAX Online Documentation Library-This offering includes theD    documentation for the OpenVMS VAX Layered Products. (QA-VYR8A-G8)          "                                 16    0  E o  OpenVMS VAX Software Layered Products Library Package- This offer-0D    ing contains both the software binaries and documentation for the.    OpenVMS VAX Layered Products. (QA-5G88A-H8)   ORDERING INFORMATION  F To order the DECset for OpenVMS VAX Systems product (includes all com-	 ponents):0   Software Licenses: Personal Use: QL-965AA-2B  Concurrent Use: QP-965AA-3Bd! Unlimited System Use: QL-965A*-**M) Software Media/Documentation: QA-965AB-H*e/ Software Documentation (Hard Copy): QA-965AA-GZV& Software Product Services: QT-965A*-**   To Order Components Separately:0  F DIGITAL Language-Sensitive Editor/Source Code Analyzer for OpenVMS VAX Systems:   Software Licenses: Personal Use: QL-057AA-2B3 Concurrent Use: QL-057AA-3B ! Unlimited System Use: QL-057**-** ) Software Media/Documentation: QA-965AB-H*n/ Software Documentation (Hard Copy): QA-965AA-GZi& Software Product Services: QT-057A*-**  - DIGITAL Test Manager for OpenVMS VAX Systems:    Software Licenses: Personal Use: QL-927AA-2B  Concurrent Use: QL-927AA-3Be! Unlimited System Use: QL-927**-**n) Software Media/Documentation: QA-965AB-H*s/ Software Documentation (Hard Copy): QA-965AA-GZt& Software Product Services: QT-927A*-**  "                                 17 s  i  B DIGITAL Performance and Coverage Analyzer for OpenVMS VAX Systems:   Software Licenses: Personal Use: QL-119AA-2B  Concurrent Use: QL-119AA-3B ! Unlimited System Use: QL-119**-**5) Software Media/Documentation: QA-965AB-H*e/ Software Documentation (Hard Copy): QA-965AA-GZ & Software Product Services: QT-119A*-**  7 DIGITAL Code Management System for OpenVMS VAX Systems:    Software Licenses: Personal Use: QL-007AA-2BM Concurrent Use: QL-007AA-3B ! Unlimited System Use: QL-007**-**A) Software Media/Documentation: QA-965AB-H*5/ Software Documentation (Hard Copy): QA-965AA-GZ & Software Product Services: QT-007A*-**  9 DIGITAL Module Management System for OpenVMS VAX Systems:e   Software Licenses: Personal Use: QL-VADAA-2BA Concurrent Use: QL-VADAA-3B7! Unlimited System Use: QL-VAD**-**7) Software Media/Documentation: QA-965AB-H* / Software Documentation (Hard Copy): QA-965AA-GZc& Software Product Services: QT-VADA*-**  F *  Denotes variant fields. For additional information on available li-D    censes, services, and media, refer to the appropriate price book.   SOFTWARE LICENSING  E This software is only furnished under a license. For more informationRD about Compaq's licensing terms and policies, contact your local Com- paq office.S  $ License Management Facility Support:  "                                 18    c  D These layered products support the OpenVMS License Management Facil- ity.  D License units for the DECset for OpenVMS VAX Systems product AND forC the component products are allocated on an Unlimited System Use ande" Personal and Concurrent Use basis.  E Each Personal Use license allows one identified individual to use the D layered product. Each Concurrent Use license allows any one individ-C ual at a time to use the layered product. These licenses are sharedI on VAX and Alpha Systems.c  D For more information on the OpenVMS License Management Facility, re-E fer to the OpenVMS Operating System Software Product Description (SPD  25.01.xx) or documentation.    SOFTWARE PRODUCT SERVICES   D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   SOFTWARE WARRANTY   F This software is provided by Compaq with a 90 day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.   H The warranty period is 90 days. It begins when the software is installedE or thirty days after delivery to the end user. Whichever occurs first_F and expires 90 days later. All warranty related support for this soft-@ ware will end one year after release of the subsequent versions.  D Warranty is provided in the country of purchase. Compaq will provideC a service location that will accept reporting (in format prescribed_E by Compaq) of a nonconformance problem caused when using the licensedqD software under normal conditions as defined by this SPD. Compaq willC remedy a nonconformance problem in the current unaltered release oflG the licensed software by issuing a correction information such as: cor-tE rection documentation, corrected code; or a notice of availability ofq  "                                 19    r  F corrected code; or a restriction or a bypass. The customer will be re-E sponsible for the preparation and submission of the problem report toy the service location.u   WARRANTY EXCLUSION  D Compaq does not warrant that the software licensed to customer shallD be error free, that the software shall operate with any hardware andE software other than as specified in this SPD, that the software shallaC satisfy customer's own specific requirements, or that copies of thebE software other than those provided or authorized by Compaq shall con-  form to the SPD.  D Compaq makes no warranties with respect to the fitness and operabil-( ity of modifications not made by Compaq.  D If the software fails to function for reasons stated above, the cus-G tomer's warranty will be invalidated and all service calls will be bil-e' lable at the prevailing per call rates.   D The previous information is valid at time of release. Please contact= your local Compaq office for the most up-to-date information.s  5 [R]  Motif is a registered trademark of Open SoftwareR      Foundation, Inc.e  B [TM] COMPAQ, and the Compaq logo, are registerd in the U.S. Patent      and Trademark Office.> [TM] DEC, DEC Ada, DEC BASIC, DIGITAL Fortran, DECset, DECwin-=      dows, DIGITAL, MicroVAX, OpenVMS, VAX, VAX C, VAX BLISS-8=      32, VAX MACRO, VAXcluster, VAXft, VAXserver, VAXstation,gB      VMScluster, and VT are trademarks of Compaq Computer Corpora-
      tion.  +  1997, 1999 Digital Equipment Corporation.  All rights reserved.        "                                 20