It is crucial to the operation of Sybase products that the environment variables are set correctly. The Studio Installer sets environment variables during the installation process. During the installation process, the Studio Installer also generates a file that you can use to reset most of the environment variables. The list in this section describes Sybase environment variables.
Environment variables are set in the user’s environment either interactively or by including them in the user’s .login and .cshrc files (for C shell) or .profile file (for Bourne shell).
You can set environment variables by running the SYBASE.csh or SYBASE.sh script file after exiting the Studio Installer.
From a Bourne, enter:
. SYBASE.sh
From a C shell, enter:
source SYBASE.csh
The script file does not set jConnect or Java utility environment variables. See the product documentation http://www.sybase.com/support/manuals.
The environment variables are:
DSLISTEN – you can set this to the name that Adaptive Server uses to listen for client connections when one is not provided on the command line during start-up. If you do not set DSLISTEN, and you provide no name during start-up, the Adaptive Server name defaults to the server name given at installation. You cannot reset DSLISTEN by running the SYBASE scripts.
DSQUERY – defines the Adaptive Server name that client programs try to connect to if an Adaptive Server is not specified by name during a connection attempt. If you do not set DSQUERY, and you do not supply the Adaptive Server name, clients attempt to connect to the server name provided during installation. You cannot reset DSQUERY by running the SYBASE scripts.
SYBASE – defines the path of the Sybase installation directory. The installation program sets up the variable SYBASE to point to the release directory specified during installation.
SYBASE_ASE – defines the installation directory of Adaptive Server components.
SYBASE_OCS – defines the installation directory of Open Client.
SYBASE_SYSAM – points to the license-management software directory. You cannot rest SYBASE_SYSAM by running the SYBASE scripts.
LM_LICENSE_FILE – optionally points to the license.dat file in:
$SYBASE/$SYBASE_SYSAM/licenses
PATH – specifies which directory path to search for executables.The Sybase executables are located in the installed component’s /bin directory.
To use Java-based features such as XML, your PATH must specify the JDK 1.2 directory. For example: /opt/sybase/java1.2/bin, where /opt/sybase is the installation directory.
When using the setup files: SYBASE.csh or SYBASE.sh, the following paths are added to the beginning of the PATH environment variable:
$SYBASE/$SYBASE_ASE/bin:$SYBASE/$SYBASE_OCS/bin
LIBPATH – specifies which directory to search for executables. The Sybase executables are located in the installed component’s /bin directory.
When using the source files: SYBASE.csh or SYBASE.sh, the following paths are prepended to the LIBPATH environment variable:
$SYBASE/$SYBASE_ASE/lib:$SYBASE/$SYBASE_OCS/lib: $SYBASE/SYBASE_FTS/lib, etc.
For instructions on setting jConnect environment variables,
see the documentation for jConnect.
