Configuring your environment for LLA use

Platform	Static LLA library	Dynamic/shared LLA library
Windows	bin\ssolidacxx.dll	lib\solidimpac.lib This is an import library file that gives you access to the actual library file bin\ssolidacxx.dll.
AIX	bin/solidac.a	lib/libssolidacxx.so This is a symbolic link that gives you access to the actual library file bin/ssolidacxx.so.
HP-UX	bin/solidac.a	lib/libssolidacxx.so This is a symbolic link that gives you access to the actual library file bin/ssolidacxx.so.
Linux	bin/solidac.a	lib/libssolidacxx.so This is a symbolic link that gives you access to the actual library file bin/ssolidacxx.so
Solaris	bin/solidac.a	lib/libssolidacxx.so This is a symbolic link that gives you access to the actual library file bin/ssolidacxx.so

Note In Linux and UNIX environments, you need to link to the symbolic link library libssolidacxx that is available in the <solidDB^®_installation_directory/lib> directory. Alternatively, rename the ssolidacxx library in the <solidDB^®_installation_directory/bin> directory as libssolidacxx.

# compiler
CC =cl
compiler flags CFLAGS = -I. -DSS_WINDOWS -DSS_WINNT
linker flags and directives
SYSLIBS = libcmt.lib kernel32.lib advapi32.lib netapi32.lib user32.lib oldnames.lib gdi32.lib
LFLAGS = ..\solidimpac.lib
OUTFILE = -Fe

# MyApp building
all: myapp

myapp: myapp.c
$(CC) $(CFLAGS) $(OUTFILE)myapp myapp.c /link$(LFLAGS)
/NODEFAULTLIB:libc.lib

In the [Accelerator] section of the solid.ini configuration file, the parameter ImplicitStart, by default, is set to Yes. This default setting starts the server automatically when you use the function SQLConnect which is required for any ODBC connection. The function SaConnect behaves in the same way. When the SQLConnect or SaConnect function is called for the first time, the server is implicitly started.

Signal handlers are used to report the occurrence of an exceptional event to the application, for example division by zero. You must not set signal handlers in user applications because they would override the signal handlers that are set by the linked library access. For example, if the user application sets a signal handler for floating point exceptions, that setting overrides the handler set by the linked library access. Thus the server is unable to catch, for example, division by zero.