Rereads the OpenSwitch configuration file at runtime.
rp_cfg config_file
The name of the configuration file to be reread. Passing a file name of NULL, default, an empty string, or simply deleting a previous entry, causes the previously processed configuration file to be reread.
This command causes the configuration file to be processed.
1> rp_cfg "OpenSwitch_ServerName.cfg" 2> go
This command causes the previously processed configuration file to be reread.
1> rp_cfg "default" 2> go
This command processes the OpenSwitch_ServerName.cfg file in /usr/sybase/config on the same host as the OpenSwitch server.
1> rp_cfg "/usr/sybase/config/OpenSwitch_ServerName.cfg" 2> go
On the Windows platform:
rp_cfg "c:\Sybase\OSW\config\OpenSwitch_ServerName.cfg"
This command processes the OpenSwitch_ServerName.cfg file in c:\sybase\OSW\config on the same Windows host as the OpenSwitch server.
When a new configuration file is processed, the way each section of the configuration file is processed differs, as described in Table 7-1.
Section |
Behavior |
|---|---|
[CONFIG] |
As new name=value pairs are processed within this section, the current value of name in OpenSwitch is replaced with value. Also, some variables, such as RMON, are meaningful only during start-up, so changing the value of these variables at runtime has no effect (for example, setting RMON to zero (0) does not cause the resource governor to be shut down after OpenSwitch has been started). |
[SERVER] |
All existing server information is replaced with the contents of the new configuration file. |
[COMPANION] |
The admin_user and admin_password is replaced with the values from the new configuration file if the companion server name remains the same. If you specify a different companion server name, restart OpenSwitch instead of reconfiguring it using rp_cfg. |
[POOL] |
All existing pool information is replaced with the contents of the new configuration file. |
[LIMIT_RESOURCE] |
When the new configuration file is processed, all existing [LIMIT_RESOURCE] settings are cleared and replaced by the contents of this section. |
After verifying that the specified config_file exists, rp_cfg clears all [LIMIT_RESOURCE] settings before processing the contents. Therefore, if this processing stops before completion, due to a syntax error, these settings may be only partially available within OpenSwitch, and the configuration file must be corrected and reprocessed.
rp_cfg removes all available pools in OpenSwitch before it processes the new configuration file. Therefore, there is a small window where no pools are available, and if a client connects at that time, it is disconnected. However, this does not affect existing connections, and since rp_cfg executes quickly and the window is almost negligible. If this causes concern, run rp_cfg when there is are fewer clients connecting to OpenSwitch.
Do not use rp_cfg to reconfigure OpenSwitch; use another registered procedure call instead. For example, to change a [CONFIG] parameter, use rp_set (see rp_set); to add a server from to pool, use rp_pool_addserver (see rp_pool_addserver); to remove a server from a pool, use rp_pool_remserver (see rp_pool_remserver).
Do not use rp_cfg to change the following configuration parameters. Because these parameters are read only once when OpenSwitch starts, changing them at runtime has no effect on a running OpenSwitch. To change these parameters, stop and restart OpenSwitch with new values set in the configuration file.
API_CHECK |
LOGIN_TIMEOUT |
RMON_INTERVAL |
CHARSET |
MAX_LOGSIZE |
SEC_PRINCIPAL |
CMON |
MAX_PACKETSIZE |
SERVER_NAME |
CONNECTIONS |
MSGQ_SIZE |
SRV_TRACE |
CTX_TRACE |
MUTUAL_AWARE |
STACKSIZE |
DEBUG_FILE |
MUTUAL_CLUSTER |
TRUNCATE_LOG |
ECHO_LOG |
PING_THREAD |
UPDATE_CFG |
INTERFACES |
RESPONSE_TIMEOUT |
USE_DONEINPROCS |
LOG_FILE |
RMON |
USERNAME_PASSWORD_ENCRYPTED |
rp_cfg was run with an argument of default or “” and no previous configuration file is available:
rp_cfg: No default configuration is available.
For example, this message appears if OpenSwitch was started without a configuration file.
This message usually indicates that a syntax error was encountered while processing the configuration file:
rp_cfg: Error while processing 'config_file'. See error logs.
You can find detailed information in the OpenSwitch error logs.
The configuration file was successfully processed, and new settings have taken effect:
rp_cfg: Successfully processed configuration file 'config_file'.
