--------------------

NOTES
=====


Missing pre-requisite software:

        - LSE (Required by several different products)
        - FMS (Required by CDD & RDB)

General:

        Install the compilers first. Some of the layered products
        check for languages in the IVP and test any which have
        been installed.

        DTR downgraded to version 4.1 as DTR 4.2 requires CDD VT4.0-0
        which I don't have available. Also fails the remote database
        test but the installation completes.

        RDB also fails the remote database test. The cause may possibly
        be in the NCP definitions.

        VAXC installs both versions 2.3 and 2.4, but both fail the IVP
        with the message: ERROR in vfork/exec test #13

        CMU-TEK-65 came from the archives at the University of Stuttgart,
        and appears to contain a TCPIP stack which may work on VMS 4
        systems. There is a mail exchange and socket layer included, but
        as this goes beyond what I'm trying to achieve (using DEC products)
        I have not done any testing. I can confirm that the .SAV files are
        indeed readable VMS Backup savesets and appear to contain several
        versions of the software.

Andy Hoffman
SenaCal Consulting Ltd. UK
21 February 2019

--------------------
BASIC032.DIR;1            ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal basic dua3:[products.basic032]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:54.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  BASIC V3.2


        Beginning installation of BASIC V3.2 at 06:54

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.

                VAX BASIC V3.2 Installation Procedure

   There are three possible installation options. They are described
   as follows: 

   1) Perform a normal installation of BASIC. 

   2) Install VAX/VMS system definitions text library only (10-45 minutes).

   3) Obtain a copy of the BASIC message text for modification. 

* Which option do you want to use [1]: 
* Do you want to install the BASIC HELP files [YES]? 
* Do you want to install the VAX/VMS system definitions [YES]? 
* Do you want to install the sample graphics programs [YES]? 
* Do you want to purge files replaced by this installation [YES]? 
%VMSINSTAL-I-RESTORE, Restoring product saveset B...

    ************************************************************************
    If you have VAX GKS V2.0 or later on your system, VAX BASIC V3.2 allows 
    you to use graphics language statements.  The procedure:

        SYS$UPDATE:BASIC$GRAPHICS_IVP.COM

    will verify that VAX BASIC graphics capabilities work on your system.
    You must execute this procedure on a terminal with graphics capabilities.
    ************************************************************************

%VMSINSTAL-I-INSHELP, Installing BASIC Help files
%VMSINSTAL-I-RESTORE, Restoring product saveset C...
%VMSINSTAL-I-INSSTARLET, Installing BASIC system definitions
%VMSINSTAL-I-INSSTARLT1, Requires approximately 10 to 45 minutes
%VMSINSTAL-I-RESTORE, Restoring product saveset D...
%VMSINSTAL-I-INSSAMPLE, Installing sample programs and PICTURE libraries
%VMSINSTAL-I-RESTORE, Restoring product saveset E...
%VMSINSTAL-I-RESTORE, Restoring product saveset F...
%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.BASIC].

    *********************************************************************
    A number of sample programs demonstrating BASIC graphics statements
    have been copied to [SYSHLP.EXAMPLES.BASIC].  

    Read [SYSHLP.EXAMPLES.BASIC]BASIC_EXAMPLES.TXT for information on the 
    sample programs provided.
    *********************************************************************

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%VMSINSTAL-I-RUNIVP, Executing installation verification procedure

%VMSINSTAL-I-IVPSUCCESS, VAX BASIC V3.2 Installation test PASSED

        Installation of BASIC V3.2 completed at 06:55



        VMSINSTAL procedure done at 06:55


--------------------
BLS32044.DIR;1            ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal bls32 dua3:[products.bls32044]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:56.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  BLS32 V4.4


        Beginning installation of BLS32 V4.4 at 06:56

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.
%VMSINSTAL-I-RESTORE, Restoring product saveset B...

* Do you want to purge files replaced by this installation [YES]? 
* Do you want to run the IVP after the installation [YES]? 

        This kit contains a  file  summarizing the new features, changes,
        restrictions,  and  compatibility issues  in this release of  VAX
        BLISS-32.  This file is named  BLS32044.RELEASE_NOTES and will be
        placed in SYS$HELP:.

        The  release notes  contains information valuable to VAX BLISS-32
        programmers.   Please  inform  your  VAX  BLISS-32  users of this
        file's existence.

        The BLISS help file contains extensive documentation on the BLISS
        language.  Since this material  requires about 525 blocks of disk
        space, its inclusion is optional.

* Do you want the long help file [YES]? 

%BLS32-I-LIBBUILD, Building the precompiled libraries

        This phase of the installation process compiles the STARLET, LIB,
        and TPAMAC L32 files.  The corresponding REQ  files  are expected
        to  be  in  SYS$LIBRARY.   If one is missing,  you will receive a
        warning message and that library file will not be created.   This
        will not interfere with the rest of the installation.


        All questions regarding the installation have now been asked.
        The system directories will now be updated.  The installation
        of VAX BLISS-32 V4.4  will  be complete in approximately 5 to
        15 minutes.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

%BLS32-I-IVP, Performing Installation Verification Procedure


     ***************************
       Successful Installation
                 of
        VAX Bliss-32 V4.4-838   
     ***************************



        Installation of BLS32 V4.4 completed at 06:57



        VMSINSTAL procedure done at 06:57


--------------------
CDD034.DIR;1              ===> INSTALLATION SUCCESSFUL BUT NEEDS LSE.
                          ===> INSTALL LSE THEN REINSTALL CDD

TSTVAX::SYSTEM <!> @sys$update:vmsinstal cdd dua3:[products.cdd034]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 07:02.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  CDD V3.4


        Beginning installation of CDD V3.4 at 07:02

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.

    *************************************************************

    The VAX Language-Sensitive Editor is not installed on your 
    system.  To have the VAX Language-Sensitive Editor support,
    you must:

        1.  Install the VAX Language-Sensitive Editor
        2.  Install or reinstall this product

    *************************************************************

* Do you want to continue the installation [NO]? yes

    *************************************************************

    The CDD$DICTIONARY  system logical name is used to identify
    the location of the root dictionary file.

    The equivalence string for CDD$DICTIONARY must resolve to a
    device and directory (e.g. DBA0:[SYSEXE]).  You should pick
    a directory on a disk that is always mounted.  We suggest the
    [SYSEXE] directory on your system disk.

    Simply press the RETURN key for the following question if you
    want the dictionary to be placed in SYS$COMMON:[SYSEXE]. Note
    that SYS$COMMON:[SYSEXE] refers to SYS$SYSTEM whether you are
    installing on a cluster or a stand alone system.

    *************************************************************


* Enter the root dictionary file's device and directory: [SYS$COMMON:[SYSEXE]]: 

* Do you want to run the IVP after the installation [YES]? 

    *************************************************************

    When you run the IVP from VMSINSTAL, the IVP creates the log
    file CDDIVP.LOG.  After the IVP runs successfully the log
    file is deleted, unless you explicitly request that it be
    saved.  If an error occurs while running the IVP, the log
    file is saved in SYS$COMMON:[SYSTEST.CDD].

    *************************************************************

* Do you want to print the log file from the IVP [NO]? 

* Do you want to save the log file from the IVP [NO]? 

* Do you want to purge files replaced by this installation [YES]? 


    *************************************************************

    The installation procedure has asked all questions
    required to complete the VAX CDD V3.4-1 installation.

    *************************************************************

%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[SYSTEST.CDD].

    *************************************************************

    Don't forget to edit the system manager's SYSTARTUP.COM
    file to submit the SYS$MANAGER:CDDSTRTUP.COM file when
    the system is booted.

    *************************************************************


    *************************************************************

    The VAX CDD V3.4-1 Installation Verification Procedure
    (IVP) has been provided and can be run after the installation
    is complete.  It is invoked as follows:

        $ @SYS$COMMON:[SYSTEST.CDD]CDDIVP

    *************************************************************

%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[SYSMGR.VAXINFO$PRODUCTS].
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Executing IVP for: VAX CDD V3.4-1


    ************************************

    VAX CDD V3.4-1

    IVP COMPLETED SUCCESSFULLY

    ************************************


IVP completed for: VAX CDD V3.4-1


        Installation of CDD V3.4 completed at 07:02



        VMSINSTAL procedure done at 07:02



--------------------
CMS030.DIR;1              ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal CMS dua3:[products.CMS030]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 07:32.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? YES
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  CMS V3.0


        Beginning installation of CMS V3.0 at 07:32

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.
* Do you want to purge files replaced by this installation [YES]? 
* Do you want to run the IVP after the installation [YES]? 
%CMS-I-DONEASK, No further questions will be asked during this installation
%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%CMS-I-ENDRESTORE, All required savesets have been successfully restored
%CMS-I-CMSPROSHR, Linking protected shareable image
%CMS-I-CMSSHR, Linking shareable image
%CMS-I-CMS, Linking main image
%CMS-I-PROHELP, Providing help
%CMS-I-PRODCL, Providing DCL verb
%CMS-I-PROEXE, Providing images 
%CMS-I-PROSTART, Providing startup procedure

        ****************************************************************
        *                                                              *
        * If this installation is performed on a cluster, you must     *
        * execute @SYS$MANAGER:CMSSTARTUP.COM on all other nodes in    *
        * the cluster.  In addition, you must add the following line   *
        * to your system startup procedure, SYS$MANAGER:SYSTARTUP.COM. *
        *                                                              *
        *             $ @SYS$MANAGER:CMSSTARTUP.COM                    *
        *                                                              *
        ****************************************************************

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%CMS-I-IVPBEGIN, Begin DEC/CMS V3.0 Installation Verification Procedure
$ set noverify
$ cms show version
DEC/CMS Version V3.0
$ cms create library [.cmstest]
%CMS-S-CREATED, CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST] created
%CMS-I-LIBIS, library is VMI$ROOT:[SYSUPD.CMS030.CMSTEST]
%CMS-S-LIBSET, library set
$ cms set library [.cmstest]
%CMS-I-LIBIS, library is VMI$ROOT:[SYSUPD.CMS030.CMSTEST]
%CMS-S-LIBSET, library set
-CMS-I-SUPERSEDE, library list superseded
$ cms create element cms$ivp_test.file ""
%CMS-S-CREATED, element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE created
$ cms reserve cms$ivp_test.file ""
%CMS-S-RESERVED, generation 1 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE reserved
$ cms show reservations

Reservations in DEC/CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST]

CMS$IVP_TEST.FILE
    (1)   SYSTEM     1      21-FEB-2019 07:32:58 ""
$ cms replace cms$ivp_test.file ""
%CMS-S-GENCREATED, generation 2 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE created
-CMS-I-NOCHANGES, no changes
$ cms verify
%CMS-I-VERCLS, class list verified
%CMS-I-VERCMD, command list verified
%CMS-I-VERELE, element list verified
%CMS-I-VERGRP, group list verified
%CMS-I-VERRES, reservation list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERFRE, internal free space list verified
%CMS-I-VERARC, archive control block verified
%CMS-I-VER2, internal contiguous space verified
%CMS-I-VERCON, control file verified
%CMS-I-VEREDF, element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE verified
%CMS-I-VEREDFS, element data files verified
%CMS-I-VERIFIED, library VMI$ROOT:[SYSUPD.CMS030.CMSTEST] verified
$ cms fetch cms$ivp_test.file/gen=1 ""
%CMS-S-FETCHED, generation 1 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE fetched
$ cms fetch cms$ivp_test.file/gen=2 ""
%CMS-I-FILEXISTS, file already exists, VMI$ROOT:[SYSUPD.CMS030]CMS$IVP_TEST.FILE;2 created
%CMS-S-FETCHED, generation 2 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE fetched
$ cms diff cms$ivp_test.file;-1 cms$ivp_test.file;0
%CMS-S-IDENTICAL, files are identical
$ set noverify
$ cms create class cl1 "test1"
%CMS-S-CREATED, class VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CL1 created
$ cms insert generation cms$ivp_test.file/gen=1 cl1 ""
%CMS-S-GENINSERTED, generation 1 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE inserted into class VMI$ROOT:[SYSUPD.C
MS030.CMSTEST]CL1
$ cms create class cl2 "test2"
%CMS-S-CREATED, class VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CL2 created
$ cms insert generation cms$ivp_test.file/gen=2 cl2 ""
%CMS-S-GENINSERTED, generation 2 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE inserted into class VMI$ROOT:[SYSUPD.C
MS030.CMSTEST]CL2
$ cms fetch cms$ivp_test.file/gen=cl2 ""
%CMS-S-FETCHED, generation 2 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE fetched
$ set noverify
$ cms show element

Elements in DEC/CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST]

CMS$IVP_TEST.FILE ""
$ cms show generation/descendants cms$ivp_test.file

Element generations in DEC/CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST]

CMS$IVP_TEST.FILE
  2     21-FEB-2019 07:32:58 SYSTEM ""
  1     21-FEB-2019 07:32:58 SYSTEM ""
  
$ cms show class

Classes in DEC/CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST]

CL1             "test1"
CL2             "test2"
$ cms show generation *.*/gen=cl2/brief

Element generations in DEC/CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST]

CMS$IVP_TEST.FILE/2
$ cms remove generation cms$ivp_test.file cl2 ""
%CMS-S-GENREMOVED, generation 2 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE removed from class VMI$ROOT:[SYSUPD.CMS
030.CMSTEST]CL2
$ cms delete class cl2 ""
%CMS-S-DELETED, class VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CL2 deleted
$ cms remove generation cms$ivp_test.file cl1 ""
%CMS-S-GENREMOVED, generation 1 of element VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CMS$IVP_TEST.FILE removed from class VMI$ROOT:[SYSUPD.CMS
030.CMSTEST]CL1
$ cms delete class cl1 ""
%CMS-S-DELETED, class VMI$ROOT:[SYSUPD.CMS030.CMSTEST]CL1 deleted
$ cms create group gr1 ""
%CMS-S-CREATED, group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR1 created
$ cms create group gr2 ""
%CMS-S-CREATED, group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR2 created
$ cms insert group/noconfirm gr1 gr2 ""
%CMS-S-INSERTED, group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR1 inserted into group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR2
$ cms remove group gr1 gr2 ""
%CMS-S-REMOVED, group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR1 removed from group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR2
$ cms modify group gr1/name=gr3/read_only ""
%CMS-S-MODIFIED, group VMI$ROOT:[SYSUPD.CMS030.CMSTEST]GR1 modified
$ cms show group */brief

Groups in DEC/CMS Library VMI$ROOT:[SYSUPD.CMS030.CMSTEST]

GR2                 GR3
$ set noverify
%CMS-S-IVPSUCCESS, DEC/CMS V3.0 IVP completed successfully
%CMS-I-IVPEND, End Installation Verification Procedure

        Installation of CMS V3.0 completed at 07:32



        VMSINSTAL procedure done at 07:32


--------------------
CMU-TEK-65.DIR;1          ==> NOT INSTALLED <===

--------------------
COBOL041.DIR;1            ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal cobol dua3:[products.cobol041]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 07:40.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  COBOL V4.1


        Beginning installation of COBOL V4.1 at 07:40

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved t
o SYS$HELP.
    
        The ANSI/Terminal-Format REFORMAT Utility may optionally be installed.

* Do you want the REFORMAT Utility installed  [YES]? 
* Do you want to run the IVP after the installation [YES]? 
* Do you want to leave COBOLIVP.COM in the [SYSTEST] directory [YES]? 

 This installation procedure creates a new version of some or all
 of the following files:

        [SYSEXE]COBOL.EXE
        [SYSEXE]REFORMAT.EXE
        [SYSLIB]DCLTABLES.EXE
        [SYSTEST]COBOLIVP.COM
        [SYSHLP]COBOL041.RELEASE_NOTES
        [SYSLIB]LSE$SYSTEM_ENVIRONMENT.ENV

* Do you want to purge files replaced by this installation [YES]? 
%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%VMSINSTAL-I-RESTORE, Restoring product saveset C...
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

        Start of VAX COBOL Installation Verification Procedure 

        Successful test of VAX COBOL V4.1-29             

        Installation of COBOL V4.1 completed at 07:40



        VMSINSTAL procedure done at 07:40



--------------------
DECNET.DIR;1         ===> INSTALLATION SUCCESSFUL (Installed as part of VMS setup)
--------------------
DIL020.DIR;1              ===> INSTALLATION SUCCESSFUL BUT
                          ===> INSTALL FORTRAN FIRST
                          ===> RE-RUN IVP AFTER ALL LANGUAGES INSTALLED.

TSTVAX::SYSTEM <!> @sys$update:vmsinstal dil dua3:[products.dil020]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:49.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  DIL V2.0


        Beginning installation of DIL V2.0 at 06:49

%VMSINSTAL-I-RESTORE, Restoring product saveset A...


                     DATA INTERCHANGE LIBRARY (DIL)

                             Installation

                              Version 2.0


* Do you want to purge files replaced by this installation [YES]? 

    This kit contains a complete set of DIL sources for VMS. They will
    be installed in on the system device directory [DIL]. If this
    directory does not presently exist, this installation procedure
    will create it.  

%VMSINSTAL-I-SYSDIR, This product creates system directory [DIL].
%CREATE-I-EXISTS, VMI$ROOT:[DIL] already exists
%CREATE-I-EXISTS, VMI$SPECIFIC:[DIL] already exists

If you intend to execute this layered product on other nodes in your
VAXcluster, and you have the appropriate software license, you must
prepare the system-specific roots on the other nodes by issuing the
following command on each node (using a suitably privileged account):

        $ CREATE /DIRECTORY SYS$SPECIFIC:[DIL] 

  This package includes a copy of the DIL Beware file (called DIL.BWR)
  which will be placed in SYS$UPDATE.

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...


  WARNING:  You need SYSNAM privilege to run the Installation
            Verification Proceedure.  If you do not have SYSNAM
            privilege, certain of the programs will fail with the
            error code 15302676.


  Please wait while the installation verification is run...



  First, let's see if you have COBOL installed on your system.

%DIRECT-W-NOFILES, no files found

  Since COBOL is not installed on this system, the COBOL IVP tests
  cannot be run.


  Now, let's see if you have FORTRAN installed on your system.


Directory SYS$COMMON:[SYSEXE]

FORTRAN.EXE;1       

Total of 1 file.

  Since FORTRAN is installed on your system, the FORTRAN IVP tests
  will be run.

Doing conversions
Tests through 15 completed successfully
Tests through 22 successfully completed
Tests through 24 successfully completed
F32T2 successfully completed
NFOPP Status return:            1
NFOPA Status return:            1
NFGND Status return:     15303467
NFACC Status return:            1
Enter some data to be sent over the link: 
NFSND Status return:            1
NFRCV Status return:            1
Data received: 
This is data for FT32T1 for the first send                                      
Enter some data to be sent over the link: 
NFSND Status return:            1
NFRCV Status return:            1
Data received: 
This is data for FT32T1 for the second send                                     
NFCLS Status return:            1
FT32T1 test successful. 
FORTRAN STOP
ROPEN status return:          1
Enter data for the record: 
RWRITE status return:          1
RCLOSE status return:          1
ROPEN status return:          1
RREAD status return:          1
The record read was: 
This is data for FD32T1 for writing to the remote file DAP.TST.                                     
RCLOSE status return:          1
** FD32T1 test successful ** 
FORTRAN STOP


  FORTRAN Tests completed.



        IVP FOR DIL V2.0 COMPLETED.



        Installation of DIL V2.0 completed at 06:49



        VMSINSTAL procedure done at 06:49



--------------------
DTR042.DIR;1              ===> INSTALLATION FAILED  <===
                          ===> REQUIRES CDD VT4.0-0 <===
--------------------
DTR041.DIR;1

TSTVAX::SYSTEM <!> @sys$update:vmsinstal dtr dua3:[products.dtr041]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 08:50.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  DTR V4.1


        Beginning installation of DTR V4.1 at 08:50

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved t
o SYS$HELP.
* Do you want to use default answers for all questions [NO]? 

    *************************************************************

    The VAX Language-Sensitive Editor is not installed on your 
    system.  To have the VAX Language-Sensitive Editor support,
    you must:

        1.  Install the VAX Language-Sensitive Editor
        2.  Install or reinstall this product

    *************************************************************

* Do you want to continue the installation [NO]? yes

    **************************************************************

    No Forms Management product has been found on this
    system. If desired, the installation may be aborted
    at this point to install a Forms Management product.
    If the installation continues, VAX DATATRIEVE will
    be built without Forms Management support.

    **************************************************************

* Do you wish to continue with the installation [YES]? 

    It is possible to do more than one installation of this
    version of VAX DATATRIEVE.  More than one installation of a
    single version may be desirable for a number of reasons
    including: 

        o Use of multiple forms management products

        o Use of multiple foreign language translations of VAX
          DATATRIEVE (such as French or German)

* Do you plan to install this version more than once [NO]? 
* Do you wish to leave the DATATRIEVE library online [NO]? 
* Do you want NEWUSER to create CDD directories for new users [YES]? 
* What would you like the parent dictionary directory to be [CDD$TOP.DTR$USERS]:
 
* Do you want DTRSHR.EXE and DTRMSGS.EXE to be installed SHARED [YES]? 
* Do you want DTR32.EXE to be installed SHARED [YES]? 
* Do you want DDMF.EXE to be installed SHARED [YES]? 
* Do you wish to have the plot definitions [YES]? 

    Some optional material is available with this kit including
    the components of VAX DATATRIEVE that can be tailored at
    the installed site.

* Do you want the optional material [NO]? 

    This version of VAX DATATRIEVE makes obsolete some files
    from previous versions of VAX DATATRIEVE.

* Do you want ALL the obsolete files deleted [YES]? 
* Do you want to purge files replaced by this installation [YES]? 

    All questions regarding the installation have now been asked.

    The installation of VAX DATATRIEVE will now continue for
    10 minutes to 30 minutes.

%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[DTR].
%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[SYSTE
ST.DTR].

    During the installation, a file called
    DTRSTUP.COM has been added to SYS$MANAGER:

    The site-dependent start-up file, SYS$MANAGER:SYSTARTUP.COM
    should have the following line added:
          $     @SYS$MANAGER:DTRSTUP.COM


    *************************************************************

    VAX DATATRIEVE User Environment Test Packages (UETPs)
    have been provided and can be run after the installation is
    complete. They are invoked from VAX DATATRIEVE as follows:

    DTR> @sys$common:[systest.dtr]dtr     ! The general test
    DTR> @sys$common:[systest.dtr]plots   ! The plots test
    DTR> @sys$common:[systest.dtr]rdb     ! The Rdb test

    *************************************************************

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Executing IVP for:  VAX DATATRIEVE V4.1-0

Running the general IVP test ...
    Test completed successfully

    *************************************

    VAX DATATRIEVE V4.1-0

    IVP COMPLETED SUCCESSFULLY

    *************************************

IVP completed for:  VAX DATATRIEVE V4.1-0

Restoring VAX DATATRIEVE demonstration RDB/VMS database 

Backed up by Rdb/VMS V2.2-0 Backup/Restore utility
A component of Rdb/VMS V2.2-0
Previous name was DTR$LIBRARY:PERSONNEL.RDB
It was logically backed up on 19-AUG-1987 21:50
Restoring relation COLLEGES
Restoring relation DEGREES
Restoring relation DEPARTMENTS
Restoring relation EMPLOYEES
Restoring relation JOBS
Restoring relation JOB_HISTORY
Restoring relation SALARY_HISTORY
Restoring relation WORK_STATUS

        Installation of DTR V4.1 completed at 08:52



        VMSINSTAL procedure done at 08:52

--------------------
FORT048.DIR;1             ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal fort dua3:[products.fort048]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:47.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  FORT V4.8


        Beginning installation of FORT V4.8 at 06:47

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
* Do you want to purge files replaced by this installation [YES]? 
* Do you wish to have the VAX FORTRAN compiler installed [YES]? 

        +-------------------------------------------------------+
        |          Installation of VAX FORTRAN V4               |
        |                       Compiler                        |
        +-------------------------------------------------------+


        This kit contains an Installation Verification Procedure
        to  verify the correct installation of the  VAX  FORTRAN
        compiler.

* Do you want to run the IVP after the installation [YES]? 

        This kit contains a file, VAXFORUPD.MEM, summarizing the
        changes made  to the VAX FORTRAN compiler since its last
        release.

* How many copies would you like to print [0]: 

        A new FORSYSDEF.TLB is available with this installation.

        In order to build your FORSYSDEF library, this procedure
        requires at least 5500 blocks of available  disk  space,
        most  of  which  is  used for temporary work files.  The
        FORSYSDEF library itself will  take  approximately  1500
        blocks  of  disk space upon completion of this procedure
        and will be placed in your SYS$LIBRARY area. 

                                  Note

        Before installing the kit, be sure to have read  section
        1.5.1.1, UPDATING FORSYSDEF.  It addresses  the question
        of when a new FORSYSDEF.TLB should be built.  

* Do you wish to build a new FORSYSDEF.TLB [NO]? yes

        Building FORSYSDEF.  This should take about 20 minutes.


        Your  VMS  system  will now be updated  to  include  the
        following new and modified file(s):


        SYS$SYSTEM:FORTRAN.EXE          [new]
        SYS$MESSAGE:FORTERR1.EXE        [new]
        SYS$MESSAGE:FORTERR2.EXE        [new]
        SYS$LIBRARY:FORTV4CLD.CLD       [new]
        SYS$TEST:FORTTEST.COM           [new]
        SYS$TEST:FORSYSDEFTST.COM       [new]
        SYS$LIBRARY:DCLTABLES.EXE       [modified]
        SYS$UPDATE:VAXFORUPD.MEM        [new]
        SYS$LIBRARY:FORSYSDEF.TLB       [new]

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

        +-------------------------------------------------------+
        |           Verification Command Procedure for          |
        |                      VAX FORTRAN                      |
        +-------------------------------------------------------+

VAX FORTRAN V4.8-276 TEST PASSED

        Installation of FORT V4.8 completed at 06:48



        VMSINSTAL procedure done at 06:48



--------------------
LAV010.DIR;1              ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal lav DUA3:[PRODUCTS.LAV010]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:35.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? yes


The following products will be processed:

  LAV V1.0


        Beginning installation of LAV V1.0 at 06:35

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

        Installation of LAV V1.0 completed at 06:35



        VMSINSTAL procedure done at 06:35



---------------------
MMS024.DIR;1              ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal mms dua3:[products.mms024]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 07:22.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  MMS V2.4


        Beginning installation of MMS V2.4 at 07:22

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.
* Do you want to run the IVP after the installation [YES]? 
* Do you want to purge files replaced by this installation [YES]? 


The installation can be aborted at any time by pressing CTRL/Y.


%MMS-I-NOMORE, There are no further questions during the DEC/MMS installation.
%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%MMS-I-NOFMSSUPP, DEC/MMS will not contain support for VAX FMS.
%MMS-I-LINKIMAGE, Linking V2.4.
%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MMS].

If you intend to execute this layered product on other nodes in your
VAXcluster, and you have the appropriate software license, you must
prepare the system-specific roots on the other nodes by issuing the
following command on each node (using a suitably privileged account):

        $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.MMS] 
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%MMS-I-BEGINIVP, Beginning V2.4 IVP.
%MMS-I-ENDIVP, V2.4 IVP SUCCESSFUL.

        Installation of MMS V2.4 completed at 07:22



        VMSINSTAL procedure done at 07:22


---------------------
PASCAL037.DIR;1           ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal pascal dua3:[products.pascal037]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 08:01.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  PASCAL V3.7


        Beginning installation of PASCAL V3.7 at 08:01

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved t
o SYS$HELP.
 
 
        *-----------------------------------------*
        *    Installation Command Procedure for   *
        *             VAX PASCAL V3.7             *
        *-----------------------------------------*
 
 
* Do you want to purge files replaced by this installation [YES]? 


    This kit contains a file summarizing the new features, changes,
    restrictions, and compatibility issues in this release of VAX 
    PASCAL.  This file is named PASCAL037.RELEASE_NOTES and is
    placed in SYS$HELP:.  

    This file contains information valuable to VAX PASCAL programmers.  
    Please inform your user community of this file's existence.



    All questions regarding the installation have now been asked.  
    The installation of VAX PASCAL V3.7 will now continue for 
    approximately 5 to 120 minutes depending on your configuration.

%VMSINSTAL-I-RESTORE, Restoring product saveset B...

  Your VMS system will now be updated to include the following new and 
  modified files:

    SYS$HELP:HELPLIB.HLB                   [modified]
    SYS$HELP:PASCAL037.RELEASE_NOTES       [new]
    SYS$LIBRARY:DCLTABLES.EXE              [modified]
    SYS$LIBRARY:LIBDEF.PAS                 [new]
    SYS$LIBRARY:MTHDEF.PAS                 [new]
    SYS$LIBRARY:PASDEF.PAS                 [new]
    SYS$LIBRARY:PASSTATUS.PAS              [new]
    SYS$LIBRARY:SIGDEF.PAS                 [new]
    SYS$MESSAGE:PASCALER1.EXE              [new]
    SYS$MESSAGE:PASCALER2.EXE              [new]
    SYS$SYSTEM:PASCAL.EXE                  [new]

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
 
 
        *-----------------------------------------*
        * Installation Verification Procedure for *
        *            VAX PASCAL V3.7              *
        *-----------------------------------------*
 
 
** Successful Installation of VAX Pascal V3.7-254 on 21-Feb-2019 at 08:01 **

        Installation of PASCAL V3.7 completed at 08:01



        VMSINSTAL procedure done at 08:01


---------------------
RDBVMSDEV023.DIR;1        ===> ERROR in IVP (REMOTE TEST)

TSTVAX::SYSTEM <!> @sys$update:vmsinstal rdbvmsdev dua3:[products.RDBVMSDEv023]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 07:17.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  RDBVMSDEV V2.3


        Beginning installation of RDBVMSDEV V2.3 at 07:17

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.


        Installation procedures for: "VAX Rdb/VMS V2.3-0" 



    Be sure you have read the section entitled

        "Preparing Your System and the Installing Account"

    in the installation guide before continuing with the installation.


    Checking system requirements ...


    *************************************************************

    This installation requires the creation of the RDB$REMOTE
    account.  You MUST choose a UIC and password for this
    account.  PLEASE NOTE that your password for the RDB$REMOTE
    account and the network object RDBSERVER MUST be exactly the
    same.  The password you supply for the RDB$REMOTE account
    will be used for the network object as well IF the account is
    created by this installation.

    **************************************************************


    *************************************************************

    The installation procedure will not proceed until you enter a
    valid user identification code (UIC) for the RDB$REMOTE
    account.

    **************************************************************

* Please enter UIC to be used for RDB$REMOTE account: [250,1]

    *************************************************************

    The entire installation will FAIL if you do not enter a valid
    password for the RDB$REMOTE account.  You will be given 
    3 chances to verify your password.  This installation
    procedure requires at least 6 characters for the
    RDB$REMOTE password.  Valid characters for a password are:

       A through Z
       a through z
       0 through 9
       $ (dollar sign)
       _ (underscore)

    As with the DCL SET PASSWORD command, your input will not
    appear on the terminal.  And to protect against typing errors
    that are not seen when entering the password, you must enter
    the password twice.

    *************************************************************

* Please enter PASSWORD to be used for RDB$REMOTE account: 

* Please verify the PASSWORD entered for RDB$REMOTE: 


* Do you want to run the IVP after the installation [YES]? 
* Do you want to purge files replaced by this installation [YES]? 

    There are no more questions.  The installation takes approximately
    40 minutes on a stand-alone VAX 11/780.



    Beginning installation ...


    Installing under VMS V4.7     - 21-FEB-2019 07:17


%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%VMSINSTAL-I-RESTORE, Restoring product saveset C...
%VMSINSTAL-I-RESTORE, Restoring product saveset D...
%VMSINSTAL-I-RESTORE, Restoring product saveset E...
%VMSINSTAL-I-RESTORE, Restoring product saveset F...
%VMSINSTAL-I-RESTORE, Restoring product saveset G...

    *************************************************************

    SYSTEM MANAGER:

    The following command line MUST be added to the system startup
    command file SYS$MANAGER:SYSTARTUP.COM for all nodes that will
    be running Rdb/VMS.

        $ @SYS$MANAGER:RMONSTART

    The following command line should be added to the system
    shutdown command file SYS$MANAGER:SYSHUTDWN.COM:for all nodes
    that will be running Rdb/VMS.

        $ @SYS$MANAGER:RMONSTOP

    *************************************************************


%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[RDB$REMOTE].

%RDBVMSDEV-I-ACCOUNT, This installation creates an account named RDB$REMOTE.

RDBSERVER has been placed in the DECnet object database as number 35.

    *************************************************************

    SYSTEM MANAGER:

    If your DECnet object database is not configured to be in
    the cluster common directory, then you will need to perform
    the following:

    In order to have remote access on another node which shares
    this cluster common root directory, you must insert
    RDBSERVER.EXE into that node's DECnet object database by:

        a) Logging into that node, and
        b) Invoking SYS$COMMON:[SYSMGR]RDBSERVER_NCP.COM.

    This command procedure inserts RDBSERVER into the node's
    permanent DECnet object database.  This procedure only needs
    to be executed ONCE per node.

    You will need to remember the password that you supplied 
    for the object RDBSERVER because you will be 
    prompted for the password in the command procedure.

    *************************************************************

 
    *************************************************************
 
    The RDBSERVER object automatically uses the RDB$REMOTE
    account created by this installation procedure.
 
    Invoking a database should look like: 
 
    $DEFINE MYDB "<node>::<dev>:<dir><db-name>"
    $RDO
    RDO> DATABASE FILE MYDB
 
    *************************************************************
 
%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.RDBVMS].
%VMSINSTAL-I-SYSDISK, This product creates system disk directory VMI$ROOT:[SYSTEST.RDBVMS].
 
    *************************************************************
 
    The Rdb/VMS Installation Verification Procedure (IVP) has
    been provided in SYS$COMMON:[SYSTEST.RDBVMS].
 
    It is invoked using the commands:
 
        $ SET DEFAULT SYS$COMMON:[SYSTEST.RDBVMS]
        $ @RDBIVP DEV
 
    *************************************************************
 

    *************************************************************

        The release notes for Rdb/VMS are available in the file
              SYS$HELP:RDBVMS023.RELEASE_NOTES

    *************************************************************

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Executing IVP for: VAX Rdb/VMS V2.3-0

Rdb/VMS monitor (RDMS_MONITOR) started
Building the test database.

Program: Loading EMPLOYEES 
Program: EMPLOYEES Loaded. Normal End-of-Job
Program: Loading JOBS
Program: JOBS Loaded. Normal End-of-Job
Program: Loading DEPTS
Program: DEPTS Loaded. Normal End-of-Job

Beginning Installation Verification Tests.


Running the after-image journaling test.
    Test completed successfully

Running the remote database test.

    *****  The remote database test failed  *****

    See SYS$UPDATE:RDBIVP_REMOTE.LOG for errors.


Running the interpreter test.
    Test completed successfully

Running the BASIC precompiler test.
    Test completed successfully

Running the FORTRAN precompiler test.
    Test completed successfully

1 test failed.

    //////////////////////////////////////

    VAX Rdb/VMS V2.3-0

    Development

    IVP FAILED

    //////////////////////////////////////


IVP completed for: VAX Rdb/VMS V2.3-0


        Installation of RDBVMSDEV V2.3 completed at 07:18



        VMSINSTAL procedure done at 07:18


TSTVAX::SYSTEM <!> type SYS$UPDATE:RDBIVP_REMOTE.LOG
%RDB-F-IO_ERROR, input or output error
-SYSTEM-F-LINKEXIT, network partner exited
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command
%RDO-F-INVNOTDON, no DATABASE invoked yet, please issue a DATABASE command

---------------------
RSX023.DIR;1              ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal rsx dua3:[products.rsx023]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:43.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  RSX V2.3


        Beginning installation of RSX V2.3 at 06:43

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.

Please select one of the following actions:

     1)  Perform the installation
     2)  Create a file with a description of the installation
     3)  Both of the above


* What would you like to do [3]: 

An optional help library is provided for use with the MCR  CLI.   This
library  supplies  help  for commands supported by MCR and for the RSX
utilities  supplied  with  VAX-11  RSX.   This  library  will  require
approximately  2000  additional  disk  blocks.  If you wish to install
this library on your system, answer yes to the following question.

* Do you want to install the MCR help library [YES]? 
* Do you want to purge files replaced by this installation [YES]? 
* Do you want to run the IVP after the installation [YES]? 

VAX11RSX.COM, the startup command procedure, is used  to  set  up  the
environment for VAX-11 RSX.  During the installation it will be placed
in  the  [SYSMGR]  directory  of  the  system  root  on   which   this
installation is being performed.  Your system startup procedure should
be modified to invoke this procedure when the system boots.   However,
it  will not be necessary to reboot the system after the installation,
since this procedure is invoked as part of the installation.  See  the
VAX-11  RSX  Installation Guide and Notes, or the procedure itself for
information.


The installation procedure has no further questions  to  ask  and  can
continue  from  this  point  without user assistance.  The rest of the
installation will take approximately 10 minutes.  If you chose to  run
the IVP it will take an additional 10 minutes.

%VMSINSTAL-I-RESTORE, Restoring product saveset B...

              ** VAXcluster common system disk setup **

If you intend to execute VAX-11 RSX on other nodes in your  VAXcluster
which  share  this  common  system  root, and you have the appropriate
software license, you must  ensure  that  SYS$MANAGER:VAX11RSX.COM  is
executed  on  each node to define the appropriate logical names and to
create the system directory synonyms required by RSX-11 software.


                    ** System $$n logical names **

RSX-11 tasks running under VAX-11 RSX can only access  VAX/VMS  rooted
directories  through  the  use  of logical names having a format which
resembles that of an RSX-11 physical  device  name.   Similarly,  many
VAX/VMS  physical  devices  (including any device on a VAXcluster) can
only be accessed by RSX-11 tasks through  the  use  of  these  logical
names.

VAX-11 RSX uses several standard system-wide logical names, as well as
internal  "logical  names"  (such as SY and TI) for this purpose.  See
the VAX-11 RSX Compatibility Mode Reference Manual (Section  2.7)  for
more detailed information on VAX-11 RSX device name mapping.

The system directory root (SYS$SYSROOT) is always mapped by the VAX-11
RSX  logical  name  LB.   However,  other devices and root directories
should be mapped by "$$n" logical names, with the string "$$" followed
by  an  octal  unit  number  from 0 to 377.  Note that even though $$n
logical  names  are  not  strictly  necessary   (except   for   rooted
directories)   on  non-VAXcluster  systems,  RSX-11  task  performance
(particularly the ALUN$ and ELP$ directives) will be improved  through
their  use.   This installation will create $$n names for all the disk
and tape devices currently present on your system.

%RSX-I-$$N, the following $$n logical names will be defined:
        $$n     VAX/VMS device
        -----   ---------------
        $$0     TSTVAX$DUA0:
        $$1     TSTVAX$DUA1:
        $$2     TSTVAX$DUA2:
        $$3     TSTVAX$DUA3:
        $$4     TSTVAX$DUB0:
        $$5     TSTVAX$DUB1:
        $$6     TSTVAX$DUB2:
        $$7     TSTVAX$DUB3:
        $$10    TSTVAX$MSA0:
        $$11    TSTVAX$MUA0:
        $$12    TSTVAX$MUA1:
        $$13    TSTVAX$MUA2:
        $$14    TSTVAX$MUA3:

%RSX-I-CONSOLE, console device CSA1: not configured; defining $$n anyway

The   file   SYS$MANAGER:VAX11RSX$DEVICE_NAMES.COM   contains   DEFINE
commands  to  create  each of the $$n logical names listed above.  The
VAX11RSX.COM startup procedure will execute  VAX11RSX$DEVICE_NAMES.COM
automatically  when  it  runs  following this installation, and during
future system startups.

If there are devices which were not displayed  above,  which  will  be
commonly  accessed by compatibility mode tasks on your system, you may
add $$n names to VAX11RSX$DEVICE_NAMES.COM.  You may also  delete  $$n
names  which you do not want to be defined system-wide from this file.
Additionally, you should define $$n names for any  rooted  directories
which  will be commonly accessed (look at the current definition of LB
with the command "SHOW LOGICAL/FULL LB", for an example of this).

You  may  also  want   to   consider   defining   the   logical   name
RSX$DEVICE_CACHE  to  control  VAX-11  RSX  use  of  $$n  names; it is
described more fully in the VAX-11 RSX Installation Guide and  Release
Notes, and in the VAX-11 RSX Compatibility Mode Reference Manual.

Additionally, to improve performance, you may wish to  reorganize  the
$$n  names  which  have  been  defined,  so  that those which are most
commonly used have the lowest unit numbers.  Currently, they have been
defined in the order in which SHOW DEVICE displays them.

VAX11RSX$DEVICE_NAMES.COM  will  not   be   modified   on   subsequent
installations  of  VAX-11  RSX.   If  you  wish  to  perform  a future
installation that requires changes  to  the  VAX11RSX$DEVICE_NAMES.COM
file,  the old file must be deleted first.  The installation will then
create a new copy of VAX11RSX$DEVICE_NAMES.COM.

%RSX-I-DESCRIBE, The installation is described in SYS$UPDATE:RSX023.TXT

 1) BACKTRANS (new image)

 2) BCK (new image)

 3) BRU (new image)

 4) CNV (new image)

 5) CRF (new image)

 6) DEF (new image)

 7) DES (new image)

 8) DMP (new image)

 9) DSC1 (new image)

10) DSP (new image)

11) DTE (new image)

12) EDI (new image)

13) FCSRES (new file)

14) FCSRES (new image)

15) FLX (new image)

16) ICM (new image)

17) IFL (new image)

18) INDSYS (new file)

19) LBR (new image)

20) LINK (miscellaneous)

21) MAC (new image)

22) MCR (new image)

23) MCRHELPLIB (new file)

24) MCRTABLES (miscellaneous)

25) MFT (new image)

26) ODT (new file)

27) PAT (new image)

28) PIP (new image)

29) QIOSYM (new file)

30) RMS11ODL (new file)

31) RMSDES (new file)

32) RMSLIB (new file)

33) RMSMAC (new file)

34) RMSRES (new file)

35) RMSRES (new image)

36) RST (new image)

37) RSX (new image)

38) RSXMAC (new file)

39) RSXSHR (new image)

40) RSXUSR (new image)

41) SLP (new image)

42) SYSLIB (new file)

43) TKB (new image)

44) VAX11RSX$DEVICE_NAMES (new file)

45) VAX11RSX (new file)

46) VMLIB (new file)

47) ZAP (new image)

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%RSX023-I-IVPSTART, Installation Verification Procedure starting

              ** Installation Verification Procedure **

The installation verification procedure (IVP) tests  that  VAX-11  RSX
installed  correctly  by testing various compatibility mode utilities.
This serves as a test of the utilities themselves and of the RSX  AME.
Also,  when  DCL commands exist for compatibility mode utilities (i.e.
LIBRARY/RSX for LBR), these will be used to test  the  translation  of
DCL commands to MCR syntax for these utilities.

Several of the compatibility  mode  utilites  will  log  their  normal
actions  to  SYS$OUTPUT.   These informational messages as well as any
error messages that may be produced by these utilities, will not be in
the standard VAX/VMS message format.  If an error occurs, the IVP will
detect it and produce an error message in the standard VAX/VMS format.
The  IVP  will  also produce informational and success messages in the
standard format.

%RSX023-I-TESTSTART, DMP testing started at 06:44:13
DMP -- DMP Version M08.01 (ANSI)

%RSX023-S-TESTSUCCESS, DMP testing completed successfully at 06:44:14
%RSX023-I-TESTSTART, LBR testing started at 06:44:14
Modules deleted:
OBJ3  

Module "OBJ1  " replaced

Module "OBJ2  " replaced

Entry points deleted:
ENT$A1
ENT$B2
ENT$A3

Modules deleted:
MCLBR3

Module "MCLBR1" replaced

Module "MCLBR2" replaced

%RSX023-S-TESTSUCCESS, LBR testing completed successfully at 06:44:15
%RSX023-I-TESTSTART, PAT testing started at 06:44:15
%RSX023-S-TESTSUCCESS, PAT testing completed successfully at 06:44:15
%RSX023-I-TESTSTART, PIP testing started at 06:44:15
PIP -- PIP Version M1600 (ANSI)

%RSX023-S-TESTSUCCESS, PIP testing completed successfully at 06:44:16
%RSX023-I-TESTSTART, FLX testing started at 06:44:16
FLX -- FLX Version 17.00 

%RSX023-S-TESTSUCCESS, FLX testing completed successfully at 06:44:16
%RSX023-I-TESTSTART, SLP testing started at 06:44:16
%RSX023-S-TESTSUCCESS, SLP testing completed successfully at 06:44:16
%RSX023-S-IVPSUCCESS, the installation verification of VAX-11 RSX Version 2.3 succeeded

        Installation of RSX V2.3 completed at 06:44



        VMSINSTAL procedure done at 06:44



---------------------
VAXC024.DIR;1             ===> INSTALLATION FAILED IVP

TSTVAX::SYSTEM <!> @sys$update:vmsinstal VAXC DUA3:[PRODUCTS.VAXC024]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:37.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  VAXC V2.4


        Beginning installation of VAXC V2.4 at 06:37

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved t
o SYS$HELP.
 
        VAX C V2.4-026 Installation is commencing ...
 
* Do you want to run the IVP after the installation [YES]? 
* Do you want to purge files replaced by this installation [YES]? 
* Do you want to extract .H files from the text library [YES]? 
 
 All the questions regarding the installation have 
 now been asked.  The installation will now continue
 for another 20 minutes.
 
%VMSINSTAL-I-RESTORE, Restoring product saveset B...
        VAX C V2.4-026 : copying images, libraries and release notes.
        VAX C V2.4-026 : extracting .H files.
 
        A summary of the Software Performance Reports (SPRs) for this release
        can be found in the file SYS$LIBRARY:VAXCSPR.DAT.
 
 
        VAX C V2.4-026 Installation is completed.
 
 
        Your VMS system will now be updated to include the following new
        and modified files:
 
        SYS$SYSTEM:VAXC.EXE             [new]
        SYS$LIBRARY:VAXCDEF.TLB         [new]
        SYS$LIBRARY:VAXCSPR.DAT         [new]
        SYS$MESSAGE:VAXCERR.EXE         [new]
        SYS$HELP:VAXC024.RELEASE_NOTES  [new]
        SYS$HELP:HELPLIB.HLB            [modified]
        SYS$LIBRARY:DCLTABLES.EXE       [modified]
        SYS$EXAMPLES:VAXCIVPP.C         [new]
        SYS$EXAMPLES:VAXCIVPC.C         [new]
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
 
        VAX C V2.4-026 Installation Verification Procedure commencing ...
 


======akh========>>>>>>>>>> ERROR in vfork/exec test #13

****** VAX C Installation Procedure FAILED ******

%NONAME-E-NOMSG, Message number 00000002
 
        VAX C V2.4-026 Installation Verification Procedure failed.
        Please consult the VAX C Installation Guide for further information.
 
%NONAME-E-NOMSG, Message number 00000002
%VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpected event.

        VMSINSTAL procedure done at 06:37



---------------------
VMSSHD010.DIR;1           ===> INSTALLATION SUCCESSFUL

TSTVAX::SYSTEM <!> @sys$update:vmsinstal vmsshd DUA3:[PRODUCTS.VMSSHD010]


        VAX/VMS Software Product Installation Procedure V4.7    


It is 21-FEB-2019 at 06:33.
Enter a question mark (?) at any time for help.

%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
* Do you want to continue anyway [NO]? yes
* Are you satisfied with the backup of your system disk [YES]? 


The following products will be processed:

  VMSSHD V1.0


        Beginning installation of VMSSHD V1.0 at 06:33

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

        Installation of VMSSHD V1.0 completed at 06:33



        VMSINSTAL procedure done at 06:33

