+<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>