DB2 Connect Quick Beginnings for Linux**

Step 7. Update the DB2 Connect Configuration

If you are not planning to use applications that employ multisite updates, skip this step and go to Step 6. Bind Utilities and Applications to the Database Server.

If multisite update (two phase commit) applications will be used at this workstation, you will need to provide information regarding the required DB2 Transaction Manager Database (for example, the TM_DATABASE). This assigned database will be used by DB2 to store information about inflight transactions.

At a command line prompt, enter the following command to update the Database Manager Configuration:

   db2 update dbm config using TM_DATABASE 1st_conn

where TM_DATABASE can have one of the following settings:

• 1ST_CONN, the first database that a connection is established to will be used as the Transaction Manager database for transactions. If this option is used, then the first database connected to must be either a DB2 Universal Database Version 5 or later database, or a DB2 Universal Database for OS/390 Version 5.1 or later database. This is the recommended setting, and it is the default value for TM_DATABASE.
• database_name, the named database that is connected to will be used. If this option is used, we recommend that the named database should be either a DB2 Universal Database version 5 or later database, or a DB2 Universal Database for OS/390 Version 5.1 or later database.