- Installing DB2 UDB Servers
- Before You Begin
- Installing DB2 UDB
- Installed Directory Structure
- Considerations in an NIS Environment
- Distributed Installation
- Sample Response Files
- Creating a Response File
- Distributed Installation with a Response File
- Installing DB2 with db2_install
- DB2 UDB Environment Definitions
- DB2 Profile Registry
- Managing the DB2 Profile Registry
- The db2set Command
- Environment Variables
- Hierarchy of the DB2 UDB Environment
- DB2 Administration Server (DAS)
- DAS Process
- DB2 Instances
- Creating the Sample Database
- Using the Command Line Processor (CLP)
- Uninstalling DB2 Products
- Stopping the DAS Instance
- Stopping All DB2 Instances
- Removing the DAS Instance
- Removing DB2 Instances
- Removing DB2 Products
DB2 Profile Registry
Much of the DB2 UDB environment is controlled by entries stored in the DB2 Profile Registry. The objective of the Profile Registry is to consolidate the DB2 UDB environment; so, key controlling factors are centrally located and easily managed. Many registry values control DB2 interfaces or communication parameters; so, the variables set in the Profile Registry may vary by platform. The following are some of the parameters that may be set in the DB2 Profile Registry.
DB2CODEPAGE— This applies to all platforms. If not set, DB2 UDB will use the code page set for the OS.
DB2DBDFT— The default database for implicit connections.
DB2COMM— This applies to all DB2 UDB servers that participate in a client/server environment. It specifies which DB2 UDB communication listeners are started with DB2 UDB.
The primary purpose of a registry is to allow you to make environmental changes without rebooting.
For a complete list of parameters and values, refer to the DB2 online documentation for Registry Variables, as shown in Figure 2.34.
Figure 2.34. Registry Variable Documentation