Starting an RCM at the command line

You must start OpenSwitch before starting the RCM.

To start an RCM at the command prompt, enter:

rcm -c config_file -e system_log -i sql.ini_or_interfaces_file

You cannot start the RCM as a Windows service.

Syntax

This section describes the command syntax and command line flags you can set at RCM start-up.

rcm [-v] [-h] [-a] [-R]

     [-c config_file]

     [-e system_log]

     [-i sql.ini or interfaces_file]

     [-T trace_flags]

     [-E filename]

Command line flags

-v – prints the version number and the copyright message, then exits.

-h – prints the help message and exits.

-a – analyzes the replication environment and exits. The RCM:

Tests the configuration parameters and prints the results to stdout

Validates all configuration parameters

Connects to the OpenSwitch server

Logs in to the active Adaptive Server

Verifies that the active databases exist

Logs in to the standby Adaptive Server

Verifies that the standby databases exist

Logs in to the Replication Server

Verifies that the logical connection exists

Tests the ranges of the tuning parameter values

See “Tuning” for more information about setting these values.

Tests the notification process if the NOTIFICATION_PROCESS parameter is set (see “Understanding RCM configuration parameters”)

Prints out all configuration parameters
-R – indicates that the current instance of RCM is redundant. When you use the -R flag, you indicate that the redundant RCM does not perform a failover, handles command processing for the secondary OpenSwitch, and assumes the control of failover if it loses its connection to the primary OpenSwitch.
-c config_file – the full path name of the RCM configuration file. If you omit the -c flag, the RCM looks for a configuration file named rcm.cfg in the current directory.
-e system_log – the full path name of the system log file. The RCM writes all system, error, and trace messages to the system log file. If you omit the -e flag, the RCM writes messages to a file named rcm.log in the current directory.
-i sql.ini_or_interfaces_file – the full path name of the Sybase sql.ini (Windows) or interfaces (UNIX) file that the RCM searches when connecting to servers. If you omit the -i flag, the RCM looks for the sql.ini (Windows) or interfaces (UNIX) file in the directory to which the SYBASE environment variable points.

On UNIX, the default interfaces file is in the Sybase installation directory ($SYBASE). On Windows, the default sql.ini is in %SYBASE%/ini.

-T trace_flags – this flag sets trace flags in the RCM. Use this flag to debug your environment. Following is the list of valid trace flags. To set more than one flag, use a comma-separated list; for example, -T A,C,F.

A	Set all trace flags.
C	Displays information on connectivity issues, including connecting and disconnecting from servers and executing commands.
E	Traces execution of the RCM when resolving OpenSwitch connection issues. It also displays end-user connection information, such as user, application, requested server, and so on.
F	Traces the execution of the failover process when the RCM coordinates the switching from the active and standby databases.
G	Displays general or miscellaneous information.
I	Traces the RCM’s initialization steps, including reading the configuration file, installing the callback handlers, and connecting to the OpenSwitch.
M	Writes all messages generated by the RCM to the system log. These messages include all connectivity messages and all messages sent to the RCM by Replication Server and Adaptive Server.
N	Displays all notification process messages.
O	Writes OpenSwitch server messages and connectivity messages generated from connections between the RCM and the OpenSwitch to the system log. Situations generating these messages are usually handled by the RCM, so these messages are typically redundant.
R	Traces the process of coordinating multiple OpenSwitch servers.
S	Writes all commands that the RCM sends to other servers to the system log.

-E filename – user name and password encryption. You can provide an optional filename argument. If you provide a filename, that file is created and the encrypted user names and passwords are written to that file and to the console. If you do not provide a filename, the encrypted user names and passwords are written only to the console.