Quick Beginnings

Installing DB2 Products from a Code Server Hard Disk or CD-ROM

To install DB2 products for OS/2, from a code server hard disk or CD-ROM, on local or remote workstations, perform the steps in the following sections:

"Step 1. Make DB2 Files Available for Installation"
"Step 2. Create a Response File for Unattended Installation"
"Step 3. Run the CMD File from the Remote Workstation"

You can also use the following procedure to remove all DB2 products from a target workstation. Simply follow the instructions below, but when editing the command file, specify D (Delete) instead of I (Install).

Step 1. Make DB2 Files Available for Installation

In this section, you make the DB2 install files accessible to the client machine where DB2 will be installed.

If performing remote installs directly from the CD-ROM:
1. Insert the appropriate CD-ROM into the drive.
2. Ensure that the CD-ROM will remain in the drive for as long as it is needed for the install. If the drive is often used for other tasks as well, consider installing from the code server hard disk instead.
If installing from a code server hard disk, you must copy the required files from the CD-ROM directories to the code server's hard disk. At the command prompt, use the xcopy command with the /s option.
- The syntax for the two commands required is:
```
   xcopy x:\db2\os2\language e:\clients\language /s
   xcopy x:\db2\os2\common e:\clients\common /s
```
  where:
  - x is the letter that designates the CD-ROM drive
  - e is the letter that designates the code server's hard disk
  - language is the two-character code that represents your language (for example, EN for English). Table 47 lists the code for each available language.

If performing a remote installation, you must enable your network clients to access the DB2 install files.

Grant shared access authority to the directory that you just created, or to the CD-ROM drive if installing directly from CD-ROM.

Step 2. Create a Response File for Unattended Installation

During an interactive installation, you provide the information needed to install DB2 and configure its environment. During an unattended installation, this information is provided as keywords and values in a response file. DB2's install package includes a ready-to-use sample response file, with default entries already in place.

If you intend to use the sample response file provided, without making any changes to its values, you can skip this step and go to "Step 3. Run the CMD File from the Remote Workstation".

To edit the sample response file:

Find the correct sample response files for the product you want to install.
If installing directly from the CD-ROM, substitute x:\os2 for e:\clients in the directory names below.
- Edit one of:
  - e:\clients\language\db2conen.rsp for DB2 Connect Enterprise Edition
  - e:\clients\language\db2cae.rsp for DB2 Client Application Enabler
  language is the two-character country code that represents your language (for example, EN for English). Table 47 lists the code for each available language.

The response file contains:

Keywords unique to installation
Environment variable settings
Configuration parameter settings.

For more information on:

DB2 environment variables, see "DB2 Registry Values and Environment Variables", or refer to the Administration Guide.
Configuration parameters, refer to the Administration Guide .

To activate an item in the response file, remove the asterisk (*) to the left of the keyword/registry value, erase the current setting to the right of the value and type in a new setting. The possible settings are listed to the right of the current setting.
An example section of a response file appears below:
```
...
FILE               = c:\sqllib
COMP               = Client Application Enabler
...
*DB2ACCOUNT        = BLANK or char(199)
*DB2BQTIME         = BLANK or 1 - MAX
...
```
Keywords unique to installation are parameters that are only specified in a response file during an unattended installation. The following is a list of keywords unique to OS/2 and Windows 3.1 unattended installation:
- FILE
  Specifies the destination directory for DB2. If you do not change this value, it defaults to x:\sqllib where x is the drive on which your operating system is installed.
  Install DB2 products only on a drive which is local to the target workstation. Installing on a non-local drive can cause performance and availability problems.
- COMP
  Specifies the components you want installed. By default, all components of the DB2 product are installed. If you do not want to install a component, add an asterisk (*) to the left of the COMP line for that component in the response file.
- OVERWRITE
  Specifies whether to automatically overwrite files during installation. Valid values for this keyword are YES and NO.
- CFGUPDATE
  Specifies whether the CONFIG.SYS file is automatically updated. Valid values for this keyword are:
  - AUTO
    Automatically updates CONFIG.SYS.
  - MANUAL
    Does not update CONFIG.SYS.
- SAVEBACKUP
  Specifies whether to save a backup version of the product when it is updated. Valid values for this keyword are YES and NO.
- DB2SYSTEM
  On OS/2, specifies a name for the system which is unique within a network.
  Note: This parameter must be specified.
- AUTO_CTRL_CENTER
  On OS/2, specifies whether or not to automatically start the Control Center each time the system is rebooted.
  Note: By default the Control Center will be automatically started unless this parameter is set to NO.
- DB2.AUTOSTART
  On OS/2, specifies whether or not to automatically start the DB2 instance each time the system is rebooted.
  Note: By default the DB2 instance will be automatically started unless this parameter is set to NO.
- ADMIN.USERID and ADMIN.PASSWORD
  On OS/2, specifies the user ID and password that will be used to log on and start the Administration Server each time your system is started. If UPM already exists on your system, the user ID and password you provide must exist and have one of the following:
  - UPM administrator authority on your system.
  - UPM local administrator authority on your system.
  If UPM is not on your system, it will be installed as part of the DB2 installation and the user ID and password you provide will be set up with the appropriate authority.
Exit the file. If you have made any changes, save the file under a new file name to preserve the original sample response file.
If you are installing directly from the CD-ROM, you must store the renamed response file on another drive.

Step 3. Run the CMD File from the Remote Workstation

A command (CMD) file contains the commands which will start the installation program. You must edit this file before running the installation.

Find and open the correct CMD file.
If installing directly from the CD-ROM, substitute x:\os2 for e:\clients in the directory names below.
- The CMD files are available in the e:\clients\language directory where language is the two-character country code that represents your language (for example, EN for English). Table 47 lists the code for each available language. For example:
  - db2conen.cmd for DB2 Connect Enterprise Edition
  - db2cae.cmd for DB2 Client Application Enabler
Edit the command in the file, to fill in the information needed for the installation.
- For OS/2:
  1. In the command file, you must specify the location of the install files. Use the following command:
```
   set beginlibpath=drive:\db2path
```
    For example, if you are installing from the code server's hard drive, specify the directory created in Step 1:
```
   set beginlibpath=x:\clients\language\install
```
    where x is the letter that designates the CD-ROM drive and language is the two-character country code that represents your language (for example, EN for English). See Table 47
  2. You must also specify the complete install command. A complete command requires the following syntax:
  The following is an example of a complete command in the sample command files:
```
   e:\clients\language\install\install /A:I /X
      /P:"IBM DB2 Client Application Enabler"
      /R:e:\clients\language\db2cae.rsp /L1:d:\error.log
      /L2:d:\history.log
```
  where:
  
  /d:\path
  Specifies the location of the install files. If installing from the code server's hard drive, specify the directory created in Step 1.
  /A
  Specifies the action to be performed.
  
  I
  Specifies install.
  Note: If you want to remove all DB2 products from a target workstation, specify D (Delete) instead of I (Install).
  
  /X
  Specifies that the installation will run in unattended mode.
  /P
  Specifies the name of the product you want to install.
  /R
  Specifies the fully qualified response file name. If you changed and renamed the sample response file provided, make sure this parameter matches the new name.
  /L1
  Specifies the fully qualified log file name, where setup information and any errors occurring during setup are logged.
  /L2
  Specifies the fully qualified history log name, where all the files processed by the installation program are listed.
- On Windows 3.1:
  A complete command requires the following syntax:
The following is an example of a complete command in the sample command files:
```
   win e:\ins\install\install /A:I /X
      /P:"IBM Client Application Enabler for Windows 3.1 V5
      /R:e:\ins\db2caew.rsp /L1:d:\L1 /L2:\L2
```
where:

/d:\path
Specifies the location of the install files. If installing from the code server's hard drive, specify the directory created in Step 1.
/R
Specifies the fully qualified response file name. If you changed and renamed the sample response file provided, make sure this parameter matches the new name.
/A
Specifies the action to be performed.

I
Specifies install.
Note: If you want to remove all DB2 products from a target workstation, specify D (Delete) instead of I (Install).

/X
Specifies that the installation will run in unattended mode.
/P
Specifies the name of the product you want to install.
/L1
Specifies the fully qualified log file name, where setup information and any errors occurring during setup are logged.
/L2
Specifies the fully qualified history log name, where all the files processed by the installation program are listed.
Save and exit the CMD file.
If you are installing directly from the CD-ROM, you must rename the CMD file, store it on another drive, and use that file name in the next step.
Start the installation by typing the CMD file's name on the command line.
When installation is complete, check the error and history logs for any errors or problems.

To configure your DB2 Connect workstation to access remote hosts, go to the Chapter 11. "Configuring Communications to Host and AS/400 Databases Manually" manual. To configure your client to access remote DB2 Connect workstations or DB2 servers, go to Chapter 32. "Configuring Client to DB2 Connect Server Communications Using the CCA".

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]