Understanding command codes

When using the OpenDB with the debug or verbose flag, the debug information displays.

The information is displayed in the following format:

Host = ODBC, Command = 4, Srvr Fd = 2, Dll Fd = 2

For example, Command = 4 means that a file is being selected as shown in the table below:

Command Code Command Supported by OpenDB server? Description
1 RP_RETIX Yes Reads an item.
2 RP_UPDITM Yes Writes an item.
3 RP_RELEASE Yes Releases an item lock.
4 RP_SEQIDS Yes Selects a file for sequential access.
5 RP_GETGRP Yes Reads a file group.
6 RP_OPEN Yes Opens a file.
7 RP_CLOSE Yes Closes a file.
8 RP_CLEARFILE Yes Clears a file.
9 RP_KEY No Index operation.
10 RP_GETSEC No Gets a data section of a file.
11 RP_GETFCB No Gets a file's FCB information.
12 RP_UPDID No Gets a new Item-Id for the update processor.
13 RP_ILIST No Gets item location information.
14 RP_FILE No File lock/unlock operation.
15 RP_CAPABILITIES Yes Get s the driver supported features.
16 RP_LOGON No Logs on the remote database.
17 RP_CRINDX No Creates an index.
18 RP_DELINDX No Deletes an index.
19 RP_DELFILE No Deletes a file.
Note: OpenDB supports only a subset of OSFI commands. When running OpenDB in debug mode, the command is displayed on the screen. However only the supported commands actually perform any operation. If an operation is not supported, OpenDB returns a command not supported error (error # 3).

This information can be useful during development to determine what operations are successful. For instance, when developing a callx on a D3 file to trigger a write to a non-D3 table, the debug output indicates whether the non-D3 file was opened and whether an attempt to write the item to the non-D3 table was made. If the operation is not successful, a remote file system error displays. See TroubleShooting.