SLAVE_SERVERS specifies hostname ( or IP address) and port number of TG which is running on a remote node. Specified this parameter, TG is act as a "Master server" and control slave servers.

ERROR_RECONNECT_COUNT parameter specifies the maximum counts that agents reconnect to the target database when the session has been cut. "Session has been cut" means like following cases.

- Instance was restarted unexpectedly durling agents operation.
- Agent had failed to send SQL specified times and session was cut.

When the agent has failed over ERROR_RECONNECT_COUNT times, agents give up to establish the connection.

* When this parameter is set to "0", retry is not executed.
* When this parameter is set to "-1", retry is executed unlimitedly.

cf. Waiting time before reconnecting is specified by ERROR_RECONNECT_WAIT parameter.

STATEMENT parameter specifies SQL statements performed in the transaction. Two or more STATEMENT phrases can be defined in one TRANSCATION field. The number of STATEMENT that can be registered in one TRANSACTION is 20 or less.

Incidentally, you can execute stored procedures as a transaction using "call <procedure name>".
* This function is supported by TG ver 0.82 or later.

e.g. 1)
<TRANSACTION
AVERAGE = 90
STATEMENT = select name , id from test;
>

e.g. 2)
<TRANSACTION
AVERAGE = 80
STATEMENT = insert into ntab values (idseq.nextval,':NAME0',to_date(':YEAR/:MONTH/:DAY','yyyy/mm/dd'));
STATEMENT = commit;
>

e.g. 3)
<TRANSACTION
AVERAGE = 10
STATEMENT = select * from test where id = :ID for update;
STATEMENT = update test set name = :NAME where id = :ID;
STATEMENT = rollback;
>

e.g. 4)
<TRANSACTION
AVERAGE = 5
STATEMENT = call statspack.snap();
>

JOB_TYPE parameter specifies the type of JOB.

Case1　JOB_TYPE = COMMAND
JOB is executed on the local node. EXECFILE parameter must be set to one command or text file where some commands are written.

Case2　JOB_TYPE = TELNET
JOB is executed on the remote node. EXECFILE parameter must be set to the text file where some commands are written.
* It is necessary to set up the TELNET server appropriately on the remote node to send some commands by using the TELNET protocol.

Case3　JOB_TYPE = SQL
JOB is executed on the target database server. EXECFILE parameter must be set to the text file where some SQL statements are written.

Case4　JOB_TYPE = PL/SQL
JOB is executed on the target database server. EXECFILE parameter must be set to the text file where some PL/SQL statements are written.

PORT parameter specifies the port number to connect to the remote node when TG executes a JOB.

Case1　JOB_TYPE = COMMAND
PORT parameter is not used.

Case2　JOB_TYPE = TELNET
PORT parameter must be set to the port number where TELNET server is listening. Default value is "23".

Case3　JOB_TYPE = SQL or PL/SQL
PORT parameter is not used.

PASSWORD parameter specifies the password to connect to the remote node when TG executes a JOB.

Case1　JOB_TYPE = COMMAND
PASSWORD parameter is not used.

Case2　JOB_TYPE = TELNET
PASSWORD parameter must be set to OS USER password.

Case3　JOB_TYPE = SQL or PL/SQL
PASSWORD parameter is not used.

USERNAME parameter specifies the username to connect to the remote node when TG executes a JOB.

Case1　JOB_TYPE = COMMAND
USERNAME parameter is not used.

Case2　JOB_TYPE = TELNET
USERNAME parameter must be set to OS USER name.

Case3　JOB_TYPE = SQL or PL/SQL
USERNAME parameter is not used.