Installation and Configuration Supplement

Important Response File Keywords

This section describes the most important keywords you will specify when performing a distributed installation. You can use response file keywords to specify the values of a database manager configuration parameters, installation components and the values of DB2 registry variables. The following areas are covered in this section:

Response File Keywords for OS/2 and Windows 32-Bit Operating Systems

This sections describes the most important keywords that you will specify when performing a distributed installation on OS/2 and Windows 32-bit operating systems. The following keywords are available for all DB2 products including Satellite. For keywords specific to the DB2 Satellite Edition, see Response File Keywords for DB2 Satellite Edition.

FILE
Specifies the destination directory for a DB2 product.

REBOOT
Specifies whether to restart the system when the installation has completed (Windows 32-bit operating systems only).

For OS/2 systems, enter /REBOOT on the install command line.

TYPE
Specifies the type of install (Windows 32-bit operating systems only).

The options are:

Note:A compact or typical install type will ignore any custom keywords (COMP).

KILL_PROCESSES
(Windows 32-bit operating systems only).

If you have an existing version of DB2 and it is running and this keyword is set to YES, it will terminate your running DB2 processes without prompt. For more information on killing DB2 processes, see Killing DB2 Processes During Interactive and Response File Installations.

PROD
Specifies the product you want installed. The options are:

DB2.AUTOSTART
Specifies whether or not to automatically start the DB2 instance each time the system is rebooted.

By default, the DB2 instance starts automatically unless this parameter is set to NO.

AUTOSTART_CCA
Specifies whether or not to automatically start the Client Configuration Assistant each time the system is rebooted.

By default, the Client Configuration Assistant starts automatically unless this parameter is set to NO.

AUTOSTART_CONTROL_CENTER
Specifies whether or not to automatically start the Control Center each time the system is rebooted.

By default the Control Center will be automatically started unless this parameter is set to NO.

AUTOSTART_FIRST_STEPS
Specifies whether or not to automatically start the First Steps application the first time the server system is rebooted. After the initial install, you can control First Steps through its interface and request it to come up on subsequent server system reboots.

By default, First Steps will be automatically started. When installing on remote systems, you can set the parameter to NO so that First Steps does not start.

CFGUPDATE
Specifies whether the config.sys file is automatically updated. (OS/2 operating systems only). Valid values for this keyword are:

AUTO
Automatically updates CONFIG.SYS.

MANUAL
Does not update CONFIG.SYS.

We recommend that you specify AUTO when performing a distributed install.

DB2SYSTEM
Specifies a name for the system which is unique within a network.

ADMIN.USERID and ADMIN.PASSWORD
Specifies the user ID and password that will be used to log on and start the Administration Server each time your system is started.
Note:Not available on Windows 9x. Available on the following DB2 products: UDBEEE, UDBEE, UDBWE, CONNEE and UDBPE.

On OS/2, if UPM already exists on your system, the user ID and password you provide must exist and have one of the following:

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.

On Windows, if the username entered does not exist on the user's machine at install time, it will be created with the appropriate authorities by the install program. If the user entered exist at install time, the user ID must be part of the local administrators group. The install will verify this during the installation process, so the install will give an error message if the username does not have the required authority.

DB2.USERID and DB2.PASSWORD
Specifies the default DB2 instance's username and password. Used by the DB2 instance to logon to the system each time your system is started.
Note:Not available on Windows 9x. Available on the following DB2 products: UDBEEE, UDBEE, UDBWE, CONNEE, UDBBE and UDBSE.

On Windows, if the username entered does exist on the user's machine at install time, it will be created with the appropriate authorities by the install program. If the user entered does exist at install time, the user ID must be part of the local administrators group. The install will verify this during the installation process, so the install will give an error message if the username does not have the required authority.

DB2CTLSV.USERID and DB2CTLSV.PASSWORD
Specifies the default Control Server instance's username and password. Used by the DB2 instance to logon to the system each time your system is started.
Note:Available on UDBEE only.

On Windows, if the username entered does not exist on the user's machine at install time, it will be created with the appropriate authorities by the install program. If the user entered does exist at install time, the user ID must be part of the local administrators group. The install will verify this during the installation process, so the install will give an error message if the username does not have the required authority.

DLFM_INST_USERID and DLFM_INST_PASSWORD
Specifies the default Data Links Manager instance's username and password. Used by the DB2 instance to logon to the system each time your system is started.
Note:Available for Data Links Manager only.

On Windows, if the username entered does not exist on the user's machine at install time, it will be created with the appropriate authorities by the install program. If the user entered does not exist at install time, the user ID must be part of the local administrators group. The install will verify this during the installation process, so the install will give an error message if the username does not have the required authority.

COMP
Specifies the components you want installed. The setup program automatically installs components that are required for a product, and ignores requested components that are not available.

For Windows 32-bit operating systems, component selections have no effect unless you specify a custom installation (TYPE = 2).

Response File Keywords for DB2 Satellite Edition

This section describes the most important keywords that you will specify when performing a distributed installation of DB2 Satellite Edition on Windows 32-bit operating systems.
Note:The response file keywords listed below are unique to DB2 Satellite Edition.

DB2.AUTOSTART
Specifies whether or not to automatically start the DB2 instance each time the system is rebooted.

By default, the DB2 instance starts automatically unless this parameter is set to NO.

DB2.SATCTLDB_USERNAME and DB2.SATCTLDB_PASSWORD
Specifies the user ID and password that will be used by the satellite when connecting to the satellite control database (SATCTLDB) on the DB2 control server. The user ID and password are used to authenticate the connection to the database. It is not mandatory that you enter this information at installation time, but it is recommended that you do so if you have the information. The user ID and password cannot be authenticated at installation time.

If you choose not to provide this information at installation time, you can do so later by running the DB2 synchronization application in test mode by issuing the db2sync -t command. You will then be prompted for the user ID and password required to make the connection.

DB2.DB2SATELLITEID
Specifies the unique ID for the satellite and sets the DB2SATELLITEID registry variable on the satellite. The ID must be unique across all groups that are recorded at the DB2 control server. It must match an ID defined for a satellite at the control server. The satellite ID is used during the synchronization process to identify the satellite. The ID can be a maximum of 20 characters.

It is not recommended that you provide the DB2SATELLITEID in the response file as it must be unique, unless you are customizing the value of DB2SATELLITEID for each system the response file will be used on. The DB2SATELLITEID can be set after the installation using the db2set command.

If not specified, the Windows login ID is used in its place during the synchronization process.

DB2.DB2SATELLITEAPPVER
Specifies the satellite's application software version. The version can be a maximum of 18 characters and numbers. The value specified must match an application version defined for the group to which the satellite belongs as defined at the satellite control server. If it does, then scripts associated with this application version will be used to maintain the satellite during the synchronization process. A default version V1R0M00 has been supplied, but this value can be changed. These values can be set or changed after installation.

DB2.USERDB_NAME
Specifies the name for the database that DB2 can create during the installation of DB2 Satellite Edition. If no value is provided, the database is not created.

DB2.USERDB_REP_SRC
Specifies that the database will be used as a DB2 replication source. DB2 will configure the database so that changes to application data can be written to change tables by the Capture program. The Apply program will then use the captured changes to synchronize application data with other systems. In addition to configuring the database to capture data changes, you must define the application tables for which changes will be gathered. For more information on the data capture changes parameter of the CREATE TABLE statement, refer to the SQL Reference. This configuration step can be done when the installation process is complete and the application tables are defined in the database.

DB2.USERDB_RECOVERABLE
Specifies that the database on the satellite is recoverable. DB2 will configure the database for forward recovery by setting the logretain parameter to recovery. You will be required to manage the database log files and take backups of the database. Before the database can be used, you will have to back it up. If this keyword is not specified, the database will not be configured for forward recovery. Database log files will be managed automatically by DB2. You will not be required to take a backup copy of the database before the database can be used. However, data can be lost if a disk failure occurs.

DB2 Control Server Response File Keywords for Windows NT and Windows 2000

This section describes the most important keywords that you will specify when performing a distributed installation of the DB2 Control Server. The DB2 Control Server provides administrative and status reporting support for satellites by using the satellite control database SATCTLDB. This database is automatically created when the Control Server component is installed. These keywords can be used to specify the values of database manager configuration parameters and the values of the DB2 registry variables.

To install the Control Server, select the CONTROL_SERVER component (COMP=CONTROL_SERVER), which is only available on UDBEE.

CTLSRV.DEDICATED_CTLSRV
Specifies whether the system on which the DB2 Control Server will be installed and will be dedicated to the DB2 Control Server. Please note, a different DB2 instance will not be created on this system.

The default is YES, the system is dedicated.

CTLSRV.AUTOSTART
Specifies whether or not to automatically start the DB2 Control Server instance (DB2CTLSV) each time the system is rebooted.

The default is YES, the DB2CTLSV instance starts automatically.

CTLSRV.SVCENAME
Specifies the DB2 Control Server instance, TCP/IP service name and can be used to override the default service name generated by the installation program. When used in conjunction with the CTLSRV.PORT_NUMBER keyword to override the default port number, you have complete control over the TCP/IP configuration for the DB2 Control Server instance.

CTLSRV.PORT_NUMBER
Specifies the DB2 Control Server instance, TCP/IP service name and can be used to override the default service name generated by the installation program. When used in conjunction with the CTLSRV.SVCENAME keyword to override the default port number, you have complete control over the TCP/IP configuration for the DB2 Control Server instance.

Killing DB2 Processes During Interactive and Response File Installations

If any DB2 processes are running when the DB2 setup command is issued, the installation of DB2 cannot occur. For example, during an interactive installation, the following message is issued: DB2 is currently running and locked by the following process(es)

The user is then prompted to kill the DB2 processes so that the installation can proceed. You can specify that any running DB2 processes are killed when the DB2 setup command is issued (Windows 32-bit operating systems only).

To kill any running DB2 processes for an interactive installation, specify the /F option for the setup command. The /F option kills the running processes, and the message and prompt are not displayed.

For a response file installation, you can use either of the following methods to kill any active DB2 processes. If you specify either of these options, the active DB2 processes are killed before the installation proceeds.

Note:You should exercise extreme caution when you kill active DB2 processes so that an installation can occur. The termination of a DB2 process can cause the loss of data.

[ Top of Page | Previous Page | Next Page ]