═══ 1. Introduction ═══

Test Engine/2 and Quality Assurance Manager/2 are supplied with the same 
installation program that permits you to selectively install different 
components of the package. The following possibilities exist: 

     o Install Test Engine/2 program 
     o Install Programming tools 
     o Install Quality Assurance Manager/2 base program 
     o Install Quality Assurance Manager/2 report generator 
     o Install Quality Assurance Manager/2 administration tools 
     o Install Quality Assurance Manager/2 review management 
     o Remove all components that were previously installed 
     o Install the database for Quality Assurance Manager/2 
     o Catalogue a remote database for Quality Assurance Manager/2 
     o Catalogue a remote database server 
     o Drop a pre-existing local database 

 Combinations of these installations are possible. However, you cannot both 
 install program items and remove them and you cannot catalogue and install the 
 database locally. 

 Note: 
 You can only remove components if they have been previously installed using 
 the installation program. 

 The installation program also allows you to create a response file for the 
 selections you have made. This file can then be used for automatic 
 installation with no user intervention. 

 Note: 
 You can prepare as many response files as you want for different types of work 
 station. 

 Installation may be carried out directly from the diskettes or over a network. 

 Note: 
 If you have only purchased Test Engine/2, Those parts of the installation 
 program relating to Quality Assurance Manager/2 will be disabled. 


═══ 2. Installing from diskettes ═══

To install from diskettes, follow these steps: 

      1. Insert Diskette 1 (Install) into the diskette drive. 

      2. Type A:\INSTALL at a command prompt. The program will copy files onto 
         your work station and start the installation program where A is the 
         diskette drive letter. 

      3. Select the options you wish to install using the pages from the 
         notebook. 

      4. Select the Install menu item to start the installation. 

      5. When the installation is complete, reboot the work station for changes 
         in your configuration to take effect. 


═══ 3. Installing from a Local Area Network ═══

The installation program may be run from a network directory. The installation 
program will be copied to the local work station in the same way as when 
installing from the diskettes. Before installing from the LAN, all the files 
from the diskettes must be copied onto the server and the path to the 
installation files must be known to the users. 

Once the files are present on the server, the procedure for installation is the 
same as installing from diskettes: 

      1. Type X:\PATH\INSTALL at a command prompt. The program will copy files 
         onto your work station and start the installation program 

         where 
         X is the remote drive letter 
         PATH is the path on that drive to the install files. 

      2. Select the options you wish to install using the pages from the 
         notebook. 

      3. Select the Install menu item to start the installation. 

      4. When the installation is complete, reboot the work station for changes 
         in your configuration to take effect. 


═══ 4. Creating a Response File ═══

Response files will normally be used when installing over the LAN. These files 
are created using the installation program and ensure that all the 
installations on a LAN are compatible. 

      1. If you have already installed Test Engine/2 or Quality Assurance 
         Manager/2 on your work station. 

          Type QAINST at a command prompt. 

        If you have not yet installed Test Engine/2 or Quality Assurance 
        Manager/2 on your work station. 

          Type X:\PATH\INSTALL at a command prompt. 
          The program will copy the necessary files onto your work station and 
          start the installation program 

          where 
          X is the remote drive letter 
          PATH is the path on that drive to the install files. 

      2. Select the options you wish to install using the pages from the 
         notebook. 

      3. Select the Create response file menu item. You will be asked for a 
         file name (default extension RSP). 

      4. Enter the required file name and ensure that the file is in the same 
         directory as the installation files. 

      5. The installation program will then create the required response file. 


═══ 5. Installing with a response file ═══

To install Test Engine/2 or Quality Assurance Manager/2 using a response file: 

      1. Type X:\PATH\INSTALL respose_file_name at a command prompt. The 
         program will copy files onto your work station and start the 
         installation program 

         where 
         X is the remote drive letter 
         PATH is the path on that drive to the install files 
         response_file_name is the name of the response file. 

 Warning: 

 The response file name MUST NOT INCLUDE THE PATH to the file. 
 The response file MUST be in the same location as the install files. 

 When the installation is complete, reboot the work station for changes in your 
 configuration to take effect. 

 Warning: 

 When installing with a response file, the installation is automatic and the 
 user is given no opportunity to change the settings for the installation. 


═══ 6. New files installed ═══

The new installation program will install itself into the OS2\INSTALL directory 
and create a new folder on the desktop containing the program and book objects. 

The installation program also installs the runtime DLL for WATCOM VX-REXX 
version 2.1c. If there is a previous of VX-REXX present on the work station, 
vrobj.dll is replaced. This will not adversely effect the performance of a 
previous VX-REXX version. If VX-REXX is not present, this DLL will be installed 
in the System DLL directory. 

If any error occurs during the installation process, details can be seen by 
viewing the file \os2\install\qainst.err. 

Warning: 

DO NOT DELETE ANY FILES NAMED QAINST.* FROM THE OS2\INSTALL DIRECTORY. 


═══ 7. Installation Program ═══

The installation program is composed of a notebook containing three pages and a 
menu. Each page allows you to determine specific aspects of your installation. 

If you do not view all the pages in the notebook, a warning is displayed. You 
should always view all the pages to ensure that your installation will be 
correct. 

During the installation phase a progress dialog is displayed (see the progress 
dialog). 

Figure: Progress Dialog 

Figure: Install program menu 


═══ 7.1. Program installation ═══

The first page of the notebook is shown below. Here you can choose which 
program elements to install. Select the items you wish to install by checking 
or unchecking the boxes. 

Figure: Program installation page 


═══ 7.2. System configuration ═══

This page of the notebook gives you the option to control how the installation 
program updates the desktop and the system files and where you want the 
components of the programs installed. 

Note:  It is recommended that you allow the installation program to update the 
CONFIG.SYS file for you. If not, you will have to add all the paths described 
below to the CONFIG.SYS by hand. The installation program will always check to 
ensure that duplicate paths do not exist. 

Folder 
You may move the folder that the installation program creates, or its contents, 
to another location after installation. However, if you move the contents then 
the remove function cannot destroy the program objects automatically and you 
will have to delete them manually. 

Source path 
Do not modify the source path unless you are sure that the given path is 
correct. When the install program is called as specified above, the system sets 
this path and it will be correct. If you wish to install from somewhere else, 
do not forget to add the trailing backslash to the path. 

Run files 
This specifies the path where executable and command files will be stored. This 
path will be added to the SET PATH= statement in the CONFIG.SYS file if you 
allow update of the system configuration. 

Figure: System configuration page 

Lib files 
This specifies where the *.lib files will be stored. This path will be added to 
the SET LIB= statement in the CONFIG.SYS file if you allow update of the system 
configuration. 

H files 
This specifies where the header files will be stored. This path will be added 
to the SET INCLUDE= statement in the CONFIG.SYS file if you allow update of the 
system configuration. 

Help files 
This specifies where the on-line help files will be stored. This path will be 
added to the SET HELP= statement in the CONFIG.SYS file if you allow update of 
the system configuration. 

Books 
This specifies where the on-line books will be stored. This path will be added 
to the SET BOOKSHELF= statement in the CONFIG.SYS file if you allow update of 
the system configuration. 

DLL files 
This specifies where the Dynamic Link Libraries will be stored. This path will 
be added to the LIBPATH= statement in the CONFIG.SYS file if you allow update 
of the system configuration. 

INI files 
This specifies where the profiles and other data files will be stored. This 
path will be added to the SET TSTNGEN= statement in the CONFIG.SYS file if you 
allow update of the system configuration. 


═══ 7.3. Database installation ═══

The third page of the dialog is used for installing the Quality Assurance 
Manager/2 database. There are two mutually exclusive options: 

     o Install the database locally 
     o Catalogue a remote database 

 In the second case you are also given the opportunity of cataloguing the 
 remote database server. 

 Note:  You can only catalogue a remote database server that communicates via 
 Net BIOS. APPN and APPC nodes will have to be catalogued using the Database 
 Manager. 

 Usually you will use the install program to install the database locally on a 
 database server and all other nodes will catalogue the database and the 
 server. 

 Figure: Database installation page 

 Local database 
 The install program gives you the option of creating or dropping a local 
 database. The database name is a constant and cannot be changed. You can also 
 choose which local drive the database will be installed on. 

 Note:  Only local drives are made available for installing the database as 
 sharing of a remote database by standalone DB2 stations will lead to 
 inconsistencies in the data. 

 Warning: 

 If you drop an existing database, all the data will be lost. Back up your 
 database before dropping. 

 Remote Database 
 The remote database name is a constant and cannot be changed. 
 The DB server drop down combo box contains a list of the catalogued servers 
 for the work station. If you select an existing server, the Catalog Node check 
 box will be disabled. If you enter a new name, this server will be catalogued 
 on your work station. 


═══ 8. Notes for users upgrading from a previous beta version ═══

The following sections supply information important for clients upgrading from 
a previous beta version of Test Engine/2 

Installation 

Previous beta versions of Test Engine/2 were not supplied with the same 
installation program and the previous installation will not be recognised by 
qainst.exe 

Note:  It is recommended that users delete any previous version manually using 
the xdel program before installing this version. 

Script files 

This production version of Test Engine/2 requires a modification of any old 
script files as these must now contain commands (see Test Engine/2 Programming 
Reference). To automate this, a command file is included on the diskettes that 
will insert the necessary modifications into your existing scripts. You MUST 
run all your scripts through this program before using them with the new Test 
Engine/2. 

To run the modification program type the following at a command prompt: 

     SPTMOD <script_file> 

     or drag the script file object onto the SPTMOD icon. 

 If you have many scripts it would be a good idea to create a batch file to 
 convert them. 

 Example 

  /** REXX batch for converting scripts with the same extension ***/

  if RxFuncQuery( 'SysFileTree') <> 0 then
      call RxFuncAdd 'SysFileTree', 'REXXUTIL', 'SysFileTree'

  call SysFileTree 'C:\*.spt', 'file.', 'FSO'

  do i = 1 to file.0
      address cmd 'sptmod' file.i
  end

  exit