                                 D                 DEC_C/C++_Run-Time_Components_for_OpenVMS_VAX_______0                 Reference and Installation Guide  )                 Order Number: AA-Q0XBA-TK                      October 1993  ?                 This guide contains instructions for installing @                 the DEC C/C++ Run-Time Components on OpenVMS VAXB                 systems. It also contains important information onB                 distributing applications that are linked to DEC CC                 /C++ Run-Time Components. This guide applies to DEC E                 C/C++ Run-Time Components Version 6.0 for OpenVMS VAX D                 and all maintenance updates throughout that version.              B                 Revision/Update Information:  This is a new guide.  E                 Operating System & Version:   OpenVMS VAX Version 5.5 8                                               or higher.@                                               Future maintenance:                                               releases may<                                               require higher7                                               versions.   @                 Software Version:             DEC C/C++ Run-TimeD                                               Components Version 6.0=                                               for OpenVMS VAX   -                 Digital Equipment Corporation &                 Maynard, Massachusetts                 F       ________________________________________________________________"       First Printing, October 1993  ;       The information in this document is subject to change @       without notice and should not be construed as a commitment9       by Digital Equipment Corporation. Digital Equipment ?       Corporation assumes no responsibility for any errors that "       may appear in this document.  @       The software described in this document is furnished underA       a license and may be used or copied only in accordance with         the terms of such license.  =       No responsibility is assumed for the use or reliability >       of software on equipment that is not supplied by Digital8       Equipment Corporation or its affiliated companies.  ?       Restricted Rights: Use, duplication, or disclosure by the @       U.S. Government is subject to restrictions as set forth in>       subparagraph (c)(1)(ii)  of the Rights in Technical Data9       and Computer Software clause at DFARS 252.227-7013.   +        Digital Equipment Corporation 1993.          All Rights Reserved.  =       The postpaid Reader's Comments forms at the end of this <       document request your critical evaluation to assist in%       preparing future documentation.   7       The following are trademarks of Digital Equipment A       Corporation: AXP, DEC, DECmcc, Digital, DECnet, DECthreads, 9       DECwindows, OpenVMS, VAX, VAX C, VAX DOCUMENT, VMS, '       VMScluster, and the DIGITAL logo.   /       The following is a third-party trademark:   @       PostScript is a registered trademark of Adobe Systems Inc.  B                                                             ZK6363  +       This document is available on CD-ROM.   A       This document was prepared using VAX DOCUMENT, Version 2.1.                                  > ______________________________________________________________  ?                                                        Contents       ? ...................................................           v   !   Distributing Dependent Products   ?  1.1  Impact on Software Development and Distribution..     1-1 ?  1.1.1   Linking Against Older Versions ................    1-3 .  1.1.2   Redistributing the DEC C/C++ Run-Time?          Components Kit.................................    1-4 ?  1.1.3   Linking with Object Libraries .................    1-4 ?  1.2  Saving the Old System Development Environment....     1-5 ?  1.3  Notifying Site Users.............................     1-7 ?  1.4  Diagnosing the Distribution Problem..............     1-7 ?  1.5  Symptoms and Appropriate Responses...............     1-9 6  1.6  Requirements for Redistribution of the DEC C/C++?       Run-Time Components Kit .........................    1-10 5  1.7  Saving the DEC C/C++ Run-Time Components Kit to ?       Allow Redistribution.............................    1-11      Preparing for Installation  .  2.1  Required Operating System Components and?       Software.........................................     2-1 ?  2.2  Installation Procedure Requirements..............     2-2 ?  2.2.1   Process Privileges ............................    2-2 ?  2.2.2   Process Account Quotas ........................    2-2 ?  2.2.3   System Parameters .............................    2-3 ?  2.2.4   Disk Space ....................................    2-4 ?  2.2.5   Backing Up Your System Disk ...................    2-5             ?                                                             iii                    B     2.2.6   Additional System Maintenance Procedures ......    2-6B     2.2.6.1   Checking System Parameter Values............     2-69     2.2.6.2   Calculating the Values for Global Pages and B               Global Sections.............................     2-63     2.2.6.3   Changing System Parameter Values with B               AUTOGEN.....................................     2-7B     2.2.6.4   Setting Dynamic System Parameter Values.....     2-8  / 3  Installing the DEC C/C++ Run-Time Components   B     3.1  Installation Procedure...........................     3-1B     3.2  Error Recovery...................................    3-12   4  After Installation   8     4.1  Running the Installation Verification ProcedureB          Separately.......................................     4-1B     4.2  Editing the System Files.........................     4-2B     4.3  VMScluster Considerations........................     4-27     4.4  Reinstalling After an OpenVMS VAX Intermediate B          Upgrade..........................................     4-3B     4.5  Reporting Problems...............................     4-3   A  Sample Installation     Examples  0     A-1     Sample DEC C/C++ Run-Time ComponentsB             Installation on an OpenVMS VAX System..........    A-2   Tables  B     1       Conventions Used in this Guide ................     vi  B     1-1     New Image Names Not Previously Available ......    1-8  5     1-2     New Image Names and Identifiers Replacing B             Existing OpenVMS Versions......................    1-9  B     2-1     Process Quotas for the Installing Account .....    2-2  B     2-2     Minimum Required System Parameter Values ......    2-4  B     2-3     Disk Space Requirements .......................    2-5   iv                             E     _________________________________________________________________   E                                                               Preface       D           This guide describes how to install the DEC C/C++ Run-TimeD           Components on VAX processors running the OpenVMS operating5           system. It is intended for system managers.   C           Keep this guide with your distribution kit. You will need C           it to install maintenance updates or to reinstall the DEC =           C/C++ Run-Time Components kit for any other reason.   <           If you have any comments or suggestions concerningA           this guide, you may send them by electronic mail to the %           following Internet address:   )              cxx_docs@casdoc.enet.dec.com   @           If you have access to a FAX machine, you can also send%           comments or suggestions to:   "              DEC C++ Documentation              603-881-0120        Document Structure  =           This guide contains four chapters and one appendix:   @           o  Chapter 1 describes the preparations for supportingE              remote software development and distribution activities.   =           o  Chapter 2 describes how to prepare for DEC C/C++ <              Run-Time Components Version 6.0 for OpenVMS VAX              installation.  B           o  Chapter 3 describes how to install the DEC C/C++ Run-9              Time Components Version 6.0 for OpenVMS VAX.   =           o  Chapter 4 describes postinstallation procedures.   4           o  Appendix A shows a sample installation.  E                                                                     v                     Associated Documentation  :       For information on the DEC C/C++ Run-Time Components;       Version 6.0 for OpenVMS VAX online release notes, see        Chapter 2.  ?       For general information on OpenVMS VAX system management, 9       see the OpenVMS operating system documentation set.   ?       For help understanding OpenVMS VAX system error messages, =       see the OpenVMS System Messages and Recovery Procedures ;       Reference Manual or the online HELP/MESSAGE facility.   @       For additional information about DECthreads, see the Guide       to DECthreads.   Conventions Used in This Guide  7       Table 1 lists the conventions used in this guide.   A       Table_1__Conventions_Used_in_this_Guide____________________   A       Convention_____________Meaning_____________________________   >       UPPERCASE TEXT         Uppercase text indicates the nameA                              of a command, a file, a parameter, a 3                              procedure, or utility.   =       $                      In interactive examples, prompts ;       @SYS$UPDATE:VMSINSTAL  or displayed text appears in a ?                              monospace font. User input appears 4                              in bold monospace font.  @       Ctrl/x                 In interactive examples, a sequence>                              such as Ctrl/x indicates that you@                              must hold down the key labeled Ctrl=                              while you press another key or a A                              pointing device button; for example, .                              Ctrl/C or Ctrl/Z.  B                                           (continued on next page)         vi                   E           Table_1_(Cont.)_Conventions_Used_in_this_Guide_____________   E           Convention_____________Meaning_____________________________   B           [YES]                  Square brackets indicate that theD                                  enclosed item is a default value inA                                  a VMSINSTAL prompt. Also, square =                                  brackets serve as delimiters ?                                  for a directory name in a file E           _______________________specification.______________________                                                                       E                                                                   vii                          E                                                                     1 E     _________________________________________________________________   E                                       Distributing Dependent Products     A           This chapter discusses the preparations sites must make >           if they support software development or distribution           activities.   7     1.1 Impact on Software Development and Distribution   B           The DEC C/C++ Run-Time Components kit contains shareable@           image run-time components. When the DEC C/C++ Run-TimeA           Components kit is installed on OpenVMS VAX Version 5.5, C           5.5-1, or 5.5-2 systems, some of the shareable image run- D           time components replace older versions of existing OpenVMSB           components. This makes the installation of the DEC C/C++?           Run-Time Components kit similar to an OpenVMS upgrade C           for sites that develop or distribute software for OpenVMS C           VAX Version 5.5, 5.5-1, or 5.5-2 systems. Software linked B           against any of the run-time images provided by the DEC CB           /C++ Run-Time Components kit cannot be executed at sitesA           having older versions of the files in their SYS$LIBRARY A           directories or at sites that do not have the new images            available.  A           Specifically, when executing the image resulting from a D           software build procedure that links an application againstA           any of the new run-time components provided on this kit A           (see Table 1-1 and Table 1-2), a user at the installing E           site will encounter errors if that user subsequently copies E           the resulting image file to another site (target site) that A           is running OpenVMS VAX Version 5.5, 5.5-1, or 5.5-2 and C           does not have the new versions of the run-time components            in their SYS$LIBRARY.   @           For example, consider a software application, VAX APP-D           XYZ, which has been developed on a cluster named GRAPES::,A           that is running OpenVMS VAX Version 5.5. As part of the D           build of VAX APP-XYZ, an executable image named XYZ.EXE isD           linked against the VAX C Run-Time Library (RTL) executable  E                                   Distributing Dependent Products 1-1                    C           (SYS$LIBRARY:VAXCRTL.EXE). VAX APP-XYZ has been built and D           distributed to other OpenVMS VAX sites that have a versionA           of SYS$SYSTEM:VAXCRTL.EXE at least as recent as the one E           distributed with OpenVMS Version 5.5 and executes properly.   A           However, if the system manager for the GRAPES:: cluster =           installs the DEC C/C++ Run-Time Components kit, one A           component of the kit is a new version of VAXCRTL.EXE (a E           more recent version than the version that exists in OpenVMS ?           VAX Version 5.5-2). Installing the DEC C/C++ Run-Time B           Components kit places this newer version in SYS$LIBRARY.>           Subsequently, if the VAX APP-XYZ software developersA           execute their build procedure, the resulting version of C           XYZ.EXE will now depend on the new version of VAXCRTL.EXE A           rather than the old version. If an offsite client takes B           delivery of the new version of VAX APP-XYZ, users at theC           remote site will encounter image activation failure while D           trying to execute XYZ.EXE. The remote user's system issuesE           the following message indicating that the necessary version /           of SYS$LIBRARY:VAXCRTL.EXE is absent:              $ run xyz 9           %DCL-W-ACTIMAGE, error activating image VAXCRTL >           -CLI-E-IMGNAME, image file SYS$LIBRARY:VAXCRTL.EXE;1D           -SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image  <           This problem can arise when new components such as@           DECC$SHR.EXE (the DEC C Run-Time Library) or CXXL$011_D           SHR.EXE (the DEC C++ Class Library) are linked against. ItB           can also occur when existing components like VAXCRTL.EXEB           (as in this example) are used that have been replaced byD           newer versions from the DEC C/C++ Run-Time Components kit.D           Because the run-time components contained on the DEC C/C++B           Run-Time Components kit are in common use, such problemsB           can arise even for programs that do not use the DEC C or           DEC C++ compilers.  C             _______________________ Warning _______________________   =             Any application that links directly or indirectly ;             against a version of VAXCRTL.EXE, VAXCRTLG.EXE, >             CMA$RTL.EXE, CMA$OPEN_RTL.EXE, CMA$LIB_SHR.EXE, or=             CMA$OPEN_LIB_SHR.EXE is affected by this problem. ;             A linkage is indirect if a shareable image that   '     1-2 Distributing Dependent Products                    =             references any of these images is linked into the              application.  B             ______________________________________________________  A           For simplicity, the rest of this chapter refers to "DEC C           C/C++ Run-Time Components software distribution problems" %           as "distribution problems."   C           For software developers who want to redistribute software B           that is developed using systems where the DEC C/C++ Run-<           Time Components kit is installed, the options are:  @           o  Link against older versions of the shareable images  ?           o  Redistribute the DEC C/C++ Run-Time Components kitc  D           o  Link with object libraries rather than shareable images  8           The following sections describe these options.  (     1.1.1 Linking Against Older Versions  A           Sites that have existing build procedures (that support E           development and distribution of software linked against the B           installed version of OpenVMS VAX and want to continue toC           link against shareable images) must preserve the existing @           link environment to eliminate the distribution problemE           without having to modify application build procedures. This C           requires some preparation and notification on the part of.6           the DEC C/C++ Run-Time Components installer.  B           Before installing the DEC C/C++ Run-Time Components kit,D           make a copy of the files in the old SYS$LIBRARY directory.C           After installing DEC C/C++ Run-Time Components but before >           executing the standard link operations, applicationsB           that need to link with pre-DEC C/C++ Run-Time ComponentsC           versions of the shareable images can be supported without @           change by temporarily defining the appropriate logical@           name (either SYS$LIBRARY or SYS$SHARE) to point to the@           old SYS$LIBRARY. With this method, the end user of theB           application sees no change from the previous, unmodifiedE           use of SYS$LIBRARY. The temporary definition of SYS$LIBRARYy$           is not needed at run time.  E                                   Distributing Dependent Products 1-3t                   E           Whether or not the end-user site has the DEC C/C++ Run-TimefE           Components installed does not matter if this method is useddE           to build the application. See Section 1.2 for more detailed >           instructions on preparing for and using this method.  <           This method does not work for new components (such=           as DECC$SHR.EXE or CXXL$011_SHR.EXE) not previouslye>           supplied on OpenVMS VAX Version 5.5, 5.5-1, or 5.5-2C           systems. You can only use these new components with newly A           developed applications. Applications that encounter thee@           distribution problem from the use of new components on>           the DEC C/C++ Run-Time Components kit can only solveB           the distribution problem by redistributing the DEC C/C++A           Run-Time Components kit itself. See Section 1.6 for theiE           requirements and setup needed for redistribution of the DEC (           C/C++ Run-Time Components kit.  >     1.1.2 Redistributing the DEC C/C++ Run-Time Components Kit  >           Redistributing the DEC C/C++ Run-Time Components kit@           requires minimal changes to the development system andB           procedures. It does not sacrifice performance or degrade>           system resources. It does require that the DEC C/C++A           Run-Time Components kit and this guide be shipped alongiB           with the application that requires the use of any of the%           components contained in it._  C           When new applications involving new components of the DEC D           C/C++ Run-Time Components kit, or new features of existingA           components, are used and object library usage is either B           impossible or undesirable, then the distribution problemD           can only be addressed by supplying the necessary shareable(           images to the end-user system.  C           See Section 1.6 for the requirements and setup needed fornB           redistribution of the DEC C/C++ Run-Time Components kit.  '     1.1.3 Linking with Object Libraries   D           Linking with object libraries rather than shareable imagesB           eliminates the problem at end-user sites, but slows downE           the image activation process and consumes system resources.       '     1-4 Distributing Dependent Products+                   D           When an OpenVMS VAX image is linked using object librariesB           instead of shareable images, all the code and local dataD           for the application are linked directly into the resultingD           .EXE file (image). This makes the image independent of anyD           shareable images on the linking system; therefore, you canC           ship the resulting image to any end-user site without the.D           distribution problem occurring. Because the image includesD           all the necessary run-time code and data needed to executeC           the program, the image is larger than if shareable images.           were used.  B           You can link some (but not all) of the components on theB           DEC C/C++ Run-Time Components kit with object libraries.D           Specifically, the VAX C RTL is available in object libraryD           form (VAXCRTL.OLB, VAXCRTLG.OLB, VAXCCURSE.OLB), as is theC           DEC C RTL (DECCRTL.OLB, DECCRTLG.OLB, DECCCURSE.OLB). TheaC           other components on the DEC C/C++ Run-Time Components kit E           are available in shareable image form only. For information B           on linking with object libraries, see the OpenVMS LinkerC           Utility Manual and the user's guides for VAX C and DEC C.l  5     1.2 Saving the Old System Development Environmentl  A           As discussed in Section 1.1.1, one method of addressingcD           the distribution problem is to save a copy of the existingD           link-time environment before installing the DEC C/C++ Run-D           Time Components kit. Software development and distributionD           sites often do this before upgrading OpenVMS VAX versions.>           This approach is simple, but does require sufficient?           additional disk space to hold the old files, and doesgB           require monitoring and deletion when the old environment            is no longer required.  A           To save the old environment, find an alternative device-E           and directory for the files. The alternative directory need B           not be on the system device. To determine the disk spaceD           required to store the old SYS$LIBRARY, enter the following           command:  6           $ DIRECTORY/SIZE=ALL/TOTAL SYS$LIBRARY:*.*;0  B           Saving the existing environment to an alternative deviceE           is simple if sufficient disk space is available to hold allaB           these files. For example, if the new directory is calledE           DISK_D:[ALTSYSLIB], enter the following command to save the.           old environment:  E                                   Distributing Dependent Products 1-5_ _  _              9           $ COPY/LOG SYS$LIBRARY:*.*;0 DISK_D:[ALTSYSLIB]   D           To link against pre-DEC C/C++ Run-Time Components versionsC           of the files in this saved environment, application buildsE           procedures only need to enter one of the following commandssB           immediately before the appropriate LINK commands. If theE           LINK command uses SYS$LIBRARY, enter the following command:e  6           $ DEFINE/USER SYS$LIBRARY DISK_D:[ALTSYSLIB]  A           If the LINK command uses SYS$SHARE, enter the followings           command:  4           $ DEFINE/USER SYS$SHARE DISK_D:[ALTSYSLIB]  B           If disk space is limited, you can store only those filesB           replaced by the DEC C/C++ Run-Time Components kit. DoingC           this only requires about 1000 blocks but requires using a C           slightly more complicated logical name assignment at linkoA           time. To use the limited file storage method, enter the @           following COPY command before installing the DEC C/C++"           Run-Time Components kit:  G           $ COPY/LOG SYS$LIBRARY:CMA$LIB_SHR.EXE,CMA$OPEN_LIB_SHR.EXE,-rL           CMA$OPEN_RTL.EXE,CMA$RTL.EXE,SMGSHR.EXE,VAXCRTL.EXE,VAXCRTLG.EXE -           DISK_D:[ALTSYSLIB]  D           This command does not place all the necessary files needed@           for linking applications in the alternative directory;D           therefore, you need a more complex logical name definitionB           to link applications with these older files. If the LINK@           command uses SYS$LIBRARY, enter the following command:  K           $ DEFINE/USER SYS$LIBRARY DISK_D:[ALTSYSLIB],SYS$SYSROOT:[SYSLIB]o  A           If the LINK command uses SYS$SHARE, enter the following            command:  I           $ DEFINE/USER SYS$SHARE DISK_D:[ALTSYSLIB],SYS$SYSROOT:[SYSLIB]s  C           This command ensures that the linker searches for all thenB           components needed for the linking applications, first inE           the alternate directory and then in the standard directory. =           If your site has previously moved SYS$LIBRARY to an D           alternative disk, make sure you use that directory instead"           of SYS$SYSROOT:[SYSLIB].  '     1-6 Distributing Dependent Productso n  n                   1.3 Notifying Site Users  B           Before you can proceed to install the DEC C/C++ Run-Time&           Components kit, you need to:  C           o  Perform the setup required to support the distributionaB              of dependent products, including saving the DEC C/C++@              Run-Time Components save set and documentation (see              Section 1.6).  B           o  Store the old SYS$LIBRARY in an alternative directory              (see Section 1.2).   @           After the installation, notify all site users that theD           DEC C/C++ Run-Time Components kit has been installed. WarnD           users that if they are building applications for executionC           on other OpenVMS VAX Version 5.5, 5.5-1, or 5.5-2 systemsdA           they may encounter the distribution problem. Notify thep           users of the:   @           o  Location of the saved DEC C/C++ Run-Time ComponentsB              kit save set, this reference and installation manual,=              the read before installing cover letter, and the D              online release notes files provided by the installation              procedure.   D           o  Location of the alternate SYS$LIBRARY directory and theE              DEFINE command needed to use the components it contains.   D           In your application's release notes, refer to Chapter 1 ofE           this guide so that software developers can take appropriate D           action to avoid causing problems for end users who execute           on remote sites.  +     1.4 Diagnosing the Distribution Problem_  A           If a software build procedure has been executed and the C           application image generated without any record (such as a E           .MAP file) of how it was linked, you can still determine if C           the image will encounter problems when the image executes B           at a remote site. Enter a single DCL command and consult>           Table 1-1 and Table 1-2. Using this method, softwareD           distributors can ensure that any applications they send toD           their user sites are free of DEC C/C++ Run-Time Components            distribution problems.  E                                   Distributing Dependent Products 1-7  h  E              @           To determine if an OpenVMS VAX executable or shareable=           image will have the distribution problem, enter thei           following command:  <           $ ANALYZE/IMAGE/OUTPUT=file-spec.ANL file-spec.EXE  @           file-spec is the file specification of the image to beB           examined. Examine the .ANL file with the TYPE command or@           an editor. At the end of the IMAGE HEADER section, youE           will see a series of image section descriptors (ISDs). EachwA           ISD describes an image section. Image sections can comesD           from object files, or shareable images that have been used"           during the LINK process.  @           Distinguishing such cases is easy: Image sections thatB           come from shareable images appear at the end and containA           additional information such as the global section name,l?           match control, and the global section major and minorfE           identifiers. By examining the list of global section names,a@           and the identifiers, and comparing them with Table 1-1D           and Table 1-2, you can determine which, if any, of the kit@           components have been referenced by the link operation.  ?           Table 1-1 lists the new DEC C/C++ Run-Time ComponentsgA           that have not appeared on any OpenVMS VAX system before,B           Version 6.0. If any of these global section names appear=           in the ISD list, then that image will encounter the E           distribution problem when executed at a remote site withoutw:           the DEC C/C++ Run-Time Components kit installed.  E           Table_1-1_New_Image_Names_Not_Previously_Available_________u  "                              MajorE           Image_Name_________Identifier____Minor_Identifier__________   ,           CMA$TIS_SHR        1             1  ,           CXXL$011_SHR_      1             1           nnn[1]  ,           DECC$SHR           2             0E           [1]nnn_is_a_version_number,_such_as_001.___________________t  E           ___________________________________________________________t  ?           Table 1-2 lists the new DEC C/C++ Run-Time Componentse>           that replace existing OpenVMS Version 5.5, 5.5-1, orA           5.5-2 shareable images and have their minor identifierso  '     1-8 Distributing Dependent Productst k  i              ?           incremented. The major and minor identifiers are alsoi?           listed. By comparing the names and identifiers in theiC           .ANL file with those in Table 1-2, you can tell if any ofrC           the new versions were referenced. If there is no match insA           either table, then the image will not encounter startups?           problems due to the DEC C/C++ Run-Time Components kitv           distribution problem.   =           Table 1-2 New Image Names and Identifiers Replacing E           __________Existing_OpenVMS_Versions________________________e  "                              MajorE           Image_Name_________Identifier____Minor_Identifier__________r  ,           VAXCRTL            4             5  E           VAXCRTLG___________4_____________5_________________________L  *     1.5 Symptoms and Appropriate Responses  @           If software developers on your system provide a targetB           site with an image file (.EXE) linked against one of theD           kit components listed in Table 1-1 and Table 1-2, and thatE           target site does not have the DEC C/C++ Run-Time Components(E           kit installed, the image file will fail to activate. One of+1           the following remedies must be applied:a  D           1. Another version of the image file must be supplied thatE              does not reference any of the kit component image files.s  D           2. The DEC C/C++ Run-Time Components kit must be supplied,<              which makes the necessary components available.  A           The following messages indicate a distribution problem:r             $ run xyzh9           %DCL-W-ACTIMAGE, error activating image VAXCRTL F           -CLI-E-IMGNAME, image file SYS$SYSROOT:[SYSLIB]VAXCRTL.EXE;1D           -SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image  ;           VAXCRTL is one of the images listed in Table 1-2.              $ run xyzE=           %DCL-W-ACTIMAGE, error activating image CMA$TIS_SHRET           -CLI-E-IMAGEFNF, image file not found SYS$SYSROOT:[SYSLIB]CMA$TIS_SHR.EXE;  ?           CMA$TIS_SHR is one of the images listed in Table 1-1.   E                                   Distributing Dependent Products 1-9                    D           The site supplying the application VAX APP-XYZ is requiredA           to provide at least one of the two remedies. If the DEC B           C/C++ Run-Time Components kit has been installed without?           providing an alternative version of SYS$LIBRARY, thena=           remedy 1 cannot be used. To use remedy 1, the oldert?           versions of the required files in SYS$LIBRARY must bei<           recovered from a backup of your system device that@           was performed before installing the DEC C/C++ Run-Time           Components kit./  ;           If the DEC C/C++ Run-Time Components save set andi?           documentation has not been saved on your system, theneD           remedy 2 cannot be used. In this case, the original sourceC           for the DEC C/C++ Run-Time Components kit will need to bepB           found. If you received the DEC C/C++ Run-Time ComponentsE           kit with a Digital layered product, you will need to obtainuA           the necessary save set and documentation from the mediaiA           for that layered product. If you received the DEC C/C++oB           Run-Time Components kit from another supplier other than8           Digital, you will need to obtain it from them.  A     1.6 Requirements for Redistribution of the DEC C/C++ Run-Timet         Components Kit  D           The DEC C/C++ Run-Time Components kit may be redistributed=           along with any application that requires any of thefD           components that are contained in it. For more information,@           see the DEC C/C++ Run-Time Components Software Product           Description (SPD).  B             ________________________ Note ________________________  9             The DEC C/C++ Run-Time Components kit and thei=             components contained within it are supported onlyo?             when the entire kit is redistributed to an end-users@             target site. Digital does not support redistribution:             of individual components contained in the kit.  B             ______________________________________________________  D           To redistribute the DEC C/C++ Run-Time Components kit, youE           must supply the items listed in Section 1.7 to the end-usere           target site.    (     1-10 Distributing Dependent Products o  a              =     1.7 Saving the DEC C/C++ Run-Time Components Kit to Allow          Redistribution  B           Digital has engineered the DEC C/C++ Run-Time Components=           kit specifically to allow redistribution with user- !           developed applications..  >           To facilitate redistribution, the DEC C/C++ Run-TimeC           Components kit installer should ensure that copies of thep$           following items are saved:  C           o  A printed or binary copy of the read before installingnD              cover letter for the DEC C/C++ Run-Time Components kit.  <              The installation procedure puts the read beforeA              installing cover letter into the SYS$HELP directory.eB              The name of the PostScript file is CRT060_RBI.PS; the5              name of the text file is CRT060_RBI.TXT.                                                       E                                  Distributing Dependent Products 1-11t D  C              :           o  A printed or binary copy of the reference andE              installation guide for the DEC C/C++ Run-Time Componentsr              kit.   >              The installation procedure puts the reference and@              installation guide into the SYS$HELP directory. TheC              name of the PostScript file is CRT060_REF_INST.PS; the :              name of the text file is CRT060_REF_INST.TXT.  E           o  The complete DEC C/C++ Run-Time Components kit save set,C              AACRT060.A.  A           Save these items immediately after installing the DEC CsA           /C++ Run-Time Components kit. These items can either beiC           saved online for easy access or on a separate medium thatsB           is available and appropriately labeled. You can copy theC           binary items from the media they are provided on with the %           DCL command COPY or BACKUP.i  >           If you do not save the DEC C/C++ Run-Time ComponentsA           kit save set, it cannot be reconstituted later from thes           installed components.m                                              (     1-12 Distributing Dependent Products t  r                    E                                                                     2 E     _________________________________________________________________n  E                                            Preparing for Installation     @           Your bill of materials (BOM) and indented bills report>           (BIL) specify the number and contents of your media.>           Be sure to verify the contents of your kit with this<           information. If your kit is damaged or if you find<           that parts of it are missing, contact your Digital           representative.   C           DEC C/C++ Run-Time Components Version 6.0 for OpenVMS VAXa@           provides online release notes, which are copied to theE           following files during installation (n is the minor releaset           number):  '           SYS$HELP:CRT06n.RELEASE_NOTESr*           SYS$HELP:CRT06n_RELEASE_NOTES.PS1           SYS$HELP:CRT06n_RELEASE_NOTES.DECW$BOOKA  E           Digital strongly recommends that you read the release notesDB           before proceeding with the installation. For information>           on accessing the online release notes, see step 5 in           Section 3.1.  9     2.1 Required Operating System Components and Softwareb  C           DEC C/C++ Run-Time Components Version 6.0 for OpenVMS VAXeB           requires the OpenVMS VAX operating system Version 5.5 orB           higher. Future DEC C/C++ Run-Time Components Version 6.0E           for OpenVMS VAX releases may require higher versions of thesE           operating system, as described in the online release notes.a  B           The OpenVMS VAX operating system comes with a variety of@           support options or components. Components include suchA           features as networking and RMS journaling. To use DEC CtD           /C++ Run-Time Components Version 6.0 for OpenVMS VAX, your@           system should be running a version of OpenVMS VAX that8           includes the base component and the following:              o  Programming support  E                                        Preparing for Installation 2-1T a  r                         o  Utilities  A           The run-time component kit supplies versions of severalr?           OpenVMS VAX component files that are more recent thano?           versions supplied as part of the OpenVMS VAX upgrades A           for Version 5.5 through Version 5.5-2. After installinge=           this kit, if you then upgrade your system to one ofhA           these intermediate versions, you will have to reinstalliA           the component kit. Otherwise, applications that use new A           features of these components may fail to work properly.   +     2.2 Installation Procedure Requirements   E           This section discusses the settings to check to ensure thatYD           your system is ready for the installation of the DEC C/C++)           Run-Time Components to proceed.v       2.2.1 Process Privileges  C           To install the DEC C/C++ Run-Time Components, you must bedA           logged in to an account that has SETPRV or at least thet           following privileges:Y             o  CMKRNLl             o  WORLD             o  SYSPRVY  C           VMSINSTAL turns off BYPASS privileges at the start of theS           installation.s        2.2.2 Process Account Quotas  ?           VMSINSTAL requires that the installation account have 0           minimum quotas, as shown in Table 2-1.  E           Table_2-1_Process_Quotas_for_the_Installing_Account________h             ASTLM     1000             BIOLM     1000             BYTLM     99,000             DIOLM     1000  E                                              (continued on next page)e  "     2-2 Preparing for Installation b  r              E           Table_2-1_(Cont.)_Process_Quotas_for_the_Installing_AccountG             ENQLM     4000  E           FILLM_____300______________________________________________X  @           Use the OpenVMS Authorize Utility to verify and changeA           process quotas for the installation account in the user @           authorization file (UAF). (Some sites may restrict theB           use of the OpenVMS Authorize Utility to certain accountsA           or people.) For instance, to change the BYTLM quota for D           the account-name installation account, you might enter the%           following command sequence:[  $           $ RUN SYS$SYSTEM:AUTHORIZE1           UAF> MODIFY account-name /BYTLM = 99000             UAF> SHOW account-name           UAF> EXITE           $ LOGOUT  A           After the quotas for the installation account have beenaA           changed, log out of the installation account and log in ?           again for the new quotas to take effect. You can thent(           proceed with the installation.  @           User account quotas are stored in the file SYSUAF.DAT.C           For more information on modifying account quotas, see the D           description of the Authorize Utility in the OpenVMS System           Management Subkit.       2.2.3 System Parameters   ?           Table 2-2 lists the minimum required system parameter @           values for the installation. Depending on the kinds ofC           programs and applications running at your site, you might /           need higher values for some settings.                   E                                        Preparing for Installation 2-3                    E           Table_2-2_Minimum_Required_System_Parameter_Values_________.  #                             MinimumnE           System_Parameter__Value________Dynamic_Value_______________t  E           OpenVMS_VAX_Version_6.0____________________________________   ,           CLISYMTBL[1]      500          500  ,           GBLPAGES[2]       200          200  ,           GBLPAGFIL         200          200  +           Global            10           10            Sections[2]   E           ___________________________________________________________iE           OpenVMS_VAX_Versions_5.5,_5.5-1,_and_5.5-2_________________a  ,           CLISYMTBL[1]      500          500  -           GBLPAGES[2]       1500         1500n  -           GBLPAGFIL         1500         1500o  +           Global            33           33e           Sections[2]oE           [1]The_CLISYMTBL_dynamic_system_parameter_must_be_set_to___p  C           a minimum value of 500 during the installation procedure.sD           You can change the setting to its original value after the#           installation is finished.wC           [2]These values represent the number of free global pagesr@           and global sections required for the installation, not@           the total number you need to run your system and other           software. E           ___________________________________________________________i       2.2.4 Disk Space  C           The DEC C/C++ Run-Time Components Version 6.0 for OpenVMS D           VAX requirements for free disk storage space are different?           during installation and after installation. Table 2-3n.           summarizes the storage requirements.  "     2-4 Preparing for Installation C  R              E           Table_2-3_Disk_Space_Requirements__________________________   =                              Blocks During       Blocks After E           Kit________________Installation________Installation________   E           OpenVMS_VAX_Version_6.0____________________________________n  5           DEC C/C++ Run-     13,000              2000A           Time Components            Version 6.0 forc           OpenVMS VAXt  3           Installation       150                 50e           Verification           Procedures  E           ___________________________________________________________eE           OpenVMS_VAX_Versions_5.5,_5.5-1,_and_5.5-2_________________c  5           DEC C/C++ Run-     17,000              6000e           Time Components            Version 6.0 foru           OpenVMS VAX   3           Installation       150                 50c           VerificationE           Procedures_________________________________________________i  D           To determine the number of free disk blocks on the currentE           system disk, enter the following command at the DCL prompt:   %           $ SHOW DEVICE SYS$SYSDEVICEs  %     2.2.5 Backing Up Your System Diskm  A           At the beginning of the installation, VMSINSTAL asks ifeA           you have backed up your system disk. Digital recommendseA           that you back up your system disk before installing any/           software.t  @           Use the backup procedures that are established at yourC           site. For details on performing a system disk backup, seerA           the section on the Backup Utility in the OpenVMS System            Management Subkit.  E                                        Preparing for Installation 2-5C o  t              2     2.2.6 Additional System Maintenance Procedures  5           This section explains how to use the SystemM=           Generation Utility (SYSGEN) and the AUTOGEN Utilitye;           to prepare your system for an installation of the <           DEC C/C++ Run-Time Components. AUTOGEN uses systemD           configuration data to automatically set system parameters.  ,     2.2.6.1 Checking System Parameter Values  B           To check the values of your system parameters, enter the           following command:  !           $ RUN SYS$SYSTEM:SYSGENm           SYSGEN>   B           At the SYSGEN> prompt, enter the SHOW command to display@           the value of a system parameter. The following example@           displays the value for the CLISYMTBL system parameter:              SYSGEN> SHOW CLISYMTBL  D           After checking the parameters with the SHOW command, enterA           the EXIT command at the SYSGEN> prompt to return to DCL D           level. For information on setting dynamic system parameter&           values, see Section 2.2.6.4.  >     2.2.6.2 Calculating the Values for Global Pages and Global             Sections  B           To install and run DEC C/C++ Run-Time Components VersionC           6.0 for OpenVMS VAX, you must have sufficient free globalxE           pages and global sections. You must first find out how many A           free global pages and sections you have on your system.eC           Then use AUTOGEN if you need to increase the global pages 0           and global sections system parameters.  D           Enter the following DCL command to determine the number of=           global pages required by SYS$LIBRARY:DCLTABLES.EXE:   .           $ DIR/SIZE SYS$LIBRARY:DCLTABLES.EXE  6           This command returns the size (in blocks) ofB           SYS$LIBRARY:DCLTABLES.EXE. As an approximation, use this<           figure as the number of global pages for the file.  A           You can use the WRITE command with the F$GETSYI lexicaleE           function to find the number of free global pages and globali?           sections. The following example shows how to get thistD           information at your terminal (the default for SYS$OUTPUT):  "     2-6 Preparing for Installation                   8           $ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES")           15848c6           $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")           24  D           If the values displayed by the system are greater than theE           values in Table 2-2, you do not need to increase the valuesSD           for these parameters. If the value of free global pages orB           global sections is less than the value in Table 2-2, you5           must increase the system parameter setting.   A           Section 2.2.6.3 describes the procedures for increasingM%           these values using AUTOGEN.   9     2.2.6.3 Changing System Parameter Values with AUTOGEN   <           Use the AUTOGEN command procedure to change system>           parameters. AUTOGEN automatically adjusts values forB           parameters that are associated with the values you resetB           manually. To change system parameters with AUTOGEN, edit           the following file:r  "           SYS$SYSTEM:MODPARAMS.DAT  A           Use an editor to access the file. To change a parameterh=           value listed in this file, delete the current valueRA           associated with that parameter and enter the new value.   =           To add a new parameter, add a line to the file that-@           includes both the name of the parameter and its value.           For example:             WSMAX = 8096  D           To modify incremental parameters such as free global pagesE           and global sections, prefix GBLPAGES and GBLSECTS with ADD_+C           . The following example increases the global page settinge           by 2000:             ADD_GBLPAGES = 2000i  C           When you set the page file quota, do not use a value thath@           exceeds the amount of page file space available on the           system.o  C           After you make all your changes, exit from the editor and B           execute the AUTOGEN procedure to recalculate your systemD           parameters. The following command recalculates your system,           parameters and reboots the system:  E                                        Preparing for Installation 2-7                    .           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT  @           When you specify REBOOT, AUTOGEN performs an automatic@           system shutdown and then reboots the system. Any usersE           logged on to the system are immediately disconnected during_C           the shutdown. The automatic reboot puts the new parametert           values into effect.p  E           AUTOGEN automatically adjusts some of the SYSGEN parametersr>           based on the consumption of resources since the last>           reboot. If you do not want to take advantage of thisA           automatic adjustment, include the /NOFEEDBACK qualifier_&           on the AUTOGEN command line.  B           For more information about using AUTOGEN, see the system=           management documentation for your operating system.e  3     2.2.6.4 Setting Dynamic System Parameter Valuest  B           Use SYSGEN to set dynamic parameters. Dynamic parameters=           changed with the SYSGEN command WRITE ACTIVE become D           active immediately without any need to reboot your system.D           Rebooting returns dynamic system parameter values to their           previous settings.  A           After you change dynamic parameter values, complete the D           installation before rebooting the system. After you finishC           the installation, you can reset the dynamic parameters tocB           their previous values or let them be reset automatically4           when you reboot your system the next time.  A           If the dynamic parameter values on your system are lessnE           than the values previously listed, use the following seriestD           of commands to change the values. This example changes the!           CLISYMTBL value to 500.   !           $ RUN SYS$SYSTEM:SYSGEN            SYSGEN> USE ACTIVE#           SYSGEN> SET CLISYMTBL 500d           SYSGEN> WRITE ACTIVE           SYSGEN> EXIT        "     2-8 Preparing for Installation    i                    E                                                                     3 E     _________________________________________________________________l  D                         Installing the DEC C/C++ Run-Time Components    ?           The installation takes approximately 3 to 10 minutes,t<           depending on your system configuration and the kit           components chosen.       3.1 Installation Procedure  C           The DEC C/C++ Run-Time Components Version 6.0 for OpenVMSE<           VAX installation procedure consists of a series ofB           questions and informational messages. See Appendix A for            a sample installation.  @           To abort the installation procedure at any time, pressC           Ctrl/Y. When you press Ctrl/Y, the installation procedurenC           deletes all the files it has created up to that point andT;           exits. You can then start the installation again.t  @           When the system prompts you with a question during theD           installation procedure, the default answer is often listed           in brackets ([]).   @           1. Log in to a privileged account and set your default0              device and directory to SYS$UPDATE.                 Username: SYSTEM               Password:              2. Invoke VMSINSTAL.  C              @SYS$UPDATE:VMSINSTAL saveset-name device-name option-      list  D              To start the installation, invoke the VMSINSTAL commandD              procedure from a privileged account, such as the SYSTEMC              account. VMSINSTAL is in the SYS$UPDATE directory. The D              elements that you specify when you invoke the VMSINSTAL.              command procedure are as follows:  E                     Installing the DEC C/C++ Run-Time Components  3-1p    t                            saveset-nameaC              The installation name for the component. For DEC C/C++$E              Run-Time Components Version 6.0 for OpenVMS VAX, use the )              following installation name:W                AACRT06na  B              n represents the minor (point) release number for DECC              C/C++ Run-Time Components Version 6.0 for OpenVMS VAX.c                device-nameB              The name of the device on which you plan to mount theB              media and the directory containing the DEC C/C++ Run-B              Time Components Version 6.0 for OpenVMS VAX save set.C              For example, DSK$: is the device name used in examplesCB              in this guide. The directory used in examples in thisD              guide is [CRT06n], where n is the minor release number.A              The actual directory name may differ because the DECMC              C/C++ Run-Time Components may be included with anotheriE              product's save set. If this is the case, for the correctr@              directory specification, see the installation guideA              for the product that includes the DEC C/C++ Run-Time !              Components save set.   A              To specify the device name on the @VMSINSTAL command               line, enter:t                DSK$:[CRT06n]                option-list<              The word OPTIONS followed by one or more of the8              following option designators-A, G, L, N, R:  &              o  Auto_answer option (A)  C                 Initially creates a file that contains your answersrD                 to VMSINSTAL questions and prompts. You can then useD                 the option (and the answer file) to save time during@                 a reinstallation (typically after upgrading your                 system).  '              o  Get save-set option (G)l  A                 Lets you store product save sets temporarily on ai5                 magnetic tape or in a disk directory.R  #              o  File log option (L)d  4     3-2 Installing the DEC C/C++ Run-Time Components o  s              8                 Logs all activity to the terminal during                 installation.                                                                                       E                     Installing the DEC C/C++ Run-Time Components  3-3s h                 6              o  Display or print the release notes (N)  ?                 Indicates that you want to see the installationY@                 question on release notes. If you do not include>                 the N option, VMSINSTAL does not ask you about@                 the release notes. You should review the release@                 notes before proceeding with the installation inB                 case they contain additional information about the                 installation.Y  ?                 If you are restarting the installation and have >                 already reviewed the release notes, you do not?                 need to specify the N option. (Even if you omit_A                 the N option when you invoke VMSINSTAL, the DEC CL@                 /C++ Run-Time Components Version 6.0 for OpenVMSA                 VAX release notes are copied automatically to theo$                 SYS$HELP directory.)  )              o  Alternate root option (R)e  C                 Lets you install the product to a system root other 0                 than that of the running system.  D              For detailed information on these software installation:              options, see the OpenVMS VAX operating system@              documentation. If you specify more than one option,C              separate the options with commas, such as OPTIONS A,N.e  C              The following example invokes VMSINSTAL to install DECEB              C/C++ Run-Time Components Version 6.0 for OpenVMS VAXA              and shows the system response. This example uses thei+              OPTIONS N release note option.h  E              $ @SYS$UPDATE:VMSINSTAL AACRT06n DSK$:[CRT06n] OPTIONS Ns  K                    OpenVMS VAX Software Product Installation Procedure V5.5   (              It is dd-mmm-yyyy at hh:mm.<              Enter a question mark (?) at any time for help.  C              The following example invokes VMSINSTAL to install DEC.B              C/C++ Run-Time Components Version 6.0 for OpenVMS VAXA              from tape drive MTA0: and shows the system response.nD              This example uses the OPTIONS N release note parameter.  4     3-4 Installing the DEC C/C++ Run-Time Components    t              =              $ @SYS$UPDATE:VMSINSTAL AACRT06n MTA0: OPTIONS Nr  K                    OpenVMS VAX Software Product Installation Procedure V5.5S  (              It is dd-mmm-yyyy at hh:mm.<              Enter a question mark (?) at any time for help.  @              If you do not supply either the product name or theD              device name, VMSINSTAL prompts you for this information@              later in the installation procedure. VMSINSTAL doesB              not prompt you for any options, so be sure to includeB              OPTIONS N on the VMSINSTAL command line to access the3              release notes during the installation._  @              When you invoke VMSINSTAL, it checks the following:  B              o  Whether you are logged in to a privileged account.E                 Digital recommends that you install software from the E                 system manager's account with your default device and ,                 directory set to SYS$UPDATE.  B              o  Whether you have adequate quotas for installation.>                 VMSINSTAL checks for the quota values shown in                 Table 2-1.  A              VMSINSTAL then checks to determine whether any users =              are logged in to the system. If users are logged @              in, VMSINSTAL asks whether you want to continue the              installation:  8              * Do you want to continue anyway [NO]?  YES  D              If you want to continue, enter YES. If you want to stop,              the installation, press Return.  #           3. Confirm system backup.   K              * Are you satisfied with the backup of your system disk [YES]?   @              If you are satisfied with the backup of your systemC              disk, press Return. Otherwise, enter NO to discontinue B              the installation. After you back up your system disk,.              you can restart the installation.  D              If you omitted the device name on the VMSINSTAL command0              line, the following prompt appears:  >              * Where will the distribution volumes be mounted:              DSK$:[CRT06n]  E                     Installing the DEC C/C++ Run-Time Components  3-5                    :              If this prompt appears, enter the name of theD              distribution (media) device and directory that contains>              the DEC C/C++ Run-Time Components Version 6.0 forB              OpenVMS VAX kit (save set). For example, if the mediaB              is contained on a CD-ROM located on unit DSK$:, enterD              DSK$:[CRT06n] in reply to this question (where n is the#              minor version number).i  B              You should now mount the first distribution volume onA              the device you specified when you invoked VMSINSTAL.   C              Depending on the type of device and whether the device D              is already mounted, the following prompt may or may not              appear:  ?              Please mount the first volume of the set on DSK$:. !              * Are you ready? YESn-              %MOUNT-I-MOUNTED, DSK$:  mounted   E              If you have not already done so, insert the distribution @              volume on the device you specified when you invokedE              VMSINSTAL. The device name appears in the line precedingiB              the question. VMSINSTAL then asks if you are ready to,              continue with the installation.  ?              If you respond YES to indicate that you are ready, C              VMSINSTAL displays a message that the media containing B              DEC C/C++ Run-Time Components Version 6.0 for OpenVMSB              VAX has been mounted on the specified device and that(              the installation has begun.  B              If you entered the wrong device name when you invokedE              VMSINSTAL and need to restart the installation, enter NOoE              in response to the Are you ready? question. To abort theS:              installation for other reasons, press Ctrl/Y.  0           4. Verify the product being installed.  7               The following products will be processed:                    AACRT V6.n  @                   Beginning installation of AACRT V6.n  at hh:mm  E                 %VMSINSTAL-I-RESTORE, Restoring product save set A...l  B              The product name and version are displayed. This saveC              set (A)  is restored to a subdirectory of SYS$UPDATE:.,  4     3-6 Installing the DEC C/C++ Run-Time Components    u              +           5. Select a release notes option.a  #              Release Notes Options:   '               1.  Display release notest%               2.  Print release notesb               3.  Both 1 and 20               4.  Copy release notes to SYS$HELP  !              * Select option [2]:M  C              If you specified OPTIONS N when you invoked VMSINSTAL,l?              you are now asked to choose one of the options fora>              reviewing the release notes. All options copy the'              release notes to SYS$HELP.o  C              If you select option 1, VMSINSTAL displays the release ?              notes immediately on the console terminal. You can B              terminate the display at any time by pressing Ctrl/C.  B              If you select option 2, VMSINSTAL prompts you for theA              name of the print queue that you want to use. EitherAD              supply the name of the print queue that you want to useC              or press Return to send the file to the default outputt'              print device. For example:t  4              * Queue name [SYS$PRINT]: CLUSTER_PRINT  C              If you select option 3, VMSINSTAL displays the release ?              notes immediately on the console terminal and then B              prompts you for a queue name for the printed version.  D              If you select option 4, the installation procedure willC              only copy the release notes to the SYS$HELP directory.   <              Next, VMSINSTAL displays the following message:  X              %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  P                       DEC C/C++ Run-Time Components V6.n for OpenVMS VAX Systems  W                Copyright (c) Digital Equipment Corporation, 1993.  All rights reserved.   C              The release notes are copied to the following files in A              the SYS$HELP directory (where n is the minor versiona              number):E  E                     Installing the DEC C/C++ Run-Time Components  3-7     a              *              SYS$HELP:CRT06n.RELEASE_NOTES-              SYS$HELP:CRT06n_RELEASE_NOTES.PSs4              SYS$HELP:CRT06n_RELEASE_NOTES.DECW$BOOK  B             ________________________ Note ________________________  <             The name of the release notes file (installed by?             VMSINSTAL) consists of the current product name andl             version number.   B             ______________________________________________________  9           6. Heed warning message about image dependency.-  B              The installation procedure now displays the following              message:   W                  This kit  provides  new  versions  of  several  OpenVMS  VAX  standardgW                  shareable   images  and  object  libraries  in  SYS$LIBRARY,  such  ashW                  VAXCRTL.EXE,  CMA$RTL.EXE, and  SMGSHR.EXE.  These provide support forDW                  several programming  capabilities provided by  OpenVMS VAX Version 6.0h1                  for C, C++, and other languages.v  W                  **********************************************************************tW                  *                          W A R N I N G                             * W                  **********************************************************************r  W                  Programs  that link  against the new  versions of any of  these files, W                  EVEN THOSE NOT WRITTEN IN DEC C OR C++, will NOT run on older versionsyW                  of OpenVMS (V5.5-2 or earlier)  unless steps are taken to save the oldoX                  SYS$LIBRARY configuration or redistribute this kit to additional sites.S                  See Chapter 1 of the DEC C/C++ Run-Time Components for OpenVMS VAX C                  Reference and Installation Guide for more details.e  W                  In  addition,  if you  update the system  version of  OpenVMS VAX, the V                  enhanced  versions of the new images and libraries may be overwrittenV                  with  versions that lack the  enhanced support.  Be sure to reinstallT                  the DEC C/C++ Run-Time Components kit after each OpenVMS VAX system                  update.  @              VMSINSTAL now asks if you wish to continue with the              installation.  7              * Continue with the installation? [N]? YESh  4     3-8 Installing the DEC C/C++ Run-Time Components    c              E              If you have adequately saved your old system development C              environment as described in Section 1.2, enter YES and.E              press Return. If you have not saved the old environment, D              you can abort the installation by pressing Return, save@              the environment, and then restart the installation.             7. Purge files.v  >              VMSINSTAL now asks you if you want to purge files4              replaced by the installation procedure.  R              * Do you want to purge files replaced by this installation [YES]? YES  D              The directories SYS$HELP, SYS$LIBRARY, SYS$MESSAGE, andE              SYS$TEST may contain previous versions of DEC C/C++ Run- C              Time Components files. These files are replaced during C              the installation with new files, but the old files are A              not automatically purged. In response to the purging B              prompt, press Return or enter YES and press Return toC              purge the files. To keep the files, enter NO and press_              Return.  C           8. Choose the Installation Verification Procedure option.n  C              VMSINSTAL now asks if you want to run the InstallationtD              Verification Procedure (IVP). The IVP checks to be sureD              that the installation is successful. Digital recommends"              that you run the IVP.  U              This kit contains an Installation Verification Procedure (IVP) to verify T              the correct installation of the DEC C/C++ Run-Time Components.  The IVP              will be placed in:t  %                 SYS$TEST:CRT$IVP.COM.e  P              After the installation is complete, you can invoke the command fileO              at any time to reverify that the DEC C/C++ Run-Time Components arecM              installed and working correctly. Answer YES to the next question N              if you wish to run the IVP at the completion of this installation              procedure.   G              * Do you want to run the IVP after the installation [YES]?   <              After DEC C/C++ Run-Time Components Version 6.0>              for OpenVMS VAX is installed, you can run the IVPC              independently to verify that the software is availablevB              on your system. You might need to run the IVP after aB              system failure to make sure that users can access DECC              C/C++ Run-Time Components Version 6.0 for OpenVMS VAX.   E                     Installing the DEC C/C++ Run-Time Components  3-9t u  e              )           9. Read informational messages.p  A              At this point, the installation procedure displays aC@              number of informational messages that report on the?              progress of the installation. There are no furthert>              questions. If the installation procedure has beenA              successful up to this point, VMSINSTAL moves the newWE              files to their target directories. The new files includet              the following:   F              SYS$HELP:CRT06n.RELEASE_NOTES                       [new]F              SYS$HELP:CRT06n.RELEASE_NOTES.PS                    [new]F              SYS$HELP:CRT06n.RELEASE_NOTES.DECW$BOOK             [new]F              SYS$HELP:CRT060_REF_INST.PS                         [new]F              SYS$HELP:CRT060_REF_INST.TXT                        [new]F              SYS$HELP:CRT060_RBI.PS                              [new]F              SYS$HELP:CRT060_RBI.TXT                             [new]F              SYS$TEST:CRT$IVP.COM                                [new]F              SYS$TEST:[CRT]CRT$ERR1.OBJ                          [new]F              SYS$TEST:[CRT]CRT$ERR2.OBJ                          [new]F              SYS$TEST:[CRT]CRT$IVP1.OBJ                          [new]F              SYS$TEST:[CRT]CRT$IVP2.OBJ                          [new]F              SYS$TEST:[CRT]CRT$IVP3.OBJ                          [new]F              SYS$TEST:[CRT]CRT$IVP4.OBJ                          [new]  E              Also, if you answered YES in response to the prompt that B              requests a file purge at step 7, previous versions ofD              the DEC C/C++ Run-Time Components files are now purged.  >              Additional components follow that are the primaryB              functional components supplied by the kit. The actualA              functional components supplied will differ depending D              on: the OpenVMS VAX version your system is running, theC              layered products already installed on your system, and 5              whether or not this is a reinstallation.i  D              VMSINSTAL displays the following reminder to invoke the/              CRT$STARTUP.COM command procedure:e  S              ********************************************************************** S              *                         R E M I N D E R                            * S              **********************************************************************g  S              If you are  installing on a  VMScluster, you  MUST execute the command S              file  SYS$STARTUP:CRT$STARTUP.COM on all members of the  cluster afteri>              installing the DEC C/C++ Run-Time Components kit.  5     3-10 Installing the DEC C/C++ Run-Time Componentso n  a              S              If you are  installing on an OpenVMS VAX system  prior to Version 6.0,eS              ensure that you invoke the  SYS$STARTUP:CRT$STARTUP.COM  startup  fileiS              prior to  starting up any other  products in the system  startup file,aS              SYS$MANAGER:SYSTARTUP_V5.COM.  See Chapter 4 of the DEC C/C++ Run-TimeeS              Components for OpenVMS VAX  Reference and Installation Guide  for more 4              details on postinstallation operations.  <              The end of the installation is indicated by the              following message:A  L              %VMSINSTAL-I-MOVEFILES, files will now be moved to their target>                                                 directories...             10.Observe the IVP.u  @              If you chose to run the IVP (step 8), VMSINSTAL now>              invokes the IVP to verify that DEC C/C++ Run-TimeA              Components Version 6.0 for OpenVMS VAX was installedn              successfully.  E              If DEC C/C++ Run-Time Components Version 6.0 for OpenVMS A              VAX was installed successfully, the IVP displays theo              following:N  T              ** DEC C/C++ Run-Time Components Installation Verification Procedure **"              ** Ending at hh:mm **  ,           11.End the installation procedure.  =                 Installation of AACRT V6.n completed at hh:mmN  1                 VMSINSTAL procedure done at hh:mm   A              Depending on whether you specified parameters on the B              VMSINSTAL command line, the * Products: prompt or theA              DCL prompt ($) may appear. If the * Products: promptpB              appears, you can return to the DCL prompt by pressing              Ctrl/Z.  C              If you removed any media from the console drive before C              beginning the installation, you should replace it now.   @              VMSINSTAL deletes or changes entries in the processA              symbol tables during the installation. Therefore, if E              you are going to continue using the installation accounttD              (such as SYSTEM) and you want to restore these symbols,1              you should log out and log in again.f  E                    Installing the DEC C/C++ Run-Time Components  3-11t                        3.2 Error Recovery  D           If VMSINSTAL detects any problems during the installation,>           it notifies you and asks if you want to continue the?           installation. In some instances, you can enter YES to D           continue. To stop the installation process and correct theB           situation, enter NO or press Return. Correct the problem'           and restart the installation.   @           If errors occur during the installation itself or whenC           the Installation Verification Procedure (IVP) is running,nB           VMSINSTAL displays failure messages. If the installation4           fails, you will see the following message:  S           %VMSINSTAL-E-INSFAIL, DEC C/C++ Run-Time Components Installation Aborted.v  6           If the IVP fails, you will see this message:  N           ** DEC C/C++ Run-Time Components Installation Verification FAILED **  @           Errors can occur during the installation if any of the%           following conditions exist:   7           o  The operating system version is incorrect.t  :           o  A prerequisite software version is incorrect.  =           o  Quotas necessary for successful installation arep              insufficient.  D           o  System parameter values for successful installation are              insufficient.  :           o  The OpenVMS Help library is currently in use.  D           o  The product license has not been registered and loaded.  C           For descriptions of the error messages generated by thesedA           conditions, see the OpenVMS VAX documentation on system A           messages, recovery procedures, and OpenVMS VAX software =           installation. If you are notified that any of thesewE           conditions exist, you should take the appropriate action as C           described in the message. For information on installation &           requirements, see Chapter 2.  9           If the installation fails, you must restart ther@           installation procedure from step 2. For an explanationA           of any system messages, see the OpenVMS System MessagesV@           and Recovery Procedures Reference Manual or the online>           HELP/MESSAGE facility. If the installation fails due  5     3-12 Installing the DEC C/C++ Run-Time Components                    <           to an IVP failure, contact a Digital field service           representative.                                                                                       E                    Installing the DEC C/C++ Run-Time Components  3-13d o  e                    E                                                                     4hE     _________________________________________________________________n  E                                                    After Installationa    ?           DEC C/C++ Run-Time Components Version 6.0 for OpenVMS B           VAX is now installed and can be used by all applicationsA           written in DEC C or DEC C++, or that use the DECthreadsq           facility.e  C           The following tasks can be performed after DEC C/C++ Run-.C           Time Components Version 6.0 for OpenVMS VAX is installed:   B           o  Running the Installation Verification Procedure (IVP)              separatelyn  ,           o  Editing the system startup file  6           o  Making the product usable on a VMScluster  C           o  Reinstalling after an OpenVMS VAX intermediate upgradee             o  Reporting problemsi  @           The following sections describe these tasks in detail.  B     4.1 Running the Installation Verification Procedure Separately  A           You usually run the Installation Verification Procedure/?           (IVP) during installation. If you want to run the IVP ?           separately to ensure the integrity of installed files ?           should system problems occur, enter the following IVP            command procedure:  !           $ @SYS$TEST:CRT$IVP.COMr  B           If an IVP fails for any reason, the following message is           displayed:  N           ** DEC C/C++ Run-Time Components Installation Verification FAILED **  E                                                After Installation 4-1  .  l                    4.2 Editing the System Files  >           To use DEC C/C++ Run-Time Components Version 6.0 for;           OpenVMS VAX with DECwindows or other applicationsh@           written in the C language, you need to edit the system@           startup file to provide for automatic inclusion of theA           DEC C/C++ Run-Time Components as known images when yourdC           system is rebooted. This step is required only on OpenVMSe+           VAX systems prior to Version 6.0.l  =           Add the command line that starts the DEC C/C++ Run-V9           Time Components kit to the system startup file,e@           SYS$MANAGER:SYSTARTUP_V5.COM. You should position thisB           new command line after the line that invokes the networkD           startup command procedure. The following example shows theE           network startup command line followed by the DEC C/C++ Run- E           Time Components Version 6.0 for OpenVMS VAX startup commande           line:e  %           $ @SYS$MANAGER:STARTNET.COMc                .                .                .(           $ @SYS$STARTUP:CRT$STARTUP.COM  B             ________________________ Note ________________________  @             This line should also precede the startup invocationB             of any applications written in the C or C++ languages,A             or that use the DECthreads facility. Examples of such @             applications are the DEC TCP/IP Services for OpenVMS@             (UCX$STARTUP.COM), DEC DCE, and DECmcc. This startup>             file must be invoked on all OpenVMS VAX nodes in a             VMScluster.   B             ______________________________________________________  !     4.3 VMScluster Considerationsl  B           After completing the initial installation on OpenVMS VAXB           systems prior to Version 6.0, you must install the DEC CE           /C++ Run-Time Components kit on all nodes in a cluster. YoumC           must run the startup on each of the other nodes and entern            the following command:  (           $ @SYS$STARTUP:CRT$STARTUP.COM       4-2 After Installation A  N              D           If you are using a dual-architecture (VAX and AXP systems)B           heterogeneous cluster, make sure the appropriate logical?           names have been set to define the scope of the SYSMANA?           DO commands before executing these commands. For more ?           information, see the OpenVMS System Manager's Manual._  >     4.4 Reinstalling After an OpenVMS VAX Intermediate Upgrade  =           If you upgrade your operating system to OpenVMS VAXt?           Version 5.5-1 or 5.5-2 after installing this kit, you ?           must reinstall the DEC C/C++ Run-Time Components kit. A           Unless you do reinstall this kit, applications that useLC           new features of the DEC C/C++ Run-Time Components kit maySB           fail to work properly, because the kit supplies versionsE           of several OpenVMS VAX component files that are more recent E           than versions supplied as part of the previous intermediate*           upgrades.*       4.5 Reporting Problems  C           If you encounter a problem while using the DEC C/C++ Run- A           Time Components Version 6.0 for OpenVMS VAX kit, report*B           it to Digital. Depending on the type of support you haveB           and the nature of the problem, take one of the following           actions:  <           o  If you have a Software Product Services SupportD              Agreement, contact your Digital Customer Support CenterE              (CSC), either by telephone or using the electronic meansiD              provided with your support agreement (such as DSNlink).>              The CSC provides telephone support for high-levelA              advisory and remedial assistance. When you initiallys<              contact the CSC, please indicate the following:  D              -  The name (OpenVMS VAX) and the version number of the/                 operating system you are using.   ?              -  The product name (DEC C/C++ Run-Time ComponentseC                 Version 6.0 for OpenVMS VAX) and the version numbers@                 of DEC C/C++ Run-Time Components Version 6.0 for*                 OpenVMS VAX you are using.  B              -  The hardware system you are using, such as a model                 number.?  E              -  A very brief description of the problem (one sentencec                 if possible).   E                                                After Installation 4-3r e  a              ,              -  How critical the problem is.  >              When you submit information electronically or areD              speaking on the phone to the appropriate DEC C/C++ Run-@              Time Components Version 6.0 for OpenVMS VAX supportC              specialist, you can provide more detailed information. @              This includes the specific commands used to compileD              and link the program, the error messages displayed, andE              relevant detailed information (possibly including sourceYE              program listings). Please attempt to narrow the cause of ?              the problem to a specific module or lines of code.e  >              CSC personnel may ask for additional information,B              such as listings of any command files, INCLUDE files,A              relevant data files, and so forth. If the program istE              longer than 50 lines, submit a copy of it electronicallyiB              or provide machine-readable media (floppy diskette or              magnetic tape).  C           o  If you have a Self-Maintenance Software Agreement, your<              can submit a Software Performance Report (SPR).  B           When you submit an SPR, please take the following steps:  E           1. Describe as accurately as possible the circumstances and B              state of the system when the problem occurred. In the)              description, please provide:a  C              -  The version number of DEC C/C++ Run-Time Componentsl7                 Version 6.0 for OpenVMS VAX being used.e  C              -  The name and version number of the operating system                  being used.   B              -  A concise description of the problem with specificC                 examples. Include any error messages displayed, thetE                 commands used to compile and link the program, and so                  on.   ?           2. Reduce the problem to as small a size as possible.   .           3. Provide a listing of the program.  D           4. When you submit an SPR, remember to include listings ofC              any command files, INCLUDE files, relevant data files,t              and so forth.       4-4 After Installation Y  m              B           5. When you submit an SPR, if the program is longer thanD              50 lines, submit a copy of it on machine-readable mediaC              (floppy diskette or magnetic tape). If necessary, alsonC              submit a copy of the program library used to build them              application.   D           6. Report only one problem per SPR. This will facilitate a              faster response.a  -           7. Mail the SPR package to Digital.t  @           Many problem reports do not contain enough informationA           to duplicate or identify the problem. Concise, completeh@           information helps Digital give you accurate and timely'           service to software problems.   C           To obtain information about purchasing a Digital SoftwareT=           Product Services Support Agreement or other supportL;           services, please contact your local Digital sales:           representative.O                                                  E                                                After Installation 4-50 F  S                    E                                                                     A E     _________________________________________________________________   E                                                   Sample Installation     B           This appendix contains a sample installation for the DECD           C/C++ Run-Time Components Version 6.0 for OpenVMS VAX kit.E           This is only a sample. Sometimes the installation procedure =           is modified in maintenance updates of this product.   B           The following sample was installed on a system where DEC?           C/C++ Run-Time Components Version 6.0 for OpenVMS VAX B           was not previously installed. Depending on which layeredD           products you have on your system, you might see additionalD           messages and questions when you perform your installation.  D           This sample installation assumes that DECnet has been shutD           down, that no users are logged in to your system, and that@           OPTIONS N is specified to print the release notes. TheC           Installation Verification Procedure (IVP) runs at the endn           of the installation.  B           Example A-1 shows a sample installation of the DEC C/C++7           Run-Time Components on an OpenVMS VAX system.                                   E                                               Sample Installation A-1p e  e              :           Example A-1 Sample DEC C/C++ Run-Time Components;                       Installation on an OpenVMS VAX SystemM  +                   Welcome to VAX/VMS V5.5-2              Username: SYSTEM           Password:*B                   Welcome to VAX/VMS version V5.5-2 on node SUBTLEC               Last interactive login on Thursday, 19-AUG-1993 14:39SE               Last non-interactive login on Monday,  9-AUG-1993 15:48   5           $ @sys$update:vmsinstal aacrt060 sys$update   @           VAX/VMS Software Product Installation Procedure V5.5-2  %           It is 19-AUG-1993 at 14:43.l  9           Enter a question mark (?) at any time for help.   H           * Are you satisfied with the backup of your system disk [YES]?>           * Enter installation options you wish to use (none):  3           The following products will be processed:T             AACRT V6.0  7           Beginning installation of AACRT V6.0 at 14:43p  @           %VMSINSTAL-I-RESTORE, Restoring product save set A ...U           %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. R             DEC C/C++ Version V06.0-60 Run-Time components for OpenVMS/VAX systems  V               Copyright (c) Digital Equipment Corporation, 1993.  All rights reserved.  T               This kit  provides  new  versions  of  several  OpenVMS  VAX  standardT               shareable   images  and  object  libraries  in  SYS$LIBRARY,  such  asT               VAXCRTL.EXE,  CMA$RTL.EXE, and  SMGSHR.EXE.  These provide support forT               several programming  capabilities provided by  OpenVMS VAX Version 6.0.               for C, C++, and other languages.  T               **********************************************************************T               *                          W A R N I N G                             *T               **********************************************************************  E                                              (continued on next page)        A-2 Sample InstallationD n  g              B           Example A-1 (Cont.) Sample DEC C/C++ Run-Time ComponentsC                               Installation on an OpenVMS VAX Systemr  T               Programs  that link  against the new  versions of any of  these files,T               EVEN THOSE NOT WRITTEN IN DEC C OR C++, will NOT run on older versionsT               of OpenVMS (V5.5-2 or earlier)  unless steps are taken to save the oldU               SYS$LIBRARY configuration or redistribute this kit to additional sites.oT               See Chapter 1 of the  DEC C/C++  Run-Time Components  for OpenVMS  VAX@               Reference and Installation Guide for more details.  T               In  addition,  if you  update the system  version of  OpenVMS VAX, theT               enhanced  versions of the new images and libraries may be  overwrittenT               with  versions that lack the  enhanced support.  Be sure to  reinstallR               the DEC C/C++ Run-Time Components kit after each OpenVMS VAX  system               update.i  2           * Continue with the installation? [N]? y  M           * Do you want to purge files replaced by this installation [YES]? n,  T               This kit  contains an  Installation  Verification  Procedure  (IVP) toS               verify the correct installation of the DEC C/C++ Run-Time Components.n(               The IVP will be placed in:  &                   SYS$TEST:CRT$IVP.COM  T               After the installation is complete, you can invoke the command file atS               any time to reverify that DEC C/C++ Run-Time Components are installedtT               and working correctly.  Answer yes to the next question if you wish toK               run the IVP at the completion of this installation procedure.s  F           * Do you want to run the IVP after the installation [YES]? y  S                   All questions and verifications regarding the installation of the R                   DEC C/C++ Run-Time Components have been completed.  Depending onM                   your configuration, time estimates for the remainder of thee2                   installation are 1 to 3 minutes.  S           %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.CRT]..  Y             Your OpenVMS system will now be updated to include the following new file(s):c  E                                              (continued on next page)     E                                               Sample Installation A-3p e  e              B           Example A-1 (Cont.) Sample DEC C/C++ Run-Time ComponentsC                               Installation on an OpenVMS VAX Systemt  G               SYS$HELP:CRT060.RELEASE_NOTES                       [new]lG               SYS$HELP:CRT060_RELEASE_NOTES.PS                    [new]lG               SYS$HELP:CRT060_RELEASE_NOTES.DECW$BOOK             [new] G               SYS$HELP:CRT060_REF_INST.PS                         [new]nG               SYS$HELP:CRT060_REF_INST.TXT                        [new]oG               SYS$HELP:CRT060_RBI.PS                              [new]dG               SYS$HELP:CRT060_RBI.TXT                             [new] G               SYS$TEST:CRT$IVP.COM                                [new] G               SYS$TEST:[CRT]CRT$ERR1.OBJ                          [new] G               SYS$TEST:[CRT]CRT$ERR2.OBJ                          [new]EG               SYS$TEST:[CRT]CRT$IVP1.OBJ                          [new] G               SYS$TEST:[CRT]CRT$IVP2.OBJ                          [new]_G               SYS$TEST:[CRT]CRT$IVP3.OBJ                          [new] G               SYS$TEST:[CRT]CRT$IVP4.OBJ                          [new]   G               SYS$STARTUP:CRT$STARTUP.COM                         [new]wG               SYS$LIBRARY:CMA$RTL.EXE                             [new]CG               SYS$LIBRARY:CMA$OPEN_RTL.EXE                        [new] G               SYS$LIBRARY:CMA$LIB_SHR.EXE                         [new]iG               SYS$LIBRARY:CMA$OPEN_LIB_SHR.EXE                    [new]RG               SYS$LIBRARY:CMA$TIS_SHR.EXE                         [new]tG               SYS$LIBRARY:CXXL$011_SHR.EXE                        [new]nG               SYS$MESSAGE:CXXL$MSG_SHR.EXE                        [new]nG               SYS$LIBRARY:DECC$SHR.EXE                            [new] G               SYS$LIBRARY:DECCCURSE.OLB                           [new].G               SYS$LIBRARY:DECCRTL.OLB                             [new] G               SYS$LIBRARY:DECCRTLG.OLB                            [new] G               SYS$LIBRARY:UCX$CRTLIBXFR.OBJ                       [new] G               SYS$LIBRARY:VAXC$EMPTY.EXE                          [new]sG               SYS$LIBRARY:VAXC$LCL.OPT                            [new] G               SYS$LIBRARY:VAXC2DECC.EXE                           [new]hG               SYS$LIBRARY:VAXCRTL.EXE                             [new]nG               SYS$LIBRARY:VAXCG2DECC.EXE                          [new] G               SYS$MESSAGE:VAXCMSG.EXE                             [new] G               SYS$LIBRARY:VAXCCURSE.OLB                           [new] G               SYS$LIBRARY:VAXCRTL.OLB                             [new]rG               SYS$LIBRARY:VAXCRTLG.EXE                            [new] G               SYS$LIBRARY:VAXCRTLG.OLB                            [new] G               SYS$LIBRARY:DECC$EMPTY.EXE                          [new]   E                                              (continued on next page)        A-4 Sample Installation0                   B           Example A-1 (Cont.) Sample DEC C/C++ Run-Time ComponentsC                               Installation on an OpenVMS VAX SystemU  T               **********************************************************************T               *                         R E M I N D E R                            *T               **********************************************************************  T               If you are  installing on a  VMScluster, you  MUST execute the commandT               file  SYS$STARTUP:CRT$STARTUP.COM on all members of the  cluster after?               installing the DEC C/C++ Run-Time Components kit._  T               If you are  installing on an OpenVMS VAX system  prior to Version 6.0,T               ensure that you invoke the  SYS$STARTUP:CRT$STARTUP.COM  startup  fileT               prior to  starting up any other  products in the system  startup file,T               SYS$MANAGER:SYSTARTUP_V5.COM.  See Chapter 4 of the DEC C/C++ Run-TimeT               Components  for OpenVMS VAX  Reference and Installation Guide for more5               details on postinstallation operations._  X           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  T             Copyright (c) Digital Equipment Corporation, 1993.  All rights reserved.  ;               *-------------------------------------------*R;               *    Installation Verification Procedure    * 7               *     for DEC C/C++ Run-Time Components *n;               *-------------------------------------------*A  ;               *-------------------------------------------* ;               *    Test that components LINK properly     * ;               *-------------------------------------------*t  ;               *-------------------------------------------* ;               *    Test that components RUN properly      *i;               *-------------------------------------------*O  E                                              (continued on next page)                   E                                               Sample Installation A-5t                   B           Example A-1 (Cont.) Sample DEC C/C++ Run-Time ComponentsC                               Installation on an OpenVMS VAX Systeme  %               Testing DEC C RTL . . . 1               Testing DEC C++ Class Library . . .m"               Testing curses . . .%               Testing DEC C RTL . . . 1               Testing DEC C++ Class Library . . .t"               Testing curses . . .)                   Testing VAX C RTL . . .r&                   Testing curses . . .*                   Testing DECthreads . . .)                   Testing VAX C RTL . . .e&                   Testing curses . . .*                   Testing DECthreads . . .)                   Testing VAX C RTL . . . &                   Testing curses . . .*                   Testing DECthreads . . .)                   Testing VAX C RTL . . . &                   Testing curses . . .*                   Testing DECthreads . . .)                   Testing VAX C RTL . . . &                   Testing curses . . .*                   Testing DECthreads . . .5                   Testing VAX C shareable usage . . . 1                   Testing shareable portion . . .l,                   Testing main portion . . .5                   Testing VAX C shareable usage . . .C1                   Testing shareable portion . . . ,                   Testing main portion . . .  W             ** DEC DEC C/C++ Run-Time Components Installation Verification Procedure **e3             ** Ending at 19-AUG-1993 14:47:05.63 **s  ?                   Installation of AACRT V6.0 completed at 14:47f  3                   VMSINSTAL procedure done at 14:50                      A-6 Sample Installation 