Netware NLM Exception

The NLM requires a utility to internally “rename” the ctsrvr.nlm binary. The NLM’s internal binary name (not to be confused with the Server Name defined in the ctsrvr.cfg file) must be unique for each NLM. The unique NLM name is accomplished with the RENNLM.EXE or RENNLMW.EXE utilities. Execute RENNLM.EXE at the command line as follows, or see the RENNLMW.EXE description below:

Each c-treeACE Server must have a separate configuration file. Since the default would point to the same file, a command line option was added to specify a configuration file when loading the c-treeACE Server. CTSRVR_CFG must be followed by the full path and file name for the configuration file, for example:

CTSRVR_CFG <path and filename>

Specify the configuration file used when executing the c-treeACE Server from the command line.

Default: Server Working directory

In addition to specifying a unique configuration file, each c-treeACE Server must be assigned a unique LOCAL_DIRECTORY and SERVER_NAME in the configuration file.

SERVER_NAME <NAME>

A name assigned to c-treeACE Server, instead of the default name.

Default: FAIRCOMS

See Also

SERVER_PORT (SERVER_PORT, http://www.faircom.com/doc/ctserver/48603.htm)

LOCAL_DIRECTORY <Path>

One of two mutually exclusive ways to supply the c-treeACE 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\. See SERVER_DIRECTORY for the other method. The trailing slash is required. If a LOCAL_DIRECTORY name is defined in the configuration script, the name will be attached to the beginning of any file name that is not absolute. If neither LOCAL_DIRECTORY nor SERVER_DIRECTORY is supplied, database and system files are stored relative to the c-treeACE Server working directory. LOCAL_DIRECTORY and SERVER_DIRECTORY cannot be used together.

SERVER_DIRECTORY <path>

See LOCAL_DIRECTORY

This configuration option has been deprecated as of c-treeACE V9.3 and later. LOCAL_DIRECTORY is now the preferred keyword to allow the server to store data and files in an alternative location. The SERVER_DIRECTORY option did not offer robust handling of relative file paths. Full paths were the only good way to ensure proper functionality. For example, with Replication and restoring dynamic dumps, a relative path caused problems in properly locating files.

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.

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

LOG_EVEN

LOG_ODD

START_EVEN

START_ODD

Legacy Notes: One of two mutually exclusive ways to supply the name of a directory path the c-treeACE Server uses 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\. See LOCAL_DIRECTORY for the other option. The trailing slash is required. If a SERVER_DIRECTORY name is defined in the configuration script, the name is attached to the beginning of any file name that is not absolute. If no SERVER_DIRECTORY or LOCAL_DIRECTORY name is supplied, all database and system files are stored relative to the c-treeACE Server working directory. SERVER_DIRECTORY and LOCAL_DIRECTORY cannot be used together. SERVER_DIRECTORY does not affect the location of the c-treeACE Server Status log, the transaction log files, or the start files.

Note: The SERVER_DIRECTORY, unlike LOCAL_DIRECTORY, becomes a part of the file name. The name entered into the transaction log includes the SERVER_DIRECTORY.

Default: Server working directory

Note: The LOCAL_DIRECTORY does not become a permanent part of the file name. The name entered into the transaction log does not include the LOCAL_DIRECTORY.

Default: Server’s working directory