--- /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.50: The DXSpider command set</TITLE>
+ <LINK HREF="adminmanual-9.html" REL=previous>
+ <LINK HREF="adminmanual.html#toc10" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+Next
+<A HREF="adminmanual-9.html">Previous</A>
+<A HREF="adminmanual.html#toc10">Contents</A>
+<HR>
+<H2><A NAME="s10">10. The DXSpider command set</A></H2>
+
+<P>Below is a complete list of commands available from the cluster prompt.
+Most maintenance tasks are automatic but there are some commands that are useful
+for a sysop. These are listed below in alphabetical order. The number in
+brackets following the command name is the permissions level needed to use
+the command.
+<P>
+<H2><A NAME="ss10.1">10.1 accept/announce (0)</A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
+line for announce</CODE>
+<P>
+<P>Create an 'accept this announce' line for a filter.
+<P>An accept filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>or
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This filter would only allow announces that were posted buy UK stations.
+You can use the tag 'all' to accept everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss10.2">10.2 accept/announce (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/ann by G,M,2
+ accept/ann input node_default by G,M,2
+ accept/ann user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.3">10.3 accept/route (8)</A>
+</H2>
+
+<P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE>
+<P>
+<P>Create an 'accept this routing PC Protocol' line for a filter.
+<P>
+<P>An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is passed thru that interface. See HELP FILTERING for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>You can use the tag 'all' to accept everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/route all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.4">10.4 accept/spots (0)</A>
+</H2>
+
+<P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE>
+<P>
+<P>Create an 'accept this spot' line for a filter.
+<P>
+<P>An accept filter line means that if the spot matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: freq HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to accept everything, eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss10.5">10.5 accept/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/spot db0sue-7 1 by_zone 14,15,16
+ accept/spot node_default all
+ set/hops node_default 10
+
+ accept/spot user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.6">10.6 accept/wcy (0)</A>
+</H2>
+
+<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss10.7">10.7 accept/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
+WCY filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wcy node_default all
+ set/hops node_default 10
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.8">10.8 accept/wwv (0)</A>
+</H2>
+
+<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv by_zone 4
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss10.9">10.9 accept/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
+WWV filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv db0sue-7 1 by_zone 4
+ accept/wwv node_default all
+ set/hops node_default 10
+
+ accept/wwv user_default by W,K
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.10">10.10 announce (0)</A>
+</H2>
+
+<P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
+<P>
+<P>Send an announcement to LOCAL users only, where <text> is the text
+of the announcement you wish to broadcast. If you do not wish to receive
+announces, use the <EM>set/noannounce</EM> command. Any announces made by
+a sysop will override set/noannounce.
+<P>
+<H2><A NAME="ss10.11">10.11 announce full (0)</A>
+</H2>
+
+<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
+<P>
+<P>This command will send your announcement across the whole cluster
+network.
+<P>
+<P>
+<H2><A NAME="ss10.12">10.12 announce sysop (5)</A>
+</H2>
+
+<P><CODE><B>announce sysop <text></B></CODE>
+<P>
+<P>Send an announcement to Sysops only
+<P>
+<H2><A NAME="ss10.13">10.13 apropos (0)</A>
+</H2>
+
+<P><CODE><B>apropos <string></B> Search the help database</CODE>
+<P>
+<P>Search the help database for <string> (it isn't case sensitive),
+and print the names of all the commands that may be relevant.
+<P>
+<H2><A NAME="ss10.14">10.14 bye (0)</A>
+</H2>
+
+<P><CODE><B>bye</B> Exit from the cluster</CODE>
+<P>
+<P>This will disconnect you from the cluster
+<P>
+<H2><A NAME="ss10.15">10.15 catchup (5)</A>
+</H2>
+
+<P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
+<P>
+<P>When you send messages the fact that you have forwarded it to another node
+is remembered so that it isn't sent again. When you have a new partner
+node and you add their callsign to your /spider/msg/forward.pl file, all
+outstanding non-private messages will be forwarded to them. This may well
+be ALL the non-private messages. You can prevent this by using these
+commmands:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ catchup GB7DJK all
+ catchup GB7DJK 300 301 302 303 500-510
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and to undo what you have just done:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ uncatchup GB7DJK all
+ uncatchup GB7DJK 300 301 302 303 500-510
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which will arrange for them to be forward candidates again.
+<P>Order is not important.
+<P>
+<H2><A NAME="ss10.16">10.16 clear/announce (8)</A>
+</H2>
+
+<P><CODE><B>clear/announce [input] <callsign> [0-9|all]</B> Clear an announce filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss10.17">10.17 clear/route (8)</A>
+</H2>
+
+<P><CODE><B>clear/route [input] ^lt;callsign> [0-9|all]</B> Clear a route filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a route filter or to
+remove the whole filter.
+<P>see CLEAR/SPOTS for a more detailed explanation.
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss10.18">10.18 clear/spots (0)</A>
+</H2>
+
+<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a spot filter or to
+remove the whole filter.
+<P>If you have a filter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and you say:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot 1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you will be left with:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you do:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>the filter will be completely removed.
+<P>
+<H2><A NAME="ss10.19">10.19 clear/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>clear/spots [input] <callsign> [0-9|all]</B> Clear a spot filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss10.20">10.20 clear/wcy (0)</A>
+</H2>
+
+<P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a WCY filter or to
+remove the whole filter.
+<P>see CLEAR/SPOTS for a more detailed explanation.
+<P>
+<H2><A NAME="ss10.21">10.21 clear/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>clear/wcy [input] <callsign> [0-9|all]</B> Clear a WCY filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss10.22">10.22 clear/wwv (0)</A>
+</H2>
+
+<P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a WWV filter or to
+remove the whole filter.
+<P>see CLEAR/SPOTS for a more detailed explanation.
+<P>
+<H2><A NAME="ss10.23">10.23 clear/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>clear/wwv [input] <callsign> [0-9|all]</B> Clear a WWV filter line</CODE>
+<P>
+<P>A sysop can clear an input or normal output filter for a user or the
+node_default or user_default.
+<P>
+<H2><A NAME="ss10.24">10.24 connect (5) </A>
+</H2>
+
+<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
+<P>
+<P>Start a connection process that will culminate in a new connection to the
+DX cluster <callsign>. This process creates a new 'client' process which will
+use the script in /spider/connect/<callsign> to effect the 'chat' exchange
+necessary to traverse the network(s) to logon to the cluster <callsign>.
+<P>
+<H2><A NAME="ss10.25">10.25 dbavail (0)</A>
+</H2>
+
+<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
+<P>
+<P>The title says it all really, this command lists all the databases defined
+in the system. It is also aliased to SHOW/COMMAND.
+<P>
+<H2><A NAME="ss10.26">10.26 dbcreate (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
+<B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
+<B>dbcreate <name> remote <node></B> Create a remote database
+entry<BR></CODE>
+<P>
+<P>DBCREATE allows you to define a database in the system. It doesn't actually
+create anything, just defines it.
+<P>The databases that are created are simple DB_File hash databases, they are
+therefore already 'indexed'.
+<P>You can define a local database with the first form of the command eg:
+<P>DBCREATE oblast
+<P>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:
+<P>DBCREATE sdx_qsl chain sql_ad
+<P>No checking is done to see if the any of the chained databases exist, in
+fact it is usually better to do the above statement first then do each of
+the chained databases.
+<P>Databases can exist offsite. To define a database that lives on another
+node do:
+<P>DBCREATE buckmaster remote gb7dxc
+<P>Remote databases cannot be chained; however, the last database in a
+a chain can be a remote database eg:
+<P>DBCREATE qsl chain gb7dxc
+<P>To see what databases have been defined do:
+<P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+<P>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:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ 's' => [
+ ..
+ ..
+ '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+ ..
+ ..
+ ],
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>to allow
+<P>SH/BUCK g1tlh
+<P>to work as they may be used to.
+<P>See DBIMPORT for the importing of existing AK1A format data to databases.
+See DBSHOW for generic database enquiry
+<P>
+<H2><A NAME="ss10.27">10.27 dbimport (9)</A>
+</H2>
+
+<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
+<P>
+<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:-
+<P>DBIMPORT oblast /tmp/OBLAST.FUL
+<P>will import the standard OBLAST database that comes with AK1A into the
+oblast database held locally.
+<P>
+<H2><A NAME="ss10.28">10.28 dbremove (9)</A>
+</H2>
+
+<P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
+<P>
+<P>DBREMOVE will completely remove a database entry and also delete any data
+file that is associated with it.
+<P>There is no warning, no comeback, no safety net.
+<P>For example:
+<P>DBREMOVE oblast
+<P>will remove the oblast database from the system and it will also remove
+the associated datafile.
+<P>I repeat:
+<P>There is no warning, no comeback, no safety net.
+<P>You have been warned.
+<P>
+<H2><A NAME="ss10.29">10.29 dbshow (0)</A>
+</H2>
+
+<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
+<P>
+<P>This is the generic user interface to the database to the database system.
+It is expected that the sysop will add an entry to the local Aliases file
+so that users can use the more familiar AK1A style of enquiry such as:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/BUCK G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but if he hasn't and the database really does exist (use DBAVAIL or
+SHOW/COMMAND to find out) you can do the same thing with:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBSHOW buck G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss10.30">10.30 debug (9)</A>
+</H2>
+
+<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
+<P>
+<P>Executing this command will only have an effect if you are running the cluster
+in debug mode i.e.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ perl -d cluster.pl
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>It will interrupt the cluster just after the debug command has finished.
+<P>
+<H2><A NAME="ss10.31">10.31 delete/user (9)</A>
+</H2>
+
+<P><CODE><B>delete/user <callsign></B> Delete a user from the User Database</CODE>
+<P>
+<P>This command will completely remove a one or more users from the database.
+<P>There is NO SECOND CHANCE.
+<P>It goes without saying that you should use this command CAREFULLY!
+<P>
+<H2><A NAME="ss10.32">10.32 demonstrate (9)</A>
+</H2>
+
+<P><CODE><B>demonstrate <call> <command></B> Demonstrate a command to another user</CODE>
+<P>
+<P>This command is provided so that sysops can demonstrate commands to
+other users. It runs a command as though that user had typed it in and
+then sends the output to that user, together with the command that
+caused it.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DEMO g7brn sh/dx iota oc209
+ DEMO g1tlh set/here
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Note that this command is similar to SPOOF and will have the same side
+effects. Commands are run at the privilege of the user which is being
+demonstrated to.
+<P>
+<H2><A NAME="ss10.33">10.33 directory (0)</A>
+</H2>
+
+<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
+<B>directory own</B> List your own messages<BR>
+<B>directory new</B> List all new messages<BR>
+<B>directory to <call></B> List all messages to <call><BR>
+<B>directory from <call></B> List all messages from <call><BR>
+<B>directory subject <string></B> List all messages with <string> in subject<BR>
+<B>directory <nn></B> List last <nn> messages<BR>
+<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
+<P>
+<P>List the messages in the messages directory.
+<P>If there is a 'p' one space after the message number then it is a
+personal message. If there is a '-' between the message number and the
+'p' then this indicates that the message has been read.
+<P>You can use shell escape characters such as '*' and '?' in the <call>
+fields.
+<P>You can combine some of the various directory commands together eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR TO G1TLH 5
+or
+ DIR SUBJECT IOTA 200-250
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can abbreviate all the commands to one letter and use ak1a syntax:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss10.34">10.34 directory (extended for sysops) (5)</A>
+</H2>
+
+<P>Works just like the user command except that sysops can see ALL messages.
+<P>
+<H2><A NAME="ss10.35">10.35 disconnect (8)</A>
+</H2>
+
+<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
+<P>
+<P>Disconnect any <call> connected locally
+<P>
+<H2><A NAME="ss10.36">10.36 dx (0)</A>
+</H2>
+
+<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
+<P>
+<P>This is how you send a DX Spot to other users. You can, in fact, now
+enter the <freq> and the <call> either way round.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will all give the same result. You can add some remarks to the end
+of the command and they will be added to the spot.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144600 this is a test
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can credit someone else by saying:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The <freq> is compared against the available bands set up in the
+cluster. See SHOW/BANDS for more information.
+<P>
+<H2><A NAME="ss10.37">10.37 export (9)</A>
+</H2>
+
+<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
+<P>
+<P>Export a message to a file. This command can only be executed on a local
+console with a fully privileged user. The file produced will be in a form
+ready to be imported back into the cluster by placing it in the import
+directory (/spider/msg/import).
+<P>This command cannot overwrite an existing file. This is to provide some
+measure of security. Any files written will owned by the same user as the
+main cluster, otherwise you can put the new files anywhere the cluster can
+access. For example:-
+<P>EXPORT 2345 /tmp/a
+<P>
+<H2><A NAME="ss10.38">10.38 export_users (9)</A>
+</H2>
+
+<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
+<P>
+<P>Export the users database to a file in ascii format. If no filename
+is given then it will export the file to /spider/data/user_asc.
+<P>If the file already exists it will be renamed to <filename>.o. In fact
+up to 5 generations of the file can be kept each one with an extra 'o' on the
+suffix.
+<P>BE WARNED: this will write to any file you have write access to. No check is
+made on the filename (if any) that you specify.
+<P>
+<H2><A NAME="ss10.39">10.39 filtering (0)</A>
+</H2>
+
+<P><CODE><B>filtering</B> Filtering things in DXSpider</CODE>
+<P>
+<P>There are a number of things you can filter in the DXSpider system. They
+all use the same general mechanism.
+<P>In general terms you can create a 'reject' or an 'accept' filter which
+can have up to 10 lines in it. You do this using, for example:-
+<P>accept/spots .....
+reject/spots .....
+<P>where ..... are the specific commands for that type of filter. There
+are filters for spots, wwv, announce, wcy and (for sysops)
+connects. See each different accept or reject command reference for
+more details.
+<P>There is also a command to clear out one or more lines in a filter and
+one to show you what you have set. They are:-
+<P>clear/spots 1
+clear/spots all
+<P>and
+<P>show/filter
+<P>There is clear/xxxx command for each type of filter.
+<P>For now we are going to use spots for the examples, but you can apply
+the principles to all types of filter.
+<P>There are two main types of filter 'accept' or 'reject'; which you use
+depends entirely on how you look at the world and what is least
+writing to achieve what you want. Each filter has 10 lines (of any
+length) which are tried in order. If a line matches then the action
+you have specified is taken (ie reject means ignore it and accept
+means gimme it).
+<P>The important thing to remember is that if you specify a 'reject'
+filter (all the lines in it say 'reject/spots' (for instance) then if
+a spot comes in that doesn't match any of the lines then you will get
+it BUT if you specify an 'accept' filter then any spots that don't
+match are dumped. For example if I have a one line accept filter:-
+<P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+<P>then automatically you will ONLY get VHF spots from or to CQ zones 14
+15 and 16. If you set a reject filter like:
+<P>reject/spots on hf/cw
+<P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
+and will work it even on CW then you could say:-
+<P>reject/spots on hf/cw and not info iota
+<P>But in that case you might only be interested in iota and say:-
+<P>accept/spots not on hf/cw or info iota
+<P>which is exactly the same. You should choose one or the other until
+you are confortable with the way it works. Yes, you can mix them
+(actually you can have an accept AND a reject on the same line) but
+don't try this at home until you can analyse the results that you get
+without ringing up the sysop for help.
+<P>You can arrange your filter lines into logical units, either for your
+own understanding or simply convenience. I have one set frequently:-
+<P>reject/spots 1 on hf/cw
+reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+<P>What this does is to ignore all HF CW spots (being a class B I can't
+read any CW and couldn't possibly be interested in HF :-) and also
+rejects any spots on VHF which don't either originate or spot someone
+in Europe.
+<P>This is an exmaple where you would use the line number (1 and 2 in
+this case), if you leave the digit out, the system assumes '1'. Digits
+'0'-'9' are available.
+<P>You can leave the word 'and' out if you want, it is implied. You can
+use any number of brackets to make the 'expression' as you want
+it. There are things called precedence rules working here which mean
+that you will NEED brackets in a situation like line 2 because,
+without it, will assume:-
+<P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+<P>annoying, but that is the way it is. If you use OR - use
+brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
+just 'and by_zone'.
+<P>If you want to alter your filter you can just redefine one or more
+lines of it or clear out one line. For example:-
+<P>reject/spots 1 on hf/ssb
+<P>or
+<P>clear/spots 1
+<P>To remove the filter in its entirty:-
+<P>clear/spots all
+<P>There are similar CLEAR commands for the other filters:-
+<P>clear/announce
+clear/wcy
+clear/wwv
+<P>ADVANCED USERS:-
+<P>Once you are happy with the results you get, you may like to experiment.
+<P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, eg:
+<P>rej/spot on hf/cw
+acc/spot on 0/30000
+acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+<P>each filter slot actually has a 'reject' slot and an 'accept'
+slot. The reject slot is executed BEFORE the accept slot.
+<P>It was mentioned earlier that after a reject test that doesn't match,
+the default for following tests is 'accept', the reverse is true for
+'accept'. In the example what happens is that the reject is executed
+first, any non hf/cw spot is passed to the accept line, which lets
+thru everything else on HF.
+<P>The next filter line lets through just VHF/UHF spots from EU.
+<P>
+<H2><A NAME="ss10.40">10.40 forward/latlong (8)</A>
+</H2>
+
+<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
+<P>
+<P>This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+<EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+<P>
+<H2><A NAME="ss10.41">10.41 forward/opername (1)</A>
+</H2>
+
+<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
+<P>
+<P>This command sends out any information held in the user file which can
+be broadcast in PC41 protocol packets. This information is Name, QTH, Location
+and Homenode. PC41s are only sent for the information that is available.
+<P>
+<H2><A NAME="ss10.42">10.42 help (0)</A>
+</H2>
+
+<P><CODE><B>help <cmd></B> Get help on a command</CODE>
+<P>
+<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
+to SH/DX, ANNOUNCE can be shortened to AN and so on.
+<P>Look at the APROPOS <string> command which will search the help database
+for the <string> you specify and give you a list of likely commands
+to look at with HELP.
+<P>
+<H2><A NAME="ss10.43">10.43 init (5)</A>
+</H2>
+
+<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
+<P>
+<P>This command attempts to re-initialise a link to a (usually) AK1A node
+that has got confused, usually by a protocol loop of some kind. It may
+work - but you usually will be better off simply disconnecting it (or
+better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
+node>).
+<P>Best of luck - you will need it.
+<P>
+<H2><A NAME="ss10.44">10.44 kill (0)</A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
+<P>
+<P>Delete a message from the local system. You will only be able to
+delete messages that you have originated or been sent (unless you are
+the sysop).
+<P>
+<H2><A NAME="ss10.45">10.45 kill (5)</A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
+<B>kill from <call></B> Remove all messages from a callsign<BR>
+<B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
+<P>
+<P>You can get rid of any message to or originating from your callsign using
+this command. You can remove more than one message at a time.
+<P>As a sysop you can kill any message on the system.
+<P>
+<H2><A NAME="ss10.46">10.46 kill full (5)</A>
+</H2>
+
+<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
+<P>
+<P>Delete a message (usually a 'bulletin') from the whole cluster system.
+<P>This uses the subject field, so any messages that have exactly the same subject
+will be deleted. Beware!
+<P>
+<H2><A NAME="ss10.47">10.47 kill/expunge (6)</A>
+</H2>
+
+<P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE>
+<P>
+<P>Deleting a message using the normal KILL commands only marks that message
+for deletion. The actual deletion only happens later (usually two days later).
+<P>The KILL EXPUNGE command causes the message to be truly deleted more or less
+immediately.
+<P>It otherwise is used in the same way as the KILL command.
+<P>
+<P>
+<H2><A NAME="ss10.48">10.48 links (0)</A>
+</H2>
+
+<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
+<P>
+<P>This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+<P>
+<P>
+<H2><A NAME="ss10.49">10.49 load/aliases (9)</A>
+</H2>
+
+<P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
+<P>
+<P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
+do this if you change this file whilst the cluster is running in order for the
+changes to take effect.
+<P>
+<H2><A NAME="ss10.50">10.50 load/badmsg (9)</A>
+</H2>
+
+<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
+<P>
+<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
+the cluster is running. This table contains a number of perl regular
+expressions which are searched for in the fields targetted of each message.
+If any of them match then that message is immediately deleted on receipt.
+<P>
+<H2><A NAME="ss10.51">10.51 load/badwords (9)</A>
+</H2>
+
+<P><CODE><B>load/badwords</B> Reload the bad words table</CODE>
+<P>
+<P>Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+<P>
+<H2><A NAME="ss10.52">10.52 load/bands (9)</A>
+</H2>
+
+<P><CODE><B>load/bands</B> Reload the band limits table</CODE>
+<P>
+<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
+the cluster is running.
+<P>
+<H2><A NAME="ss10.53">10.53 load/cmd_cache (9)</A>
+</H2>
+
+<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
+<P>
+<P>Normally, if you change a command file in the cmd or local_cmd tree it will
+automatially be picked up by the cluster program. Sometimes it can get confused
+if you are doing a lot of moving commands about or delete a command in the
+local_cmd tree and want to use the normal one again. Execute this command to
+reset everything back to the state it was just after a cluster restart.
+<P>
+<H2><A NAME="ss10.54">10.54 load/forward (9)</A>
+</H2>
+
+<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
+<P>Reload the /spider/msg/forward.pl file if you have changed it
+manually whilst the cluster is running.
+<P>
+<H2><A NAME="ss10.55">10.55 load/messages (9)</A>
+</H2>
+
+<P><CODE><B>load/messages</B> Reload the system messages file</CODE>
+<P>
+<P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
+commands) you can have them take effect during a cluster session by executing this
+command. You need to do this if get something like :-
+<P>unknown message 'xxxx' in lang 'en'
+<P>
+<H2><A NAME="ss10.56">10.56 load/prefixes (9)</A>
+</H2>
+
+<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
+<P>
+<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
+whilst the cluster is running.
+<P>
+<H2><A NAME="ss10.57">10.57 merge (5)</A>
+</H2>
+
+<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
+<P>
+<P>MERGE allows you to bring your spot and wwv database up to date. By default
+it will request the last 10 spots and 5 WWVs from the node you select. The
+node must be connected locally.
+<P>You can request any number of spots or wwv and although they will be appended
+to your databases they will not duplicate any that have recently been added
+(the last 2 days for spots and last month for WWV data).
+<P>
+<H2><A NAME="ss10.58">10.58 msg (9)</A>
+</H2>
+
+<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
+<P>
+<P>Alter message parameters like To, From, Subject, whether private or bulletin
+or return receipt (RR) is required or whether to keep this message from timing
+out.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can look at the status of a message by using:-
+<P>STAT/MSG <msgno>
+<P>This will display more information on the message than DIR does.
+<P>
+<H2><A NAME="ss10.59">10.59 pc (8)</A>
+</H2>
+
+<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
+<P>
+<P>Send some arbitrary text to a locally connected callsign. No processing is done on
+the text. This command allows you to send PC Protocol to unstick things if problems
+arise (messages get stuck etc). eg:-
+<P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
+<P>You can also use in the same way as a talk command to a connected user but
+without any processing, added of "from <blah> to <blah>" or whatever.
+<P>pc G1TLH Try doing that properly!!!
+<P>
+<H2><A NAME="ss10.60">10.60 ping (1)</A>
+</H2>
+
+<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
+<P>
+<P>his command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
+Any visible cluster node can be PINGed.
+<P>
+<P>
+<H2><A NAME="ss10.61">10.61 rcmd (1)</A>
+</H2>
+
+<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
+<P>
+<P>This command allows you to send nearly any command to another DX Cluster
+node that is connected to the system.
+<P>Whether you get any output is dependant on a) whether the other system knows
+that the node callsign of this cluster is in fact a node b) whether the
+other system is allowing RCMDs from this node and c) whether you have
+permission to send this command at all.
+<P>
+<H2><A NAME="ss10.62">10.62 read (0)</A>
+</H2>
+
+<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
+<B>read <msgno></B> Read the specified message<BR></CODE>
+<P>
+<P>You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+<P>
+<P>
+<H2><A NAME="ss10.63">10.63 read (extended for sysops) (5) </A>
+</H2>
+
+<P><CODE><B>read <msgno></B> Read a message on the system</CODE>
+<P>
+<P>As a sysop you may read any message on the system
+<P>
+<H2><A NAME="ss10.64">10.64 reject/announce</A>
+</H2>
+
+<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
+for announce</CODE>
+<P>
+<P>Create an 'reject this announce' line for a filter.
+<P>An reject filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann by_zone 14,15,16 and not by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss10.65">10.65 reject/announce (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/ann by G,M,2
+ reject/ann input node_default by G,M,2
+ reject/ann user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.66">10.66 reject/route (8)</A>
+</H2>
+
+<P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE>
+<P>
+<P>Create an 'reject this routing PC Protocol' line for a filter.
+<P>
+<P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is NOT passed thru that interface. See HELP FILTERING for more info. Please
+read this to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/route all (equiv to [very] restricted mode)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.67">10.67 reject/spots (0)</A>
+</H2>
+
+<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
+<P>
+<P>Create a 'reject this spot' line for a filter.
+<P>A reject filter line means that if the spot matches this filter it is
+dumped (not passed on). See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: on HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss10.68">10.68 reject/spots (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
+Reject spot filter sysop version </CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/spot db0sue-7 1 by_zone 14,15,16
+ reject/spot node_default all
+ set/hops node_default 10
+
+ reject/spot user_default by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.69">10.69 reject/wcy (0)</A>
+</H2>
+
+<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss10.70">10.70 reject/wcy (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
+WCY reject filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>reject/wcy gb7djk all
+<P>
+<H2><A NAME="ss10.71">10.71 reject/wwv (0)</A>
+</H2>
+
+<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv by_zone 14,15,16
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss10.72">10.72 reject/wwv (extended for sysops) (8)</A>
+</H2>
+
+<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
+WWV reject filter sysop version</CODE>
+<P>
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv db0sue-7 1 by_zone 4
+ reject/wwv node_default all
+
+ reject/wwv user_default by W
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.73">10.73 reply (0)</A>
+</H2>
+
+<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
+<B>reply <msgno></B> Reply (privately) to the specified message<BR>
+<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
+<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
+message<BR>
+<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
+<P>
+<P>You can reply to a message and the subject will automatically have
+"Re:" inserted in front of it, if it isn't already present.
+<P>You can also use all the extra qualifiers such as RR, PRIVATE,
+NOPRIVATE, B that you can use with the SEND command (see SEND
+for further details)
+<P>
+<H2><A NAME="ss10.74">10.74 send (0)</A>
+</H2>
+
+<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
+<B>send RR <call></B> Send a message and ask for a read receipt<BR>
+<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
+<B>send PRIVATE <call></B> Send a personal message<BR>
+<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
+<P>
+<P>All the SEND commands will create a message which will be sent either to
+an individual callsign or to one of the 'bulletin' addresses.
+<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
+it will mark the message as personal and send it to the cluster node that
+that callsign is connected to.
+<P>You can have more than one callsign in all of the SEND commands.
+<P>You can have multiple qualifiers so that you can have for example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
+receive a read receipt when they have read the message.
+<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
+SP is an alias for SEND PRIVATE
+<P>
+<H2><A NAME="ss10.75">10.75 set/address (0)</A>
+</H2>
+
+<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
+<P>
+<P>Literally, record your address details on the cluster.
+<P>
+<H2><A NAME="ss10.76">10.76 set/announce (0)</A>
+</H2>
+
+<P><CODE><B>set/announce</B> Allow announce messages</CODE>
+<P>
+<P>Allow announce messages to arrive at your terminal.
+<P>
+<H2><A NAME="ss10.77">10.77 set/arcluster (5)</A>
+</H2>
+
+<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
+the node_call an AR-Cluster type node</CODE>
+<P>
+<P>Set the node_call as an AR-Cluster type node
+<P>
+<H2><A NAME="ss10.78">10.78 set/baddx (8)</A>
+</H2>
+
+<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated</CODE>
+<P>
+<P>Setting a word as 'baddx' will prevent spots with that word in the callsign
+field of a DX spot from going any further. They will not be displayed and they
+will not be sent onto other nodes.
+<P>The word must be wriiten in full, no wild cards are allowed eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/baddx FORSALE VIDEO FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To allow a word again, use the following command ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/baddx VIDEO
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.79">10.79 set/badnode (6)</A>
+</H2>
+
+<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
+being propagated</CODE>
+<P>
+<P>Setting a callsign as a 'badnode' will prevent spots from that node
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+<P>The call can be a full or partial call (or a prefix), eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/badnode K1TTT
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will stop anything from K1TTT (including any SSID's)
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/badnode K1TTT
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will allow spots from him again.
+<P>Use with extreme care. This command may well be superceded by FILTERing.
+<P>
+<H2><A NAME="ss10.80">10.80 set/badspotter (8)</A>
+</H2>
+
+<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
+<P>
+<P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+<P>The call must be written in full, no wild cards are allowed eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/badspotter VE2STN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ unset/badspotter VE2STN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will allow spots from him again.
+<P>Use with extreme care. This command may well be superceded by FILTERing.
+<P>
+<H2><A NAME="ss10.81">10.81 set/badword (8)</A>
+</H2>
+
+<P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE>
+<P>
+<P>Setting a word as a 'badword' will prevent things like spots,
+announces or talks with this word in the the text part from going any
+further. They will not be displayed and they will not be sent onto
+other nodes.
+<P>The word must be written in full, no wild cards are allowed eg:-
+<P>set/badword annihilate annihilated annihilation
+<P>will stop anything with these words in the text.
+<P>unset/badword annihilated
+<P>will allow text with this word again.
+<P>
+<P>
+<H2><A NAME="ss10.82">10.82 set/beep (0)</A>
+</H2>
+
+<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
+<P>
+<P>Add a beep to DX and other terminal messages.
+<P>
+<H2><A NAME="ss10.83">10.83 set/bbs (5)</A>
+</H2>
+
+<P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE>
+<P>
+<H2><A NAME="ss10.84">10.84 set/clx (5)</A>
+</H2>
+
+<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
+the node_call a CLX type node</CODE>
+<P>
+<P>Set the node_call as a CLX type node
+<P>
+<H2><A NAME="ss10.85">10.85 set/debug (9)</A>
+</H2>
+
+<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
+<P>
+<P>You can choose to log several different levels. The levels are
+<P>chan
+state
+msg
+cron
+connect
+<P>You can show what levels you are logging with the <EM>show/debug</EM>
+command.
+<P>You can remove a debug level with unset/debug <name>
+<P>
+<H2><A NAME="ss10.86">10.86 set/dx (0)</A>
+</H2>
+
+<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
+<P>
+<P>You can stop DX messages with the <EM>unset/dx</EM> command
+<P>
+<H2><A NAME="ss10.87">10.87 set/dxgrid (0)</A>
+</H2>
+
+<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
+<P>
+<P>Some logging programs do not like the additional information at
+the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
+command to remove the grid squares.
+<P>
+<H2><A NAME="ss10.88">10.88 set/dxnet (5)</A>
+</H2>
+
+<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
+the node_call a DXNet type node</CODE>
+<P>
+<P>Set the node_call as a DXNet type node
+<P>
+<H2><A NAME="ss10.89">10.89 set/echo (0)</A>
+</H2>
+
+<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
+<P>
+<P>If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+<P>You can remove the echo with the <EM>unset/echo</EM> command
+<P>The setting is stored in your user profile.
+<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+<P>
+<H2><A NAME="ss10.90">10.90 set/email (0)</A>
+</H2>
+
+<P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE>
+<P>
+<P>If any personal messages come in for your callsign then you can use
+these commands to control whether they are forwarded onto your email
+address. To enable the forwarding do something like:-
+<P>SET/EMAIL mike.tubby@somewhere.com
+<P>You can have more than one email address (each one separated by a space).
+Emails are forwarded to all the email addresses you specify.
+<P>You can disable forwarding by:-
+<P>UNSET/EMAIL
+<P>
+<H2><A NAME="ss10.91">10.91 set/here (0)</A>
+</H2>
+
+<P><CODE><B>set/here</B> Set the here flag</CODE>
+<P>
+<P>Let others on the cluster know you are here by only displaying your
+callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
+command to let people know you are away. This simply puts brackets
+around your callsign to indicate you are not available.
+<P>
+<H2><A NAME="ss10.92">10.92 set/homenode (0)</A>
+</H2>
+
+<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
+<P>
+<P>Tell the cluster system where you normally connect to. Any Messages sent
+to you will normally find their way there should you not be connected.
+eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/HOMENODE gb7djk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.93">10.93 set/hops (8)</A>
+</H2>
+
+<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
+Set hop count</CODE>
+<P>
+<P>Set the hop count for a particular type of broadcast for a node.
+<P>This command allows you to set up special hop counts for a node
+for currently: announce, spots, wwv and wcy broadcasts.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+eg:
+ set/hops gb7djk ann 10
+ set/hops gb7mbc spots 20
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Set SHOW/HOPS for information on what is already set. This command
+creates a filter and works in conjunction with the filter system.
+<P>
+<H2><A NAME="ss10.94">10.94 set/isolate (9)</A>
+</H2>
+
+<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
+<P>
+<P>Connect a node to your system in such a way that you are a full protocol
+member of its network and can see all spots on it, but nothing either leaks
+out from it nor goes back into from the rest of the nodes connected to you.
+<P>You can potentially connect several nodes in this way.
+<P>You can see which nodes are isolated with the show/isolate (1) command.
+<P>You can remove the isolation with the command unset/isolate.
+<P>
+<H2><A NAME="ss10.95">10.95 set/language (0)</A>
+</H2>
+
+<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
+<P>
+<P>You can select the language that you want the cluster to use. Currently
+the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
+<P>
+<H2><A NAME="ss10.96">10.96 set/location (0)</A>
+</H2>
+
+<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
+<P>
+<P>You can set your latitude and longitude manually or alternatively use the
+<EM>set/qra</EM> command which will do the conversion for you.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/location 54 04 N 2 02 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss10.97">10.97 set/sys_location (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
+<P>
+<P>In order to get accurate headings and such like you must tell the system
+what your latitude and longitude is. If you have not yet done a SET/QRA
+then this command will set your QRA locator for you. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/LOCATION 52 22 N 0 57 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.98">10.98 set/logininfo (0)</A>
+</H2>
+
+<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
+<P>
+<P>Show users and nodes when they log in and out of the local cluster. You
+can stop these messages by using the <EM>unset/logininfo</EM> command.
+<P>
+<P>
+<H2><A NAME="ss10.99">10.99 set/lockout (9)</A>
+</H2>
+
+<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
+<P>
+<P>You can show who is locked out with the <EM>show/lockout</EM> command.
+To allow the user to connect again, use the <EM>unset/lockout</EM> command.
+<P>
+<H2><A NAME="ss10.100">10.100 set/name (0)</A>
+</H2>
+
+<P><CODE><B>set/name <your_name></B> Set your name</CODE>
+<P>
+<P>Tell the cluster what your name is, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/name Dirk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.101">10.101 set/node (9)</A>
+</H2>
+
+<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
+<P>
+<P>Tell the system that the call(s) are to be treated as AK1A cluster and
+fed PC Protocol rather normal user commands.
+<P>From version 1.41 you can also set the following types of cluster
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
+<P>
+<H2><A NAME="ss10.102">10.102 set/obscount (9)</A>
+</H2>
+
+<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
+<P>
+<P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
+SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
+counter which is decremented on every outgoing ping and then reset to
+the 'obscount' value on every incoming ping. The default value of this
+parameter is 2.
+<P>What this means is that a neighbouring node will be pinged twice at
+(default) 300 second intervals and if no reply has been heard just before
+what would be the third attempt, that node is disconnected.
+<P>If a ping is heard then the obscount is reset to the full value. Using
+default values, if a node has not responded to a ping within 15 minutes,
+it is disconnected.
+<P>
+<H2><A NAME="ss10.103">10.103 set/page (0)</A>
+</H2>
+
+<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
+<P>
+<P>Tell the system how many lines you wish on a page when the number of lines
+of output from a command is more than this. The default is 20. Setting it
+explicitly to 0 will disable paging.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/PAGE 30
+ SET/PAGE 0
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The setting is stored in your user profile.
+<P>
+<H2><A NAME="ss10.104">10.104 set/password (0)</A>
+</H2>
+
+<P><CODE><B>set/password</B> Set your own password</CODE>
+<P>
+<P>This command only works for a 'telnet' user (currently). It will
+only work if you have a password already set. This initial password
+can only be set by the sysop.
+<P>When you execute this command it will ask you for your old password,
+then ask you to type in your new password twice (to make sure you
+get it right). You may or may not see the data echoed on the screen
+as you type, depending on the type of telnet client you have.
+<P>
+<H2><A NAME="ss10.105">10.105 set/password (9)</A>
+</H2>
+
+<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
+<P>
+<P>The password for a user can only be set by a full sysop. The string
+can contain any characters.
+<P>The way this field is used depends on context. If it is being used in
+the SYSOP command context then you are offered 5 random numbers and you
+have to supply the corresponding letters. This is now mainly for ax25
+connections.
+<P>If it is being used on incoming telnet connections then, if a password
+is set or the:
+<P>set/var $main::passwdreq = 1
+<P>command is executed in the startup script, then a password prompt is
+given after the normal 'login: ' prompt.
+<P>The command "unset/password" is provided to allow a sysop to remove a
+users password completely in case a user forgets or loses their password.
+<P>
+<H2><A NAME="ss10.106">10.106 set/pinginterval (9)</A>
+</H2>
+
+<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
+<P>
+<P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
+in order to determine the rolling quality of the link and, in future, to
+affect routing decisions. The default interval is 300 secs or 5 minutes.
+<P>You can use this command to set a different interval. Please don't.
+<P>But if you do the value you enter is treated as minutes up 60 and seconds
+for numbers greater than that.
+<P>This is used also to help determine when a link is down at the far end
+(as certain cluster software doesn't always notice), see SET/OBSCOUNT
+for more information.
+<P>
+<H2><A NAME="ss10.107">10.107 set/privilege (9)</A>
+</H2>
+
+<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
+<P>
+<P>Set the privilege level on a callsign. The privilege levels that pertain
+to commands are as default:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ 0 - normal user
+ 1 - allow remote nodes normal user RCMDs
+ 5 - various privileged commands (including shutdown, but not disc-
+ connect), the normal level for another node.
+ 8 - more privileged commands (including disconnect)
+ 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
+ LEVEL.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you are a sysop and you come in as a normal user on a remote connection
+your privilege will automatically be set to 0.
+<P>
+<H2><A NAME="ss10.108">10.108 set/spider (5)</A>
+</H2>
+
+<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
+the node_call a DXSpider type node</CODE>
+<P>
+<P>Set the node_call as a DXSpider type node
+<P>
+<H2><A NAME="ss10.109">10.109 set/sys_qra (9)</A>
+</H2>
+
+<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
+<P>
+<H2><A NAME="ss10.110">10.110 set/qra (0)</A>
+</H2>
+
+<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
+<P>
+<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
+done a SET/LOCATION then your latitude and longitude will be set roughly
+correctly (assuming your locator is correct ;-). For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/QRA JO02LQ
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.111">10.111 set/qth (0)</A>
+</H2>
+
+<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
+<P>
+<P>Tell the system where your are. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/qth East Dereham, Norfolk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.112">10.112 set/register (9)</A>
+</H2>
+
+<P><CODE><B>set/register <call></B> Mark a user as registered</CODE>
+<P>
+<P>Registration is a concept that you can switch on by executing the
+<P>set/var $main::regreq = 1
+<P>command (usually in your startup file)
+<P>If a user is NOT registered then, firstly, instead of the normal
+motd file (/spider/data/motd) being sent to the user at startup, the
+user is sent the motd_nor file instead. Secondly, the non registered
+user only has READ-ONLY access to the node. The non-registered user
+cannot use DX, ANN etc.
+<P>The only exception to this is that a non-registered user can TALK or
+SEND messages to the sysop.
+<P>To unset a user use the 'unset/register' command
+<P>
+<H2><A NAME="ss10.113">10.113 set/talk (0)</A>
+</H2>
+
+<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
+<P>
+<P>Allow talk messages to arrive at your console. You can switch off
+talks with the <EM>unset/talk</EM> command.
+<P>
+<H2><A NAME="ss10.114">10.114 set/wcy (0)</A>
+</H2>
+
+<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
+<P>
+<P>Allow WCY information to be seen at your console. You can switch off
+WCY messages with the <EM>unset/wcy</EM> command.
+<P>
+<H2><A NAME="ss10.115">10.115 set/wwv (0)</A>
+</H2>
+
+<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
+<P>
+<P>Allow WWV information to be seen at your console. You can switch off
+WWV messages with the <EM>unset/wwv</EM> command.
+<P>
+<H2><A NAME="ss10.116">10.116 set/wx (0)</A>
+</H2>
+
+<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
+<P>
+<P>Allow WX information to be seen at your console. You can switch off
+WX messages with the <EM>unset/wx</EM> command.
+<P>
+<H2><A NAME="ss10.117">10.117 show/baddx (1)</A>
+</H2>
+
+<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
+<P>
+<P>Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+<P>
+<H2><A NAME="ss10.118">10.118 show/badnode (6)</A>
+</H2>
+
+<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
+<P>
+<P>Display all the bad node callsigns in the system, see SET/BADNODE
+for more information.
+<P>
+<H2><A NAME="ss10.119">10.119 show/badspotter (1)</A>
+</H2>
+
+<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
+<P>
+<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+<P>
+<H2><A NAME="ss10.120">10.120 show/badword (1)</A>
+</H2>
+
+<P><CODE><B>show/badword</B> Show all the bad words in the system</CODE>
+<P>
+<P>Display all the bad words in the system, see SET/BADWORD
+for more information.
+<P>
+<H2><A NAME="ss10.121">10.121 show/configuration (0)</A>
+</H2>
+
+<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
+<P>
+<P>This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional <EM>node</EM>,
+you can specify a particular node to look at.
+<P>This command is normally abbreviated to: sh/c
+<P>BE WARNED: the list that is returned can be VERY long
+<P>
+<H2><A NAME="ss10.122">10.122 show/configuration/node (0)</A>
+</H2>
+
+<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
+<P>
+<P>Show all the nodes connected locally and the nodes they have connected.
+<P>
+<H2><A NAME="ss10.123">10.123 show/connect (1)</A>
+</H2>
+
+<P><CODE><B>show/connect</B> Show all the active connections</CODE>
+<P>
+<P>This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+<P>
+<H2><A NAME="ss10.124">10.124 show/date (0)</A>
+</H2>
+
+<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>This is very nearly the same as SHOW/TIME, the only difference the format
+of the date string if no arguments are given.
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss10.125">10.125 show/debug (9)</A>
+</H2>
+
+<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
+<P>
+<P>The levels can be set with <EM>set/debug</EM>
+<P>
+<H2><A NAME="ss10.126">10.126 show/dx (0)</A>
+</H2>
+
+<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
+<P>
+<P>If you just type SHOW/DX you will get the last so many spots
+(sysop configurable, but usually 10).
+<P>In addition you can add any number of these options in very nearly
+any order to the basic SHOW/DX command, they are:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+on <band> - eg 160m 20m 2m 23cm 6mm
+on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+<number> - the number of spots you want
+<from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+<prefix> - for a spotted callsign beginning with <prefix>
+*<suffix> - for a spotted callsign ending in <suffix>
+*<string>* - for a spotted callsign containing <string>
+
+day <number> - starting <number> days ago
+day <from>-<to> - <from> days <to> days ago
+
+info <text> - any spots containing <text> in the info or remarks
+
+by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
+
+qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
+
+qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.127">10.127 show/dxcc (0)</A>
+</H2>
+
+<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
+<P>
+<P>This command takes the <prefix> (which can be a full or partial
+callsign if desired), looks up which internal country number it is
+and then displays all the spots as per SH/DX for that country.
+<P>The options for SHOW/DX also apply to this command.
+e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.128">10.128 sh/dxstats (0)</A>
+</H2>
+
+<P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE>
+<P>
+<P>Show the total DX spots for the last 31 days
+<P>
+<P>
+<H2><A NAME="ss10.129">10.129 show/files (0)</A>
+</H2>
+
+<P><CODE><B>show/files [<filearea> [<string>]]</B> List
+the contents of a filearea</CODE>
+<P>
+<P>SHOW/FILES on its own will show you a list of the various fileareas
+available on the system. To see the contents of a particular file
+area type:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES <filearea>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>where <filearea> is the name of the filearea you want to see the
+contents of.
+<P>You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES bulletins arld*
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>See also TYPE - to see the contents of a file.
+<P>
+<H2><A NAME="ss10.130">10.130 show/filter (0)</A>
+</H2>
+
+<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
+<P>
+<P>Show the contents of all the filters that are set by you. This command
+displays all the filters set - for all the various categories.
+<P>
+<H2><A NAME="ss10.131">10.131 show/filter (extended for sysops) (5)</A>
+</H2>
+
+<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
+<P>
+<P>A sysop can look at any filters that have been set.
+<P>
+<H2><A NAME="ss10.132">10.132 show/hfstats (0)</A>
+</H2>
+
+<P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE>
+<P>
+<P>Show the HF DX spots breakdown by band for the last 31 days
+<P>
+<H2><A NAME="ss10.133">10.133 show/hftable (0)</A>
+</H2>
+
+<P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE>
+<P>
+<P>Show the HF DX Spotter table for your country for the last 31 days
+<P>
+<H2><A NAME="ss10.134">10.134 show/hops (8)</A>
+</H2>
+
+<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
+<P>
+<P>This command shows the hop counts set up for a node. You can specify
+which category you want to see. If you leave the category out then
+all the categories will be listed.
+<P>
+<H2><A NAME="ss10.135">10.135 show/isolate (1)</A>
+</H2>
+
+<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
+<P>
+<P>Show which nodes are currently set to be isolated.
+<P>
+<H2><A NAME="ss10.136">10.136 show/lockout (9)</A>
+</H2>
+
+<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
+<P>
+<P>Show a list of callsigns that have been excluded (locked out) of the
+cluster locally with the <EM>set/lockout</EM> command
+<P>
+<H2><A NAME="ss10.137">10.137 show/log (8)</A>
+</H2>
+
+<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
+<P>
+<P>This command outputs a short section of the system log. On its own
+it will output a general logfile. With the optional callsign it will
+show output from the log associated with that callsign.
+<P>
+<H2><A NAME="ss10.138">10.138 show/moon (0)</A>
+</H2>
+
+<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
+rise and set times</CODE>
+<P>
+<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>In addition, it will show the gain or loss dB relative to the nominal
+distance of 385,000Km due to the ellipsoidal nature of the orbit.
+<P>If all else fails it will show the Moonrise and set times for the node
+that you are connected to.
+<P>For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MOON
+ SH/MOON G1TLH W5UN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.139">10.139 show/muf (0)</A>
+</H2>
+
+<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
+the likely propagation to <prefix></CODE>
+<P>
+<P>This command allow you to estimate the likelihood of you contacting
+a station with the prefix you have specified. The output assumes a modest
+power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
+<P>The result predicts the most likely operating frequencies and signal
+levels for high frequency (shortwave) radio propagation paths on
+specified days of the year and hours of the day. It is most useful for
+paths between 250 km and 6000 km, but can be used with reduced accuracy
+for paths shorter or longer than this.
+<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+used to predict the MUF given the predicted flux, day of the year,
+hour of the day and geographic coordinates of the transmitter and
+receiver. This routine is reasonably accurate for the purposes here,
+with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+than the programs used by major shortwave broadcasting organizations,
+such as the Voice of America.
+<P>The command will display some header information detailing its
+assumptions, together with the locations, latitude and longitudes and
+bearings. It will then show UTC (UT), local time at the other end
+(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+(Zen) and the likely signal strengths. Then for each frequency for which
+the system thinks there is a likelihood of a circuit it prints a value.
+<P>The value is currently a likely S meter reading based on the conventional
+6dB / S point scale. If the value has a '+' appended it means that it is
+1/2 an S point stronger. If the value is preceeded by an 'm' it means that
+there is likely to be much fading and by an 's' that the signal is likely
+to be noisy.
+<P>By default SHOW/MUF will show the next two hours worth of data. You
+can specify anything up to 24 hours worth of data by appending the no of
+hours required after the prefix. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>produces:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+<P>inputting:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W 24
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will get you the above display, but with the next 24 hours worth of
+propagation data.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Gives you an estimate of the long path propagation characterics. It
+should be noted that the figures will probably not be very useful, nor
+terrible accurate, but it is included for completeness.
+<P>
+<H2><A NAME="ss10.140">10.140 show/newconfiguration (0)</A>
+</H2>
+
+<P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE>
+<P>
+<P>This command allows you to see all the users that can be seen
+and the nodes to which they are connected.
+<P>This command produces essentially the same information as
+SHOW/CONFIGURATION except that it shows all the duplication of
+any routes that might be present It also uses a different format
+which may not take up quite as much space if you don't have any
+loops.
+<P>BE WARNED: the list that is returned can be VERY long
+<P>
+<H2><A NAME="ss10.141">10.141 show/newconfiguration/node (0)</A>
+</H2>
+
+<P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE>
+<P>
+<P>Show all the nodes connected to this node in the new format.
+<P>
+<H2><A NAME="ss10.142">10.142 show/node (1)</A>
+</H2>
+
+<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
+number of nodes</CODE>
+<P>
+<P>Show the type and version (if connected) of the nodes specified on the
+command line. If no callsigns are specified then a sorted list of all
+the non-user callsigns known to the system will be displayed.
+<P>
+<H2><A NAME="ss10.143">10.143 show/prefix (0)</A>
+</H2>
+
+<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
+<P>
+<P>This command takes the <callsign> (which can be a full or partial
+callsign or a prefix), looks up which internal country number
+it is and then displays all the relevant prefixes for that country
+together with the internal country no, the CQ and ITU regions.
+<P>See also SHOW/DXCC
+<P>
+<P>
+<H2><A NAME="ss10.144">10.144 show/program (5)</A>
+</H2>
+
+<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
+<P>
+<P>Show the name and location where every program module was load from. This
+is useful for checking where you think you have loaded a .pm file from.
+<P>
+<H2><A NAME="ss10.145">10.145 show/qra (0)</A>
+</H2>
+
+<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
+between locators<BR>
+<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
+<P>
+<P>This is a multipurpose command that allows you either to calculate the
+distance and bearing between two locators or (if only one locator is
+given on the command line) the distance and beraing from your station
+to the locator. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA IO92QL
+SH/QRA JN06 IN73
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The first example will show the distance and bearing to the locator from
+yourself, the second example will calculate the distance and bearing from
+the first locator to the second. You can use 4 or 6 character locators.
+<P>It is also possible to convert a latitude and longitude to a locator by
+using this command with a latitude and longitude as an argument, for
+example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA 52 41 N 0 58 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.146">10.146 show/qrz (0)</A>
+</H2>
+
+<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
+<P>
+<P>This command queries the QRZ callbook server on the internet
+and returns any information available for that callsign. This service
+is provided for users of this software by http://www.qrz.com
+<P>
+<H2><A NAME="ss10.147">10.147 show/registered (9)</A>
+</H2>
+
+<P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE>
+<P>
+<H2><A NAME="ss10.148">10.148 show/route (0)</A>
+</H2>
+
+<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
+<P>
+<P>This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ sh/route n2tly
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.149">10.149 show/satellite (0)</A>
+</H2>
+
+<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
+Show satellite tracking data</CODE>
+<P>
+<P>Show the tracking data from your location to the satellite of your choice
+from now on for the next few hours.
+<P>If you use this command without a satellite name it will display a list
+of all the satellites known currently to the system.
+<P>If you give a name then you can obtain tracking data of all the passes
+that start and finish 5 degrees below the horizon. As default it will
+give information for the next three hours for every five minute period.
+<P>You can alter the number of hours and the step size, within certain
+limits.
+<P>Each pass in a period is separated with a row of '-----' characters
+<P>So for example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.150">10.150 show/sun (0)</A>
+</H2>
+
+<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
+sun rise and set times</CODE>
+<P>
+<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>If all else fails it will show the sunrise and set times for the node
+that you are connected to.
+<P>For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.151">10.151 show/time (0)</A>
+</H2>
+
+<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss10.152">10.152 show/vhfstats (0)</A>
+</H2>
+
+<P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE>
+<P>
+<P>Show the VHF DX spots breakdown by band for the last 31 days
+<P>
+<H2><A NAME="ss10.153">10.153 show/vhftable (0)</A>
+</H2>
+
+<P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE>
+<P>
+<P>Show the VHF DX Spotter table for your country for the last 31 days
+<P>
+<H2><A NAME="ss10.154">10.154 show/wcy (0)</A>
+</H2>
+
+<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
+<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
+<P>
+<P>Display the most recent WCY information that has been received by the system
+<P>
+<H2><A NAME="ss10.155">10.155 show/wwv (0)</A>
+</H2>
+
+<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
+<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
+<P>
+<P>Display the most recent WWV information that has been received by the system
+<P>
+<P>
+<H2><A NAME="ss10.156">10.156 shutdown (5)</A>
+</H2>
+
+<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
+<P>
+<P>Shutdown the cluster and disconnect all the users. If you have Spider
+set to respawn in /etc/inittab it will of course restart.
+<P>
+<H2><A NAME="ss10.157">10.157 spoof (9)</A>
+</H2>
+
+<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
+<P>
+<P>This is a very simple yet powerful command for the sysop. It allows you to
+issue commands as if you were a different user. This is very useful for the
+kind of things that users seem to always get wrong.. like home_node for
+example.
+<P>
+<H2><A NAME="ss10.158">10.158 stat/db (5)</A>
+</H2>
+
+<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
+<P>
+<P>Show the internal status of a database descriptor.
+<P>Depending on your privilege level you will see more or less information.
+This command is unlikely to be of much use to anyone other than a sysop.
+<P>
+<H2><A NAME="ss10.159">10.159 stat/channel (5)</A>
+</H2>
+
+<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
+<P>
+<P>Show the internal status of the channel object either for the channel that
+you are on or else for the callsign that you asked for.
+<P>Only the fields that are defined (in perl term) will be displayed.
+<P>
+<H2><A NAME="ss10.160">10.160 stat/msg (5)</A>
+</H2>
+
+<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
+<P>
+<P>This command shows the internal status of a message and includes information
+such as to whom it has been forwarded, its size, origin etc etc.
+<P>
+<P>If no message number is given then the status of the message system is
+displayed.
+<P>
+<H2><A NAME="ss10.161">10.161 stat/route_node (5)</A>
+</H2>
+
+<P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE>
+<P>
+<H2><A NAME="ss10.162">10.162 stat/route_user (5)</A>
+</H2>
+
+<P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE>
+<P>
+<H2><A NAME="ss10.163">10.163 stat/user (5)</A>
+</H2>
+
+<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
+<P>
+<P>Shows the full contents of a user record including all the secret flags
+and stuff.
+<P>Only the fields that are defined (in perl term) will be displayed.
+<P>
+<H2><A NAME="ss10.164">10.164 sysop (0)</A>
+</H2>
+
+<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
+<P>
+<P>The system automatically reduces your privilege level to that of a
+normal user if you login in remotely. This command allows you to
+regain your normal privilege level. It uses the normal system: five
+numbers are returned that are indexes into the character array that is
+your assigned password (see SET/PASSWORD). The indexes start from
+zero.
+<P>You are expected to return a string which contains the characters
+required in the correct order. You may intersperse those characters
+with others to obscure your reply for any watchers. For example (and
+these values are for explanation :-):
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you type:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>They will all match. If there is no password you will still be offered
+numbers but nothing will happen when you input a string. Any match is
+case sensitive.
+<P>
+<H2><A NAME="ss10.165">10.165 talk (0)</A>
+</H2>
+
+<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
+<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
+<B>talk <callsign> > <node_call> [<text>]</B>
+Send a text message to <callsign> via <node_call></CODE>
+<P>
+<P>Send a short message to any other station that is visible on the cluster
+system. You can send it to anyone you can see with a SHOW/CONFIGURATION
+command, they don't have to be connected locally.
+<P>The second form of TALK is used when other cluster nodes are connected
+with restricted information. This usually means that they don't send
+the user information usually associated with logging on and off the cluster.
+<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
+see GB7TLH in the SH/C list but with no users, then you would use the
+second form of the talk message.
+<P>If you want to have a ragchew with someone you can leave the text message
+out and the system will go into 'Talk' mode. What this means is that a
+short message is sent to the recipient telling them that you are in a 'Talking'
+frame of mind and then you just type - everything you send will go to the
+station that you asked for.
+<P>All the usual announcements, spots and so on will still come out on your
+terminal.
+<P>If you want to do something (such as send a spot) you precede the normal
+command with a '/' character, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To leave talk mode type:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ /EX
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.166">10.166 type (0)</A>
+</H2>
+
+<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
+<P>
+<P>Type out the contents of a file in a filearea. So, for example, in
+filearea 'bulletins' you want to look at file 'arld051' you would
+enter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ TYPE bulletins/arld051
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>See also SHOW/FILES to see what fileareas are available and a
+list of content.
+<P>
+<H2><A NAME="ss10.167">10.167 who (0)</A>
+</H2>
+
+<P><CODE><B>who</B> Show who is physically connected locally</CODE>
+<P>
+<P>This is a quick listing that shows which callsigns are connected and
+what sort of connection they have
+<P>
+<H2><A NAME="ss10.168">10.168 wx (0)</A>
+</H2>
+
+<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
+<B>wx full <text> </B> Send a weather message to all cluster users</CODE>
+<P>
+<P>Weather messages can sometimes be useful if you are experiencing an extreme
+that may indicate enhanced conditions
+<P>
+<H2><A NAME="ss10.169">10.169 wx (enhanced for sysops) (5)</A>
+</H2>
+
+<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
+<P>
+<P>Send a weather message only to other cluster nodes and not to general users.
+<P>
+<P>
+<P>
+<HR>
+Next
+<A HREF="adminmanual-9.html">Previous</A>
+<A HREF="adminmanual.html#toc10">Contents</A>
+</BODY>
+</HTML>
projects / spider.git / commitdiff