                   "           VAX C Installation Guide  #           Order Number: AA-L491G-TE                  December 1989   F           This document contains instructions for installing VAX C andG           the VMS Debugger for multiprocess debugging (DEBUG MP) on the G           VMS operating system. It also explains how to read the online D           release notes before or after installing the product. This0           document applies to VAX C Version 3.1.          F           Revision/Update Information:  This revised manual supersedes+                                         the @                                         VAX C Installation GuideC                                         (Order Number AA-L491F-TE).   B           Operating System and Version: VMS Version 5.0 or higher.G                                         Future maintenance releases may @                                         require higher versions.  9           Software Version:             VAX C Version 3.1             '           digital equipment corporation             maynard, massachusetts         =           ___________________________________________________ '           First Printing, February 1982            Revised, October 1984            Revised, April 1985            Revised, April 1986            Revised, March 1987             Revised, February 1989            Revised, December 1989  G           The information in this document is subject to change without G           notice and should not be construed as a commitment by Digital F           Equipment Corporation. Digital Equipment Corporation assumesB           no responsibility for any errors that may appear in this           document.   F           The software described in this document is furnished under aG           license and may be used or copied only in accordance with the             terms of such license.  A           No responsibility is assumed for the use or reliability B           of software on equipment that is not supplied by Digital<           Equipment Corporation or its affiliated companies.  C           Restricted Rights: Use, duplication, or disclosure by the D           U.S. Government is subject to restrictions as set forth inF           subparagraph (c)(1)(ii)  of the Rights in Technical Data and9           Computer Software clause at DFARS 252.227-7013.   G            Digital Equipment Corporation 1982, 1984, 1985, 1986, 1987,            1989.              All Rights Reserved.           Printed in U.S.A.   G           The postpaid Reader's Comments forms at the end of this docu- F           ment request your critical evaluation to assist in preparing           future documentation.   H           The following are trademarks of Digital Equipment Corporation:  .           DEC             DIBOL         UNIBUS+           DEC/CMS         EduSystem     VAX 2           DEC/MMS         IAS           VAXcluster+           DECnet          MASSBUS       VMS *           DECsystem-10    PDP           VT           DECSYSTEM-20    PDT /           DECUS           RSTS          DIGITAL            DECwriter       RSX   G                                                                  ZK5346                                    G                                                                Contents G        ________________________________________________________________     H        Preface .......................................................v.G        Preparing to Install VAX C ................................... 1 G          Prerequisite Software....................................... 1 G          Accessing the Online Release Notes........................   1 G          Installation Procedure Requirements.......................   2 G          User Account Quotas and Privileges........................   4 G          VMS License Management Facility ...........................  5 G          Using VMSINSTAL..............................................6 G        Installing VAX C...............................................8 G          Installing VAX C on a VAXcluster..........................  16 G        Installing VAX DEBUG MP.......................................17 G        After the Installation........................................23 6        Running the Installation Verification ProcedureG          Separately..................................................23 G        Error Conditions..............................................24 G        Installing VAX C as a Shared Image..........................  25 G        Maintenance Updates ..........................................26 G        Determining and Reporting Problems..........................  26 G        Sample Installation ..........................................27                 G                                                                     iii                                  G                                                                 Preface G        ________________________________________________________________       E           This document describes how to install VAX C Version 3.1 on G           the VMS operating system. It is intended for system managers.   C           For users of VMS versions prior to Version 5.2, this doc- B           ument also describes how to install the VMS Debugger forC           multiprocess debugging (DEBUG MP). Installing DEBUG MP is G           optional; if you do not install it, multiprocess debugging is            not available.  F           Keep this document with your distribution kit. You will needE           it to install maintenance updates or to reinstall VAX C for            any other reason.   G           At the back of this document are two Reader's Comments forms. D           If you have any comments about this document, fill out oneD           form and mail it; your comments will be considered for the2           next revision of the installation guide.  E           For more information about installing VAX C on VMS systems, D           see your processor-specific installation/operations guide.  F           The installation procedure is described step-by-step and is,E           for the most part, self-explanatory. The system prompts you F           to answer questions and to change volumes, and waits for you!           to tell it to continue.   G           Defaults appear in brackets ([])  throughout the installation 7           procedure. Text you type is indicated in red.   G                                                                       v                  C        ____________________________________________________________   !        Preparing to Install VAX C   F           Your bill of materials (BOM) and indented bills report (BIL)C           specify the number and contents of your media. Be sure to B           check the contents of your kit against this information.D           If your kit is damaged or if you find that parts of it are4           missing, call your Digital representative.  D           Distribution media must be mounted in numerical order. TheF           installation procedure prompts you to mount the volumes. ForG           more information on how to mount distribution media, see your F           processor-specific installation/operations guide, which also@           details several options to the installation procedure.  C        ____________________________________________________________           Prerequisite Software  E           If the optional software package VAX Common Data Dictionary F           (CDD) is on your system and you plan to run the Installation?           Verification Procedure (IVP), you need to execute the D           SYS$COMMON:[SYSMGR]CDDSTRTUP.COM file (which installs pro-D           tected images that the IVP needs) before you begin the in-           stallation of VAX C.  C        ____________________________________________________________   )        Accessing the Online Release Notes   D           VAX C provides online release notes. The prompt to displayD           or print the release notes during the installation appearsA           in step 5 of the installation procedure when you invoke D           VMSINSTAL with the OPTIONS N parameter. Digital recommendsA           that you do not choose option 5 if you wish to display, +           print, or copy the release notes.   B           To obtain the release notes after the installation, typeB           or print the file SYS$HELP:VAXC031.RELEASE_NOTES. OnlineD           help also directs you to the release notes file. After the3           installation, type the following command:   G                                             VAX C Installation Guide  1                  ,             $ HELP CC RELEASE_NOTES <RETURN>  C        ____________________________________________________________   *        Installation Procedure Requirements  D           The installation takes approximately 20 to 60 minutes, de-E           pending on the type of media and your system configuration. E           Before installing VAX C, you must have the following privi-            leges and resources:  G            o SETPRV privileges, or CMKRNL, WORLD, and SYSPRV privileges   F            o A minimum of 11500 blocks of free disk space during VAX CB              installation; 9200 blocks are used after installation  E            o A minimum of 4000 blocks of free disk space during DEBUG E              MP installation; 3000 blocks are used after installation   7            o A minimum of 512K bytes of physical memory   F            o A minimum of 900 free global pages plus the size (in num-F              ber of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE              at installation  @            o A minimum of 8 free global sections at installation  +                                        NOTE   @               You must ensure that your system has the necessaryB               global page and global section SYSGEN quotas for the@               installation. Failure to do so could cause the DCL8               tables to be corrupted in some situations.  C           To determine the number of available global pages on your F           system, invoke the VMS Install Utility by typing the follow-           ing command:  8             $ INSTALL :== $INSTALL/COMMAND_MODE <RETURN>             $ INSTALL <RETURN>  "        2  VAX C Installation Guide                 *           Then type the following command:  1             INSTALL> LIST/GLOBAL/SUMMARY <RETURN>   ;                     Summary of Local Memory Global Sections   K             309 Global Sections Used,  28866/13134 Global Pages Used/Unused   "             INSTALL> EXIT <RETURN>  F           When you issue these commands, the system displays a summaryE           of the number of global sections used, the number of global D           pages used, and the number of global pages unused. To exit>           from the VMS Install Utility, type the EXIT command.  C           VAX C requires approximately 900 contiguous global pages, G           and the debugger requires approximately 210 contiguous global F           pages. If there are fewer than 1110 pages available, you canF           delete an existing known image with the VMS Install Utility,D           or you can increase the GBLPAGES system parameter with theD           VMS System Generation Utility (SYSGEN) by editing the fileE           SYS$SYSTEM:MODPARAMS.DAT and then invoking the AUTOGEN com- F           mand procedure, SYS$UPDATE:AUTOGEN.COM. For more informationG           on the AUTOGEN command procedure, see your processor-specific (           installation/operations guide.  F           You can determine the number of available global sections by%           invoking SYSGEN as follows:   ,             $ RUN SYS$SYSTEM:SYSGEN <RETURN>(             SYSGEN> USE CURRENT <RETURN>-             SYSGEN> SHOW GBLSECTIONS <RETURN>   !             SYSGEN> EXIT <RETURN>   C           The last number displayed is the maximum number of global D           sections. Compare this number to the number of global sec-B           tions in use displayed by the VMS Install Utility. VAX CG           requires 8 global sections and the debugger requires 5 global D           sections. Therefore, if the number of global sections usedD           plus 13 exceeds the maximum number of global sections, you  G                                             VAX C Installation Guide  3                  C           must increase the number of available global sections be- F           fore you can install VAX C. To increase the number, you mustB           increase the GBLSECTIONS system parameter with SYSGEN byE           editing the file SYS$SYSTEM:MODPARAMS.DAT and then invoking D           the SYS$UPDATE:AUTOGEN.COM procedure. For more informationC           on the AUTOGEN.COM procedure, see your processor-specific (           installation/operations guide.  D           If the number of global sections used plus 13 is less thanB           the maximum number of global sections, you can exit from           SYSGEN and continue.  C        ____________________________________________________________   )        User Account Quotas and Privileges   G           To use VAX C, each account must have TMPMBX and NETMBX privi- /           leges and the following requirements:   +            o AST limit (ASTLM) 20 (minimum)   4            o Buffered I/O quota (BIOLM) 20 (minimum)  B            o Buffered I/O byte count quota (BYTLM) 20480 (minimum)  2            o Direct I/O quota (DIOLM) 12 (minimum)  /            o Enqueue quota (ENQLM) 20 (minimum)   1            o Open file limit (FILLM) 16 (minimum)   ?            o Paging file quota (PGFLQUOTA) 1500 pages (minimum)   B            o Subprocess creation quota (PRCLM) by user requirement              (minimum)  D            o Working set size (WSDEF) 300 pages (minimum) 500 to 700              pages (optimum)  B           Use the VMS Authorize Utility (AUTHORIZE) to compare theF           current values of these quotas with the requirements for VAXF           C. For example, the account used in the following example is           the SYSTEM account:   "        4  VAX C Installation Guide                 -             $ SET DEFAULT SYS$SYSTEM <RETURN> $             $ RUN AUTHORIZE <RETURN>%             UAF> SHOW SYSTEM <RETURN>   E           To change the values of these quotas, use the VMS Authorize E           Utility's MODIFY command. For more information, see the VMS #           Authorize Utility Manual.   C        ____________________________________________________________   &        VMS License Management Facility  E           The VMS License Management Facility (LMF) is available with D           Version 5.0 of the VMS operating system. Since you are in-G           stalling VAX C on a system running VMS Version 5.0 or higher, 8           you must register your VAX C software license.  G           The license registration information you need is contained in F           the Product Authorization Key (PAK) that is shipped with VAXE           C. The PAK is a paper certificate that contains information A           about the license you have to run a particular piece of            software.   G           During the installation, you are asked if you have registered D           the VAX C license and loaded the appropriate authorizationG           key. You must register and load your license for VAX C before E           you start the installation in order to run the Installation <           Verification Procedure (IVP) and use the software.  F           To register a license under VMS Version 5.0, first log in toF           the system manager's account, SYSTEM. You then have a choice2           of two ways to perform the registration:  D            o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When itE              prompts you for information, respond with data from your -              Product Authorization Key (PAK).   G            o Issue the LICENSE REGISTER DCL command, on the DCL command E              line, with the appropriate qualifiers that correspond to $              information on the PAK.  G                                             VAX C Installation Guide  5                  F           For complete information on using LMF, see the manual on theB           License Management Utility in the VMS documentation set.  C        ____________________________________________________________           Using VMSINSTAL  D           After you log in to a privileged account to install VAX C,D           invoke VMSINSTAL, the command procedure that installs thisG           product. An example of this procedure is shown in steps 1 ands,           2 of the Installing VAX C section.  C           The VMSINSTAL command procedure has the following syntax:n  =             $ @SYS$UPDATE:VMSINSTAL VAXC03n ddcu: [OPTIONS N]              n B           Represents the maintenance update of VAX C. Refer to theE           label on the VAX C distribution kit or the VAX C BOM or BILy8           for the maintenance update number of your kit.  D           You can also type an asterisk (*)  in place of VAXC03n. IfG           you are installing from magnetic tape, you can use the aster-aE           isk to save installation time; the asterisk causes VAX C toa5           be installed with a minimum of tape passes.t             ddcu: F           Represents a device name where the distribution volumes willB           be mounted for the VAX C installation media, where dd isA           the device code, c is the controller code, and u is the C           unit number. It is not necessary to use the console driveeG           to install VAX C. If you do use the console drive, you shouldjD           replace any media you removed from the drive. CSA1: is the8           device name used in examples in this document.             OPTIONS NrD           Is an optional parameter you should provide if you want toC           be prompted to display or print the release notes. If youbD           do not include the OPTIONS N parameter, VMSINSTAL does notE           prompt you to display or print the release notes. VMSINSTALi  "        6  VAX C Installation Guide a  m            C           permits the use of several other options. For more infor-pB           mation on the other options, see your processor-specific(           installation/operations guide.  B           If you do not supply the first two parameters, VMSINSTALF           prompts you for the product and device names. If you wish toE           be prompted for the product and device names and to displayl9           or print the release notes, type the following:n  ,             $ @SYS$UPDATE:VMSINSTAL <RETURN>  =           When you invoke VMSINSTAL, it checks the following:e  C            o Whether you logged in to a privileged account. DIGITALnA              recommends that you install software from the systemoE              manager's account with your default device and directory               set to SYS$UPDATE.a  ?            o Whether you have adequate quotas for installation. =              VMSINSTAL checks for the following quota values:                  _ ASTLM = 24                 _ BIOLM = 18                 _ BYTLM = 18000                  _ DIOLM = 18                 _ ENQLM = 30                 _ FILLM = 20  C              VMSINSTAL then checks whether the following conditions               exist:   0               o Whether DECnet is up and running  =               o Whether any users are logged in to the system   F              If VMSINSTAL detects either of these conditions, you willG              be asked whether you want to continue the installation. If.D              you want to continue, type YES. If you want to stop the(              installation, press RETURN.  G                                             VAX C Installation Guide  7                  C        ____________________________________________________________a          Installing VAX Cn  C           This section contains excerpts from the installation pro-eD           cedure and explains each step. Defaults appear in brackets0           throughout the installation procedure.  @           To abort the installation procedure at any time, pressC           CTRL/Y. When you press CTRL/Y, the installation procedure D           deletes all files it has created up to that point and thenF           returns you to DCL level. If you want to retry the installa-E           tion procedure after pressing CTRL/Y, you must proceed from.           step 2.g  E           Step 1: Log in to a privileged account and set your default.-           device and directory to SYS$UPDATE.           <RETURN>.  &             Username: SYSTEM  <RETURN>&             Password:         <RETURN>-             $ SET DEFAULT SYS$UPDATE <RETURN>M  #           Step 2: Invoke VMSINSTAL..  9             $ @VMSINSTAL VAXC031 CSA1: OPTIONS N <RETURN>o  F                   VAX/VMS Software Product Installation Procedure V5.0  '             It is 11-OCT-1988 at 17:00. ;             Enter a question mark (?) at any time for help.   J             * Are you satisfied with the backup of your system disk [YES]?        <RETURN>   C           If you are satisfied with the backup of your system disk,_F           press RETURN. Otherwise, type NO and press RETURN to discon-!           tinue the installation.3  "        8  VAX C Installation Guide m  t            ;           Step 3: Insert the first installation kit volume.   >             Please mount the first volume of the set on CSA1:.)             * Are you ready? YES <RETURN> 5             The following products will be processed:P                 VAX C 3.1f  <                 Beginning installation of VAX C 3.1 at 17:03  @             %VMSINSTAL-I-RESTORE, Restoring product saveset A...  G           To indicate that you want to continue the installation, mountt/           volume 1, type YES, and press RETURN.   A           Step 4: Insert the subsequent installation kit volumes.   E             %BACKUP-I-READYREAD, mount volume 2 on _CSA1: for reading   /             Enter "YES" when ready: YES<RETURN>s  G           VMSINSTAL prompts you to insert the next volume and waits for G           you to type YES after inserting it. If you type NO, VMSINSTAL E           displays the prompt again. This prompt is displayed only if >           your installation kit contains more than one volume.  0           Step 5: Select a release notes option.  F           This step applies only if you specified OPTIONS N in step 2.  "             Release Notes Options:  (                 1. Display release notes&                 2. Print release notes                 3. Both 1 and 2 1                 4. Copy release notes to SYS$HELP ?                 5. Do not display, print, or copy release notes   )             * Select option [2]: <RETURN>_  G                                             VAX C Installation Guide  9                  F           If you select option 1, VMSINSTAL displays the release notesC           on line immediately. You can terminate the display at anyoA           time by pressing CTRL/C. After you view them, VMSINSTAL /           copies the release notes to SYS$HELP.   C           If you select option 2, VMSINSTAL prompts you for a queueuD           name. Either type a queue name or press RETURN to send theB           file to the default output print device. After you print?           them, VMSINSTAL copies the release notes to SYS$HELP.   .             * Queue name [SYS$PRINT]: <RETURN>  F           If you select option 3, VMSINSTAL displays the release notesC           on line immediately. You can terminate the display at any_A           time by pressing CTRL/C. VMSINSTAL then prompts you foraC           a queue name. Either type a queue name or press RETURN to E           send the file to the default output print device. The VAX Cn4           release notes are then copied to SYS$HELP.  G           If you select option 4, VMSINSTAL copies the release notes tod           SYS$HELP immediately.e  G           If you select option 5, VMSINSTAL does not display, print, or_!           copy the release notes._  A           If you are installing on VMS Version 5.2 or higher, the C           release notes menu is slightly different, and the release 5           notes are automatically copied to SYS$HELP.a  +                                        NOTEc  A               This version of the release notes file installed bytD               VMSINSTAL is labeled with the current product name andA               version number. For example, VAXC031.RELEASE_NOTES. @               Take care not to delete release notes for previous                versions of VAX C.      #        10  VAX C Installation Guide     p            8           Next, VMSINSTAL displays the following prompt:  G             * Do you want to continue the installation [N]?: Y <RETURN>   U             %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully_9                                        moved to SYS$HELP._A                     VAX C V3.1-001 Installation is commencing ...m  F           If you want to continue the installation, type YES and pressF           RETURN. If you type NO or press RETURN, VMSINSTAL discontin-G           ues the installation. As long as you did not choose option 5, E           VMSINSTAL still moves the release notes to SYS$HELP; other-CG           wise, you need to repeat the installation procedure to obtainl&           a copy of the release notes.  :           Step 6: Respond to License Registration Queries.  C           VAX C supports the VMS License Management Facility (LMF).EG           The installation procedure displays license information aboutoF           your product and then asks if you have registered and loadedG           your authorization key for VAX C. The following is an example            of such information:               Product:       C             Producer:      DEC             Version:       3.1&             Release Date:  dd-mmm-yyyy  P             * Does this product have an authorization key registered and loaded?  G           If you have not registered and loaded your authorization key,EC           you must answer NO to this question. You have to registercA           and load your product authorization key to successfullynA           complete the installation. If you have not done so, younF           should stop the installation, register and load your product?           authorization key, and then restart the installation.A      G                                            VAX C Installation Guide  11t a  n            .           Step 7: Select installation options.  E              This kit contains an Installation Verification Procedure E              (IVP) to verify the  correct  installation of the VAX  C0              compiler.  E              After the  installation is  complete, you can invoke theR@              IVP at any time to reverify that VAX C is installed<              and working correctly by executing the command:  #                  @SYS$TEST:VAXC$IVPs  O             * Do you want to run the IVP after the installation [YES]? <RETURN>U  F           The Installation Verification Procedure (IVP) checks whetherD           the installation procedure was successful. Press RETURN toG           run the IVP after the installation. If you do not want to runn5           the IVP, type NO in response to the prompt.s  +                                        NOTE   A               If the Common Data Dictionary (CDD) is installed on A               your system, then the CDD startup procedure must beeA               executed before you run the IVP. Otherwise, the IVPcB               will fail. See the Prerequisite Software section for               more information.N  V             * Do you want to purge files replaced by this installation [YES] ?<RETURN>  A           The directories SYS$HELP, SYS$MESSAGE, SYS$LIBRARY, andnB           SYS$SYSTEM may contain previous versions of VAX C files.C           These files are replaced during the installation with new @           files, but the old files are not automatically purged.D           Purging is recommended. In response to the purging prompt,B           press RETURN to purge the files or type NO to keep them.  W             * Do you want to extract the .H files from the text library [YES] ?<RETURN>     #        12  VAX C Installation Guidee b  e            G           The VAX C definition files (commonly referred to as .H files) C           are distributed as library modules. This saves space both,F           on the distribution kit and on your system. However, you mayC           want to extract the modules and place them in .H files invD           order to use #include control lines of the following form:  !             #include <filename.H>   F           If the programs on your system use this form of the #includeG           directive, you can either change the source files to refer to E           the library module (as in #include module_name), or you caneF           request that the installation procedure extract the .H files!           after installing VAX C.   A           If you want the installation procedure to extract these D           files, press RETURN; otherwise, type NO in response to the           prompt.   +                                        NOTE_  ?               If you do not extract the .H files during the in- =               stallation, old versions of the .H files in theE@               SYS$LIBRARY area may still remain. To avoid possi-@               ble programming errors, you may want to delete old&               versions of these files.  [             * Do you want to install the DECwindows Compiler Interface for C [YES]?<RETURN>t  A           If anyone on your system wishes to be able to compile CmF           programs using the DECwindows FileView interface, you shouldF           press RETURN in response to this prompt. If your system doesE           not have the DECwindows FileView application installed, youiF           will not receive this prompt. Instead, the following message           will be issued:p  I             The DECwindows FileView application files are not present and L             therefore the DECwindows Compiler Interface cannot be installed.  +                                        NOTEl  A               You are no longer prompted to install PPLRTL.EXE inn  G                                            VAX C Installation Guide  13< U               B               SYS$SHARE. If you are installing on a version of VMS?               prior to Version 5.2, a new version of PPLRTL.EXEhA               is moved to SYS$SHARE and is put into IMAGELIB.OLB.eB               The old version of PPLRTL.EXE is not purged from the               system._  B               If you are installing on VMS Version 5.2, PPLRTL.EXEA               is included with your system and VAXCPAR.OLB is note               required.   .           Step 8: Read informational messages.  C           The VAX C installation procedure produces a number of in-rA           formational messages that report on the progress of the            installation.a  F           The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE filesC           are updated to include the new versions of the VAX C HELPa@           text and the CC command-line definition, respectively.  L             Your VMS system will now be updated to include the following new             and modified files:a  7             SYS$SYSTEM:VAXC.EXE                   [new]n7             SYS$LIBRARY:VAXCDEF.TLB               [new]u7             SYS$LIBRARY:VAXCSPR.DAT               [new] 7             SYS$MESSAGE:VAXCERR.EXE               [new]s7             SYS$HELP:VAXC031.RELEASE_NOTES        [new]e<             SYS$HELP:HELPLIB.HLB                  [modified]<             SYS$LIBRARY:DCLTABLES.EXE             [modified]7             SYS$COMMON:[SYSTEST]VAXC$IVP.COM      [new]y7             SYS$COMMON:[SYSTEST.VAXC]VAXCIVPP.C   [new] 7             SYS$COMMON:[SYSTEST.VAXC]VAXCIVPC.C   [new] 7             VUE$LIBRARY:CC$DWCI.EXE               [new] 7             VUE$LIBRARY:CC$DWCI.UID               [new] 7             SYS$HELP:CC$DWCI.HLB                  [new] 7             VUE$LIBRARY:VUE$COMPILE.COM           [new]e  D           If you typed YES in response to the prompt that requests aD           file purge at step 7, previous versions of the VAX C files/           are now purged except for PPLRTL.EXE.n  #        14  VAX C Installation Guide                  G           The success of the installation is indicated by the following_           message:  K             %VMSINSTAL-I-MOVEFILES, files will now be moved to their targett             directories...  A           If the installation procedure is successful, the new ori?           modified files are moved to their target directories.s  B           Step 9: Observe the Installation Verification Procedure.  D           If you chose to run the IVP in step 7, VMSINSTAL now callsB           the IVP to verify that VAX C was successfully installed.  F                VAX C V3.1-001 Installation Verification Procedure  ...      O             ****** VAX C Installation Certification Procedure SUCCESSFUL ******         Y                VAX C V3.1-001 Installation Verification Procedure completed successfully.l  2           Step 10: End the installation procedure.  ;                Installation of VAX C 3.1 completed at 17:32n  0                VMSINSTAL procedure done at 17:33               $ LOGOUT <RETURN> <             SYSTEM     logged out at 11-OCT-1988 17:34:00.00  B           When the product installation procedure is complete, youE           can choose to install more products or to log out (as shown,G           here.) If you removed any media from the console drive beforet@           beginning the installation, you should replace it now.  G                                            VAX C Installation Guide  15o e  e            D           VMSINSTAL deletes or changes entries in the process symbolE           tables during the installation. Therefore, if you are goingsE           to continue using the system manager's account and you want A           to restore these symbols, you should log out and log inp           again.  C        ____________________________________________________________   '        Installing VAX C on a VAXclusterG  E           If you want to run VAX C on multiple nodes of a VAXcluster,oC           first check to see that you have the appropriate software C           license. Then, follow these steps after installing VAX C:   F            1.Issue the LICENSE LOAD command to activate the license onE              each node in the VAXcluster on which VAX C is to be exe-eE              cuted as described in the VMS License Management Utilityr              Manual.  A            2.To use the product on other nodes in the VAXcluster,RC              you must replace the version of the DCL tables that is A              installed on the other VAXcluster nodes. To do this,A)              perform the following steps:l  0               a.Log in to a node on the cluster.  B               b.Run INSTALL and enter the following command at the                  INSTALL> prompt:  E                   INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <RETURN>k  B               c.Repeat steps a and b for each node of the cluster.              #        16  VAX C Installation Guide  0               C        ____________________________________________________________L          Installing VAX DEBUG MP  E           This section contains excerpts from the installation proce- E           dure for the VMS Debugger for multiprocess debugging (DEBUG E           MP) provided with VAX C Version 3.1 and explains each step.eF           Defaults appear in brackets throughout the installation pro-           cedure.e  +                                        NOTEo  ?               VAX C will install on Version 5.0 and higher. VAXtC               DEBUG MP only installs on Version 5.0-001 and higher. ?               However, VAX DEBUG MP will not install on Version_B               5.2 and higher because those versions of VMS already9               contain a debugger with this functionality.h  @           To abort the installation procedure at any time, pressC           CTRL/Y. When you press CTRL/Y, the installation procedurerD           deletes all files it has created up to that point and thenF           returns you to DCL level. If you want to retry the installa-E           tion procedure after pressing CTRL/Y, you must proceed from            step 2.   E           Step 1: Log in to a privileged account and set your defaulte-           device and directory to SYS$UPDATE.           <RETURN>   &             Username: SYSTEM  <RETURN>&             Password:         <RETURN>-             $ SET DEFAULT SYS$UPDATE <RETURN>             G                                            VAX C Installation Guide  17R R               #           Step 2: Invoke VMSINSTAL.   <             $ @VMSINSTAL DEBUGMP050 CSA1: OPTIONS N <RETURN>  F                   VAX/VMS Software Product Installation Procedure V5.0  '             It is 17-AUG-1988 at 17:35. ;             Enter a question mark (?) at any time for help.i  G             %VMSINSTAL-W-DECNET, Your DECnet network is up and running.t  ?             * Do you want to continue anyway [NO]? YES <RETURN>   S             * Are you satisfied with the backup of your system disk [YES]? <RETURN>e  C           If you are satisfied with the backup of your system disk,aG           press RETURN. Otherwise, enter NO and press RETURN to discon- !           tinue the installation.t  ;           Step 3: Insert the first installation kit volume.f  >             Please mount the first volume of the set on CSA1:.)             * Are you ready? YES <RETURN>o5             The following products will be processed:                  DEBUGMP V5.0  ?                 Beginning installation of DEBUGMP V5.0 at 17:37c  @             %VMSINSTAL-I-RESTORE, Restoring product saveset A...  G           To indicate that you want to continue the installation, mount /           volume 1, type YES, and press RETURN.i  A           Step 4: Insert the subsequent installation kit volumes.n  E             %BACKUP-I-READYREAD, mount volume 2 on _CSA1: for reading   /             Enter "YES" when ready: YES<RETURN>t  #        18  VAX C Installation Guideo p  E            G           VMSINSTAL prompts you to insert the next volume and waits for.G           you to type YES after inserting it. If you type NO, VMSINSTALiE           displays the prompt again. This prompt is displayed only ift>           your installation kit contains more than one volume.  0           Step 5: Select a release notes option.  F           This step applies only if you specified OPTIONS N in step 2.  "             Release Notes Options:  *                  1.  Display release notes(                  2.  Print release notes!                  3.  Both 1 and 2 3                  4.  Copy release notes to SYS$HELP A                  5.  Do not display, print, or copy release notes   )             * Select option [2]: <RETURN>   F           If you select option 1, VMSINSTAL displays the release notesC           on line immediately. You can terminate the display at anygA           time by pressing CTRL/C. After you view them, VMSINSTALa/           copies the release notes to SYS$HELP.   C           If you select option 2, VMSINSTAL prompts you for a queuepD           name. Either type a queue name or press RETURN to send theB           file to the default output print device. After you print?           them, VMSINSTAL copies the release notes to SYS$HELP.e  .             * Queue name [SYS$PRINT]: <RETURN>  F           If you select option 3, VMSINSTAL displays the release notesC           on line immediately. You can terminate the display at anygC           time by pressing CTRL/C. VMSINSTAL then prompts you for ahF           queue name. Either type a queue name or press RETURN to sendG           the file to the default output print device. The VAX DEBUG MPn4           release notes are then copied to SYS$HELP.  G           If you select option 4, VMSINSTAL copies the release notes toe           SYS$HELP immediately.n  G                                            VAX C Installation Guide  19s                 G           If you select option 5, VMSINSTAL does not display, print, oro!           copy the release notes.   +                                        NOTE   A               This version of the release notes file installed by D               VMSINSTAL is labeled with the current product name andC               version number. Take care not to delete release notes 4               for previous versions of the debugger.  8           Next, VMSINSTAL displays the following prompt:  H             Do you want to continue the installation [NO]?: YES <RETURN>G             %VMSINSTAL-I-RELMOVED, The products release notes have beenaB                                    successfully moved to SYS$HELP.  F           If you want to continue the installation, type YES and pressB           the RETURN key. If you enter NO or press the RETURN key,2           VMSINSTAL discontinues the installation.  .           Step 6: Select installation options.  V             * Do you want to purge files replaced by this installation [YES]? <RETURN>  A           The directories SYS$HELP, SYS$LIBRARY, SYS$MESSAGE, and F           SYS$MANAGER may contain previous versions of debugger files.C           These files are replaced during the installation with new @           files, but the old files are not automatically purged.D           Purging is recommended. In response to the purging prompt,B           press RETURN to purge the files or type NO to keep them.  .           Step 7: Read informational messages.  B           The DEBUG MP installation procedure produces a number ofC           informational messages that report on the progress of the            installation.n      #        20  VAX C Installation Guide                  O                Your VMS system will now be updated to include the following new "                and modified files:  6                 SYS$LIBRARY:DEBUG.EXE            [new]6                 SYS$LIBRARY:DEBUGSHR.EXE         [new]6                 SYS$LIBRARY:TRACE.EXE            [new]6                 SYS$MESSAGE:DBGTBKMSG.EXE        [new]6                 SYS$HELP:DBG$HELP.HLB            [new]6                 SYS$MANAGER:DEBUGSTART.COM       [new]6                 SYS$HELP:DEBUG050MP.RELEASE_NOTES[new]  H                 If your VAX is part of a VAXcluster, you *must* manuallyL                 invoke the file SYS$MANAGER:DEBUGSTART.COM on all the memberL                 nodes of your VAXcluster, after this installation completes.  L                 It will use the INSTALL utility to make the new images knownI                 to the system on each node. This is automatically done byeN                 VMSINSTAL on your local VAX. If you fail to do this, DEBUG andJ                 TRACE will not operate properly. You should also add theseM                 commands to SYS$MANAGER:SYSTARTUP.COM if they are not alreadyg                 there.  H                 The file DEBUGSTART.COM contains the following commands:  6                 $ INSTALL:=$SYS$SYSTEM:INSTALL/COMMAND                 $ INSTALLaB                 REPLACE/OPEN/HEADER/SHARED   SYS$LIBRARY:DEBUG.EXEE                 REPLACE/OPEN/HEADER/SHARED   SYS$LIBRARY:DEBUGSHR.EXEVF                 REPLACE/OPEN/HEADER/SHARED   SYS$LIBRARY:DBGTBKMSG.EXEB                 REPLACE/OPEN/HEADER/SHARED   SYS$LIBRARY:TRACE.EXT                 EXIT  B           If you typed YES in response to the prompt that requestsC           a file purge, previous versions of debugger files are now            purged.f  C           The end of the installation is indicated by the followingt           message:  D             %VMSINSTAL-I-MOVEFILES, Files will now be moved to their9                                     target directories...?  G                                            VAX C Installation Guide  21n                 1           Step 8: Verify successful installation.   A           The installation procedure now invokes the Installation G           Verification Procedure (IVP) to verify that DEBUG MP was suc- F           cessfully installed. If DEBUG MP was successfully installed,1           the IVP displays the following message:t  #                 Beginning DEBUG IVPt  Q                      ************************************************************lQ                      *                                                          *fQ                      *    I N S T A L L A T I O N    V E R I F I C A T I O N    *aQ                      *                                                          * Q                      *     P R O C E D U R E   h a s   S u c c e e d e d  !     * Q                      *                                                          *aQ                      ************************************************************   1           Step 9: End the installation procedure.i  >                Installation of DEBUGMP V5.0 completed at 17:50  0                VMSINSTAL procedure done at 17:51               $ LOGOUT <RETURN> 9             SYSTEM     logged out at 17-AUG-1988 17:53:10f  C           When the product installation is complete, you can choose,E           to install more products or log out (as shown here). If you G           removed any media from the console drive before beginning thed2           installation, you should replace it now.  D           VMSINSTAL deletes or changes entries in the process symbolE           tables during the installation. Therefore, if you are goinggE           to continue using the system manager's account and you wanthA           to restore these symbols, you should log out and log ino           again.  D           If you performed the installation on a cluster common sys-@           tem disk and you will not be rebooting the cluster af-C           ter completing the installation, you must invoke the filepA           SYS$MANAGER:DEBUGSTART.COM on each node of the cluster.i  #        22  VAX C Installation Guide  i  n            C        ____________________________________________________________p          After the Installationl  E           VAX C is now installed and can be invoked by all users withE           the CC command.   F           The installation procedure modifies the DCL command table so           that theG           CC command is recognized and processed. However, the previous B           command table is still in effect for those users who areF           currently logged in. All logged-in users who want to use theD           CC command for the newly installed product must log out of&           the system and log in again.  B           To ensure that the debugger will operate properly, checkB           that DEBUGSTART.COM is invoked by SYS$MANAGER:SYSTARTUP_C           V5.COM. If it is not already invoked by the site-specific A           startup procedure, edit SYS$MANAGER:SYSTARTUP_V5.COM to             invoke DEBUGSTART.COM.  C        ____________________________________________________________   A        Running the Installation Verification Procedure Separatelyg  F           The Installation Verification Procedure (IVP) is usually runC           at installation. If you want to run the IVP separately touD           ensure the integrity of installed files if system problems9           occur, execute the following command procedure:s  9             $ @SYS$SYSROOT:[SYSTEST]VAXC$IVP.COM <RETURN>   E           If the IVP fails for any reason, the following messages are            displayed:               The VAX C 3.1 7             Installation Verification Procedure failed. P             Please consult the VAX C Installation Guide for further information.  C             %VMSINSTAL-E-IVPFAIL, The IVP for VAX C 3.1 has failed.E  G                                            VAX C Installation Guide  23E X               C        ____________________________________________________________           Error ConditionsS  G           If the installation procedure fails for any reason, a message *           like the following is displayed:  L             %VMSINSTAL-E-INSFAIL, The installation of VAX C V3.1 has failed.  F           An error during the installation can occur if one or more of)           the following conditions exist:   7            o The operating system version is incorrect.   <            o The prerequisite software version is incorrect.  A            o Quotas necessary for successful installation are in- D              sufficient (see the Installation Procedure Requirements              section).  D            o Process quotas required by VMSINSTAL are incorrect (see*              the Using VMSINSTAL section).  6            o The VMS HELP library is currently in use.  E            o The PAK for VAX C was registered incorrectly, not regis-o               tered, or unloaded.  C           For descriptions of the error messages generated by thesec>           conditions, see the VMS System Messages and RecoveryD           Procedures Reference Volume or your processor-specific in-&           stallation/operations guide.  E           If you are notified that any of these conditions exist, you E           should take the appropriate action as described in the mes- E           sage. You may need to change a system parameter or increaser$           an authorized quota value.  F           If the installation fails, you must restart the installationD           procedure from step 2. If the installation fails due to anF           IVP failure, contact a Digital field service representative.  #        24  VAX C Installation Guide                  C        ____________________________________________________________e  )        Installing VAX C as a Shared Imageh  C           If VAX C will be used extensively on your system, you canbC           reduce the system overhead and memory requirements by in-oD           stalling it as a shared image. To perform the installationD           on a system that is currently running, use the VMS InstallB           Utility while you are logged in to a privileged account.C           If errors occur, see the VMS System Messages and Recoveryt&           Procedures Reference Volume.  ?           First, determine the number of available global pages B           and global sections on your system. See the InstallationE           Procedure Requirements section for information on how to do            this.r  E           Then, invoke the VMS Install Utility and install VAX C as ae8           shared image by typing the following commands:  -             $ RUN SYS$SYSTEM:INSTALL <RETURN>C  A             INSTALL> ADD SYS$SYSTEM:VAXC.EXE/OPEN/SHARED <RETURN>eE             INSTALL> ADD SYS$MESSAGE:VAXCERR.EXE/OPEN/SHARED <RETURN>e"             INSTALL> EXIT <RETURN>  @           Then, update the system startup file to install VAX C.  B           To ensure that VAX C is installed as a shared image eachF           time the system is bootstrapped, include the following linesD           in SYS$MANAGER:SYSTARTUP_V5.COM (the site-specific startup           file):  /             $ INSTALL :== $INSTALL/COMMAND_MODEo             $ INSTALL 1               ADD SYS$SYSTEM:VAXC.EXE/OPEN/SHAREDo5               ADD SYS$MESSAGE:VAXCERR.EXE/OPEN/SHARED     G                                            VAX C Installation Guide  25     e            C        ____________________________________________________________I          Maintenance Updates  C           Digital may periodically issue maintenance updates of VAX_D           C. Each update consists of an installation kit. You shouldB           install this kit as described in this document or in anyB           documentation that may accompany the maintenance update.  A           Each time a maintenance update is released, the versionlD           number changes. For example, the previous version was 3.0.E           Therefore, the version number of this maintenance update isAG           3.1. In addition, the maintenance update includes new releaseoF           notes. The release notes describe the changes that have been3           made to VAX C since the previous release.   C           The update release notes are provided on line. You shouldtG           read the release notes when you first install VAX C; they arelD           also accessible at any time after the product is installedD           (if option 5 was not selected). For information on readingF           the release notes at the time that you install VAX C, followB           the installation procedure through step 5. To locate theF           release notes after VAX C is installed, display or print theD           file SYS$HELP:VAXC03n.RELEASE_NOTES, or type the following           command:  ,             $ HELP CC RELEASE_NOTES <RETURN>  C        ____________________________________________________________>  )        Determining and Reporting ProblemsN  F           If an error occurs while you are using VAX C and you believeG           that the error is caused by a problem with VAX C, take one of             the following actions:  C            o If you purchased VAX C within the past 90 days and youuE              think the problem is caused by a software error, you can58              submit a Software Performance Report (SPR).  #        26  VAX C Installation GuideE Y               B            o If you have a Basic or DECsupport Software Agreement,D              call your Customer Support Center. With these services,C              you receive telephone support that provides high-levelsD              advisory and remedial assistance. For more information,7              contact your local Digital representative.   G            o If you have a Self-Maintenance Software Agreement, you can 8              submit a Software Performance Report (SPR).  G           If you find an error in the VAX C documentation, fill out and G           submit a Reader's Comments form from the back of the document0D           in which the error was found. Include the section and page+           number where the error was found.   C        ____________________________________________________________           Sample Installation  D           This section contains a sample installation of VAX C. NoteG           that this is only a sample. Sometimes the installation proce-RB           dure is modified in maintenance updates of this product.@           Because this installation guide is not usually revisedB           for maintenance updates, be sure to read the Read BeforeB           Installing or Using VAX C letter before you install thisC           product. This letter notes any significant changes in the.2           installation that vary from this sample.  E           The sample installation shown here is divided into two seg-t           ments:  (            o A sample VAX C installation  A            o A sample VMS Debugger for multiprocessing (DEBUG MP)i              installation           G                                            VAX C Installation Guide  273 B               $           Sample VAX C Installation:  -                     Welcome to VAX/VMS V5.0-2,  %             Username: SYSTEM <RETURN>              Password: <RETURN><              Welcome to VAX/VMS version V5.0-2 on node XXXXXD                 Last interactive login on Tuesday, 31-OCT-1989 19:09H                 Last non-interactive login on Tuesday, 31-OCT-1989 13:27$             $ set default sys$update0             $ @vmsinstal vaxc031 Csa1: options n  J                     VAX/VMS Software Product Installation Procedure V5.0-2  '             It is 31-OCT-1989 at 19:12. ;             Enter a question mark (?) at any time for help.   G             %VMSINSTAL-W-DECNET, Your DECnet network is up and running. ?             * Do you want to continue anyway [NO]? yes <RETURN>pS             * Are you satisfied with the backup of your system disk [YES]? <RETURN>t  5             The following products will be processed:C                 VAXC V3.1t  @                     Beginning installation of VAXC V3.1 at 19:13  A             %VMSINSTAL-I-RESTORE, Restoring product saveset A ...c  &                 Release Notes Options:  -                     1.  Display release notesy+                     2.  Print release notesa$                     3.  Both 1 and 26                     4.  Copy release notes to SYS$HELPC                     5.  Do not display, print or copy release notesl  "             * Select option [2]: 4@             * Do you want to continue the installation? <RETURN>U             %VMSINSTAL-I-RELMOVED, The product's release notes have been successfullye5                                    moved to SYS$HELP.   A                     VAX C V3.1-001 Installation is commencing ...   #        28  VAX C Installation Guide                  #                     Product:      Ce%                     Producer:     DECo%                     Version:      3.1i-                     Release Date: 14-AUG-1989   P             * Does this product have an authorization key registered and loaded?U                                                                          YES <RETURN>   D             This kit contains an Installation Verification ProcedureD             (IVP) to verify the  correct  installation of the VAX  C             compiler.   D             After the  installation is  complete, you can invoke the?             IVP at any time to reverify that VAX C is installed ;             and working correctly by executing the command:   #                  @SYS$TEST:VAXC$IVPv  O             * Do you want to run the IVP after the installation [YES]? <RETURN>tV             * Do you want to purge files replaced by this installation [YES]? <RETURN>S             * Do you want to extract .H files from the text library [YES]? <RETURN>E  >              All the questions regarding the installation have@              now been asked.  The installation will now continue=              for between 20 and 60 minutes, depending on youre;              CPU type and the installation options you havea              chosen.  A             %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Q                     VAX C V3.1-001 : copying images, libraries and release notes.d9                     VAX C V3.1-001 : extracting .H files.   Q             A summary of the Software Performance Reports (SPRs) for this releaseY=             can be found in the file SYS$LIBRARY:VAXCSPR.DAT.G  >                      VAX C V3.1-001 Installation is completed.  L             Your VMS system will now be updated to include the following new             and modified files:E  G                                            VAX C Installation Guide  29u u               I                     SYS$SYSTEM:VAXC.EXE                             [new] I                     SYS$LIBRARY:VAXCDEF.TLB                         [new].I                     SYS$LIBRARY:VAXCSPR.DAT                         [new]kI                     SYS$MESSAGE:VAXCERR.EXE                         [new]eI                     SYS$HELP:VAXC031.RELEASE_NOTES                  [new]DN                     SYS$HELP:HELPLIB.HLB                            [modified]N                     SYS$LIBRARY:DCLTABLES.EXE                       [modified]I                     SYS$COMMON:[SYSTEST]VAXC$IVP.COM                [new]tI                     SYS$COMMON:[SYSTEST.VAXC]VAXCIVPP.C             [new]AI                     SYS$COMMON:[SYSTEST.VAXC]VAXCIVPC.C             [new]/I                     SYS$LIBRARY:VAXCPAR.OLB                         [new] I                     VUE$LIBRARY:CC$DWCI.EXE                         [new]SI                     VUE$LIBRARY:CC$DWCI.UID                         [new]BI                     SYS$HELP:CC$DWCI.HLB                            [new]nI                     VUE$LIBRARY:VUE$COMPILE.COM                     [new]fI                     SYS$LIBRARY:PPLRTL.EXE                          [new]sZ             %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  M             VAX C V3.1-001 Installation Verification Procedure commencing ...g    O             ****** VAX C Installation Certification Procedure SUCCESSFUL ******u  V             VAX C V3.1-001 Installation Verification Procedure completed successfully.  8             Installation of VAXC V3.1 completed at 19:52  -             VMSINSTAL procedure done at 19:53y  '           Sample DEBUG MP Installation:l  -             $ SET DEFAULT SYS$UPDATE <RETURN>eA             $ @VMSINSTAL DEBUGMP050 SYS$UPDATE OPTIONS N <RETURN>   H                     VAX/VMS Software Product Installation Procedure V5.0  '             It is 17-AUG-1988 at 17:35. ;             Enter a question mark (?) at any time for help.   #        30  VAX C Installation Guide                  G             %VMSINSTAL-W-DECNET, Your DECnet network is up and running. ?             * Do you want to continue anyway [NO]? YES <RETURN> S             * Are you satisfied with the backup of your system disk [YES]? <RETURN>   5             The following products will be processed:                  DEBUGMP V5.0  C                     Beginning installation of DEBUGMP V5.0 at 17:35   A             %VMSINSTAL-I-RESTORE, Restoring product saveset A ...t  &                 Release Notes Options:  -                     1.  Display release notes +                     2.  Print release notes $                     3.  Both 1 and 26                     4.  Copy release notes to SYS$HELPD                     5.  Do not display, print, or copy release notes  )             * Select option [2]: <RETURN> .             * Queue name [SYS$PRINT]: <RETURN>L             Job DEBUG050MP (queue SYS_PRINT, entry 316) started on node_LPA0  D             * Do you want to continue the installation? YES <RETURN>I             %VMSINSTAL-I-RELMOVED , The product's release notes have been C                                     successfully moved to SYS$HELP.eV             * Do you want to purge files replaced by this installation [YES]? <RETURN>  C                 Your VMS system will now be modified to include thed$                 following new files:  7                 SYS$LIBRARY:DEBUG.EXE             [new]n7                 SYS$LIBRARY:DEBUGSHR.EXE          [new]a7                 SYS$LIBRARY:TRACE.EXE             [new] 7                 SYS$MESSAGE:DBGTBKMSG.EXE         [new]_7                 SYS$HELP:DBG$HELP.HLB             [new]e7                 SYS$MANAGER:DEBUGSTART.COM        [new]n7                 SYS$HELP:DEBUG050MP.RELEASE_NOTES [new]   H                 If your VAX is part of a VAXcluster, you *must* manuallyL                 invoke the file SYS$MANAGER:DEBUGSTART.COM on all the memberL                 nodes of your VAXcluster, after this installation completes.  G                                            VAX C Installation Guide  31e                 L                 It will use the INSTALL utility to make the new images knownI                 to the system on each node. This is automatically done by,N                 VMSINSTAL on your local VAX. If you fail to do this, DEBUG andJ                 TRACE will not operate properly. You should also add theseM                 commands to SYS$MANAGER:SYSTARTUP.COM if they are not alreadyG                 there.  H                 The file DEBUGSTART.COM contains the following commands:  6                 $ INSTALL:=$SYS$SYSTEM:INSTALL/COMMAND                 $ INSTALLrA                 REPLACE/OPEN/HEADER/SHARED  SYS$LIBRARY:DEBUG.EXE.D                 REPLACE/OPEN/HEADER/SHARED  SYS$LIBRARY:DEBUGSHR.EXEE                 REPLACE/OPEN/HEADER/SHARED  SYS$MESSAGE:DBGTBKMSG.EXEeA                 REPLACE/OPEN/HEADER/SHARED  SYS$LIBRARY:TRACE.EXES                 EXIT  D             %VMSINSTAL-I-MOVEFILES, Files will now be moved to their9                                     target directories...              Beginning DEBUG IVPo  M                  ************************************************************ M                  *                                                          * M                  *    I N S T A L L A T I O N    V E R I F I C A T I O N    *uM                  *                                                          *_M                  *     P R O C E D U R E   h a s   S u c c e e d e d  !     * M                  *                                                          *pM                  ************************************************************f  C                     Installation of DEBUGMP V5.0 completed at 22:28r  5                     VMSINSTAL procedure done at 22:29               #        32  VAX C Installation Guidet