Database Administrator's Guide

NULL_STRING

NULL_STRING null

This option is used in conjunction with the tamper-proof settings file under the server. Configuration options that are in the encrypted settings file, ctsrvr.set, cannot be overridden in the ctsrvr.cfg file. The NULL_STRING keyword lets you define a symbol that represents a null string so that options can be blocked in the settings file without activating them.

This is an encrypted file restricted to administrators at certain FairCom installations.

LOCAL_DIRECTORY null

With the above entry example in the server settings file, LOCAL_DIRECTORY is blocked from use in the standard ctsrvr.cfg file but it is not activated.

LOCAL_DIRECTORY <Path>

The preferred way to supply FairCom Server with the name of a directory path for processing files without absolute names. Absolute names include a specific volume or drive reference as part of the name, for example, d:\fairserv\data\. The trailing slash is required.

Note: The other method, the SERVER_DIRECTORY configuration option, has been deprecated. LOCAL_DIRECTORY is the preferred keyword to allow the server to store data and files in an alternative location.

SERVER_DIRECTORY <path>

See LOCAL_DIRECTORY (LOCAL_DIRECTORY, LOCAL_DIRECTORY)

Note: This configuration option has been deprecated as of FairCom DB V9.3 and later. LOCAL_DIRECTORY (LOCAL_DIRECTORY, LOCAL_DIRECTORY) is now the preferred keyword to allow the server to store data and files in an alternative location.

To avoid potential problems with the use of this option, it has been disabled. When this option is specified in ctsrvr.cfg, the c-tree Server fails to start and displays the following message:

The SERVER_DIRECTORY option is no longer supported.

Use the LOCAL_DIRECTORY option instead.

The message is logged to CTSTATUS.FCS. On Unix systems it is also written to standard output and on Windows systems it is displayed in a dialog box when the c-tree Server is not running as a Windows service.

Relocating Transaction Logs

Use these configuration keywords to relocate transaction logs if this has been the purpose of using this keyword in the past:

LOG_EVEN (LOG_EVEN, LOG_EVEN)

LOG_ODD (LOG_ODD, LOG_ODD)

START_EVEN

START_ODD

These configuration options can include an environment variable name that will be substituted with its value when the configuration file is read.

Legacy Notes

The SERVER_DIRECTORY option was one of two mutually exclusive ways to supply the name of a directory path the FairCom DB Server used when processing all files not having absolute names (i.e., absolute names include a specific volume or drive reference as part of the name). For example, d:\fairserv\data\ (the trailing slash was required). The other option, LOCAL_DIRECTORY (LOCAL_DIRECTORY, LOCAL_DIRECTORY), is now the preferred keyword to allow the server to store data and files in an alternative location.

If a SERVER_DIRECTORY name was defined in the configuration script, the name was attached to the beginning of any file name that was not absolute. If no SERVER_DIRECTORY or LOCAL_DIRECTORY name was supplied, all database and system files were stored relative to the FairCom DB Server working directory. SERVER_DIRECTORY and LOCAL_DIRECTORY cannot be used together. SERVER_DIRECTORY did not affect the location of the FairCom DB Server Status log, the transaction log files, or the start files.

Note: The SERVER_DIRECTORY, unlike LOCAL_DIRECTORY, became part of the file name. The name entered into the transaction log included the SERVER_DIRECTORY.

Default: Server working directory