--- /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 User Manual : The DXSpider command reference</TITLE>
+ <LINK HREF="usermanual-11.html" REL=previous>
+ <LINK HREF="usermanual.html#toc12" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+Next
+<A HREF="usermanual-11.html">Previous</A>
+<A HREF="usermanual.html#toc12">Contents</A>
+<HR>
+<H2><A NAME="s12">12. The DXSpider command reference</A></H2>
+
+<P>Below is a complete list of commands available from the cluster prompt.
+These are listed below in alphabetical order.
+<P>
+<H2><A NAME="ss12.1">12.1 accept/announce</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="ss12.2">12.2 accept/spots </A>
+</H2>
+
+<P><CODE><B>accept/announce [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="ss12.3">12.3 accept/wcy </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="ss12.4">12.4 accept/wwv </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="ss12.5">12.5 announce </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
+<P>
+<H2><A NAME="ss12.6">12.6 announce full </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>
+<H2><A NAME="ss12.7">12.7 apropos </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="ss12.8">12.8 bye </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="ss12.9">12.9 clear/spots </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="ss12.10">12.10 dbavail </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="ss12.11">12.11 dbshow </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>
+<H2><A NAME="ss12.12">12.12 directory </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>
+<H2><A NAME="ss12.13">12.13 dx </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="ss12.14">12.14 help </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="ss12.15">12.15 kill </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="ss12.16">12.16 links </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>
+<H2><A NAME="ss12.17">12.17 read </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>
+<H2><A NAME="ss12.18">12.18 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="ss12.19">12.19 reject/spots </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="ss12.20">12.20 reject/wcy </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="ss12.21">12.21 reject/wwv </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="ss12.22">12.22 reply </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="ss12.23">12.23 send </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="ss12.24">12.24 set/address </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="ss12.25">12.25 set/announce </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="ss12.26">12.26 set/beep </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="ss12.27">12.27 set/dx </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="ss12.28">12.28 set/dxgrid</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="ss12.29">12.29 set/echo </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="ss12.30">12.30 set/here</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="ss12.31">12.31 set/homenode </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="ss12.32">12.32 set/language </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) <EM>sp</EM> (Spanish)
+and <EM>nl</EM> (Dutch).
+<P>
+<H2><A NAME="ss12.33">12.33 set/location </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>
+<H2><A NAME="ss12.34">12.34 set/logininfo </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>
+<H2><A NAME="ss12.35">12.35 set/name </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="ss12.36">12.36 set/page </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="ss12.37">12.37 set/qra </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="ss12.38">12.38 set/qth</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="ss12.39">12.39 set/talk</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="ss12.40">12.40 set/wcy</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="ss12.41">12.41 set/wwv</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="ss12.42">12.42 set/wx </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="ss12.43">12.43 show/date </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="ss12.44">12.44 show/dx </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="ss12.45">12.45 show/dxcc </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="ss12.46">12.46 show/files </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="ss12.47">12.47 show/filter </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="ss12.48">12.48 show/moon </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="ss12.49">12.49 show/muf </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>inputing:-
+<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="ss12.50">12.50 show/prefix </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>
+<H2><A NAME="ss12.51">12.51 show/qra </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="ss12.52">12.52 show/qrz</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="ss12.53">12.53 show/route </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="ss12.54">12.54 show/satellite </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="ss12.55">12.55 show/sun </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="ss12.56">12.56 show/time </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="ss12.57">12.57 show/wcy </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="ss12.58">12.58 show/wwv</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>
+<H2><A NAME="ss12.59">12.59 sysop </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="ss12.60">12.60 talk </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="ss12.61">12.61 type </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="ss12.62">12.62 who </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="ss12.63">12.63 wx </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>
+<HR>
+Next
+<A HREF="usermanual-11.html">Previous</A>
+<A HREF="usermanual.html#toc12">Contents</A>
+</BODY>
+</HTML>
projects / spider.git / blobdiff