Select this option if the application is not managed by a transaction processing (TP) monitor. If you are unsure whether a TP monitor is used, select this option.
Select this option if a transaction processing (TP) monitor manages the application. Users of IBM WebSphere and Microsoft Transaction Server do not require this parameter to be set.
Select a TP monitor from the drop-down list or type the name of another TP monitor.
Select this option if you intend to use TCP/IP to connect to a host or AS/400 database.
See the Installation and Configuration Supplement for more information about setting up TCP/IP.
Select this option if you intend to use SNA to connect to a host or AS/400 database, or if you intend to use SNA to connect from a host or AS/400 client.
See the Installation and Configuration Supplement for more information about setting up SNA.
Select this option if you want to use the first database to which your application connects.
If the keyword 1ST_CONN is defined for the TM_DATABASE parameter, the first database to which the application connects in the transaction will be used as the transaction manager (TM) database.
The DB2 transaction manager (TM) assigns identifiers to transactions, monitors their progress, and assumes responsibility for transaction success or failure. The information about a transaction is stored in the designated TM database.
Select this option to select a specific database as the transaction manager (TM) database.
Select a database from the drop-down list or type the name of another database.
Specifies that DB2 Universal Database for OS/2, Windows or UNIX servers is involved in the multisite update.
Specifies that DB2 for OS/390 Version 5.0, DB2 Universal Database for OS/390 Version 6.0, or later is involved in the multisite update.
Specifies that any other type of database server or version of the product is involved in the multisite update.
TCP/IP is the only protocol used among servers involved in the multisite update. If you are not sure, select No.
Other protocols, in addition to TCP/IP are used among servers involved in the multisite update. If you are not sure, select No.
Identifies the name of the sync point manager (SPM) for the given instance. This field is prefilled with the machine's TCP/IP host name. If TCP/IP is not available on the machine, this field is blank. If you have redefined the machine's TCP/IP host name, then this new value prefills this field.
If SNA is used for communication between the host or AS/400 and the DB2 Connect or DB2 LAN-based server, then this field contains a local logical unit (LU) alias. You must ensure that your host or AS/400 can communicate with an LU by this name. If you are required to use a specific LU, then type the LU alias of that LU over the prefilled value, or select one from the list if a list is available.
Note: This LU will be created or verified by DB2 Connect or DB2 Universal Database.
If TCP/IP is used for communication between DB2 Connect and DB2 for OS/390 Version 5.0 or later, then this field contains a unique name within your network. If you know that the prefilled value conflicts with another DB2 Connect instance (on this or any other workstation) then change the value to be unique.
Note: Performing a multisite update using TCP/IP is only supported by DB2 Connect workstations accessing DB2 for OS/390 Version 5.0 or later servers.
The sync point manager log file size should be large enough to maintain performance, but small enough to prevent wasted space. The size required depends on the number of transactions using protected conversations, and how often COMMIT or ROLLBACK is issued.
This field contains a default value. Optionally, you can adjust this value, by typing a log file size in the field.
Specifies the directory where the sync point manager (SPM) logs are written. By default, the logs are written to the sqllib\spmlog directory, which, in a high-volume transaction environment, can cause an I/O bottleneck. Use this parameter to have the SPM log files placed on a faster disk than the current sqllib\spmlog directory. This allows for better concurrency among the SPM agents.
Identifies the number of agents that can simultaneously perform resync operations. The default is 20, and the allowable range is 10 - 256 agents.
Accept the default value or type a value in the allowable range.