Overview of configuration for Open Server

All Open Server applications require some basic configuration information, obtained during initialization and connection, including:

  1. The location of the Sybase installation directory as defined by the SYBASE environment variable.

  2. A locale name. Open Server uses the values of the following POSIX environment variables as locale names:

    • LC_ALL

    • LANG, if LC_ALL is not defined

    Open Server later uses this value to obtain localization information from locales.dat. If neither environment variable is defined, Open Server uses “default” as the locale name.

  3. Localized message and character set files. Open Server looks in locales.dat for an entry whose name matches the locale name determined above. Open Server then loads the localized messages and character set files specified in locales.dat.

  4. The name of the target server. Open Server obtains the name of the Open Server application from one of the following sources, in the order listed:

    • The Open Server application, which can provide the server name in the call to srv_init

    • The DSLISTEN environment variable, if the application does not specify its name

    • The default name SYBASE, if DSLISTEN is not set

  5. The target server’s network address. Open Server gets the target server’s address(es) from either the directory service or from interfaces:

    Directory service – Open Server looks for an entry in the [DIRECTORY] section of libtcl.cfg to determine where to look up server address information. The setting of the CS_DS_PROVIDER property determines which [DIRECTORY] entry the application searches for, or defaults to the first entry of the [DIRECTORY] section.

    interfaces – If a directory service is not used, or if it is used and fails, Open Server searches for the SERVERNAME entry in interfaces that matches the name as determined above and uses the corresponding target address.

  6. When a client requests a connection that uses a network-based security mechanism, Open Server looks up the corresponding security driver in the [SECURITY] section of libtcl.cfg.