DXSpider Sysop Command Reference

ACCEPT

accept set a filter to accept something
Create a filter to accept something. There are 2 types of filter, accept and reject. See Help Filtering for more info.

accept/announce <call> [input] [0-9] <pattern>

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 the default 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

accept/announce [0-9] <pattern>

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 is passed onto the user. 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:

 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

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)

or

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

accept/route <call> [0-9] <pattern>

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

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

 acc/route all

accept/spots <call> [input] [0-9] <pattern>

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

accept/spots [0-9] <pattern>

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 in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: freq HF (but don't get too hung up about that)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...

accept/wcy <call> [input] [0-9] <pattern>

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

accept/wcy [0-9] <pattern>

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 can filter 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 and you either want them or not (see UNSET/WCY if you don't want them).This command is really provided for future use. See HELP FILTER for information.

accept/wwv <call> [input] [0-9] <pattern>

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 the default 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

accept/wwv [0-9] <pattern>

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 can filter 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 broadcasts by stations in the US). See HELP FILTER for information.

ANNOUNCE

announce <text>

announce <text> - Send an announcement to LOCAL users only

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

announce full <text>

announce full <text> - Send an announcement cluster wide

This will send your announcement cluster wide

announce sysop <text>

announce sysop <text> - Send an announcement to Sysops only

APROPOS

apropos <string>

apropos <string> - Search help database for <string>

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

BLANK

blank [<string>] [<nn>]

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

In its basic form this command prints one or more blank lines. However if you 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 maximum of 9 lines.

BYE

bye

bye - Exit from the cluster

This will disconnect you from the cluster

CATCHUP

catchup <node call> all|[<msgno> ...]

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

CHAT

chat <group> <text>

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

It is now possible to JOIN a group and have network wide conferencing to that group. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seem to work too well anyway. This system uses the existing ANN system and is compatible with both other DXSpider 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)

To leave a group type:

 LEAVE FOC

You can see which groups you are in by typing:

 STAT/USER

and you can see whether your mate is in the group, if he connects to the same node as you, by typing:

 STAT/USER g1tlh

To send a message to a group type:

 CHAT FOC hello everyone

or

 CH #9000 hello I am back

CLEAR

clear/announce <callsign> [input] [0-9|all]

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 the node_default or user_default.

clear/announce [1|all]

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

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

clear/route <callsign> [input] [0-9|all]

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 then ode_default or user_default.

clear/route [1|all]

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.

clear/spots <callsign> [input] [0-9|all]

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 the node_default or user_default.

clear/spots [0-9|all]

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.

clear/wcy <callsign> [input] [0-9|all]

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 the node_default or user_default.

clear/wcy [1|all]

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.

clear/wwv <callsign> [input] [0-9|all]

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 the node_default or user_default.

clear/wwv [1|all]

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.

CONNECT

connect <callsign>

connect <callsign> - Start a connection to another DX Cluster

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

DBAVAIL

dbavail

dbavail - Show a list of all the Databases in the system

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

DBCREATE

dbcreate <name>

dbcreate <name> - Create a database entry

dbcreate <name> chain <name> [<name>..]

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

dbcreate <name> cmd <dxspider command>

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 actually create 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

You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:

 DBCREATE sdx_qsl chain sql_ad

No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. Databases can exist offsite. To define a database that lives on another node do:

 DBCREATE buckmaster remote gb7dxc

Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:

 DBCREATE qsl chain gb7dxc

To see what databases have been defined do:

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

It would be normal for you to add an entry into your local Aliases file to allow people to use the 'SHOW/<dbname>' style syntax. So you would need to add a line like:

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

to allow

 SH/BUCK g1tlh

to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-

 DBCREATE dxqsl cmd show/dxqsl

You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry

dbcreate <name> remote <node>

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

DBIMPORT

dbimport <dbname> <filename>

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

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

 DBIMPORT oblast /tmp/OBLAST.FUL

will import the standard OBLAST database that comes with AK1A into the oblast database held locally.

DBREMOVE

dbremove <dbname>

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

will remove the oblast database from the system and it will also remove the associated data file. I repeat: There is no warning, no comeback, no safety net. You have been warned.

DBSHOW

dbshow <dbname> <key>

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 file so 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 or SHOW/COMMAND to find out) you can do the same thing with:

 DBSHOW buck G1TLH

DEBUG

debug

debug - Set the cluster program into debug mode

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

       perl -d cluster.pl

It will interrupt the cluster just after the debug command has finished.

DELETE

delete/usdb <callsign> ...

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

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

delete/user <callsign> ...

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!

DEMONSTRATE

demonstrate <call> <command>

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 and then sends the output to that user, together with the command that caused it.

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

Note that this command is similar to SPOOF and will have the same side effects. Commands are run at the privilege of the user which is being demonstrated to.

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

Disconnect any <call> connected locally

DX

dx [by <call>] <freq> <call> <remarks>

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, now enter 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 end of 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.

ECHO

echo <line>

echo <line> - Echo the line to the output This command is useful in scripts and so forth for printing the line that you give to the command to the output. You can use this in user_default scripts and the SAVE command for titling and so forth. The 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.

EXPORT

export <msgno> <filename>

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

Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready 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 can access. For example:

 EXPORT 2345 /tmp/a

export_users [<filename>]

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

Export the users database to a file in ascii format. If no file name is 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 fact up to 5 generations of the file can be kept each one with an extra 'o' on the suffix. BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.

FILTERING

filtering...

filtering... - Filtering things in DXSpider

There are a number of things you can filter in the DXSpider system. They all use the same general mechanism. In general terms you can create a 'reject' or an 'accept' filter which can 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. There are filters for spots, wwv, announce, wcy and (for sysops) connects. See each different accept or reject command reference for more details. There is also a command to clear out one or more lines in a filter and one 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 apply the principles to all types of filter. There are two main types of filter 'accept' or 'reject'; which you use depends entirely on how you look at the world and what is least writing to achieve what you want. Each filter has 10 lines (of any length) which are tried in order. If a line matches then the action you have specified is taken (ie reject means ignore it and accept means 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 if a spot comes in that doesn't match any of the lines then you will get it BUT if you specify an 'accept' filter then any spots that don't match 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 IOTA and 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 until you are comfortable with the way it works. Yes, you can mix them (actually you can have an accept AND a reject on the same line) but don't try this at home until you can analyze the results that you get without 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 your own 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't read any CW and couldn't possibly be interested in HF :-) and also rejects any spots on VHF which don't either originate or spot someone in Europe. This is an example where you would use the line number (1 and 2 in this 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 can use any number of brackets to make the 'expression' as you want it. There are things called precedence rules working here which mean that 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 - use brackets. Whilst we are here CASE is not important. 'And BY_Zone' is just 'and by_zone'. If you want to alter your filter you can just redefine one or more lines of it or clear out one line. For example:

 reject/spots 1 on hf/ssb

or

 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 EU can 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 executed first, any non hf/cw spot is passed to the accept line, which lets thru everything else on HF. The next filter line lets through just VHF/UHF spots from EU.

FORWARD

forward/latlong <node_call>

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

This command sends all the latitude and longitude information that your cluster is holding against callsigns. One advantage of receiving this information is that more locator information is held by you. This means that more locators are given on the DX line assuming you have SET/DXGRID enabled. This could be a LOT of information though, so it is not recommended on slow links.

forward/opernam <call>

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.

FTx

enable/autoftx

enable/autoftx - Enable detected automatically generated FTx spots to be output on the screen

To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

enable/ftx

enable/ftx - Enable FTx spots to be output on the screen

To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

disable/autoftx

disable/autoftx - Disable detected automatically generated FTx spots from being output on the screen

To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

disable/ftx

disable/ftx - Disable FTx spots from being output on the screen

To allow users an easy way to choose how many and the source of FTx spots. Stat/user will show how these flags are set - IF they are set (whether on or off). If these commands are not used, then stat/user will not show their values. This is by design. This is a best effort filter.

HELP

help

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 abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on. Look at the APROPOS <string> command which will search the help database for the <string> you specify and give you a list of likely commands to look at with HELP.

INIT

init <node>

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

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

JOIN

join <group>

join <group> - Join a chat or conference group

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

 JOIN FOC

KILL

kill

kill

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

kill <from msgno>-<to msgno>

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

kill <from>-<to>

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

kill <msgno> [<msgno..]

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

kill <msgno> [<msgno> ...]

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.

kill expunge <msgno> [<msgno..]

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

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

kill from <call>

kill from <call> - Remove all messages from a callsign

kill full <msgno> [<msgno..]

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

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

 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!

kill full <msgno> [<msgno]

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

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

kill to <call>

kill to <call> - Remove all messages to a callsign

kill from <regex>

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

kill to <regex>

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

LEAVE

leave <group>

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

LINKS

links

links - Show which nodes is physically connected

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

LOAD

load/aliases

load/aliases - Reload the command alias table

Reload the /spider/cmd/Aliases file after you have edited it. You will need to do this if you change this file whilst the cluster is running in order for the changes to take effect.

load/badmsg

load/badmsg - Reload the bad msg table

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

load/badwords

load/badwords - Reload the bad words table

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

load/bands

load/bands - Reload the band limits table

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

load/cmd_cache

load/cmd_cache - Reload the automatic command cache

Normally, if you change a command file in the cmd or local_cmd tree it will automatically be picked up by the cluster program. Sometimes it can get confused if you are doing a lot of moving commands about or delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart.

load/forward

load/forward - Reload the msg forwarding routing table

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

load/keps

load/keps - Load new keps data

load/keps [nn]

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

If there is no message number then reload the current Keps data from the 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, run convkeps.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.

load/messages

load/messages - Reload the system messages file

If you change the /spider/perl/Messages file (usually whilst fiddling/writing new commands) you can have them take effect during a cluster session by executing this command. You need to do this if get something like :

 unknown message 'xxxx' in lang 'en'

load/prefixes

load/prefixes - Reload the prefix table

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

MERGE

merge <node> [<no spots>/<no wwv>]

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 default it will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally. You can request any number of spots or wwv and although they will be appended to your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

MSG

msg <cmd> <msgno> [data ... ]

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

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

 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

You can look at the status of a message by using:

 STAT/MSG <msgno>

This will display more information on the message than DIR does.

PC

pc <call> <text>

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

Send some arbitrary text to a locally connected callsign. No processing is done on the text. This command allows you to send PC Protocol to unstick things if problems arise (messages get stuck etc). eg:

  pc gb7djk PC33^GB7TLH^GB7DJK^400^

or

  pc G1TLH Try doing that properly!!!

Send any text you like to the callsign requested. This is used mainly to send PC 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 but without any processing, added of "from <blah> to <blah" or whatever.

PING

ping <node call>

ping <node call> - Check the link quality between nodes

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

RCMD

rcmd <node call> <cmd>

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

This command allows you to send nearly any command to another DX Cluster node that is connected to the system. Whether you get any output is dependent on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all.

READ

read

read - Read the next unread personal message addressed to you

read <msgno>

read <msgno> - Read the specified message

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

read-

read-

As a sysop you may read any message on the system

REJECT

reject

reject - Set a filter to reject something

Create a filter to reject something. There are 2 types of filter, accept and reject. See HELP FILTERING for more info.

reject/announce <call> [input] [0-9] <pattern>

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 the default 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

reject/announce [0-9] <pattern>

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 is passed onto the user. 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:

 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

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

reject/route <call> [0-9] <pattern>

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

reject/spots <call> [input] [0-9] <pattern>

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 the default 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

reject/spots [0-9] <pattern>

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 is dumped (not passed on). 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:

 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
 on <range> same as 'freq'
 call <prefixes> eg: G,PA,HB9i
 nfo <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 in SHOW/BANDS and you can use a sub-band name like: cw, rtty, data, ssb -thus: hf/ssb. You can also just have a simple range like: 0/30000 -this is more efficient than saying simply: on HF (but don't get too hung up about that)some examples:

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

reject/wcy <call> [input] [0-9] <pattern>

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 the default for nodes and users eg:

 reject/wcy gb7djk all

reject/wcy [0-9] <pattern>

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 can filter 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 and you either want them or not (see UNSET/WCY if you don't want them). This command is really provided for future use. See HELP FILTER for information.

reject/wwv <call> [input] [0-9] <pattern>

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 the default for nodes and users eg:

 reject/wwv db0sue-7 1 by_zone 4
 reject/wwv node_default all
 reject/wwv user_default by W

reject/wwv [0-9] <pattern>

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 can filter 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 broadcasts by stations in the US). See HELP FILTER for information.

REPLY

reply

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

reply <msgno>

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

reply b <msgno>

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

reply noprivate <msgno>

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

reply rr <msgno>

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 SEND for further details)

SAVE

save [-d -t -a] <filename> "<cmd>" [...]

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

This sysop only command allows you to save the output of one or more commands to a file. For example:

 save /spider/packclus/dxstats show/dxstat

will save the output of the normal command "show/dxstat" to the file "dxstats" in the files area. You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:

 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

The -a flag means append to the file instead of overwriting it. You can have more than one command on the line, to do this you MUST enclose each command in double quotes (") eg:

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

or

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

You can only write into places that the cluster has permission for (which is that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well. It is likely that you will want to run these commands in a crontab type situation. You would do that something like:

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

Note that you still enclose each command with (") characters but you must enclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See the admin manual for more details.

SEND

send <call> [<call> ...]

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

send copy <msgno> <call>

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

send noprivate <call>

send noprivate <call> - Send a message to all stations

All the SEND commands will create a message which will be sent either to an individual callsign or to one of the 'bulletin' addresses. SEND <call> on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that that callsign is connected to. If the <call> you have specified is in fact a known bulletin category on your node (eg: ALL) then the message should automatically 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 will receive a read receipt when they have read the message. SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak). SP is an alias for SEND PRIVATE. The system will ask you for a subject. Conventionally this should be no longer than 29 characters for compatibility. Most modern cluster software 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 you can 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 (such as DX announcements and so on are suppressed and stored for latter display(up to 20 such lines are stored, as new ones come along, so the oldest lines 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 typing the command preceded by a '/' character on a new line, so:

 /dx g1tlh 144010 strong signal

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

 //sh/vhftable

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

send private <call>

send private <call> - Send a personal message

send rr <call>

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

SET

set/address <your address>

set/address <your address> - Record your postal address

set/announce

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

set/anntalk

set/anntalk - Allow talk like announce messages on your terminal

set/arcluster <call> [<call>..]

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

set/baddx <call>..

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

set/badnode <call>..

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

set/badspotter <call>..

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

set/badword <word>..

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

set/bbs <call> [<call>..]

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

set/beep

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

set/clx <call> [<call>..]

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

set/debug <name>

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

set/dx

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

set/dxcq

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

set/dxgrid

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

set/dxitu

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

set/dxnet <call> [<call>..]

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

set/echo

set/echo - Make the cluster echo your input

set/email <email> ...

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

set/external_ip <external_ip>

set/external_ip - Set the external IPv4 address for the node and the local terminal masquerade automatically with best effort.

set/here

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

set/homenode <node>

set/homenode <node> - Set your normal cluster callsign

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

 SET/HOMENODE gb7djk

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

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

set/isolate

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 protocol member of its network and can see all spots on it, but nothing either leaks out from it nor goes back into from the rest of the nodes connected to you. You can potentially connect several nodes in this way.

set/language <lang>

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

You can select the language that you want the cluster to use. Currently the languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).

set/location <lat & long>

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

set/lockout <call>

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

set/logininfo

set/logininfo - Inform when a station logs in/out locally

set/name <your name>

set/name <your name> - Set your name

Tell the system what your name is eg:

 SET/NAME Dirk

set/node <call> [<call>..]

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

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

set/obscount <count> <call>

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

From 1.35 onwards neighboring nodes are pinged at regular intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' counter which is decremented on every outgoing ping and then reset to the 'obscount' value on every incoming ping. The default value of this parameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just before what would be the third attempt, that node is disconnected. If a ping is heard then the obscount is reset to the full value. Using default values, if a node has not responded to a ping within 15 minutes, it is disconnected. You can set this parameter between 1 and 9. It is STRONGLY recommended that you don't change the default.

set/page <lines per page>

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 line of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging.

 SET/PAGE 30  SET/PAGE 0

The setting is stored in your user profile.

set/password

set/password - Set your own password

This command only works for a 'telnet' user (currently). It will only work if you have a password already set. This initial password can only be set by the sysop. When you execute this command it will ask you for your old password, then ask you to type in your new password twice (to make sure you get it right). You may or may not see the data echoed on the screen as you type, depending on the type of telnet client you have.

set/password <callsign> <string>

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

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

 set/var $main::passwdreq = 1

command is executed in the startup script, then a password prompt is given after the normal 'login:' prompt.

set/pinginterval <nodecall>

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

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

Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance! You can switch this off by setting it to 0.

set/privilege <n> <call> [<call..]

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

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

 0 - normal user
 1 - allow remote nodes normal user RCMDs
 5 - various privileged commands (including shutdown, but not disconnect), 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.

If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.

set/prompt <string>

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

set/qra <locator>

set/qra <locator> - Set your QRA Grid locator

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

 SET/QRA JO02LQ

set/qth <your qth>

set/qth <your qth> - Set your QTH

Tell the system where you are. For example:

 SET/QTH East Dereham, Norfolk

set/register <call> ...

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

set/spider <call> [<call>..]

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

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

set/startup

set/startup - Create your own startup script

Create a startup script of DXSpider commands which will be executed every time that you login into this node. You can only input the whole script afresh, it is not possible to 'edit' it. Inputting a new script is just like typing in a message using SEND. To finish inputting type: /EX on a newline, to abandon the script type: /ABORT. You may find the (curiously named) command BLANK useful to break up the output. If you simply want a blank line, it is easier to input one or more spaces and press the <return> key. See UNSET/STARTUP to remove a script.

set/startup <call>

set/startup <call> - Create a user startup script

set/sys_location <lat & long>

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

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

 SET/LOCATION 52 22 N 0 57 E

set/sys_qra <locator>

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

set/talk

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

set/usdb <call> <state> <city>

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

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

 set/usdb g1tlh nh downtown rindge

set/usstate

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

set/wcy

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

set/wwv

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

set/wx

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

SHOW

show/baddx

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

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

show/badnode

show/badnode - Show all the bad nodes in the system

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

show/badspotter

show/badspotter - Show all the bad spotters in the system

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

show/badword

show/badword - Show all the bad words in the system

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

show/chat [<group>] [<lines>]

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 for all groups. If you use a group name then it will show only chat for that group.

show/configuration [<node>]

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

This command allows you to see all the users that can be seen and the nodes to which they are connected. This command is normally abbreviated to: sh/c. Normally, 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 long. It 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 with that prefix.

 SH/C GB7DJK
 SH/C SK

show/configuration/node

show/configuration/node - Show all the nodes connected locally

Show all the nodes connected to this node.

show/connect

show/connect - Show all the active connections

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

show/contest <year and month>

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

show/date [<prefix>|<callsign>]

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

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

show/db0sdx <callsign>

show/db0sdx <callsign> - Show QSL information from DB0SDX database

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

show/debug

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

show/dup_ann

show/dup_ann - Show duplicate announcement records

show/dup_spots

show/dup_spots - Show duplicate spot records

show/dx

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 nearly any 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

show/dxcc <prefix>

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 is and 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

This is an alias for: SH/DX dxcc

show/dxqsl <callsign>

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

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

 sh/dxqsl 4k9w

You can check the raw input spots yourself with:

 sh/dx 4k9w qsl

This gives you more background information.

show/dxstats [days] [date]

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

show/external_ip

show/external_ip - Show the external IP set/detected for the node and local terminal masquerade

show/fdx

show/fdx - Show the DX data in realtime format.

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

show/files [<file area> [<string>]]

show/files [<file area> [<string>]] - List the contents of a file area

SHOW/FILES on its own will show you a list of the various file areas available on the system. To see the contents of a particular file area type:

  SH/FILES <file area>

where <file area> is the name of the file area you want to see the contents of. You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a file area eg:

  SH/FILES bulletins arld*

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

show/filter

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

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

show/hfstats [days] [date]

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

show/hftable [days] [date] [prefix ...]

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 is specially 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 have to list all possible prefixes for each country. If you want more or less days than the default simply include the number 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 you did against all your mates). You can also say 'all' which will then print the worldwide statistics.

 sh/hftable all

show/hops <call> [ann|spots|route|wcy|wwv]

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 specify which category you want to see. If you leave the category out then all the categories will be listed.

show/isolate

show/isolate - Show list of ISOLATED nodes

show/lockout <prefix>|all

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

show/log [<callsign>]

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

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

show/moon [ndays] [<prefix>|<callsign>]

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 those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. 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 node that 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, so if you want to see yesterday's times then do:

 SH/MOON -1

or in three days time:

 SH/MOON +3 W9

Up to 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 UTC times of rise and set on the requested UTC day.

show/muf <prefix> [<hours>][long]

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

This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD). The result predicts the most likely operating frequencies and signal levels for high frequency (shortwave) radio propagation paths on specified days of the year and hours of the day. It is most useful for paths between 250 km and 6000 km, but can be used with reduced accuracy for paths shorter or longer than this. The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and used to predict the MUF given the predicted flux, day of the year, hour of the day and geographic coordinates of the transmitter and receiver. This routine is reasonably accurate for the purposes here, with a claimed RMS error of 3.8 MHz, but much smaller and less complex than the programs used by major shortwave broadcasting organizations, such as the Voice of America. The command will display some header information detailing its assumptions, together with the locations, latitude and longitudes and bearings. It will then show UTC (UT), local time at the other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path(Zen) and the likely signal strengths. Then for each frequency for which the system thinks there is a likelihood of a circuit it prints a value. The value is currently a likely S meter reading based on the conventional 6dB / S point scale. If the value has a '+' appended it means that it is 1/2 an S point stronger. If the value is proceeded by an 'm' it means that there is likely to be much fading and by an 's' that the signal is likely to be noisy. By default SHOW/MUF will show the next two hours worth of data. You can specify anything up to 24 hours worth of data by appending the no of hours required after the prefix. For example:

 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). inputting:

 SH/MUF W 24

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

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

Gives you an estimate of the long path propagation characteristics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness.

show/mydx

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

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

show/newconfiguration [<node>]

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

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

show/newconfiguration/node

show/newconfiguration/node - Show all the nodes connected locally

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

show/node [<callsign> ...]

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

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

show/prefix <callsign>

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

show/program

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

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

show/qra <lat> <long>

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

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

 SH/QRA IO92Q
 SH/QRA JN06 IN73

The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators. It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, for example:

 SH/QRA 52 41 N 0 58 E

show/qra <locator> [<locator>]

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

show/qrz <callsign>

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

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

show/registered [<prefix>]

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

show/route <callsign> ...

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

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

 sh/route n2tly

show/satellite <name> [<hours> <interval>]

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

Show the tracking data from your location to the satellite of your choice from now on for the next few hours. If you use this command without a satellite name it will display a list of all the satellites known currently to the system. If you give a name then you can obtain tracking data of all the passes that start and finish 5 degrees below the horizon. As default it will give information for the next three hours for every five minute period. 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 '-----' characters. So for example:

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

show/startup

show/startup - View your own startup script

View the contents of a startup script created with SET/STARTUP.

show/startup <call>

show/startup <call> - View a user startup script

show/station all [<regex>]

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

show/station [<callsign> ..]

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.

show/sun [ndays] [<prefix>|<callsign>]

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 those locations. If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation. If all else fails it will show the sunrise and set times for the node that 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, so if you want to see yesterday's times then do:

 SH/SUN -1

or in three days time:

 SH/SUN +3 W9

Up to 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 UTC times of rise and set on the requested UTC day.

show/time [<prefix>|<callsign>]

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

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

show/usdb [call ..]

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

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

 sh/usdb k1xx

show/vhfstats [days] [date]

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

show/vhftable [days] [date] [prefix ...]

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 is specially treated in the code) you must list all the relevant prefixes:

 sh/vhftable g gm gd gi gj gw gu

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

 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

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 you did against all your mates). You can also say 'all' which will then print the worldwide statistics.

 sh/vhftable all

show/wcy

show/wcy - Show last 10 WCY broadcasts

show/wcy <n>

show/wcy <n> - Show last <n> WCY broadcasts Display the most recent WCY information that has been received by the system.

show/wm7d <callsign>

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

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

show/wwv

show/wwv - Show last 10 WWV broadcasts

show/wwv <n>

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

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

SHUTDOWN

shutdown

shutdown - Shutdown the cluster Shutdown the cluster and disconnect all the users

SPOOF

spoof <call> <command>

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 without me having to write a special 'sysop' version for every user command. It allows 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

STAT

stat/channel [<callsign>]

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.

stat/db <dbname>

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.

stat/msg

stat/msg - Show the status of the message system

stat/msg <msgno>

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

This command shows the internal status of a message and includes information such 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.

stat/route_node <callsign>

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

stat/route_node all

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

stat/route_user <callsign>

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

stat/route_user all

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

stat/user [<callsign>]

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

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

SYSOP

sysop

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 to regain your normal privilege level. It uses the normal system: five numbers are returned that are indexes into the character array that is your assigned password (see SET/PASSWORD). The indexes start from zero. You are expected to return a string which contains the characters required in the correct order. You may intersperse those characters with others to obscure your reply for any watchers. For example (and these values are for explanation :-):

 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 offered numbers but nothing will happen when you input a string. Any match is case sensitive.

TALK

talk <call> > <node> [<text>]

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 cluster system. 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 connected with 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 only see GB7TLH in the SH/C list but with no users, then you would use the second form of the talk message. If you want to have a ragchew with someone you can leave the text message out and the system will go into 'Talk' mode. What this means is that a short message is sent to the recipient telling them that you are in a 'Talking' frame of mind and then you just type - everything you send will go to the station that you asked for. All the usual announcements, spots and so on will still come out on your terminal. If you want to do something (such as send a spot) you precede 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 extension to the '/' command which allows 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.

talk <call> [<text>]

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

TYPE

type <filearea>/<name>

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

Type out the contents of a file in a file area. So, for example, in file area 'bulletins' you want to look at file 'arld051' you would enter:

  TYPE bulletins/arld051

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

UNCATCHUP

uncatchup <node call> all|[msgno> ...]

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 partner node and you add their callsign to your /spider/msg/forward.pl file, all outstanding non-private messages will be forwarded to them. This may well be ALL the non-private messages. You can prevent this by using these commands:

 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.

UNSET

unset/announce

unset/announce - Stop announce messages coming out on your terminal

unset/anntalk

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 the welter of useless ones.

 set/anntalk

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

unset/baddx <call>..

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 any further. They will not be displayed and they will not be sent onto other 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

unset/badnode <call>..

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 must enter them specifically.

 unset/badnode K1TTT

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

unset/badspotter <call>..

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 automatically stop spots from this user, regardless of whether or which SSID he uses. DO NOT USE SSIDs in the callsign, just use the callsign as above or below.

 unset/badspotter VE2STN

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

unset/badword <word>..

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 any further. They will not be displayed and they will not be sent onto other 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.

unset/beep

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

unset/debug <name>

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

You can show what levels you are logging with SHOW/DEBUG

unset/dx

unset/dx - Stop DX messages coming out on your terminal

unset/dxcq

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

Display both the Spotter's and the Spotted's CQ Zone on the end of a DX announcement (there is just enough room). Some user programs cannot 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/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

unset/dxgrid

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 end of a DX announcement (there is just enough room). Some user programs cannot cope with this. You can use this command to reset (or set)this feature. Conflicts with: SET/DXCQ, SET/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

unset/dxitu

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

Display both the Spotter's and the Spotted's ITU Zone on the end of a DX announcement (there is just enough room). Some user programs cannot 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/USSTATE. Do a STAT/USER to see which flags you have set if you are confused.

unset/echo

unset/echo - Stop the cluster echoing your input

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

unset/email

unset/email - Stop personal msgs being forwarded by email

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

 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

unset/here

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

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

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

unset/isolate

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

Remove isolation from a node - SET/ISOLATE

unset/lockout <call>

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

unset/logininfo

unset/logininfo - No longer inform when a station logs in/out locally

unset/password <call> ...

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

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

unset/privilege

unset/privilege - Remove any privilege for this session

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

unset/prompt

unset/prompt - Set your prompt back to default

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

 SET/PROMPT clx >

There are some substitutions that can be added to the prompt:

 %C - callsign [which will have ( and ) around it if not here]
 %D - date
 %T - time
 %M - cluster 'mycall'

The standard prompt is defined as:

 SET/PROMPT %C de %M %D %T dxspider >

UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to normal.

unset/register <call> ...

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

command (usually in your startup file). If a user is NOT registered then, firstly, instead of the normal motd file (/spider/data/motd) being sent to the user at startup, the user is sent the motd_nor file instead. Secondly, the non-registered user only has READ-ONLY access to the node. The non-registered user cannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK or SEND messages to the sysop.

unset/startup

unset/startup - Remove your own startup script

You can remove your startup script with UNSET/STARTUP.

unset/startup <call>

unset/startup <call> - Remove a user startup script

unset/talk

unset/talk - Stop TALK messages coming out on your terminal

unset/usstate

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/DXITU. Do a STAT/USER to see which flags you have set if you are confused.

unset/wcy

unset/wcy - Stop WCY messages coming out on your terminal

unset/wwv

unset/wwv - Stop WWV messages coming out on your terminal

unset/wx

unset/wx - Stop WX messages coming out on your terminal

WHO

who

who - Show who is physically connected

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

WX

wx <text>

wx <text> - Send a weather message to local users

wx full <text>

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

wx sysop <text>

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

Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions.

DXSpider Sysop Command Reference

ACCEPT

accept/announce <call> [input] [0-9] <pattern>

accept/announce [0-9] <pattern>

accept/route <call> [0-9] <pattern>

accept/spots <call> [input] [0-9] <pattern>

accept/spots [0-9] <pattern>

accept/wcy <call> [input] [0-9] <pattern>

accept/wcy [0-9] <pattern>

accept/wwv <call> [input] [0-9] <pattern>

accept/wwv [0-9] <pattern>

ANNOUNCE

announce <text>

announce full <text>

announce sysop <text>

APROPOS

apropos <string>

BLANK

blank [<string>] [<nn>]

BYE

bye

CATCHUP

catchup <node call> all|[<msgno> ...]

CHAT

chat <group> <text>

CLEAR

clear/announce <callsign> [input] [0-9|all]

clear/announce [1|all]

clear/route <callsign> [input] [0-9|all]

clear/route [1|all]

clear/spots <callsign> [input] [0-9|all]

clear/spots [0-9|all]

clear/wcy <callsign> [input] [0-9|all]

clear/wcy [1|all]

clear/wwv <callsign> [input] [0-9|all]

clear/wwv [1|all]

CONNECT

connect <callsign>

DBAVAIL

dbavail

DBCREATE

dbcreate <name>

dbcreate <name> chain <name> [<name>..]

dbcreate <name> cmd <dxspider command>

dbcreate <name> remote <node>

DBIMPORT

dbimport <dbname> <filename>

DBREMOVE

dbremove <dbname>

DBSHOW

dbshow <dbname> <key>

DEBUG

debug

DELETE

delete/usdb <callsign> ...

delete/user <callsign> ...

DEMONSTRATE

demonstrate <call> <command>

DIRECTORY

directory

directory <from>-<to>

directory <nn>

directory all

directory from <call>

directory new

directory own

directory subject <string>

directory to <call>

directory-

DISCONNECT

disconnect <call> [<call> ...]

DX

dx [by <call>] <freq> <call> <remarks>

ECHO

echo <line>

EXPORT

export <msgno> <filename>

export_users [<filename>]

FILTERING

filtering...