Client-Library and Server-Library support dynamic loading of directory and security drivers. This allows you to change a driver that an application uses and to use features as they become available at your site, without re-linking the application.
$SYBASE/$SYBASE_OCS/config/libtcl.cfg configures directory and security drivers. This file maps symbolic strings to the appropriate driver and any required initialization information.
Client-Library or Server-Library applications, including Sybase utility programs such as dscp, locate the appropriate drivers specified in libtcl.cfg as follows:
If the driver file name in libtcl.cfg has path components (contains a slash), that path is used. Otherwise, the search continues to step 2.
Depending on your platform, the directories specified by these environment variables are searched, for example:
Sun Solaris and Linux platforms – LD_LIBRARY_PATH
HP/UX and HP Itanium 32-bit – SHLIB_PATH
HP/UX and HP Itanium 64-bit – LD_LIBRARY_PATH
IBM RS6000 – LIBPATH
If the driver is not located, the search continues to step 3.
The library locations and environment variables are listed in Table 5-5.
The path $SYBASE/$SYBASE_OCS/lib is used (or $SYBASE/$SYBASE_OCS/devlib for applications built with debug-mode libraries).
