|
This chapter explains how to control TG in the command-line. |
| |
| AUTOEXEC |
| |
Synopsis |
: |
autoexec < on | off > |
| options |
: |
|
| |
|
- |
| |
|
enables or disables a job executed automatically. When this setting is made "OFF", Even if the event set as a trigger occured, JOB is not executed. |
| |
| |
| CHECK |
| |
Synopsis |
: |
check config |
| options |
: |
|
| |
|
config |
| |
|
tests agent be able to connect to the target database using a current configration. |
| |
| |
| DELETE |
| |
Synopsis |
: |
delete config < config-name > |
| options |
: |
|
| |
|
config < config-name > |
| |
|
deletes specified configration which is registered in TG. |
| |
| |
| EDIT |
| |
Synopsis |
: |
edit config
edit job <job-number> |
| options |
: |
|
| |
|
config |
| |
|
Open current configration using a editor which is specified by EDITOR system parmeter. |
| |
|
|
| |
|
job <job-number> |
| |
|
Open specified JOB by job-number using a EDITOR which is specified by EDITOR system parmeter. |
| |
| |
| EXECUTE |
| |
Synopsis |
: |
execute job < job-number > |
| options |
: |
|
| |
|
job < job-number > |
| |
|
execute specified JOB by job-number manually. The JOB of which JOB_TYPE is "USER_REQUEST" is never executed as long as this command is not used. |
| |
| |
| EXIT |
| |
Synopsis |
: |
exit |
| options |
: |
|
| |
|
- |
| |
|
Terminates TG. |
| |
| |
| HELP |
| |
Synopsis |
: |
help |
| options |
: |
|
| |
|
- |
| |
|
Access the command-line help system. |
| |
| |
| LIST |
| |
Synopsis |
: |
list config |
| options |
: |
|
| |
|
config |
| |
|
Displays the list of jobs which are registed in TG. |
| |
| |
| MASTERSERVER |
| |
Synopsis |
: |
masterserver < on | off > |
| options |
: |
|
| |
|
- |
| |
|
Change Multi-server mode on / off. When this setting is made "OFF", REMOTE_SERVER parameter is ignored. |
| |
| |
| MONITOR |
| |
Synopsis |
: |
monitor [ detail | summary ] [ < monitoring-time > ] [ wait ]
|
| options |
: |
|
| |
|
- |
| |
|
Monitors agent status until the return key is hit. The meaning of each field is as follows.
| |
Ags |
: |
Displays the command that is issued to agents. Agents try to change them directed status. However, Agents waiting results of the query might take time for a while to change their status.
- DISC(DISCONNECTED)
Agents are disconnecting or disconnected from the target database.
- WAIT(WAITING)
Agents are freezing or trying to stop transactions.
- ACTV(ACTIVE)
Agents are executing or trying to start transactions. |
| |
|
|
|
| |
Act |
: |
Displays the number of active agents. |
| |
|
|
|
| |
SES |
: |
Displays the number of agents that are connected with the target database. |
| |
|
|
|
| |
ErD |
: |
Displays the number of agents that are disconnected from the target database due to the error or trouble of the database. |
|
|
|
| |
ERR |
: |
Displays the number of agents that are failed to execute the query. |
| |
|
|
|
| |
TPS |
: |
Displays the number of transactions that are executed in one second. |
|
| |
|
|
| |
|
[ < monitoring-time > ] |
| |
|
Specifies the monitoring time in seconds. When you want to stop the monitoring, use RESETMONITOR command. |
| |
|
|
| |
|
[ wait ] |
| |
|
The prompt is not returned until the monitoring period ends. This command is used to execute TG from the batch file or the shell script. |
| |
| |
| NORMAL |
| |
Synopsis |
: |
normal |
| options |
: |
|
| |
|
- |
| |
|
Changes agent status from verbose-mode to normal-mode. For details of verbose-mode, see the section of VERBOSE command. |
| |
| |
| RELOAD |
| |
Synopsis |
: |
reload config |
| options |
: |
|
| |
|
config |
| |
|
When configuration file (tg.conf) is changed, the change is reflected in TG. This command cannot be executed while Agent is connecting with the target database. In that case, execute this command again after issuing the DISCONNECT command and breaking the connection. |
| |
| |
| REGIST |
| |
Synopsis |
: |
regist config < config-name > |
| options |
: |
|
| |
|
config < config-name > |
| |
|
Registers a current configration in TG giving a name. The registered configuration can be called by the REPLACE command. |
| |
| |
| RENAME |
| |
Synopsis |
: |
rename config < old config-name > < new config-name > |
| options |
: |
|
| |
|
config < old config-name > < new config-name > |
| |
|
Renames specified configration name. |
| |
| |
| REPLACE |
| |
Synopsis |
: |
replace config < config-name > |
| options |
: |
|
| |
|
config < config-name > |
| |
|
Loads specified configuration which is registered in TG. When this command is issued, current configration is overwrited with the loaded configuration. |
| |
| |
| RESETMONITOR |
| |
Synopsis |
: |
resetmonitor |
| options |
: |
|
| |
|
- |
| |
|
Stops the monitoring forcely which is given a period using MONITOR <monitoring time> command. |
| |
| |
| SET |
| |
Synopsis |
: |
set drivertype < thin | oci | oci8 >
set hostname <hostname or IP address>
set logfile <logfile-name>
set password <password>
set port <port-number>
set sessions <amount of agents>
set sidname <SID-name>
set thinktime <thinktime>
set tnsnames <tnsnames>
set username <user-name> |
| options |
: |
|
| |
|
- |
| |
|
Gives a value each parameter.
* When TG ends, the value given by the SET command is lost. |
| |
| |
| SHOW |
| |
Synopsis |
: |
show config
show sysconfig
show trans
show variables
show jobs |
| options |
: |
|
| |
|
- |
| |
|
shows each configuration.
| |
Config |
: |
Shows the configration which is used by agents connecting to the target database. This configration is specified at the field of DATABASE in "tg.conf" configration file. |
| |
|
|
|
| |
Sysconfig |
: |
Shows the whole attribution of TG. For example, log filename, editor, etc ... |
| |
|
|
|
| |
Trans |
: |
Shows the transaction information registered in TG. This information is specified at the field of TRANSACTION in "tg.cong" configration file. |
| |
|
|
|
| |
Variables |
: |
Shows the random variables information registered in TG. This information is specified at the field of VARIABLE in "tg.conf" configration file. |
|
|
|
| |
Jobs |
: |
Shows the jobs information registered in TG. This information is specified at the field of JOB in "tg.conf" configration file. |
|
| |
| |
| SPOOL |
| |
Synopsis |
: |
spool <spool filename | on | off > |
| options |
: |
|
| |
|
<spool filename | off > |
| |
|
Stores query results in the specified logfile. |
| |
|
|
| |
|
< on | off > |
| |
|
Stores query results in the "YYYYMMDDHH24MISS.log" logfile. |
| |
| |
| VERBOSE |
| |
Synopsis |
: |
verbose [Agent-ID] |
| options |
: |
|
| |
|
- |
| |
|
Changes agent status into the verbose-mode. Verbose Mode lets you look at the actual agents processing. Executing SQL statements, getting results of the query, etc... However, verbose-mode consumes a lot of CPU time. Please use this mode only for specific. |
| |
|
|
| |
|
[ Agent-ID ] |
| |
|
Changes specified agent into the verbose-mode with Agent-ID. |
| |
| |
| ! |
| |
Synopsis |
: |
!<command> |
| options |
: |
|
| |
|
< command > |
| |
|
Executes external commands or batch files, shell scripts, etc. |
| |
| |
| CONNECT |
| |
Synopsis |
: |
connect [ all ] |
| options |
: |
|
| |
|
- |
| |
|
Generates agents and makes them connect to the target database. The number of agents is specified at SESSIONS parameter in "tg.conf" configration file.。 |
| |
|
|
| |
|
[ All ] |
| |
|
The prompt is not returned until all Agents connect to the target database. This option is used when TG is executed in a batch file or schell script. |
| |
| |
| DISCONNECT |
| |
Synopsis |
: |
connect [ all ] |
| options |
: |
|
| |
|
- |
| |
|
Makes agents disconnect from the target database. |
| |
|
|
| |
|
[ All ] |
| |
|
The prompt is not returned until all Agents disconnect from the target database. This option is used when TG is executed in a batch file or schell script. |
| |
| |
| START |
| |
Synopsis |
: |
start |
| options |
: |
|
| |
|
- |
| |
|
Changes agent status from "WAIT" into "ACTIVE".
*This command can be issued When agent status is "WAIT". |
| |
| |
| STOP |
| |
Synopsis |
: |
stop |
| options |
: |
|
| |
|
- |
| |
|
Changes agent status from "ACTIVE" into "WAIT".
*When this command is issued, the session between Agents and the target database is kept, never cut. |
| |
|
