+<sect1>load/forward (9)
+
+<P>
+<tt>
+<bf>load/forward</bf> Reload the msg forwarding routing table
+</tt>
+
+Reload the /spider/msg/forward.pl file if you have changed it
+manually whilst the cluster is running.
+
+<sect1>load/messages (9)
+
+<P>
+<tt>
+<bf>load/messages</bf> Reload the system messages file
+</tt>
+
+<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 :-
+
+unknown message 'xxxx' in lang 'en'
+
+<sect1>load/prefixes (9)
+
+<P>
+<tt>
+<bf>load/prefixes</bf> Reload the prefix table
+</tt>
+
+<P>
+Reload the /spider/data/prefix_data.pl file if you have changed it manually
+whilst the cluster is running.
+
+<sect1>merge (5)
+
+<P>
+<tt>
+<bf>merge <node> [<no spots>/<no wwv>]</bf> Ask for the
+latest spots and WWV
+</tt>
+
+<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.
+
+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).
+
+<sect1>msg (9)
+
+<P>
+<tt>
+<bf>msg <cmd> <msgno> [data ...]</bf> Alter various message
+parameters
+</tt>
+
+<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.
+
+<tscreen><verb>
+ 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
+</verb></tscreen>
+
+You can look at the status of a message by using:-
+
+ STAT/MSG <msgno>
+
+This will display more information on the message than DIR does.
+
+<sect1>pc (8)
+
+<P>
+<tt>
+<bf>pc <call> <text></bf> Send text (eg PC Protocol) to <call>
+</tt>
+
+<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:-
+
+ pc gb7djk PC33^GB7TLH^GB7DJK^400^
+
+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.
+
+ pc G1TLH Try doing that properly!!!
+
+<sect1>ping (1)
+
+<P>
+<tt>
+<bf>ping <node></bf> Check the link quality between nodes
+</tt>
+
+<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.
+
+
+<sect1>rcmd (1)
+
+<P>
+<tt>
+<bf>rcmd <node call> <cmd></bf> Send a command to another DX cluster
+</tt>
+
+<P>
+This command allows you to send nearly any command to another DX Cluster
+node that is connected to the system.
+
+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.
+
+<sect1>read (0)
+
+<P>
+<tt>
+<bf>read</bf> Read the next unread personal message addressed to you<newline>
+<bf>read <msgno></bf> Read the specified message<newline>
+</tt>
+
+<P>
+You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+
+
+<sect1>read (extended for sysops) (5)
+
+<P>
+<tt>
+<bf>read <msgno></bf> Read a message on the system
+</tt>
+
+<P>
+As a sysop you may read any message on the system
+
+<sect1>reject/announce
+
+<P>
+<tt>
+<bf>reject/announce [0-9] <pattern></bf> Set a reject filter
+for announce
+</tt>
+
+<P>
+Create an 'reject this announce' line for a filter.
+
+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.
+
+You can use any of the following things in this line:-
+
+<tscreen><verb>
+ 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)
+</verb></tscreen>
+
+some examples:-
+
+<tscreen><verb>
+ rej/ann by_zone 14,15,16 and not by G,M,2
+</verb></tscreen>
+
+You can use the tag 'all' to reject everything eg:
+
+<tscreen><verb>
+ rej/ann all
+</verb></tscreen>
+
+but this probably for advanced users...
+
+<sect1>reject/announce (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>reject/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version
+</tt>
+
+<P>
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+<tscreen><verb>
+ reject/ann by G,M,2
+ reject/ann input node_default by G,M,2
+ reject/ann user_default by G,M,2
+</verb></tscreen>
+
+<sect1>reject/spots (0)
+
+<P>
+<tt>
+<bf>reject/spots [0-9] <pattern></bf> Set a reject filter
+line for spots
+</tt>
+
+<P>
+Create a 'reject this spot' line for a filter.
+
+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.
+
+You can use any of the following things in this line:-
+
+<tscreen><verb>
+ 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>
+</verb></tscreen>
+
+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)
+
+some examples:-
+
+<tscreen><verb>
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+You can use the tag 'all' to reject everything eg:
+
+<tscreen><verb>
+ rej/spot 3 all
+</verb></tscreen>
+
+but this probably for advanced users...
+
+<sect1>reject/spots (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>reject/spots <call> [input] [0-9] <pattern></bf>
+ Reject spot filter sysop version
+</tt>
+
+<P>
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+<tscreen><verb>
+ 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
+</verb></tscreen>
+
+<sect1>reject/wcy (0)
+
+<P>
+<tt>
+<bf>reject/wcy [0-9] <pattern></bf> Set a reject WCY filter
+</tt>
+
+<P>
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+<tscreen><verb>
+ 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>
+</verb></tscreen>
+
+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).
+
+This command is really provided for future use.
+
+See HELP FILTER for information.
+
+<sect1>reject/wcy (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>reject/wcy <call> [input] [0-9] <pattern></bf>
+ WCY reject filter sysop version
+</tt>
+
+<P>
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+ reject/wcy gb7djk all
+
+<sect1>reject/wwv (0)
+
+<P>
+<tt>
+<bf>reject/wwv [0-9] <pattern></bf> Set a reject WWV filter
+</tt>
+
+<P>
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+<tscreen><verb>
+ 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>
+</verb></tscreen>
+
+for example
+
+<tscreen><verb>
+ reject/wwv by_zone 14,15,16
+</verb></tscreen>
+
+is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+
+See HELP FILTER for information.
+
+<sect1>reject/wwv (extended for sysops) (8)
+
+<P>
+<tt>
+<bf>reject/wwv <call> [input] [0-9] <pattern></bf>
+ WWV reject filter sysop version
+</tt>
+
+<P>This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+<tscreen><verb>
+ reject/wwv db0sue-7 1 by_zone 4
+ reject/wwv node_default all
+
+ reject/wwv user_default by W
+</verb></tscreen>
+
+<sect1>reply (0)
+
+<P>
+<tt>
+<bf>reply</bf> Reply (privately) to the last message that you have read<newline>
+<bf>reply <msgno></bf> Reply (privately) to the specified message<newline>
+<bf>reply B <msgno></bf> Reply as a Bulletin to the specified message<newline>
+<bf>reply NOPrivate <msgno></bf> Reply as a Bulletin to the specified
+message<newline>
+<bf>reply RR <msgno></bf> Reply to the specified message with read
+receipt<newline>
+</tt>
+
+<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.
+
+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)
+
+<sect1>send (0)
+
+<P>
+<tt>
+<bf>send <call> [<call> ...]</bf> Send a message to
+one or more callsigns<newline>
+<bf>send RR <call></bf> Send a message and ask for a read receipt<newline>
+<bf>send COPY <msgno> <call></bf> Send a copy of a message
+to someone<newline>
+<bf>send PRIVATE <call></bf> Send a personal message<newline>
+<bf>send NOPRIVATE <call></bf> Send a message to all stations<newline>
+</tt>
+
+<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.
+
+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.
+
+You can have more than one callsign in all of the SEND commands.
+
+You can have multiple qualifiers so that you can have for example:-
+
+<tscreen><verb>
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+</verb></tscreen>
+
+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.
+
+SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
+SP is an alias for SEND PRIVATE
+
+<sect1>set/address (0)
+
+<P>
+<tt>
+<bf>set/address <your_address></bf> Record your postal address
+</tt>
+
+<P>
+Literally, record your address details on the cluster.
+
+<sect1>set/announce (0)
+
+<P>
+<tt>
+<bf>set/announce</bf> Allow announce messages
+</tt>
+
+<P>
+Allow announce messages to arrive at your terminal.
+
+<sect1>set/arcluster (5)
+
+<P>
+<tt>
+<bf>set/arcluster <node_call> [<node_call> ...]</bf> Make
+the node_call an AR-Cluster type node
+</tt>
+
+<P>
+Set the node_call as an AR-Cluster type node
+
+<sect1>set/baddx (8)
+
+<P>
+<tt>
+<bf>set/baddx <call></bf> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated
+</tt>
+
+<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.
+
+The word must be wriiten in full, no wild cards are allowed eg:-
+
+<tscreen><verb>
+ set/baddx FORSALE VIDEO FR0G
+</verb></tscreen>
+
+To allow a word again, use the following command ...
+
+<tscreen><verb>
+ unset/baddx VIDEO
+</verb></tscreen>
+
+<sect1>set/badnode (6)
+
+<P>
+<tt>
+<bf>set/badnode <node_call></bf> Stop spots from this node_call
+being propagated
+</tt>
+
+<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.
+
+The call can be a full or partial call (or a prefix), eg:-
+
+<tscreen><verb>
+ set/badnode K1TTT
+</verb></tscreen>
+
+will stop anything from K1TTT (including any SSID's)
+
+<tscreen><verb>
+ unset/badnode K1TTT
+</verb></tscreen>
+
+will allow spots from him again.
+
+Use with extreme care. This command may well be superceded by FILTERing.
+
+<sect1>set/badspotter (8)
+
+<P>
+<tt>
+<bf>set/badspotter <call></bf> Stop spots from this callsign being propagated
+</tt>
+
+<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.
+
+The call must be written in full, no wild cards are allowed eg:-
+
+<tscreen><verb>
+ set/badspotter VE2STN
+</verb></tscreen>
+
+will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+
+<tscreen><verb>
+ unset/badspotter VE2STN
+</verb></tscreen>
+
+will allow spots from him again.
+
+Use with extreme care. This command may well be superceded by FILTERing.
+
+<sect1>set/beep (0)
+
+<P>
+<tt>
+<bf>set/beep</bf> Add beeps to terminal messages
+</tt>
+
+<P>
+Add a beep to DX and other terminal messages.
+
+<sect1>set/clx (5)
+
+<P>
+<tt>
+<bf>set/clx <node_call> [<node_call> ...]</bf> Make
+the node_call a CLX type node
+</tt>
+
+<P>
+Set the node_call as a CLX type node
+
+<sect1>set/debug (9)
+
+<P>
+<tt>
+<bf>set/debug <name></bf> Add a debug level to the debug set
+</tt>
+
+<P>
+You can remove this level with unset/debug <name>
+
+<sect1>set/dx (0)
+
+<P>
+<tt>
+<bf>set/dx</bf>Allow DX messages to arrive at your terminal
+</tt>
+
+<P>
+You can stop DX messages with the <em>unset/dx</em> command
+
+<sect1>set/dxgrid (0)
+
+<P>
+<tt>
+<bf>set/dxgrid</bf>Allow grid squares on the end of DX messages
+</tt>
+
+<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.
+
+<sect1>set/dxnet (5)
+
+<P>
+<tt>
+<bf>set/dxnet <node_call> [<node_call> ...]</bf> Make
+the node_call a DXNet type node
+</tt>
+
+<P>
+Set the node_call as a DXNet type node
+
+<sect1>set/echo (0)
+
+<P>
+<tt>
+<bf>set/echo</bf> Make the cluster echo your input
+</tt>
+
+<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.
+
+You can remove the echo with the <em>unset/echo</em> command
+
+The setting is stored in your user profile.
+
+YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+
+<sect1>set/here (0)
+
+<P>
+<tt>
+<bf>set/here</bf> Set the here flag
+</tt>
+
+<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.
+
+<sect1>set/homenode (0)
+
+<P>
+<tt>
+<bf>set/homenode <node_call></bf> Set your home cluster
+</tt>
+
+<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:-
+
+<tscreen><verb>
+ SET/HOMENODE gb7djk
+</verb></tscreen>
+
+<sect1>set/hops (8)
+
+<P>
+<tt>
+<bf>set/hops <node_call> ann|spots|wwv|wcy <n></bf>
+Set hop count
+</tt>
+
+<P>
+Set the hop count for a particular type of broadcast for a node.
+
+This command allows you to set up special hop counts for a node
+for currently: announce, spots, wwv and wcy broadcasts.
+
+<tscreen><verb>
+eg:
+ set/hops gb7djk ann 10
+ set/hops gb7mbc spots 20
+</verb></tscreen>
+
+Set SHOW/HOPS for information on what is already set. This command
+creates a filter and works in conjunction with the filter system.
+
+<sect1>set/isolate (9)
+
+<P>
+<tt>
+<bf>set/isolate <node call></bf> Isolate a node from the rest of the network
+</tt>
+
+<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.
+
+You can potentially connect several nodes in this way.
+
+You can see which nodes are isolated with the show/isolate (1) command.
+
+You can remove the isolation with the command unset/isolate.
+
+<sect1>set/language (0)
+
+<P>
+<tt>
+<bf>set/language <language></bf> Set the language you wish to use
+</tt>
+
+<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).
+
+<sect1>set/location (0)
+
+<P>
+<tt>
+<bf>set/location <lat and long></bf> Set your latitude and longitude
+</tt>
+
+<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.
+
+<tscreen><verb>
+ set/location 54 04 N 2 02 E
+</verb></tscreen>
+
+
+<sect1>set/sys_location (9)
+
+<P>
+<tt>
+<bf>set/sys_location <lat & long></bf> Set your cluster latitude and longitude
+</tt>
+
+<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:-
+
+<tscreen><verb>
+ SET/LOCATION 52 22 N 0 57 E
+</verb></tscreen>
+
+<sect1>set/logininfo (0)
+
+<P>
+<tt>
+<bf>set/logininfo</bf> Show logins and logouts of nodes and users
+</tt>
+
+<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.
+
+
+<sect1>set/lockout (9)
+
+<P>
+<tt>
+<bf>set/lockout <call></bf> Stop a callsign connecting to the cluster
+</tt>
+
+<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.
+
+<sect1>set/name (0)
+
+<P>
+<tt>
+<bf>set/name <your_name></bf> Set your name
+</tt>
+
+<P>
+Tell the cluster what your name is, eg:-
+
+<tscreen><verb>
+ set/name Dirk
+</verb></tscreen>
+
+<sect1>set/node (9)
+
+<P>
+<tt>
+<bf>set/node <call> [<call> ...]</bf> Make the callsign an AK1A cluster
+</tt>
+
+<P>
+Tell the system that the call(s) are to be treated as AK1A cluster and
+fed PC Protocol rather normal user commands.
+
+From version 1.41 you can also set the following types of cluster
+
+<tscreen><verb>
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
+</verb></tscreen>
+
+To see what your nodes are set to, use the <em>show/nodes</em> command.
+
+<sect1>set/obscount (9)
+
+<P>
+<tt>
+<bf>set/obscount <count> <node call></bf> Set the 'pump-up'
+obsolescence counter
+</tt>
+
+<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.
+
+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.
+
+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.
+
+<sect1>set/page (0)
+
+<P>
+<tt>
+<bf>set/page <n></bf> Set the number of lines per page
+</tt>
+
+<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.
+
+<tscreen><verb>
+ SET/PAGE 30
+ SET/PAGE 0
+</verb></tscreen>
+
+The setting is stored in your user profile.
+
+
+<sect1>set/password (9)
+
+<P>
+<tt>
+<bf>set/password <callsign> <string></bf> Set a users password
+</tt>
+
+<P>
+The password for a user can only be set by a full sysop. The string
+can contain any characters but any spaces are removed (you can type in
+spaces - but they won't appear in the password). You can see the
+result with STAT/USER. The password is the usual 30 character baycom
+type password.
+
+<sect1>set/pinginterval (9)
+
+<P>
+<tt>
+<bf>set/pinginterval <time> <node call></bf> Set the ping time
+to neighbouring nodes
+</tt>
+
+<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.
+
+You can use this command to set a different interval. Please don't.
+
+But if you do the value you enter is treated as minutes up 60 and seconds
+for numbers greater than that.
+
+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.
+
+<sect1>set/privilege (9)
+
+<P>
+<tt>
+<bf>set/privilege <n> <call> [<call> ...]</bf> Set the
+privilege level on a call
+</tt>
+
+<P>
+Set the privilege level on a callsign. The privilege levels that pertain
+to commands are as default:-
+
+<tscreen><verb>
+ 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.
+</verb></tscreen>
+
+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.
+
+<sect1>set/spider (5)
+
+<P>
+<tt>
+<bf>set/spider <node_call> [<node_call> ...]</bf> Make
+the node_call a DXSpider type node
+</tt>
+
+<P>
+Set the node_call as a DXSpider type node
+
+<sect1>set/sys_qra (9)
+
+<P>
+<tt>
+<bf>set/sys_qra <locator></bf> Set your cluster QRA locator
+</tt>
+
+<sect1>set/qra (0)
+
+<P>
+<tt>
+<bf>set/qra <locator></bf> Set your QRA locator
+</tt>
+
+<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:-
+
+<tscreen><verb>
+ SET/QRA JO02LQ
+</verb></tscreen>
+
+<sect1>set/qth (0)
+
+<P>
+<tt>
+<bf>set/qth <your QTH></bf> Set your QTH
+</tt>
+
+<P>
+Tell the system where your are. For example:-
+
+<tscreen><verb>
+ set/qth East Dereham, Norfolk
+</verb></tscreen>
+
+<sect1>set/talk (0)
+
+<P>
+<tt>
+<bf>set/talk</bf> Allow talk messages to be seen at your console
+</tt>
+
+<P>
+Allow talk messages to arrive at your console. You can switch off
+talks with the <em>unset/talk</em> command.
+
+<sect1>set/wcy (0)
+
+<P>
+<tt>
+<bf>set/wcy</bf> Allow WCY messages to be seen at your console
+</tt>
+
+<P>
+Allow WCY information to be seen at your console. You can switch off
+WCY messages with the <em>unset/wcy</em> command.
+
+<sect1>set/wwv (0)
+
+<P>
+<tt>
+<bf>set/wwv</bf> Allow WWV messages to be seen at your console
+</tt>
+
+<P>
+Allow WWV information to be seen at your console. You can switch off
+WWV messages with the <em>unset/wwv</em> command.
+
+<sect1>set/wx (0)
+
+<P>
+<tt>
+<bf>set/wx</bf> Allow WX messages to be seen at your console
+</tt>
+
+<P>
+Allow WX information to be seen at your console. You can switch off
+WX messages with the <em>unset/wx</em> command.
+
+<sect1>show/baddx (1)
+
+<P>
+<tt>
+<bf>show/baddx</bf>Show all the bad dx calls in the system
+</tt>
+
+<P>
+Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+
+<sect1>show/badnode (6)
+
+<P>
+<tt>
+<bf>show/badnode</bf> Show all the bad nodes in the system
+</tt>
+
+<P>
+Display all the bad node callsigns in the system, see SET/BADNODE
+for more information.
+
+<sect1>show/badspotter (1)
+
+<P>
+<tt>
+<bf>show/badspotter</bf>Show all the bad spotters in the system
+</tt>
+
+<P>
+Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+
+<sect1>show/date (0)
+
+<P>
+<tt>
+<bf>show/date [<prefix>|<callsign>]</bf> Show
+the local time
+</tt>
+
+<P>
+This is very nearly the same as SHOW/TIME, the only difference the format
+of the date string if no arguments are given.
+
+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.
+
+<sect1>show/dx (0)
+
+<P>
+<tt>
+<bf>show/dx [options]</bf> interrogate the spot database
+</tt>
+
+<P>
+If you just type SHOW/DX you will get the last so many spots
+(sysop configurable, but usually 10).
+
+In addition you can add any number of these options in very nearly
+any order to the basic SHOW/DX command, they are:-
+
+<tscreen><verb>
+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.
+</verb></tscreen>
+
+e.g.
+
+<tscreen><verb>
+ 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
+</verb></tscreen>
+
+<sect1>show/dxcc (0)
+
+<P>
+<tt>
+<bf>show/dxcc <prefix></bf> Interrogate the spot database by country
+</tt>
+
+<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.
+
+The options for SHOW/DX also apply to this command.
+e.g.
+
+<tscreen><verb>
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+</verb></tscreen>
+
+<sect1>show/files (0)
+
+<P>
+<tt>
+<bf>show/files [<filearea> [<string>]]</bf> List
+the contents of a filearea
+</tt>
+
+<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:-
+
+<tscreen><verb>
+ SH/FILES <filearea>
+</verb></tscreen>
+
+where <filearea> is the name of the filearea you want to see the
+contents of.
+
+You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+
+<tscreen><verb>
+ SH/FILES bulletins arld*
+</verb></tscreen>
+
+See also TYPE - to see the contents of a file.
+
+<sect1>show/filter (0)
+
+<P>
+<tt>
+<bf>show/filter</bf> Show the filters you have set
+</tt>
+
+<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.
+
+<sect1>show/filter (extended for sysops) (5)
+
+<P>
+<tt>
+<bf>show/filter <callsign></bf> Show the filters set by <callsign>
+</tt>
+
+<P>
+A sysop can look at any filters that have been set.
+
+<sect1>show/hops (8)
+
+<P>
+<tt>
+<bf>show/hops <node_call> [ann|spots|wcy|wwv|]</bf> Show the hop
+counts for a node
+</tt>
+
+<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.
+
+<sect1>show/isolate (1)