--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider Administration Manual v1.47: Databases</TITLE>
+ <LINK HREF="adminmanual-7.html" REL=next>
+ <LINK HREF="adminmanual-5.html" REL=previous>
+ <LINK HREF="adminmanual.html#toc6" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="adminmanual-7.html">Next</A>
+<A HREF="adminmanual-5.html">Previous</A>
+<A HREF="adminmanual.html#toc6">Contents</A>
+<HR>
+<H2><A NAME="s6">6. Databases</A></H2>
+
+<P>Spider allows the creation of local or remote databases. It supports
+chained databases, allowing several different databases to be scanned
+with one simple command. Importing of databases is limited at present
+to the standard AK1A databases such as OBLAST and the DB0SDX QSL
+database but will expand with time.
+<P>
+<H2><A NAME="ss6.1">6.1 Creating databases</A>
+</H2>
+
+<P>Creating a database could not be more simple. All the commands are
+sent from the cluster prompt as the <EM>sysop</EM> user.
+<P>To create a database you use the command <EM>dbcreate</EM>. It can
+be used in 3 different ways like so ..
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate <name>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To simply create a database locally, you just tell the command the
+name of the database. This does not create the actual database, it
+simply defines it to say that it exists.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate <name> chain <name> [<name>...]
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This creates a chained database entry. The first database will be
+scanned, then the second, the third etc...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate <name> remote <name>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This creates a remote entry. the first name field is the database
+name at the remote node, then the remote switch, then the actual
+node_call of the remote node, for example...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbcreate buckmaster remote gb7dxc
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Remote databases cannot be chained, however, the last database in a
+chain can be a remote database.
+<P>
+<H2><A NAME="ss6.2">6.2 Importing databases</A>
+</H2>
+
+<P>The only databases that Spider can currently import are the standard
+AK1A databases such as OBLAST or the DB0SDX qsl and address database.
+This will be added to with time.
+<P>To import such a database, first put the file somewhere useful like /tmp
+and then issue the following command ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbimport oblast /tmp/OBLAST.FUL
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This will update the existing local oblast database or create it if
+it does not exist.
+<P>
+<H2><A NAME="ss6.3">6.3 Checking available databases</A>
+</H2>
+
+<P>Once a database is created, you will want to check that it has been
+added. To do this use the <EM>dbavail</EM> command. This will
+output the available databases. For example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbavail
+DB Name Location Chain
+qsl Local
+buck GB7ADX
+hftest GB7DXM
+G0VGS de GB7MBC 3-Feb-2001 1925Z >
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss6.4">6.4 Looking up databases</A>
+</H2>
+
+<P>To look for information in a defined database, simply use the <EM>dbshow</EM>
+command, for example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbshow buckmaster G0YLM
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will show the information for the callsign G0YLM from the buckmaster
+database if it exists. To make things more standard for the users
+you can add an entry in the Aliases file so that it looks like a standard
+<EM>show</EM> command like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Now you can simply use show/buckmaster or an abreviation.
+<P>
+<H2><A NAME="ss6.5">6.5 Removing databases</A>
+</H2>
+
+<P>To delete an existing database you use the <EM>dbremove</EM> command.
+For example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dbremove oblast
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would remove the oblast database and its associated datafile from the
+system. There are no warnings or recovery possible from this command.
+If you remove a database it ceases to exist and would have to be created
+from scratch if you still required it.
+<P>
+<HR>
+<A HREF="adminmanual-7.html">Next</A>
+<A HREF="adminmanual-5.html">Previous</A>
+<A HREF="adminmanual.html#toc6">Contents</A>
+</BODY>
+</HTML>
projects / spider.git / blobdiff