•
Note: The DB2 DB2ICRT command is not available for a non-root installation of DB2 database products on Linux and UNIX operating system.On Linux or UNIX operating systems, this utility is located in the DB2DIR/instance directory, where DB2DIR represents the location where the DB2 Connect is installed. On Windows operating system, this utility is located under the DB2PATH\bin directory where DB2PATH is the location where the DB2 Connect is installed.The db2icrt command takes the following parameters:Next, use CATALOG TCP/IP NODE, CATALOG DCS DATABASE and CATALOG DATABASE step by step to finish the connection setup.The CATALOG TCP/IP NODE command syntax is as follows:CATALOG TCP/IP NODE takes the following parameters:Specifies that a TCP/IP administration server node is to be cataloged. This parameter cannot be specified if the SECURITY SOCKS parameter is specified.
Note: The CATALOG DCS DATABASE command syntax is as follows:CATALOG DCS DATABASE takes the following parameters:The DB2 CATALOG DATABASE command syntax is as follows:DB2 CATALOG DATABASE takes the following parameters:The authentication value is stored for remote databases (it appears in the output from the LIST DATABASE DIRECTORY command) but it is not stored for local databases
• Set the DB2INSTANCE environment variable to reference the instance that contains the databases that you want Tuxedo to use. Set the PATH variable to include the DB2 Connect directories. Confirm the User ID and Password that can connect to the DB2 databases, you could find some example below:
• Update the tp_mon_name database manager configuration parameter with the value TUXEDO. This parameter identifies the name of the transaction processing (TP) monitor product being used.You can activate the concentrator feature by setting the value of MAX_CONNECTIONS to any number greater than the default. The default value for MAX_CONNECTIONS is equivalent to the value of MAX_COORDAGENTS. Because each application will have one logical agent, MAX_CONNECTIONS actually controls the number of applications that can be connected to the database instance, while MAX_COORDAGENTS controls the number of inbound connections that can be active at any time. MAX_CONNECTIONS will take a numeric range from MAX_COORDAGENTS up to 64,000. The default number of logical agents is equal to MAX_COORDAGENTS.
• Add a definition for DB2 Connect to the Tuxedo resource manager definition file ($TUXDIR/udataobj/RM). In the examples that follow, UDB_XA is the locally-defined Tuxedo resource manager name for DB2 Connect, and db2xa_switch_std is the DB2-defined name for a structure of type xa_switch_t.If no, the system database directory entry must have been incorrectly cataloged using AUTHENTICATION SERVER (this is the default if AUTHENTICATION is not specified explicitly). If this is the case, then re-catalog the entry using AUTHENTICATION DCS or CLIENT.Password is not available to send to the target server database. If the system database directory entry is cataloged using AUTHENTICATION DCS, then a password has to be flowed from the DB2 Client to the target server database. On certain platforms, for example AIX, the password can only be obtained if it is provided on the CONNECT statement.