|
For client applications, the Version operation (B_VERSION) returns the local MicroKernel version and the Requester version, if applicable. If a client application opens a file on a server or specifies a server file path name in the Key Buffer, the Version operation also returns the MicroKernel version on that server. For server-based applications, the Version operation returns the server-based MicroKernel version and revision numbers.
Either the MicroKernel or the Requester must be loaded before you can issue a Version operation.
If you have both a workstation MicroKernel and client Requester configured for access and the Version operation is successful, the operation returns the version information for the workstation MicroKernel, the client Requester, and the server-based MicroKernel.
Specify a 15-byte Data Buffer and Data Buffer Length.
If both the client Requester and the workstation MicroKernel are loaded and you specify only a 5-byte Data Buffer and Data Buffer Length, the operation returns only the client Requester's version information.
If you specify only a 10-byte Data Buffer and Data Buffer Length, the operation returns the client Requester and the local workstation engine.
If you specify a 15-byte Data Buffer and Data Buffer Length, the operation returns the client Requester, the local workstation engine, and the server engine (if applicable).
In the Data Buffer, the Version operation returns a 5-byte Version Block for each MicroKernel or Requester, according to the format shown in Table 2-40. The fifth byte of each block identifies each MicroKernel or Requester.
For example, if you are running Pervasive.SQL for Windows NT/2000 v8.10, the Version operation returns the following hexadecimal values in the Data Buffer:
After converting these values to decimal, the version number is 8 and the revision number is 10. If the Version operation is unsuccessful, the MicroKernel returns a nonzero status code.
The Version operation has no effect on positioning.
|
Chapter contents
Prev topic: Update Chunk (53)
|