CT-Library client API processing

Figure 6-3 shows the interaction between a Sybase Open Client CT-Library API and the DirectConnect server.

Figure 6-3: CT-Library client API example

A Sybase Open Client CT-Library API interacts with DirectConnect to create a process flow.

The CT-Library client API processing flow includes these steps:

  1. When a CT-Library application issues a request, it uses the ct_connect call to initiate a connect event to a specific access service.

  2. The CT-Library API executes the request using the ct_command and ct_send calls. This initiates a language event in the DirectConnect server.

  3. The CT-Library API uses ct_fetch to return the requested results to the client application.

  4. The CT-Library API terminates the request with ct_close. This call initiates a disconnect event in the DirectConnect server.

NoteCT-Library is used by both Replication Server and ASE/CIS to connect to the DirectConnect server.

Procedure calls for the CT-Library API are described in the Sybase Open Client Client-Library/C Reference Manual.

NoteSybase no longer provides a back-end, server-side ODBC driver to access Microsoft SQL Server, DB2 UDB, or ODBC-accessible data sources. Instead, obtain an ODBC driver from the vendor of your database, and follow vendor instructions to configure it to be compatible with the Sybase ODBC driver manager. For more information, see the Enterprise Connect Data Access installation guide for your platform.