11. The DXSpider Command Reference

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)

  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 

  acc/ann by_state va,nh,ri,nh

  acc/ann all

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

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

  by = call  by_dxcc = call_dxcc 

  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>

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

  acc/spot 3 all

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

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>

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>

  accept/wwv by_zone 4

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

  blank - 

  blank abc

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 chat <group> <text> (0)

chat <group> <text> Chat or Conference to a group

It is now possible to JOIN a group and have network wide conferencing to thatgroup. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seemto work too well anyway.This system uses the existing ANN system and is compatible with both otherDXSpider nodes and AK1A clusters (they use ANN/<group>). You can be a member of as many "groups" as you want. To join a group type:-

  JOIN FOC    (where FOC is the group name)

  LEAVE FOC

  STAT/USER

  STAT/USER g1tlh

  CHAT FOC hello everyone

  CH #9000 hello I am back

11.19 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.20 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.21 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.22 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.23 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.24 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)

  clear/spot 1

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

  clear/spot all

11.25 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.26 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.27 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.28 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.29 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.30 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.31 dbcreate <name> (9)

dbcreate <name> Create a database entry

11.32 dbcreate <name> chain <name> [<name>..] (9)

dbcreate <name> chain <name> [<name>..] Create a chained database entry

11.33 dbcreate <name> cmd <dxspider command> (9)

dbcreate <name> cmd <dxspider command> make a local command available as a DB

DBCREATE allows you to define a database in the system. It doesn't actuallycreate anything, just defines it.The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'.You can define a local database with the first form of the command eg:

  DBCREATE oblast

  DBCREATE sdx_qsl chain sql_ad

  DBCREATE buckmaster remote gb7dxc

  DBCREATE qsl chain gb7dxc

  DBAVAIL (or it will have been aliased to SHOW/COMMAND)

  's' => [    ..    ..    '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',    ..    ..   ],

  SH/BUCK g1tlh

  DBCREATE dxqsl cmd show/dxqsl

11.34 dbcreate <name> remote <node> (9)

dbcreate <name> remote <node> Create a remote database entry

11.35 dbimport <dbname> <filename> (9)

dbimport <dbname> <filename> Import AK1A data into a database

If you want to import or update data in bulk to a database you can usethis command. It will either create or update entries into an existingdatabase. For example:-

  DBIMPORT oblast /tmp/OBLAST.FUL

11.36 dbremove <dbname> (9)

dbremove <dbname> Delete a database

DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:

  DBREMOVE oblast 

11.37 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

  DBSHOW buck G1TLH

11.38 debug (9)

debug Set the cluster program into debug mode

Executing this command will only have an effect if you are running the clusterin debug mode i.e.

        perl -d cluster.pl

11.39 delete/usdb <callsign> ... (9)

delete/usdb <callsign> ... Delete this user from the US State Database

This command will completely remove a one or more callsignsfrom the US States database.There is NO SECOND CHANCE.It goes without saying that you should use this command CAREFULLY!Note that these callsign may be re-instated by any weekly updates from the FCC.

11.40 delete/user <callsign> ... (9)

delete/user <callsign> ... Delete this user from the User Database

This command will completely remove a one or more users from the database.There is NO SECOND CHANCE.It goes without saying that you should use this command CAREFULLY!

11.41 demonstrate <call> <command> (9)

demonstrate <call> <command> Demonstrate a command to another user

This command is provided so that sysops can demonstrate commands to other users. It runs a command as though that user had typed it in andthen sends the output to that user, together with the command that caused it.

  DEMO g7brn sh/dx iota oc209  DEMO g1tlh set/here

11.42 directory (0)

directory List messages

11.43 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

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

11.44 directory <nn> (0)

directory <nn> List last <nn> messages

11.45 directory all (0)

directory all List all messages

11.46 directory from <call> (0)

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

11.47 directory new (0)

directory new List all new messages

11.48 directory own (0)

directory own List your own messages

11.49 directory subject <string> (0)

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

11.50 directory to <call> (0)

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

11.51 directory- (5)

directory-

Sysops can see all users' messages.

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

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

Disconnect any <call> connected locally

11.53 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 

   DX FR0G 144600 this is a test

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

11.54 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

  echo GB7DJK is a dxcluster

  GB7DJK is a dxcluster

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

  GB7DJK          g1tlh   Dirk          g3xvf   Richard

11.55 export <msgno> <filename> (9)

export <msgno> <filename> Export a message to a file

Export a message to a file. This command can only be executed on a localconsole with a fully privileged user. The file produced will be in a formready to be imported back into the cluster by placing it in the import directory (/spider/msg/import).This command cannot overwrite an existing file. This is to provide some measure of security. Any files written will owned by the same user as the main cluster, otherwise you can put the new files anywhere the cluster canaccess. For example:-

  EXPORT 2345 /tmp/a

11.56 export_users [<filename>] (9)

export_users [<filename>] Export the users database to ascii

Export the users database to a file in ascii format. If no filenameis given then it will export the file to /spider/data/user_asc.If the file already exists it will be renamed to <filename>.o. In factup to 5 generations of the file can be kept each one with an extra 'o' on thesuffix. BE WARNED: this will write to any file you have write access to. No check ismade on the filename (if any) that you specify.

11.57 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 .....

  clear/spots 1  clear/spots all

  show/filter

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

  reject/spots on hf/cw

  reject/spots on hf/cw and not info iota

  accept/spots not on hf/cw or info iota

  accept/spots by_state VA,NH,RI,ME

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

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

  reject/spots 1 on hf/ssb

  clear/spots 1

  clear/spots all

  clear/announce  clear/wcy  clear/wwv

  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)

11.58 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.59 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.60 help (0)

help The HELP Command

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

  HELP <cmd>

11.61 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.62 join <group> (0)

join <group> Join a chat or conference group

JOIN allows you to join a network wide conference group. To join agroup (called FOC in this case) type:-

  JOIN FOC

11.63 kill (5)

kill

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

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

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

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

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

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

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

11.67 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.68 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.69 kill from <call> (5)

kill from <call> Remove all messages from a callsign

11.70 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

  KILL from g1tlh

  KILL to g1tlh

  KILL FULL 1234

11.71 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.72 kill to <call> (5)

kill to <call> Remove all messages to a callsign

11.73 kill from <regex> (0)

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

11.74 kill to <regex> (0)

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

11.75 leave <group> (0)

leave <group> Leave a chat or conference group

LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:-

  LEAVE FOC

11.76 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.77 load/aliases (9)

load/aliases Reload the command alias table

Reload the /spider/cmd/Aliases file after you have editted it. Youwill need to do this if you change this file whilst the cluster isrunning in order for the changes to take effect.

11.78 load/badmsg (9)

load/badmsg Reload the bad msg table

Reload the /spider/msg/badmsg.pl file if you have changed it manually whilstthe cluster is running. This table contains a number of perl regular expressions which are searched for in the fields targetted of each message. If any of them match then that message is immediately deleted on receipt.

11.79 load/badwords (9)

load/badwords Reload the bad words table

Reload the /spider/data/badwords file if you have changed it manually whilstthe cluster is running. This file contains a list of words which, if foundon certain text portions of PC protocol, will cause those protocol framesto be rejected. It will all put out a message if any of these words areused on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.

11.80 load/bands (9)

load/bands Reload the band limits table

Reload the /spider/data/bands.pl file if you have changed it manually whilstthe cluster is running.

11.81 load/cmd_cache (9)

load/cmd_cache Reload the automatic command cache

Normally, if you change a command file in the cmd or local_cmd tree itwill automatially be picked up by the cluster program. Sometimes itcan get confused if you are doing a lot of moving commands about ordelete a command in the local_cmd tree and want to use the normal oneagain. Execute this command to reset everything back to the state itwas just after a cluster restart.

11.82 load/forward (9)

load/forward Reload the msg forwarding routing table

Reload the /spider/msg/forward.pl file if you have changed itmanually whilst the cluster is running.

11.83 load/keps (5)

load/keps Load new keps data

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

11.85 load/messages (9)

load/messages Reload the system messages file

If you change the /spider/perl/Messages file (usually whilstfiddling/writing new commands) you can have them take effect during acluster session by executing this command. You need to do this if getsomething like :-unknown message 'xxxx' in lang 'en'

11.86 load/prefixes (9)

load/prefixes Reload the prefix table

Reload the /spider/data/prefix_data.pl file if you have changed itmanually whilst the cluster is running.

11.87 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.88 msg <cmd> <msgno> [data ... ] (9)

msg <cmd> <msgno> [data ... ] Alter various message parameters

Alter message parameters like To, From, Subject, whether private or bulletinor return receipt (RR) is required or whether to keep this message from timingout.

  MSG TO <msgno> <call>     - change TO callsign to <call>  MSG FRom <msgno> <call>   - change FROM callsign to <call>  MSG PRrivate <msgno>      - set private flag  MSG NOPRrivate <msgno>    - unset private flag  MSG RR <msgno>            - set RR flag  MSG NORR <msgno>          - unset RR flag  MSG KEep <msgno>          - set the keep flag (message won't be deleted ever)  MSG NOKEep <msgno>        - unset the keep flag  MSG SUbject <msgno> <new> - change the subject to <new>  MSG WAittime <msgno>      - remove any waitting time for this message  MSG NOREad <msgno>        - mark message as unread  MSG REad <msgno>          - mark message as read  MSG QUeue                 - queue any outstanding bulletins  MSG QUeue 1               - queue any outstanding private messages

  STAT/MSG <msgno>      

11.89 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!!!

11.90 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.91 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.92 read (0)

read Read the next unread personal message addressed to you

11.93 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.94 read- (5)

read-

As a sysop you may read any message on the system

11.95 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.96 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.97 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)

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

  rej/ann all

11.98 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

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

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

11.99 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.100 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>

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

  rej/spot 3 all

11.101 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.102 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.103 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.104 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>

  reject/wwv by_zone 14,15,16

11.105 reply (0)

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

11.106 reply <msgno> (0)

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

11.107 reply b <msgno> (0)

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

11.108 reply noprivate <msgno> (0)

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

11.109 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.110 save [-d -t -a] <filename> "<cmd>" [...] (9)

save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file

This sysop only cammand allows you to save the output of one or morecommands to a file. For example:-

  save /spider/packclus/dxstats show/dxstat

  save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002  save -t /tmp/a <cmd> creates /tmp/a_2301Z  save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z

  save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"

  save /tmp/a "sh/hfstats","blank +","sh/vhfstats"

  0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')

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

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

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

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

11.113 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

  ...  bye then Jim  73 Dirk  /ex

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

  /dx g1tlh 144010 strong signal

  //sh/vhftable

11.114 send private <call> (0)

send private <call> Send a personal message

11.115 send rr <call> (0)

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

11.116 set/address <your address> (0)

set/address <your address> Record your postal address

11.117 set/announce (0)

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

11.118 set/anntalk (0)

set/anntalk Allow talk like announce messages on your terminal

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

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

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

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

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

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

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

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

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

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

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

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

11.125 set/beep (0)

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

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

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

11.127 set/debug <name> (9)

set/debug <name> Add a debug level to the debug set

11.128 set/dx (0)

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

11.129 set/dxcq (0)

set/dxcq Show CQ Zones on the end of DX announcements

11.130 set/dxgrid (0)

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

11.131 set/dxitu (0)

set/dxitu Show ITU Zones on the end of DX announcements

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

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

11.133 set/echo (0)

set/echo Make the cluster echo your input

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

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

11.135 set/here (0)

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

11.136 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.137 set/hops <call> ann|spots|route|wwv|wcy <n> (8)

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

11.138 set/isolate (9)

set/isolate Isolate a node from the rest of the network

Connect a node to your system in such a way that you are a full protocolmember of its network and can see all spots on it, but nothing either leaksout from it nor goes back into from the rest of the nodes connected to you.You can potentially connect several nodes in this way.

11.139 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),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).

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

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

11.141 set/lockout <call> (9)

set/lockout <call> Stop a callsign connecting to the cluster

11.142 set/logininfo (0)

set/logininfo Inform when a station logs in locally

11.143 set/name <your name> (0)

set/name <your name> Set your name

Tell the system what your name is eg:-

  SET/NAME Dirk

11.144 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.145 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.146 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

11.147 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.148 set/password <callsign> <string> (9)

set/password <callsign> <string> Set a users password

The password for a user can only be set by a full sysop. The stringcan contain any characters. The way this field is used depends on context. If it is being used inthe SYSOP command context then you are offered 5 random numbers and youhave to supply the corresponding letters. This is now mainly for ax25connections.If it is being used on incoming telnet connections then, if a passwordis set or the:

  set/var $main::passwdreq = 1

11.149 set/pinginterval <time> <nodecall> (9)

set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes

As from release 1.35 all neighbouring nodes are pinged at regular intervalsin order to determine the rolling quality of the link and, in future, toaffect routing decisions. The default interval is 300 secs or 5 minutes.You can use this command to set a different interval. Please don't. But if you do the value you enter is treated as minutes up 30 and secondsfor numbers greater than that.This is used also to help determine when a link is down at the far end(as certain cluster software doesn't always notice), see SET/OBSCOUNTfor more information.If you must change it (and it may be useful for internet connected nodeson dynamic IP addresses that go away after a set time of usage) the timecan be specified as:-

  5      which if less than 30 is converted to minutes otherwise is          taken as the no of seconds between pings.   120s   120 seconds  5m     5 minutes  1h     1 hour

11.150 set/privilege <n> <call> [<call..] (9)

set/privilege <n> <call> [<call..] Set privilege level on a call

Set the privilege level on a callsign. The privilege levels that pertainto commands are as default:-

  0 - normal user  1 - allow remote nodes normal user RCMDs  5 - various privileged commands (including shutdown, but not disc-      connect), the normal level for another node.  8 - more privileged commands (including disconnect)  9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS      LEVEL.

11.151 set/prompt <string> (0)

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

11.152 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.153 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.154 set/register <call> ... (9)

set/register <call> ... Mark a user as registered

11.155 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.156 set/sys_location <lat & long> (9)

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

In order to get accurate headings and such like you must tell the systemwhat your latitude and longitude is. If you have not yet done a SET/QRAthen this command will set your QRA locator for you. For example:-

  SET/LOCATION 52 22 N 0 57 E

11.157 set/sys_qra <locator> (9)

set/sys_qra <locator> Set your cluster QRA Grid locator

11.158 set/talk (0)

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

11.159 set/usdb <call> <state> <city> (9)

set/usdb <call> <state> <city> add/update a US DB callsign

This command allows you to add or alter a callsign in the US statedatabase. Use with extreme caution. Anything you do here will beoverwritten by any weekly updates that affect this callsign

  set/usdb g1tlh nh downtown rindge

11.160 set/usstate (0)

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

11.161 set/wcy (0)

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

11.162 set/wwv (0)

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

11.163 set/wx (0)

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

11.164 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.165 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.166 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.167 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.168 show/chat [<group>] [<lines>] (0)

show/chat [<group>] [<lines>] Show any chat or conferencing

This command allows you to see any chat or conferencing that has occurred whilst you were away. SHOW/CHAT on its own will show data forall groups. If you use a group name then it will show only chat forthat group.

11.169 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 

  SH/C GB7DJK

  SH/C SK

11.170 show/configuration/node (0)

show/configuration/node Show all the nodes connected locally

Show all the nodes connected to this node.

11.171 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.172 show/contest <year and month> (0)

show/contest <year and month> Show all the contests for a month

Show all known contests which are maintained at http://www.sk3bg.se/contest/for a particular month or year. The format is reasonably flexible.For example:-

  SH/CONTEST sep2003  SH/CONTEST 03 march

11.173 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.174 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.175 show/debug (9)

show/debug Show what levels of debug information you are logging

11.176 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  

 real or rt      - Format the output the same as for real time spots. The                   formats are deliberately different (so you can tell                   one sort from the other). This is useful for some                    logging programs that can't cope with normal sh/dx                    output. An alias of SHOW/FDX is available.

 filter          - Filter the spots, before output, with the user's                    spot filter. An alias of SHOW/MYDX is available.

 zone <zones>    - look for spots in the cq zone (or zones) specified.                   zones are numbers separated by commas.

 by_zone <zones> - look for spots spotted by people in the cq zone                   specified.

 itu <itus>      - look for spots in the itu zone (or zones) specified                   itu zones are numbers separated by commas.

 by_itu <itus>   - look for spots spotted by people in the itu zone                   specified.

 state <list>    - look for spots in the US state (or states) specified                   The list is two letter state codes separated by commas.

 by_state <list> - look for spots spotted by people in the US state                   specified.

 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   SH/DX zone 4,5,6   SH/DX by_zone 4,5,6   SH/DX state in,oh   SH/DX by_state in,oh

11.177 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

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

11.178 show/dxqsl <callsign> (0)

show/dxqsl <callsign> Show any QSL info gathered from spots

The node collects information from the comment fields in spots (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.This command allows you to interrogate that database and if the callsignis found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate ifit is spotted enough times.For example:-

  sh/dxqsl 4k9w

  sh/dx 4k9w qsl

11.179 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.180 show/fdx (0)

show/fdx Show the DX data in realtime format.

Normally SHOW/DX outputs spot data in a different format to therealtime data. This is a deliberate policy (so you can tell the difference between the two). Some logging programs cannot handlethis so SHOW/FDX outputs historical data in real time format.This is an alias for: SHOW/DX real

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

   SH/FILES bulletins arld*

11.182 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.183 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.184 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 

  sh/hftable 20 pa

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

  sh/hftable all 

11.185 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.186 show/isolate (1)

show/isolate Show list of ISOLATED nodes

11.187 show/lockout <prefix>|all (9)

show/lockout <prefix>|all Show the list of locked out or excluded callsigns

11.188 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.189 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

  SH/MOON -1 

  SH/MOON +3 W9

11.190 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

  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

  SH/MUF W 24

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

11.191 show/mydx (0)

show/mydx Show the DX data filtered with your spot filter.

SHOW/DX potentially shows all the spots available in the system. UsingSHOW/MYDX will, instead, filter the availble spots using any spot filter that you have set, first. This command, together with ACCEPT/SPOT or REJECT/SPOT, will allowyou to customise the spots that you receive.So if you have said: ACC/SPOT on hfDoing a SHOW/MYDX will now only, ever, show HF spots. All the other options on SH/DX can still be used.

11.192 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.193 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.194 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.195 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.196 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.197 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

 SH/QRA 52 41 N 0 58 E

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

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

11.199 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.200 show/registered [<prefix>] (9)

show/registered [<prefix>] Show the registered users

11.201 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.202 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.203 show/station all [<regex>] (6)

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

11.204 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

11.205 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

  SH/SUN -1 

  SH/SUN +3 W9

11.206 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.207 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.208 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.209 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

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

  sh/vhftable all 

11.210 show/wcy (0)

show/wcy Show last 10 WCY broadcasts

11.211 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.212 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.213 show/wwv (0)

show/wwv Show last 10 WWV broadcasts

11.214 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.215 shutdown (5)

shutdown Shutdown the cluster

Shutdown the cluster and disconnect all the users

11.216 spoof <call> <command> (9)

spoof <call> <command> Do a command as though you are another user

This command is provided so that sysops can set a user's parameters withoutme having to write a special 'sysop' version for every user command. Itallows you to pretend that you are doing the command as the user you specify.eg:-

   SPOOF G1TLH set/name Dirk   SPOOF G1TLH set/qra JO02LQ

11.217 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.218 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.219 stat/msg (1)

stat/msg Show the status of the message system

11.220 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.221 stat/route_node <callsign> (5)

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

11.222 stat/route_node all (5)

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

11.223 stat/route_user <callsign> (5)

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

11.224 stat/route_user all (5)

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

11.225 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.226 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

 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573

11.227 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

   /EX

  //sh/hftable

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

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

11.229 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

11.230 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

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

11.231 unset/announce (0)

unset/announce Stop announce messages coming out on your terminal

11.232 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

  set/anntalk 

11.233 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

  unset/baddx VIDEO

11.234 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 

  unset/badnode K1TTT

11.235 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 

  unset/badspotter VE2STN

11.236 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 

  unset/badword annihilated

11.237 unset/beep (0)

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

11.238 unset/debug <name> (9)

unset/debug <name> Remove a debug level from the debug set

You can choose to log several different levels. The levels are

 chan state msg cron connect

11.239 unset/dx (0)

unset/dx Stop DX messages coming out on your terminal

11.240 unset/dxcq (0)

unset/dxcq Stop CQ Zones on the end of DX announcements

Display both the Spotter's and the Spotted's CQ Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused.

11.241 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.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused.

11.242 unset/dxitu (0)

unset/dxitu Stop ITU Zones on the end of DX announcements

Display both the Spotter's and the Spotted's ITU Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused.

11.243 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.244 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

  UNSET/EMAIL

11.245 unset/here (0)

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

11.246 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

  unset/hops gb7djk ann  unset/hops gb7mbc spots

11.247 unset/isolate (9)

unset/isolate Stop Isolation of a node from the rest of the network

Remove isolation from a node - SET/ISOLATE

11.248 unset/lockout <call> (9)

unset/lockout <call> Allow a callsign to connect to the cluster

11.249 unset/logininfo (0)

unset/logininfo Inform when a station logs out locally

11.250 unset/password <call> ... (9)

unset/password <call> ... Delete (remove) a user's password

This command allows the sysop to completely delete and remove a password for a user.

11.251 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.252 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 >

11.253 unset/register <call> ... (9)

unset/register <call> ... Mark a user as not registered

Registration is a concept that you can switch on by executing the

  set/var $main::regreq = 1 

11.254 unset/talk (0)

unset/talk Stop TALK messages coming out on your terminal

11.255 unset/usstate (0)

unset/usstate 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.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused.

11.256 unset/wcy (0)

unset/wcy Stop WCY messages coming out on your terminal

11.257 unset/wwv (0)

unset/wwv Stop WWV messages coming out on your terminal

11.258 unset/wx (0)

unset/wx Stop WX messages coming out on your terminal

11.259 who (0)

who Show who is physically connected

This is a quick listing that shows which callsigns are connected andwhat sort of connection they have

11.260 wx <text> (0)

wx <text> Send a weather message to local users

11.261 wx full <text> (0)

wx full <text> Send a weather message to all cluster users

11.262 wx sysop <text> (5)

wx sysop <text> Send a weather message to other clusters only

Weather messages can sometimes be useful if you are experiencing an extremethat may indicate enhanced conditions