oplrqb 

Starts the Broker in background mode.

oplrqb -v

Starts the Broker in background mode and displays version information as part of startup process.

oplrqb -dv

Starts the Broker in foreground debug mode using default log level 7 (most amount of session log information). This occupies your terminal session in the foreground, and echoes the output of all OpenLink Data Access Clients to the terminal window.

oplrqb -dvl 1

Starts the Broker in foreground debug mode using default log level 1 (lowest amount of session log information). This occupies your terminal session in the foreground, and echoes the output of all OpenLink Data Access Clients to the terminal window.

oplrqb -dvL /tmp/openlink.log

Starts the Broker in foreground debug mode using default log level 7 (most amount of session log information). This occupies your terminal session in the foreground, and echoes the output of all OpenLink Data Access Clients to the file "/tmp/openlink.log" .

oplshut 

Shuts down the Request Broker on the local machine. When a connection is still active, and the user calls oplshut without additional arguments, the broker will enter a gracefull shutdown state which means that it will not accept any new connections, but remains active until all active connections are terminated.

The shutdown state will be reported on the foreground screen or broker log:

oplrqb: shutdown mode initiated by openlink@127.0.0.1

Any client that tries to connect to the broker will get the following error message:

odbctest DSN=ora8i
OpenLink ODBC Demonstration program
This program shows an interactive SQL processor
[OpenLink][ODBC]the broker is being shut down, SQLSTATE=08004
[OpenLink][ODBC]Connection rejected by data source, SQLSTATE=08004

oplshut -f 

Shuts down the Request Broker on the local machine without waiting for clients to terminate.

If you use the -f (or force) flag, the broker will kill all active connections regardless what the client application is doing, which can lead to problems if the applications are not written to handle such events. Depending on the database, open transactions will be rolled back etc.

Many databases like Oracle and Progress implement the same concept where the gracefull shutdown option is the default, but a shutdown can be forced in case of a big calamity, or when a connection remains lingering.

oplshut -fy 

Same functionality as prior command, but without asking for confirmation.

oplshut +port 16000

Shuts down the Request Broker running on the TCP Listen port of "16000". Note that the default Request Broker Listen port is 5000, thus this option is not necessary unless you specified a different Listen port at install-time.

oplshut -s 

Shows the current active OpenLink Data Access Client connections.

oplshut -k 81 93 

Try to terminate the database agent sessions with process IDs 81 and 93.

oplshut -h 12.34.56.78

Shuts down the Request Broker on remote machine with IP address "12.34.56.78".

When:

	Note 1:
	When starting oplrqb without options, it will attempt to auto start an existing service. if that fails, it will attempt methods 2 and 3 (see below)

	Note 2:
	You'll need to do +service create first, the broker doesn't do this by itself.

When:

	Note:
	Start up mode is different when launched from a dos box. If there are no command line options specified, the broker will now default to +debug when started in a dos box. the +foreground and +debug options take precedence over method 1 (starting the service)

When:

	Note:
	It will attempt to locate oplrqb.ini in the current directory, unless +config file has been specified.

To summarize, here is some pseudo code:

if OS = NT or OS = Win2000 or OS = XP then
  if no +foreground or +debug options then
    if there is a service installed then
      silently attempt to start the service
      if this succeeds then exit
    endif
endif
if +foreground or +debug options then
  allocate a debugging console
  run in the foreground
else if started from a dos box then
  set +foreground and +debug
  allocate a debugging console
  run in the foreground
else
  create the splash window and assume tray behavior
endif
Note: it is possible to make the oplrqb service allocate a debugging
console. To do this, specify +debug while creating the service
(example: oplrqb +service create +debug)

Multiple instances of the broker work only for NT/XP/2000 when running as a service.

There is one default instance (unnamed) which is used when no +instance command line flag has been specified.

examples:

oplrqb +service create

Registers the default service instance. This service will use the oplrqb.ini rulebook in the current directory

oplrqb +service create +instance 1 +config f:\openlink

Registers the oplrqb_1 service instance This service will use the oplrqb.ini rulebook in f:\openlink

oplrqb +service create +config f:\openlink\test\debug.ini +debug

Registers the default service instance. This service will use the debug.ini rulebook in f:\openlink\test This service will produce debug output in a console. This service will not auto start, use oplrqb +service start

Other service commands:

  +service auto [+instance id]    Set start up type to Automatic
  +service manual [+instance id]  Set start up type to Manual
  +service start [+instance id]   Start up the service
  +service stop [+instance id]    Stops up the service
  +service delete [+instance id]  Unregisters up the service

+service list has been extended to show the rulebook that the instance uses as well as other status information.

To configure another Broker instance manually: