The DXSpider Administration Manual v1.50: The DXSpider command set

11.1 accept (0)

accept Set a filter to accept something

Create a filter to accept somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.

11.2 accept/announce <call> [input] [0-9] <pattern> (8)

accept/announce <call> [input] [0-9] <pattern> Announce filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  accept/ann by G,M,2  accept/ann input node_default by G,M,2  accept/ann user_default by G,M,2

11.3 accept/announce [0-9] <pattern> (0)

accept/announce [0-9] <pattern> Set an 'accept' filter line for announce

Create an 'accept this announce' line for a filter. An accept filter line means that if the announce matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-


  info <string>            eg: iota or qsl  by <prefixes>            eg: G,M,2           origin <prefixes>  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  origin_state <states>                eg: VA,NH,RI,NH  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  by_state <states>  channel <prefixes>  wx 1                     filter WX announces  dest <prefixes>          eg: 6MUK,WDX      (distros)

some examples:-


  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)


  acc/ann by G,M,2

for american states


  acc/ann by_state va,nh,ri,nh

You can use the tag 'all' to accept everything eg:


  acc/ann all

but this probably for advanced users...

11.4 accept/route <call> [0-9] <pattern> (8)

accept/route <call> [0-9] <pattern> Set an 'accept' filter line for routing

Create an 'accept this routing PC Protocol' line for a filter. An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter it is passed thru that interface. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-


  call <prefixes>        the callsign of the thingy  call_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  call_itu <prefixes or numbers>     or: G,GM,GW  call_zone <prefixes or numbers>  call_state <states>                eg: VA,NH,RI,NH  origin <prefixes>      really the interface it came in on  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  origin_state <states>                eg: VA,NH,RI,NH

some examples:-


  acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)  acc/route gb7djk call gb7djk     (equiv to SET/ISOLATE)

you can now use 'by' as a synonym for 'call' so:


  by = call  by_dxcc = call_dxcc

and so onYou can use the tag 'all' to accept everything eg:


  acc/route all

11.5 accept/spots <call> [input] [0-9] <pattern> (8)

accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  accept/spot db0sue-7 1 by_zone 14,15,16  accept/spot node_default all  set/hops node_default 10


  accept/spot user_default by G,M,2

11.6 accept/spots [0-9] <pattern> (0)

accept/spots [0-9] <pattern> Set an 'accept' filter line for spots

Create an 'accept this spot' line for a filter. An accept filter line means that if the spot matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-


  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 <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  call_itu <prefixes or numbers>     or: G,GM,GW  call_zone <prefixes or numbers>  call_state <states>                eg: VA,NH,RI,ME  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  by_state <states>                eg: VA,NH,RI,ME  origin <prefixes>  channel <prefixes>

'call' means the callsign that has spotted 'by' whoever.For frequencies, you can use any of the band names defined inSHOW/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 gettoo hung up about that)some examples:-


  acc/spot 1 on hf/cw  acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

You can use the tag 'all' to accept everything, eg:


  acc/spot 3 all

for US states


  acc/spots by_state VA,NH,RI,MA,ME

but this probably for advanced users...

11.7 accept/wcy <call> [input] [0-9] <pattern> (8)

accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  accept/wcy node_default all  set/hops node_default 10

11.8 accept/wcy [0-9] <pattern> (0)

accept/wcy [0-9] <pattern> set an 'accept' WCY filter

It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-


  by <prefixes>            eg: G,M,2           origin <prefixes>  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  channel <prefixes>

There are no examples because WCY Broadcasts only come from one place andyou 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.

11.9 accept/wwv <call> [input] [0-9] <pattern> (8)

accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  accept/wwv db0sue-7 1 by_zone 4  accept/wwv node_default all  set/hops node_default 10


  accept/wwv user_default by W,K

11.10 accept/wwv [0-9] <pattern> (0)

accept/wwv [0-9] <pattern> set an 'accept' WWV filter

It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-


  by <prefixes>            eg: G,M,2           origin <prefixes>  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  channel <prefixes>

for example


  accept/wwv by_zone 4

is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information.

11.11 announce <text> (0)

announce <text> Send an announcement to LOCAL users only

<text> is the text of the announcement you wish to broadcast

11.12 announce full <text> (0)

announce full <text> Send an announcement cluster wide

This will send your announcement cluster wide

11.13 announce sysop <text> (5)

announce sysop <text> Send an announcement to Sysops only

11.14 apropos <string> (0)

apropos <string> Search help database for <string>

Search the help database for <string> (it isn't case sensitive), and printthe names of all the commands that may be relevant.

11.15 blank [<string>] [<nn>] (0)

blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)

In its basic form this command prints one or more blank lines. However ifyou pass it a string it will replicate the string for the width of the screen (default 80) and then print that one or more times, so:


  blank 2

prints two blank lines


  blank -

prints a row of - characters once.


  blank abc

prints 'abcabcabcabcabcabc....'This is really only of any use in a script file and you can print a maximumof 9 lines.

11.16 bye (0)

bye Exit from the cluster

This will disconnect you from the cluster

11.17 catchup <node call> all|[<msgno> ...] (5)

catchup <node call> all|[<msgno> ...] Mark a message as sent

11.18 clear/announce <callsign> [input] [0-9|all] (8)

clear/announce <callsign> [input] [0-9|all] Clear a announce filter line

A sysop can clear an input or normal output filter for a user or thenode_default or user_default.

11.19 clear/announce [1|all] (0)

clear/announce [1|all] Clear a announce filter line

This command allows you to clear (remove) a line in a annouce filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.

11.20 clear/route <callsign> [input] [0-9|all] (8)

clear/route <callsign> [input] [0-9|all] Clear a route filter line

A sysop can clear an input or normal output filter for a user or thenode_default or user_default.

11.21 clear/route [1|all] (0)

clear/route [1|all] Clear a route filter line

This command allows you to clear (remove) a line in a route filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.

11.22 clear/spots <callsign> [input] [0-9|all] (8)

clear/spots <callsign> [input] [0-9|all] Clear a spot filter line

A sysop can clear an input or normal output filter for a user or thenode_default or user_default.

11.23 clear/spots [0-9|all] (0)

clear/spots [0-9|all] Clear a spot filter line

This command allows you to clear (remove) a line in a spot filter or to remove the whole filter.If you have a filter:-


  acc/spot 1 on hf/cw  acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

and you say:-


  clear/spot 1

you will be left with:-


  acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

If you do:


  clear/spot all

the filter will be completely removed.

11.24 clear/wcy <callsign> [input] [0-9|all] (8)

clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line

A sysop can clear an input or normal output filter for a user or thenode_default or user_default.

11.25 clear/wcy [1|all] (0)

clear/wcy [1|all] Clear a WCY filter line

This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.

11.26 clear/wwv <callsign> [input] [0-9|all] (8)

clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line

A sysop can clear an input or normal output filter for a user or thenode_default or user_default.

11.27 clear/wwv [1|all] (0)

clear/wwv [1|all] Clear a WWV filter line

This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.

11.28 connect <callsign> (5)

connect <callsign> Start a connection to another DX Cluster

Start a connection process that will culminate in a new connection to theDX cluster <callsign>. This process creates a new 'client' process which willuse the script in /spider/connect/<callsign> to effect the 'chat' exchangenecessary to traverse the network(s) to logon to the cluster <callsign>.

11.29 dbavail (0)

dbavail Show a list of all the Databases in the system

Title says it all really, this command lists all the databases definedin the system. It is also aliased to SHOW/COMMAND.

11.30 dbshow <dbname> <key> (0)

dbshow <dbname> <key> Display an entry, if it exists, in a database

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 fileso that users can use the more familiar AK1A style of enquiry such as:


  SH/BUCK G1TLH

but if he hasn't and the database really does exist (use DBAVAIL orSHOW/COMMAND to find out) you can do the same thing with:


  DBSHOW buck G1TLH

11.31 directory (0)

directory List messages

11.32 directory <from>-<to> (0)

directory <from>-<to> List messages <from> message <to> message

List the messages in the messages directory.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.You can use shell escape characters such as '*' and '?' in the <call>fields.You can combine some of the various directory commands together eg:-


   DIR TO G1TLH 5


   DIR SUBJECT IOTA 200-250

You can abbreviate all the commands to one letter and use ak1a syntax:-


   DIR/T G1* 10   DIR/S QSL 10-100 5

11.33 directory <nn> (0)

directory <nn> List last <nn> messages

11.34 directory all (0)

directory all List all messages

11.35 directory from <call> (0)

directory from <call> List all messages from <call>

11.36 directory new (0)

directory new List all new messages

11.37 directory own (0)

directory own List your own messages

11.38 directory subject <string> (0)

directory subject <string> List all messages with <string> in subject

11.39 directory to <call> (0)

directory to <call> List all messages to <call>

11.40 directory- (5)

directory-

Sysops can see all users' messages.

11.41 disconnect <call> [<call> ...] (8)

disconnect <call> [<call> ...] Disconnect a user or cluster

Disconnect any <call> connected locally

11.42 dx [by <call>] <freq> <call> <remarks> (0)

dx [by <call>] <freq> <call> <remarks> Send a DX spot

This is how you send a DX Spot to other users. You can, in fact, nowenter the <freq> and the <call> either way round.


   DX FR0G 144.600   DX 144.600 FR0G   DX 144600 FR0G

will all give the same result. You can add some remarks to the endof the command and they will be added to the spot.


   DX FR0G 144600 this is a test

You can credit someone else by saying:-


   DX by G1TLH FR0G 144.600 he isn't on the cluster

The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

11.43 echo <line> (0)

echo <line> Echo the line to the output

This command is useful in scripts and so forth for printing theline that you give to the command to the output. You can use thisin user_default scripts and the SAVE command for titling and so forthThe script will interpret certain standard "escape" sequences as follows:-


  \t - becomes a TAB character (0x09 in ascii)  \a - becomes a BEEP character (0x07 in ascii)  \n - prints a new line

So the following example:-


  echo GB7DJK is a dxcluster

produces:-


  GB7DJK is a dxcluster

on the output. You don't need a \n on the end of the line you want to send.A more complex example:-


  echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard

produces:-


  GB7DJK          g1tlh   Dirk          g3xvf   Richard

on the output.

11.44 filtering... (0)

filtering... Filtering things in DXSpider

There are a number of things you can filter in the DXSpider system. Theyall use the same general mechanism.In general terms you can create a 'reject' or an 'accept' filter whichcan have up to 10 lines in it. You do this using, for example:-


  accept/spots .....  reject/spots .....

where ..... are the specific commands for that type of filter. Thereare filters for spots, wwv, announce, wcy and (for sysops)connects. See each different accept or reject command reference formore details.There is also a command to clear out one or more lines in a filter andone to show you what you have set. They are:-


  clear/spots 1  clear/spots all

and


  show/filter

There is clear/xxxx command for each type of filter.For now we are going to use spots for the examples, but you can applythe principles to all types of filter.There are two main types of filter 'accept' or 'reject'; which you usedepends entirely on how you look at the world and what is leastwriting to achieve what you want. Each filter has 10 lines (of anylength) which are tried in order. If a line matches then the actionyou have specified is taken (ie reject means ignore it and acceptmeans gimme it).The important thing to remember is that if you specify a 'reject'filter (all the lines in it say 'reject/spots' (for instance)) then ifa spot comes in that doesn't match any of the lines then you will getit BUT if you specify an 'accept' filter then any spots that don'tmatch are dumped. For example if I have a one line accept filter:-


  accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

then automatically you will ONLY get VHF spots from or to CQ zones 1415 and 16. If you set a reject filter like:


  reject/spots on hf/cw

Then you will get everything EXCEPT HF CW spots, If you am interested in IOTAand will work it even on CW then you could say:-


  reject/spots on hf/cw and not info iota

But in that case you might only be interested in iota and say:-


  accept/spots not on hf/cw or info iota

which is exactly the same. You should choose one or the other untilyou are confortable with the way it works. Yes, you can mix them(actually you can have an accept AND a reject on the same line) butdon't try this at home until you can analyse the results that you getwithout ringing up the sysop for help.Another useful addition now is filtering by US state


  accept/spots by_state VA,NH,RI,ME

You can arrange your filter lines into logical units, either for yourown understanding or simply convenience. I have one set frequently:-


  reject/spots 1 on hf/cw  reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)

What this does is to ignore all HF CW spots (being a class B I can'tread any CW and couldn't possibly be interested in HF :-) and alsorejects any spots on VHF which don't either originate or spot someonein Europe.This is an exmaple where you would use the line number (1 and 2 inthis case), if you leave the digit out, the system assumes '1'. Digits'0'-'9' are available.You can leave the word 'and' out if you want, it is implied. You canuse any number of brackets to make the 'expression' as you wantit. There are things called precedence rules working here which meanthat you will NEED brackets in a situation like line 2 because,without it, will assume:-


  (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16

annoying, but that is the way it is. If you use OR - usebrackets. Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and by_zone'.If you want to alter your filter you can just redefine one or morelines of it or clear out one line. For example:-


  reject/spots 1 on hf/ssb


  clear/spots 1

To remove the filter in its entirty:-


  clear/spots all

There are similar CLEAR commands for the other filters:-


  clear/announce  clear/wcy  clear/wwv

ADVANCED USERS:-Once you are happy with the results you get, you may like to experiment. my example that filters hf/cw spots and accepts vhf/uhf spots from EUcan be written with a mixed filter, eg:


  rej/spot on hf/cw  acc/spot on 0/30000  acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)

each filter slot actually has a 'reject' slot and an 'accept'slot. The reject slot is executed BEFORE the accept slot.It was mentioned earlier that after a reject test that doesn't match,the default for following tests is 'accept', the reverse is true for'accept'. In the example what happens is that the reject is executedfirst, any non hf/cw spot is passed to the accept line, which letsthru everything else on HF.The next filter line lets through just VHF/UHF spots from EU.

11.45 forward/latlong <node_call> (8)

forward/latlong <node_call> Send latitude and longitude information to another cluster

This command sends all the latitude and longitude information that yourcluster is holding against callsigns. One advantage of recieving thisinformation is that more locator information is held by you. Thismeans that more locators are given on the DX line assuming you haveSET/DXGRID enabled. This could be a LOT of information though, soit is not recommended on slow links.

11.46 forward/opernam <call> (1)

forward/opernam <call> Send out information on this <call> to all clusters

This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.

11.47 help (0)

help The HELP Command

HELP is available for a number of commands. The syntax is:-


  HELP <cmd>

Where <cmd> is the name of the command you want help on.All commands can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE can be shortened to AN and so on.Look at the APROPOS <string> command which will search the help databasefor the <string> you specify and give you a list of likely commandsto look at with HELP.

11.48 init <node> (5)

init <node> Re-initialise a link to an AK1A compatible node

This command attempts to re-initialise a link to a (usually) AK1A nodethat has got confused, usually by a protocol loop of some kind. It maywork - but you usually will be better off simply disconnecting it (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F <yournode>).Best of luck - you will need it.

11.49 kill (5)

kill

As a sysop you can kill any message on the system.

11.50 kill <from msgno>-<to msgno> (0)

kill <from msgno>-<to msgno> Delete a range of messages

11.51 kill <from>-<to> (5)

kill <from>-<to> Remove a range of messages from the system

11.52 kill <msgno> [<msgno..] (0)

kill <msgno> [<msgno..] Delete a message from the local system

11.53 kill <msgno> [<msgno> ...] (0)

kill <msgno> [<msgno> ...] Remove or erase a message from the system

You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.

11.54 kill expunge <msgno> [<msgno..] (6)

kill expunge <msgno> [<msgno..] Expunge a message

Deleting a message using the normal KILL commands only marks that messagefor deletion. The actual deletion only happens later (usually two days later).The KILL EXPUNGE command causes the message to be truly deleted more or lessimmediately.It otherwise is used in the same way as the KILL command.

11.55 kill from <call> (5)

kill from <call> Remove all messages from a callsign

11.56 kill full <msgno> [<msgno..] (5)

kill full <msgno> [<msgno..] Delete a message from the whole cluster

Delete a message from the local system. You will only be able todelete messages that you have originated or been sent (unless you arethe sysop).


  KILL 1234-1255

Will delete all the messages that you own between msgnos 1234 and 1255.


  KILL from g1tlh

will delete all the messages from g1tlh (if you are g1tlh). Similarly:


  KILL to g1tlh

will delete all messages to g1tlh.


  KILL FULL 1234

will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!

11.57 kill full <msgno> [<msgno] (5)

kill full <msgno> [<msgno] Remove a message from the entire cluster

Remove this message from the entire cluster system as well as your node.

11.58 kill to <call> (5)

kill to <call> Remove all messages to a callsign

11.59 kill from <regex> (0)

kill from <regex> Delete messages FROM a callsign or pattern

11.60 kill to <regex> (0)

kill to <regex> Delete messages TO a callsign or pattern

11.61 links (0)

links Show which nodes is physically connected

This is a quick listing that shows which links are connected andsome information about them. See WHO for a list of all connections.

11.62 load/keps (5)

load/keps Load new keps data

11.63 load/keps [nn] (5)

load/keps [nn] Load new keps data from message

If there is no message number then reload the current Keps data fromthe Keps.pm data file. You create this file by running


 /spider/perl/convkeps.pl <filename>

on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, runconvkeps.pl on it and then load the data, all in one step.These messages are sent to ALL by GB7DJK (and others) from time to time.

11.64 merge <node> [<no spots>/<no wwv>] (5)

merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV

MERGE allows you to bring your spot and wwv database up to date. By defaultit 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 appendedto your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

11.65 pc <call> <text> (8)

pc <call> <text> Send arbitrary text to a connected callsign

Send some arbitrary text to a locally connected callsign. Noprocessing is done on the text. This command allows you to send PCProtocol to unstick things if problems arise (messages get stucketc). eg:-


   pc gb7djk PC33^GB7TLH^GB7DJK^400^


   pc G1TLH Try doing that properly!!!

Send any text you like to the callsign requested. This is used mainly to sendPC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user butwithout any processing, added of "from <blah> to <blah" or whatever.

11.66 ping <node call> (1)

ping <node call> Check the link quality between nodes

This command allows you to send a frame to another cluster node onthe network and get a return frame. The time it takes to do thisis a good indication of the quality of the link. The actual timeit takes is output to the console in seconds.Any visible cluster node can be PINGed.

11.67 rcmd <node call> <cmd> (1)

rcmd <node call> <cmd> Send a command to another DX Cluster

This command allows you to send nearly any command to another DX Clusternode that is connected to the system. Whether you get any output is dependant on a) whether the other system knowsthat the node callsign of this cluster is in fact a node b) whether theother system is allowing RCMDs from this node and c) whether you havepermission to send this command at all.

11.68 read (0)

read Read the next unread personal message addressed to you

11.69 read <msgno> (0)

read <msgno> Read the specified message

You can read any messages that are sent as 'non-personal' and also anymessage either sent by or sent to your callsign.

11.70 read- (5)

read-

As a sysop you may read any message on the system

11.71 reject (0)

reject Set a filter to reject something

Create a filter to reject somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.

11.72 reject/announce <call> [input] [0-9] <pattern> (8)

reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  reject/ann by G,M,2  reject/ann input node_default by G,M,2  reject/ann user_default by G,M,2

11.73 reject/announce [0-9] <pattern> (0)

reject/announce [0-9] <pattern> Set a 'reject' filter line for announce

Create an 'reject this announce' line for a filter. A reject filter line means that if the announce matches this filter it ispassed onto the user. See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-


  info <string>            eg: iota or qsl  by <prefixes>            eg: G,M,2           origin <prefixes>  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  origin_state <states>                eg: VA,NH,RI,ME  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  by_state <states>                eg: VA,NH,RI,ME  channel <prefixes>  wx 1                     filter WX announces  dest <prefixes>          eg: 6MUK,WDX      (distros)

some examples:-


  rej/ann by_zone 14,15,16 and not by G,M,2

You can use the tag 'all' to reject everything eg:


  rej/ann all

but this probably for advanced users...

11.74 reject/route <call> [0-9] <pattern> (8)

reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing

Create an 'reject this routing PC Protocol' line for a filter. 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:-


  call <prefixes>        the callsign of the thingy  call_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  call_itu <prefixes or numbers>     or: G,GM,GW  call_zone <prefixes or numbers>  call_state <states>                eg: VA,NH,RI,ME  origin <prefixes>      really the interface it came in on  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  origin_state <states>                eg: VA,NH,RI,ME

some examples:-


  rej/route gb7djk call_dxcc 61,38 (everything except  UK+EIRE nodes)

You can use the tag 'all' to reject everything eg:


  rej/route all     (equiv to [very] restricted mode)

as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

11.75 reject/spots <call> [input] [0-9] <pattern> (8)

reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  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

11.76 reject/spots [0-9] <pattern> (0)

reject/spots [0-9] <pattern> Set a 'reject' filter line for spots

Create a 'reject this spot' line for a filter. A reject filter line means that if the spot matches this filter it isdumped (not passed on). See HELP FILTERING for more info. Please read thisto understand how filters work - it will save a lot of grief later on.You can use any of the following things in this line:-


  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 <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  call_itu <prefixes or numbers>     or: G,GM,GW  call_zone <prefixes or numbers>  call_state <states>                eg: VA,NH,RI,ME  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  by_state <states>                eg: VA,NH,RI,ME  origin <prefixes>  channel <prefixes>

'call' means the callsign that has spotted 'by' whoever.For frequencies, you can use any of the band names defined inSHOW/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 gettoo hung up about that)some examples:-


  rej/spot 1 on hf  rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)

You can use the tag 'all' to reject everything eg:


  rej/spot 3 all

but this probably for advanced users...

11.77 reject/wcy <call> [input] [0-9] <pattern> (8)

reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  reject/wcy gb7djk all

11.78 reject/wcy [0-9] <pattern> (0)

reject/wcy [0-9] <pattern> set a 'reject' WCY filter

It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-


  by <prefixes>            eg: G,M,2           origin <prefixes>  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  channel <prefixes>

11.79 reject/wwv <call> [input] [0-9] <pattern> (8)

reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version

This version allows a sysop to set a filter for a callsign as well as thedefault for nodes and users eg:-


  reject/wwv db0sue-7 1 by_zone 4  reject/wwv node_default all


  reject/wwv user_default by W

11.80 reject/wwv [0-9] <pattern> (0)

reject/wwv [0-9] <pattern> set a 'reject' WWV filter

It is unlikely that you will want to do this, but if you do then you canfilter on the following fields:-


  by <prefixes>            eg: G,M,2           origin <prefixes>  origin_dxcc <prefixes or numbers>    eg: 61,62 (from eg: sh/pre G)  origin_itu <prefixes or numbers>     or: G,GM,GW  origin_zone <prefixes or numbers>  by_dxcc <prefixes or numbers>  by_itu <prefixes or numbers>  by_zone <prefixes or numbers>  channel <prefixes>

for example


  reject/wwv by_zone 14,15,16

is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information.

11.81 reply (0)

reply Reply (privately) to the last message that you have read

11.82 reply <msgno> (0)

reply <msgno> Reply (privately) to the specified message

11.83 reply b <msgno> (0)

reply b <msgno> Reply as a Bulletin to the specified message

11.84 reply noprivate <msgno> (0)

reply noprivate <msgno> Reply as a Bulletin to the specified message

11.85 reply rr <msgno> (0)

reply rr <msgno> Reply to the specified message with read receipt

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 SENDfor further details)

11.86 send <call> [<call> ...] (0)

send <call> [<call> ...] Send a message to one or more callsigns

11.87 send copy <msgno> <call> (0)

send copy <msgno> <call> Send a copy of a message to someone

11.88 send noprivate <call> (0)

send noprivate <call> Send a message to all stations

All the SEND commands will create a message which will be sent either toan individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that isit will mark the message as personal and send it to the cluster node thatthat callsign is connected to. If the <call> you have specified is in facta known bulletin category on your node (eg: ALL) then the message shouldautomatically become a bulletin.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:-


  SEND RR COPY 123 PRIVATE G1TLH G0RDI

which should send a copy of message 123 to G1TLH and G0RDI and you willreceive 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 PRIVATEThe system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern clustersoftware should accept more.You will now be prompted to start entering your text. You finish the message by entering '/EX' on a new line. For instance:


  ...  bye then Jim  73 Dirk  /ex

If you have started a message and you don't want to keep it then youcan abandon the message with '/ABORT' on a new line, like:-


  line 1  line 2  oh I just can't be bothered with this  /abort

If you abort the message it will NOT be sent.When you are entering the text of your message, most normal output (suchas DX announcements and so on are suppressed and stored for latter display(upto 20 such lines are stored, as new ones come along, so the oldestlines are dropped).Also, you can enter normal commands commands (and get the output immediately) whilst in the middle of a message. You do this by typingthe command preceeded by a '/' character on a new line, so:-


  /dx g1tlh 144010 strong signal

Will issue a dx annoucement to the rest of the cluster. Also, you can add the output of a command to your message by preceeding the command with '//', thus :-


  //sh/vhftable

This will show YOU the output from SH/VHFTABLE and also store it in themessage. You can carry on with the message until you are ready to send it.

11.89 send private <call> (0)

send private <call> Send a personal message

11.90 send rr <call> (0)

send rr <call> Send a message and ask for a read receipt

11.91 set/address <your address> (0)

set/address <your address> Record your postal address

11.92 set/announce (0)

set/announce Allow announce messages to come out on your terminal

11.93 set/anntalk (0)

set/anntalk Allow talk like announce messages on your terminal

11.94 set/arcluster <call> [<call>..] (5)

set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node

11.95 set/baddx <call>.. (8)

set/baddx <call>.. Stop callsigns in a dx spot being propagated

11.96 set/badnode <call>.. (8)

set/badnode <call>.. Stop spots from this node being propagated

11.97 set/badspotter <call>.. (8)

set/badspotter <call>.. Stop spots from this callsign being propagated

11.98 set/badword <word>.. (8)

set/badword <word>.. Stop things with this word being propagated

11.99 set/bbs <call> [<call>..] (5)

set/bbs <call> [<call>..] Make the callsign a BBS

11.100 set/beep (0)

set/beep Add a beep to DX and other messages on your terminal

11.101 set/clx <call> [<call>..] (5)

set/clx <call> [<call>..] Make the callsign an CLX node

11.102 set/dx (0)

set/dx Allow DX messages to come out on your terminal

11.103 set/dxgrid (0)

set/dxgrid Allow QRA Grid Squares on the end of DX announcements

11.104 set/dxnet <call> [<call>..] (5)

set/dxnet <call> [<call>..] Make the callsign an DXNet node

11.105 set/dxstate (0)

set/dxstate Allow US State info on the end of DX announcements

11.106 set/echo (0)

set/echo Make the cluster echo your input

11.107 set/email <email> ... (0)

set/email <email> ... Set email address(es) and forward your personals

11.108 set/here (0)

set/here Tell the system you are present at your terminal

11.109 set/homenode <node> (0)

set/homenode <node> Set your normal cluster callsign

Tell the cluster system where you normally connect to. Any Messages sentto you will normally find their way there should you not be connected.eg:-


  SET/HOMENODE gb7djk

11.110 set/hops <call> ann|spots|route|wwv|wcy <n> (8)

set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count

11.111 set/language <lang> (0)

set/language <lang> Set the language you want to use

You can select the language that you want the cluster to use. Currentlythe languages available are en (English), de (German), es (Spanish) and nl (Dutch).

11.112 set/location <lat & long> (0)

set/location <lat & long> Set your latitude and longitude

11.113 set/logininfo (0)

set/logininfo Inform when a station logs in locally

11.114 set/name <your name> (0)

set/name <your name> Set your name

Tell the system what your name is eg:-


  SET/NAME Dirk

11.115 set/node <call> [<call>..] (5)

set/node <call> [<call>..] Make the callsign an AK1A cluster

Tell the system that the call(s) are to be treated as AK1A cluster andfed PC Protocol rather normal user commands.

11.116 set/obscount <count> <call> (8)

set/obscount <count> <call> Set the 'pump-up' obscelence PING counter

From 1.35 onwards neighbouring nodes are pinged at regular intervals (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'counter which is decremented on every outgoing ping and then reset tothe 'obscount' value on every incoming ping. The default value of thisparameter 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 beforewhat would be the third attempt, that node is disconnected.If a ping is heard then the obscount is reset to the full value. Usingdefault values, if a node has not responded to a ping within 15 minutes,it is disconnected.You can set this parameter between 1 and 9.It is STRONGLY recommended that you don't change the default.

11.117 set/page <lines per page> (0)

set/page <lines per page> Set the lines per page

Tell the system how many lines you wish on a page when the number of lineof output from a command is more than this. The default is 20. Setting itexplicitly to 0 will disable paging.


  SET/PAGE 30  SET/PAGE 0

The setting is stored in your user profile.

11.118 set/password (0)

set/password Set your own password

This command only works for a 'telnet' user (currently). It willonly work if you have a password already set. This initial passwordcan only be set by the sysop.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 youget it right). You may or may not see the data echoed on the screenas you type, depending on the type of telnet client you have.

11.119 set/prompt <string> (0)

set/prompt <string> Set your prompt to <string>

11.120 set/qra <locator> (0)

set/qra <locator> Set your QRA Grid locator

Tell the system what your QRA (or Maidenhead) locator is. If you have notdone a SET/LOCATION then your latitude and longitude will be set roughlycorrectly (assuming your locator is correct ;-). For example:-


  SET/QRA JO02LQ

11.121 set/qth <your qth> (0)

set/qth <your qth> Set your QTH

Tell the system where you are. For example:-


  SET/QTH East Dereham, Norfolk

11.122 set/spider <call> [<call>..] (5)

set/spider <call> [<call>..] Make the callsign an DXSpider node

Tell the system that the call(s) are to be treated as DXSpider node andfed new style DX Protocol rather normal user commands.

11.123 set/talk (0)

set/talk Allow TALK messages to come out on your terminal

11.124 set/wcy (0)

set/wcy Allow WCY messages to come out on your terminal

11.125 set/wwv (0)

set/wwv Allow WWV messages to come out on your terminal

11.126 set/wx (0)

set/wx Allow WX messages to come out on your terminal

11.127 show/baddx (1)

show/baddx Show all the bad dx calls in the system

Display all the bad dx callsigns in the system, see SET/BADDXfor more information.

11.128 show/badnode (1)

show/badnode Show all the bad nodes in the system

Display all the bad node callsigns in the system, see SET/BADNODEfor more information.

11.129 show/badspotter (1)

show/badspotter Show all the bad spotters in the system

Display all the bad spotter's callsigns in the system, see SET/BADSPOTTERfor more information.

11.130 show/badword (1)

show/badword Show all the bad words in the system

Display all the bad words in the system, see SET/BADWORDfor more information.

11.131 show/configuration [<node>] (0)

show/configuration [<node>] Show all the nodes and users visible

This command allows you to see all the users that can be seenand the nodes to which they are connected.This command is normally abbreviated to: sh/cNormally, the list returned will be just for the nodes from your country (because the list otherwise will be very long).


  SH/C ALL

will produce a complete list of all nodes. BE WARNED: the list that is returned can be VERY longIt is possible to supply a node or part of a prefix and you will get a list of the users for that node or list of nodes starting withthat prefix.


  SH/C GB7DJK


  SH/C SK

11.132 show/configuration/node (0)

show/configuration/node Show all the nodes connected locally

Show all the nodes connected to this node.

11.133 show/connect (1)

show/connect Show all the active connections

This command shows information on all the active connections known tothe node. This command gives slightly more information than WHO.

11.134 show/date [<prefix>|<callsign>] (0)

show/date [<prefix>|<callsign>] Show the local time

This is very nearly the same as SHOW/TIME, the only difference the formatof the date string if no arguments are given.If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.

11.135 show/db0sdx <callsign> (0)

show/db0sdx <callsign> Show QSL infomation from DB0SDX database

This command queries the DB0SDX QSL server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qslinfo.de.See also SHOW/QRZ, SHOW/WM7D.

11.136 show/dx (0)

show/dx Interrogate the spot database

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 commands in very nearlyany order to the basic SHOW/DX command, they are:-


 on <band>       - eg 160m 20m 2m 23cm 6mm on <region>     - eg hf vhf uhf shf      (see SHOW/BANDS) on <from>/<to>  - eg 1000/4000 14000-30000  (in Khz)    <from>-<to>


 <number>        - the number of spots you want <from>-<to>     - <from> spot no <to> spot no in the selected list <from>/<to>


 <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     <from>/<to>


 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.


 dxcc            - treat the prefix as a 'country' and look for spots                   from that country regardless of actual prefix.                   eg dxcc oq2


                   You can also use this with the 'by' keyword so                    eg by W dxcc


 e.g.


   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   SH/DX dxcc oq2   SH/DX dxcc oq2 by w dxcc

11.137 show/dxcc <prefix> (0)

show/dxcc <prefix> Interrogate the spot database by country

This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it isand then displays all the spots as per SH/DX for that country.This is now an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this command. e.g.


   SH/DXCC G   SH/DXCC W on 20m iota

This can be done with the SHOW/DX command like this:-


   SH/DX dxcc g   SH/DX dxcc w on 20m iota

11.138 show/dxstats [days] [date] (0)

show/dxstats [days] [date] Show the DX Statistics

Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).

11.139 show/files [<filearea> [<string>]] (0)

show/files [<filearea> [<string>]] List the contents of a filearea

SHOW/FILES on its own will show you a list of the various fileareasavailable on the system. To see the contents of a particular filearea type:-


   SH/FILES <filearea>

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 astring to see a selection of files in a filearea eg:-


   SH/FILES bulletins arld*

See also TYPE - to see the contents of a file.

11.140 show/filter (0)

show/filter Show the contents of all the filters you have set

Show the contents of all the filters that are set. This command displaysall the filters set - for all the various categories.

11.141 show/hfstats [days] [date] (0)

show/hfstats [days] [date] Show the HF DX Statistics

Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).

11.142 show/hftable [days] [date] [prefix ...] (0)

show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table

Show the HF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a <date> (default: today).If there are no prefixes then it will show the table for your country.Remember that some countries have more than one "DXCC country" in them(eg G :-), to show them (assuming you are not in G already which isspecially treated in the code) you must list all the relevant prefixes


  sh/hftable g gm gd gi gj gw gu

Note that the prefixes are converted into country codes so you don't haveto list all possible prefixes for each country.If you want more or less days than the default simply include thenumber you require:-


  sh/hftable 20 pa

If you want to start at a different day, simply add the date in some recognizable form:-


  sh/hftable 2 25nov02  sh/hftable 2 25-nov-02   sh/hftable 2 021125   sh/hftable 2 25/11/02

This will show the stats for your DXCC for that CQWW contest weekend. You can specify either prefixes or full callsigns (so you can see how youdid against all your mates). You can also say 'all' which will then printthe worldwide statistics.


  sh/hftable all

11.143 show/hops <call> [ann|spots|route|wcy|wwv] (8)

show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a node

This command shows the hop counts set up for a node. You can specifywhich category you want to see. If you leave the category out then all the categories will be listed.

11.144 show/isolate (1)

show/isolate Show list of ISOLATED nodes

11.145 show/log [<callsign>] (8)

show/log [<callsign>] Show excerpts from the system log

This command outputs a short section of the system log. On its ownit will output a general logfile. With the optional callsign it willshow output from the log associated with that callsign.

11.146 show/moon [ndays] [<prefix>|<callsign>] (0)

show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times

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 thoselocations.If you don't specify any prefixes or callsigns, it will show the times foryour QTH (assuming you have set it with either SET/LOCATION or SET/QRA),together with the current azimuth and elevation.In addition, it will show the illuminated fraction of the moons disk.If all else fails it will show the Moonrise and set times for the nodethat you are connected to. For example:-


  SH/MOON  SH/MOON G1TLH W5UN

You can also use this command to see into the past or the future, soif you want to see yesterday's times then do:-


  SH/MOON -1

or in three days time:-


  SH/MOON +3 W9

Upto 366 days can be checked both in the past and in the future.Please note that the rise and set times are given as the UT times of rise and set on the requested UT day.

11.147 show/muf <prefix> [<hours>][long] (0)

show/muf <prefix> [<hours>][long] Show the likely propagation to a prefix

This command allow you to estimate the likelihood of you contactinga station with the prefix you have specified. The output assumes a modestpower of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)The result predicts the most likely operating frequencies and signallevels for high frequency (shortwave) radio propagation paths onspecified days of the year and hours of the day. It is most useful forpaths between 250 km and 6000 km, but can be used with reduced accuracyfor paths shorter or longer than this.The command uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to predict the MUF given the predicted flux, day of the year,hour of the day and geographic coordinates of the transmitter andreceiver. This routine is reasonably accurate for the purposes here,with a claimed RMS error of 3.8 MHz, but much smaller and less complexthan the programs used by major shortwave broadcasting organizations,such as the Voice of America.The command will display some header information detailing itsassumptions, together with the locations, latitude and longitudes andbearings. 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 whichthe system thinks there is a likelihood of a circuit it prints a value.The value is currently a likely S meter reading based on the conventional6dB / S point scale. If the value has a '+' appended it means that it is1/2 an S point stronger. If the value is preceeded by an 'm' it means thatthere is likely to be much fading and by an 's' that the signal is likelyto be noisy. By default SHOW/MUF will show the next two hours worth of data. Youcan specify anything up to 24 hours worth of data by appending the no ofhours required after the prefix. For example:-


  SH/MUF W

produces:


  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

indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3).inputing:-


  SH/MUF W 24

will get you the above display, but with the next 24 hours worth ofpropagation data.


  SH/MUF W L 24  SH/MUF W 24 Long

Gives you an estimate of the long path propagation characterics. Itshould be noted that the figures will probably not be very useful, norterrible accurate, but it is included for completeness.

11.148 show/newconfiguration [<node>] (0)

show/newconfiguration [<node>] Show all the nodes and users visible

This command allows you to see all the users that can be seenand the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication ofany routes that might be present It also uses a different formatwhich may not take up quite as much space if you don't have anyloops.BE WARNED: the list that is returned can be VERY long

11.149 show/newconfiguration/node (0)

show/newconfiguration/node Show all the nodes connected locally

Show all the nodes connected to this node in the new format.

11.150 show/node [<callsign> ...] (1)

show/node [<callsign> ...] Show the type and version number of nodes

Show the type and version (if connected) of the nodes specified on thecommand line. If no callsigns are specified then a sorted list of allthe non-user callsigns known to the system will be displayed.

11.151 show/prefix <callsign> (0)

show/prefix <callsign> Interrogate the prefix database

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 countrytogether with the internal country no, the CQ and ITU regions. See also SHOW/DXCC

11.152 show/program (5)

show/program Show the locations of all the included program modules

Show the name and location where every program module was load from. Thisis useful for checking where you think you have loaded a .pm file from.

11.153 show/qra <lat> <long> (0)

show/qra <lat> <long> Convert lat/long to a QRA Grid locator

This is a multipurpose command that allows you either to calculate thedistance and bearing between two locators or (if only one locator isgiven on the command line) the distance and beraing from your stationto the locator. For example:-


 SH/QRA IO92QL  SH/QRA JN06 IN73

The first example will show the distance and bearing to the locator fromyourself, the second example will calculate the distance and bearing fromthe first locator to the second. You can use 4 or 6 character locators.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, forexample:-


 SH/QRA 52 41 N 0 58 E

11.154 show/qra <locator> [<locator>] (0)

show/qra <locator> [<locator>] Show distance between QRA Grid locators

11.155 show/qrz <callsign> (0)

show/qrz <callsign> Show any callbook details on a callsign

This command queries the QRZ callbook server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.

11.156 show/route <callsign> ... (0)

show/route <callsign> ... Show the route to the callsign

This command allows you to see to which node the callsigns specified areconnected. It is a sort of inverse sh/config.


 sh/route n2tly

11.157 show/satellite <name> [<hours> <interval>] (0)

show/satellite <name> [<hours> <interval>] Show tracking data

Show the tracking data from your location to the satellite of your choicefrom now on for the next few hours.If you use this command without a satellite name it will display a listof all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passesthat start and finish 5 degrees below the horizon. As default it willgive information for the next three hours for every five minute period.You can alter the number of hours and the step size, within certain limits. Each pass in a period is separated with a row of '-----' charactersSo for example:-


 SH/SAT AO-10  SH/SAT FENGYUN1 12 2

11.158 show/station all [<regex>] (6)

show/station all [<regex>] Show list of users in the system

11.159 show/station [<callsign> ..] (0)

show/station [<callsign> ..] Show information about a callsign

Show the information known about a callsign and whether (and where)that callsign is connected to the cluster.


  SH/ST G1TLH

If no callsign is given then show the information for yourself.

11.160 show/sun [ndays] [<prefix>|<callsign>] (0)

show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times

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 thoselocations.If you don't specify any prefixes or callsigns, it will show the times foryour QTH (assuming you have set it with either SET/LOCATION or SET/QRA),together with the current azimuth and elevation.If all else fails it will show the sunrise and set times for the nodethat you are connected to. For example:-


  SH/SUN  SH/SUN G1TLH K9CW ZS

You can also use this command to see into the past or the future, soif you want to see yesterday's times then do:-


  SH/SUN -1

or in three days time:-


  SH/SUN +3 W9

Upto 366 days can be checked both in the past and in the future.Please note that the rise and set times are given as the UT times of rise and set on the requested UT day.

11.161 show/time [<prefix>|<callsign>] (0)

show/time [<prefix>|<callsign>] Show the local time

If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.

11.162 show/usdb [call ..] (0)

show/usdb [call ..] Show information held on the FCC Call database

Show the City and State of a Callsign held on the FCC database ifhis is being run on this system, eg:-


  sh/usdb k1xx

11.163 show/vhfstats [days] [date] (0)

show/vhfstats [days] [date] Show the VHF DX Statistics

Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).

11.164 show/vhftable [days] [date] [prefix ...] (0)

show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table

Show the VHF DX Spotter table for the list of prefixes for the last <days> no of days (default is 31), starting from a date (default: today).If there are no prefixes then it will show the table for your country.Remember that some countries have more than one "DXCC country" in them(eg G :-), to show them (assuming you are not in G already which isspecially treated in the code) you must list all the relevant prefixes


  sh/vhftable g gm gd gi gj gw gu


  sh/vhftable 20 pa

If you want to start at a different day, simply add the date in some recognizable form:-


  sh/vhftable 2 25nov02  sh/vhftable 2 25-nov-02   sh/vhftable 2 021125   sh/vhftable 2 25/11/02


  sh/vhftable all

11.165 show/wcy (0)

show/wcy Show last 10 WCY broadcasts

11.166 show/wcy <n> (0)

show/wcy <n> Show last <n> WCY broadcasts

Display the most recent WCY information that has been received by the system

11.167 show/wm7d <callsign> (0)

show/wm7d <callsign> Show callbook details on a US callsigns

This command queries the WM7D callbook server on the internetand returns any information available for that US callsign. This serviceis provided for users of this software by http://www.wm7d.net.See also SHOW/QRZ.

11.168 show/wwv (0)

show/wwv Show last 10 WWV broadcasts

11.169 show/wwv <n> (0)

show/wwv <n> Show last <n> WWV broadcasts

Display the most recent WWV information that has been received by the system

11.170 shutdown (5)

shutdown Shutdown the cluster

Shutdown the cluster and disconnect all the users

11.171 stat/channel [<callsign>] (5)

stat/channel [<callsign>] Show the status of a channel on the cluster

Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for.Only the fields that are defined (in perl term) will be displayed.

11.172 stat/db <dbname> (5)

stat/db <dbname> Show the status of a database

Show the internal status of a database descriptor.Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

11.173 stat/msg (1)

stat/msg Show the status of the message system

11.174 stat/msg <msgno> (1)

stat/msg <msgno> Show the status of a message

This command shows the internal status of a message and includes informationsuch as to whom it has been forwarded, its size, origin etc etc.If no message number is given then the status of the message system is displayed.

11.175 stat/route_node <callsign> (5)

stat/route_node <callsign> Show the data in a Route::Node object

11.176 stat/route_node all (5)

stat/route_node all Show list of all Route::Node objects

11.177 stat/route_user <callsign> (5)

stat/route_user <callsign> Show the data in a Route::User object

11.178 stat/route_user all (5)

stat/route_user all Show list of all Route::User objects

11.179 stat/user [<callsign>] (5)

stat/user [<callsign>] Show the full status of a user

Shows the full contents of a user record including all the secret flagsand stuff.Only the fields that are defined (in perl term) will be displayed.

11.180 sysop (0)

sysop Regain your privileges if you login remotely

The system automatically reduces your privilege level to that of anormal user if you login in remotely. This command allows you toregain your normal privilege level. It uses the normal system: fivenumbers are returned that are indexes into the character array that isyour assigned password (see SET/PASSWORD). The indexes start fromzero.You are expected to return a string which contains the charactersrequired in the correct order. You may intersperse those characterswith others to obscure your reply for any watchers. For example (andthese values are for explanation :-):


  password = 012345678901234567890123456789  > sysop  22 10 15 17 3

you type:-


 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573

They will all match. If there is no password you will still be offerednumbers but nothing will happen when you input a string. Any match iscase sensitive.

11.181 talk <call> > <node> [<text>] (0)

talk <call> > <node> [<text>] Send a text message to another station via a node

Send a short message to any other station that is visible on the clustersystem. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally.The second form of TALK is used when other cluster nodes are connectedwith restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster.If you know that G3JNB is likely to be present on GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users, then you would use thesecond form of the talk message.If you want to have a ragchew with someone you can leave the text messageout and the system will go into 'Talk' mode. What this means is that ashort 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 willgo to the station that you asked for. All the usual announcements, spots and so on will still come out on yourterminal.If you want to do something (such as send a spot) you preceed the normal command with a '/' character, eg:-


   /DX 14001 G1TLH What's a B class licensee doing on 20m CW?   /HELP talk

To leave talk mode type:

/EX

If you are in 'Talk' mode, there is an extention to the '/' command whichallows you to send the output to all the people you are talking to. You do with the '//' command. For example:-


  //sh/hftable

will send the hftable as you have it to all the people you are currently talking to.

11.182 talk <call> [<text>] (0)

talk <call> [<text>] Send a text message to another station

11.183 type <filearea>/<name> (0)

type <filearea>/<name> Look at the contents of a file in one of the fileareas

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


   TYPE bulletins/arld051

See also SHOW/FILES to see what fileareas are available and a list of content.

11.184 uncatchup <node call> all|[msgno> ...] (5)

uncatchup <node call> all|[msgno> ...] Unmark a message as sent

When you send messages the fact that you have forwarded it to another node is remembered so that it isn't sent again. When you have a new partnernode and you add their callsign to your /spider/msg/forward.pl file, alloutstanding non-private messages will be forwarded to them. This may wellbe ALL the non-private messages. You can prevent this by using these commmands:-


  catchup GB7DJK all  catchup GB7DJK 300 301 302 303 500-510

and to undo what you have just done:-


  uncatchup GB7DJK all  uncatchup GB7DJK 300 301 302 303 500-510

which will arrange for them to be forward candidates again.Order is not important.

11.185 unset/announce (0)

unset/announce Stop announce messages coming out on your terminal

11.186 unset/anntalk (0)

unset/anntalk Stop talk like announce messages on your terminal

The announce system on legacy cluster nodes is used as a talk substitute because the network is so poorly connected. If you:


  unset/anntalk

you will suppress several of these announces, you may miss the odd useful one as well, but you would probably miss them anyway in thewelter of useless ones.


  set/anntalk

allows you to see them again. This is the default.

11.187 unset/baddx <call>.. (8)

unset/baddx <call>.. Propagate a dx spot with this callsign again

Setting a word as 'baddx' will prevent spots with that word in the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going anyfurther. They will not be displayed and they will not be sent ontoother nodes.The word must be written in full, no wild cards are allowed eg:-


  set/baddx FORSALE VIDEO FR0G

To allow a word again, use the following command ...


  unset/baddx VIDEO

11.188 unset/badnode <call>.. (8)

unset/badnode <call>.. Allow spots from this node again

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 must be a full eg:-


  set/badnode K1TTT

will stop anything from K1TTT. If you want SSIDs as well then you mustenter them specifically.


  unset/badnode K1TTT

will allow spots from him again.Use with extreme care. This command may well be superceeded by FILTERing.

11.189 unset/badspotter <call>.. (8)

unset/badspotter <call>.. Allow spots from this callsign again

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


  set/badspotter VE2STN

will stop anything from VE2STN. This command will automaticallystop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsignas above or below.


  unset/badspotter VE2STN

will allow spots from him again.Use with extreme care. This command may well be superceded by FILTERing.

11.190 unset/badword <word>.. (8)

unset/badword <word>.. Propagate things with this word again

Setting a word as a 'badword' will prevent things like spots,announces or talks with this word in the the text part from going anyfurther. They will not be displayed and they will not be sent ontoother nodes.The word must be written in full, no wild cards are allowed eg:-


  set/badword annihilate annihilated annihilation

will stop anything with these words in the text.


  unset/badword annihilated

will allow text with this word again.

11.191 unset/beep (0)

unset/beep Stop beeps for DX and other messages on your terminal

11.192 unset/dx (0)

unset/dx Stop DX messages coming out on your terminal

11.193 unset/dxgrid (0)

unset/dxgrid Stop QRA Grid Squares on the end of DX announcements

A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. You can use this command to reset (or set)this feature.

11.194 unset/dxstate (0)

unset/dxstate Stop US State info on the end of DX announcements

If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's State will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID.Some user programs cannot cope with this. You can use this command to reset (or set) this feature.

11.195 unset/echo (0)

unset/echo Stop the cluster echoing your input

If you are connected via a telnet session, different implimentationsof telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this commandto change the setting appropriately. The setting is stored in your user profile.YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

11.196 unset/email (0)

unset/email Stop personal msgs being forwarded by email

If any personal messages come in for your callsign then you can usethese commands to control whether they are forwarded onto your emailaddress. To enable the forwarding do something like:-


  SET/EMAIL mike.tubby@somewhere.com

You can have more than one email address (each one separated by a space).Emails are forwarded to all the email addresses you specify.You can disable forwarding by:-


  UNSET/EMAIL

11.197 unset/here (0)

unset/here Tell the system you are absent from your terminal

11.198 unset/hops <call> ann|spots|route|wwv|wcy (8)

unset/hops <call> ann|spots|route|wwv|wcy Unset hop count

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.eg:


  set/hops gb7djk ann 10  set/hops gb7mbc spots 20

Set SHOW/HOPS for information on what is already set. This commandcreates a filter and works in conjunction with the filter system. You can unset the hops with command UNSET/HOPS. For example:-


  unset/hops gb7djk ann  unset/hops gb7mbc spots

11.199 unset/logininfo (0)

unset/logininfo Inform when a station logs out locally

11.200 unset/privilege (0)

unset/privilege Remove any privilege for this session

You can use this command to 'protect' this session from unauthoriseduse. If you want to get your normal privilege back you will need toeither logout and login again (if you are on a console) or use theSYSOP command.

11.201 unset/prompt (0)

unset/prompt Set your prompt back to default

This command will set your user prompt to exactly the string that you say. The point of this command to enable a user to interface to programsthat are looking for a specific prompt (or else you just want a differentfixed prompt).


  SET/PROMPT clx >

UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back tonormal.

Next Previous Contents