Microsoft KB Archive/66028

INF: DBSETBUSY, DBSETIDLE, DBSETINTERRUPT Not Included

PSS ID Number: Q66028 Article last modified on 02-03-1994

1.10 1.11 4.20 OS/2

Support for the DB-LIBRARY (db-lib) functions DBSETBUSY, DBSETIDLE, and DBSETINTERRUPT is not included with the versions of DB-LIBRARY included with SQL Server versions 1.1 and later. These DB-LIBRARY functions originally were provided with the SQL Server NDK and were also included with SQL Server version 1.0. They were dropped from SQL Server versions 1.1 and later for the following reasons: 1. These functions were ports of function calls from the Sybase libraries and were intended for use in a UNIX multitasking environment. Multitasking of this sort is impossible under MS-DOS, and is implemented differently under OS/2. Thus, these three DB-LIBRARY functions did not work well. 2. Also, very similar functionality can be achieved by using the DBDATAREADY call. The DBDATAREADY function is ordinarily used after a call to DBSQLSEND and before a call to DBSQLOK. After DBSQLSEND is executed, SQL Server begins executing the commands in the command buffer. When DBSQLOK is called, DB-LIBRARY waits for SQL Server processing to be completed before returning control to the application program. The DBDATAREADY function provides a way to determine when the command processing has been completed. DBDATAREADY should be called repeatedly in a loop (after DBSQLSEND and before DBSQLOK) until it returns a nonzero value. At this point, the application can call DBSQLOK. During this DBDATAREADY loop, the program still has control and can do other things while waiting for the data to be ready. With the program able to do other things during this waiting period, the DB-LIBRARY DBSETBUSY, DBSETIDLE, and DBSETINTERRUPT calls are no longer needed.

= Additional reference words: 1.10 1.11 4.20 dblib =

Copyright Microsoft Corporation 1994.