Programming Issues

Known programming issues and workarounds, if any, relevant to SAP Open Server.

Programming Issues
CR#	Description
	Upgrading to a new version Workaround: SAP recommends the following: Rebuild all statically linked applications (srvlib), using the new version of the software. Recompile and relink the applications using the new header files and libraries. For dynamically linked applications, recompile and relink using the SDK libraries that now include “syb” in the library names. Note: If you have made any changes to the application files, you must recompile. Ensure that the runtime libraries are for the same major release as the version used to build the application.
682932	Generic 64-bit x86 Workaround: On Solaris x86-64 (64-bit), the libraries are built using generic 64-bit x86 instructions.
575063	Linking static libraries Workaround:When statically linking the SAP Open Client and SAP Open Server libraries, you must link your application to librt, the Realtime Extensions library. Static linking requires that you add `-lrt` to your makefile.
	Programming with thread-safe libraries Workaround: To use the Sybase thread-safe libraries, you must compile and link your code with thread safety options. You must use the `-mt -D_REENTRANT` option on the cc command.
	Timeslice Property and Multithreaded Library Versions Workaround: The SRV_S_TIMESLICE SAP Open Server property is not supported if you use the multithreaded versions of the Sybase libraries. Applications can set this property, but it has no effect; therefore, you must change existing application code that depends on timeslice events before relinking with the multithreaded libraries. Applications can call srv_capability to determine if the timeslice feature is supported.