The Open Client features that are available depend on which versions of the software you are running. These combinations are described below.
Adaptive Server 15.0 and Open Client 15.0 are completely compatible. However, before you use Open Client 15.0 with Adaptive Server 15.0:
Relink your Open Client application with the 15.0 libraries.
Use CS_VERSION to establish the new version number.
If you are using jConnect, reconnect the drivers.
If you are running an Open Client application earlier than 15.0 with Adaptive Server and have not relinked your application with 15.0 Open Client, the Open Client pre-release 15.0 functionality is fine, but the release 15.0 limits are not enabled. Adaptive Server sends the data according to the pre-release 15.0 limits, and truncates any data beyond these limits.
If an Open Client 15.0 connects to an Adaptive Server, which then queries a remote Adaptive Server that is earlier than release 12.5, the remote server truncates any wide data before returning any results.
All servers and clients in a transaction must at a minimum be at release 12.5 to use the new wide limits.
Starting with Adaptive Server release 15.0, you must use the Sybase ODBC and OLEDB release 15.0 drivers that come with the Adaptive Server 15 SDK (instead of DataDirect).
If your application depends on jConnect 5.5, Sybase recommends you migrate the application to jConnect 6.05 or use an existing jConnect 5.5 release area.
The library-naming convention has changed in Open Client 15.0. The letters “syb” are now embedded in Open Client libraries, for example, libsybct.a, replaces libct.a.
Open Client connections in versions earlier than 15.0, were established when a client requested a packet size (for example, using isql -A or CS_PACKETSIZE).
With Adaptive Server 15.0, client connections can still use this method of connection, but the packet size is considered a suggestion to Adaptive Server, and Adaptive Server negotiates a packet size based on the server-configured packet size.
No code changes or recompilation is needed, however if you need your client application to use a particular packet size, you can restrict this feature using these methods:
Open client – use ct_capability( CS_N)_SRVPKTSIZE).
jConnect – specify Packetsize | Restricted maximum.
ADO.NET/ODBC/OLEDB – specify the Connection normalized computed columns property RestrictedMaximumPacketSize.
