+<sect1>dbcreate <name> (9)
+
+<P>
+<tt>
+<bf>dbcreate <name></bf> Create a database entry
+</tt>
+
+<P>
+<sect1>dbcreate <name> chain <name> [<name>..] (9)
+
+<P>
+<tt>
+<bf>dbcreate <name> chain <name> [<name>..]</bf> Create a chained database entry
+</tt>
+
+<P>
+<sect1>dbcreate <name> cmd <dxspider command> (9)
+
+<P>
+<tt>
+<bf>dbcreate <name> cmd <dxspider command></bf> make a local command available as a DB
+</tt>
+
+<P>
+DBCREATE allows you to define a database in the system. It doesn't actually
+create anything, just defines it.
+
+The databases that are created are simple DB_File hash databases, they are
+therefore already 'indexed'.
+
+You can define a local database with the first form of the command eg:
+
+<tscreen><verb>
+ DBCREATE oblast
+</verb></tscreen>
+
+You can also chain databases with the addition of the 'chain' keyword.
+This will search each database one after the other. A typical example
+is:
+
+<tscreen><verb>
+ DBCREATE sdx_qsl chain sql_ad
+</verb></tscreen>
+
+No checking is done to see if the any of the chained databases exist, in
+fact it is usually better to do the above staement first then do each of
+the chained databases.
+
+Databases can exist offsite. To define a database that lives on another
+node do:
+
+<tscreen><verb>
+ DBCREATE buckmaster remote gb7dxc
+</verb></tscreen>
+
+Remote databases cannot be chained; however, the last database in a
+a chain can be a remote database eg:
+
+<tscreen><verb>
+ DBCREATE qsl chain gb7dxc
+</verb></tscreen>
+
+To see what databases have been defined do:
+
+<tscreen><verb>
+ DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+</verb></tscreen>
+
+It would be normal for you to add an entry into your local Aliases file
+to allow people to use the 'SHOW/<dbname>' style syntax. So you would
+need to add a line like:-
+
+<tscreen><verb>
+ 's' => [
+ ..
+ ..
+ '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+ ..
+ ..
+ ],
+</verb></tscreen>
+
+to allow
+
+<tscreen><verb>
+ SH/BUCK g1tlh
+</verb></tscreen>
+
+to work as they may be used to.
+
+You can also make local commands available as 'pseudo' databases. You
+can therefore make spider special commands available as a database. I
+imagine that this will be primarily useful for remote access from
+legacy nodes. For example:-
+
+<tscreen><verb>
+ DBCREATE dxqsl cmd show/dxqsl
+</verb></tscreen>
+
+You also use one of these databases in a chain. This may be useful
+locally.
+
+See DBIMPORT for the importing of existing AK1A format data to databases.
+See DBSHOW for generic database enquiry
+
+<sect1>dbcreate <name> remote <node> (9)
+
+<P>
+<tt>
+<bf>dbcreate <name> remote <node></bf> Create a remote database entry
+</tt>
+
+<P>
+<sect1>dbimport <dbname> <filename> (9)
+
+<P>
+<tt>
+<bf>dbimport <dbname> <filename></bf> Import AK1A data into a database
+</tt>
+
+<P>
+If you want to import or update data in bulk to a database you can use
+this command. It will either create or update entries into an existing
+database. For example:-
+
+<tscreen><verb>
+ DBIMPORT oblast /tmp/OBLAST.FUL
+</verb></tscreen>
+
+will import the standard OBLAST database that comes with AK1A into the
+oblast database held locally.
+<sect1>dbremove <dbname> (9)
+
+<P>
+<tt>
+<bf>dbremove <dbname></bf> Delete a database
+</tt>
+
+<P>
+DBREMOVE will completely remove a database entry and also delete any data
+file that is associated with it.
+
+There is no warning, no comeback, no safety net.
+
+For example:
+
+<tscreen><verb>
+ DBREMOVE oblast
+</verb></tscreen>
+
+will remove the oblast database from the system and it will also remove
+the associated datafile.
+
+I repeat:
+
+There is no warning, no comeback, no safety net.
+
+You have been warned.