Getting Started : Product and installation package information : solidDB® server package : Library file names
  
Library file names
The solidDB® server provides many files as linkable libraries.
Most of the library files fall into one of the following categories:
▪ODBC drivers
▪Shared memory access and linked library access files
▪Communication library files
▪SA (Server API) library file
All platforms do not have every file. For example, some communication library files are available on Windows environments only.
Some library files are static, that is, they are linked to the client application executable program when you do a compile-and-link operation. Other library files are dynamic: these files are stored separately from your executable program and are loaded into memory when your program runs. For many libraries, the solidDB® server provides both a static and a dynamic version on some or all platforms.
Library files are found in the following two directories:
▪bin
▪lib
As a rule, the bin directory contains dynamic libraries (in addition to executable files), while the lib directory contains static libraries. On Windows environments, the lib directory also contains the import libraries.
Additionally, on Windows environments, the ODBC and communication .dll libraries are copied to the C:\Windows\system32 directory.
If you use the 32-bit installation program to install the solidDB® server on a 64-bit environment, the .dll library files are copied to the C:\Windows\SysWOW64 directory.
The exact library file names depend on the platform. See the following tables for examples on Windows and Linux environments:
Example: solidDB® library files in Windows 32-bit package
File name
Description
bin\
 
  sacw3270.dll
ODBC library - ASCII
  snpw3270.dll
NamedPipes communication protocol link library
  socw3270.dll
ODBC library - Unicode
  sosw3270.dll
ODBC Driver Manager setup library
  ssaw3270.dll
solidDB® SA API library
  ssolidac70.dll
Linked library access (LLA) dynamic library
  stcw3270.dll
TCP/IP communication protocol link library
lib\
 
  solidctrlstub.lib
solidDB® Control API (SSC) stub library. This static library is used if you want to write code that can be run either locally with the linked library access library, or remotely without the linked library access.
  solidimpac.lib
Linked library access (LLA) import library
  solidimpodbca.lib
ODBC import library - ASCII
  solidimpodbcu.lib
ODBC import library - Unicode
  solidimpsa.lib
solidDB® SA API import library
Example: solidDB® library files in Linux 32-bit package
File name
Description
bin\
 
  sacl2x70.so
ODBC shared library - ASCII
  socl2x70.so
ODBC shared library - Unicode
  ssal2x70.so
solidDB® SA API library
  ssolidac70.so
Linked library access (LLA) shared library
  ssolidsma70.so
Shared memory access (SMA) shared library
lib\
 
  solidctrlstub.a
 
solidDB® Control API (SSC) stub library. This static library is used if you want to write code that can be run either locally with the linked library access library, or remotely without the linked library access.
  solidac.a
Linked library access (LLA) static library
  solidodbca.a
ODBC static library - ASCII
  solidodbcu.a
ODBC static library - Unicode
  solidsa.a
solidDB® SA API static library
  libssolidac70.so
Symbolic link for shared LLA library
  libssolidsma70.so
Symbolic link for shared SMA library
  libsacl2x70.so
Symbolic link for shared ODBC library - ASCII
  libsocl2x70.so
Symbolic link for shared ODBC library - Unicode
  libssal2x70.so
Symbolic link for shared solidDB® SA API library
  libsolidodbca.a
Symbolic link for static ODBC library - ASCII
  libsolidodbcu.a
Symbolic link for static ODBC library - Unicode
  libsolidsa.a
Symbolic link for static solidDB® SA API library
  libsolidac.a
Symbolic link for static LLA library
For a list of the library file names on your installation of solidDB® server, see the SDK Notes in the solidDB® package, accessible through the Welcome page in your solidDB® installation directory.
Dynamic library file naming conventions
Dynamic library files use the following naming convention:
sLLpppVV.eee
where
▪LL = purpose of the library
ac: ODBC library - ASCII
np: NamedPipes communication protocol link library
oc: ODBC library - Unicode
os: ODBC Driver Manager setup (for Windows only)
sa: solidDB® SA API library
solidac: Linked library access (LLA) dynamic library
solidsma: Shared memory access (SMA) dynamic library
tc: TCP/IP communication protocol link library
▪ppp = platform
a5x64: AIX, 64-bit
l2x: Linux for x86
l2x64: Linux for x86, 64-bit
lzx64: Linux for System z, 64-bit
s0x64: Solaris 10 (SPARC, 64-bit)
s0xi64: Solaris 10 (ix86, 64-bit)
w32: Windows 32-bit (x86)
w64: Windows 64-bit (x86)
▪VV = first two digits of the solidDB® version, for example 70 for version 7.0, 63 for version 6.3
▪eee = platform-specific file name extension:
*.dll Dynamic Link Library for Windows
*.so (Shared Object) for AIX, HP-UX, Linux, and Solaris
See also
solidDB® server package