User guide

given on the command line See Stopping Servers
for
more information
-stopclient <client_id>
Issues the Stop Client command which requests the
connected server to terminate the specified client
thread.
The <client_id> is an id of a client as displayed by
the Show Clients command See Stopping Clients
for
more information. There is no default value for
<client_id>
If the controller is invoked with the appropriate connect information and one of command
keywords, the controller will issue the desired request to the server, optionally display the
results, and terminate immediately.
If more than one command keyword is present, only one will be issued using the
precedence as shown in the preceding table.
Example
An example of issuing command keyword to the controller:
$java -jar rdb$jdbc_home:rdbthincontrol.jar -u jan –
-controlpass mpass -node nd1 -port 1701 –stopserver
6.1.2 Controller Command Line
If no command keyword is used on the controller invocation, the application will go into
command line prompt mode allowing multiple commands to be issued.
If valid connection information is provided at the controller invocation (node, port, user
and password), the controller will automatically attempt to connect to the specified server.
If a connection has not been established or a different server connection is required, then
the Connect command can be issued at the control command line. See Connecting to
Servers for more information.
If username and password are not provided on the connect command line, then the values
of the configuration options when the controller was invoked will be used. If a
configuration file is specified, the configuration file session characteristics will be used.
See Session Section
within XML formatted Configuration File for more information on
session characteristics.
Commands may be issued at the control command line either within the context of a server
connection or outside the context of a specific server connection.
69