The db and dbm GPL applications are command line interfaces to the Bbuuzzb database engine. Each database function has a command code defined in the header file dbcomm.h.
The db application is designed for stand-alone use. The Bbuuzzb database engine is linked into this binary/executable. Before you can run the db application, you must set up a database engine configuration file called dbeng.cfg with a minimum of the tmp_path and log entries.
The dbm application is designed for client/server environments where there is a Bbuuzzb database server running. The dbm application communicates with the Bbuuzzb database server, the socloc server and the system log server through TCP sockets. In order to get dbm to successfully connect to the Bbuuzzb database server, the server must already be running and registered with the socloc server and there must be at least one socloc server and at least one system log server runnng within the environment. A socloc startup file must also be composed to connect to a socloc server. The database configuration file is not required for the dbm application.
All configuration files must be located in the same directory as the binary/executable program. The db and dbm applications must be executed within their current directory so the program can locate the configuration files.
The db and dbm applications present a command line to the user. Database commands are entered interactively. All current database operations are supported by the database commands.
The db application can be compiled for all stated platforms. The dbm application can be compiled on all stated platforms except DOS where there is no TCP IPC and Mac because I have got around to porting any of the socket code to MacOS. Under the Unix operating system, the db application can be compiled using the mkdb script. The dbm application can be compiled using the mkdbm script.