2 # please put your help in in alphabetical order
4 # a string search is done in the command field (case is ignored)
5 # and all commands matching the asked for command are printed out
7 # the order of the fields in each header is
8 # privilege, command, Description
9 # if the command ends in a - then that line isn't printed, but any
10 # subsequent lines are
12 # Comment lines are indented before printing
14 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
15 <text> is the text of the announcement you wish to broadcast
17 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
18 This will send your announcement cluster wide
20 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
22 === 0^APROPOS <string>^Search help database for <string>
23 Search the help database for <string> (it isn't case sensitive), and print
24 the names of all the commands that may be relevant.
26 === 0^BYE^Exit from the cluster
27 This will disconnect you from the cluster
29 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
30 Start a connection process that will culminate in a new connection to the
31 DX cluster <callsign>. This process creates a new 'client' process which will
32 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
33 necessary to traverse the network(s) to logon to the cluster <callsign>.
35 === 9^CATCH <node call> All|[<msgno> ...]^Mark a message as sent
36 === 9^UNCATCH <node call> All|[msgno> ...]^Unmark a message as sent
37 When you send messages the fact that you have forwarded it to another node
38 is remembered so that it isn't sent again. When you have a new partner
39 node and you add their callsign to your /spider/msg/forward.pl file, all
40 outstanding non-private messages will be forwarded to them. This may well
41 be ALL the non-private messages. You can prevent this by using these
45 catch GB7DJK 300 301 302 303
47 and to undo what you have just done:-
50 uncatch GB7DJK 300 301 302 303
52 which will arrange for them to be forward candidates again.
54 === 0^DBAVAIL^Show a list of all the Databases in the system
55 Title says it all really, this command lists all the databases defined
56 in the system. It is also aliased to SHOW/COMMAND.
58 === 9^DBCREATE <name>^Create a database entry
59 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
60 === 9^DBCREATE <name> remote <node>^Create a remote database entry
61 DBCREATE allows you to define a database in the system. It doesn't actually
62 create anything, just defines it.
64 The databases that are created are simple DB_File hash databases, they are
65 therefore already 'indexed'.
67 You can define a local database with the first form of the command eg:
71 You can also chain databases with the addition of the 'chain' keyword.
72 This will search each database one after the other. A typical example
75 DBCREATE sdx_qsl chain sql_ad
77 No checking is done to see if the any of the chained databases exist, in
78 fact it is usually better to do the above staement first then do each of
79 the chained databases.
81 Databases can exist offsite. To define a database that lives on another
84 DBCREATE buckmaster remote gb7dxc
86 Remote databases cannot be chained; however, the last database in a
87 a chain can be a remote database eg:
89 DBCREATE qsl chain gb7dxc
91 To see what databases have been defined do:
93 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
95 It would be normal for you to add an entry into your local Aliases file
96 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
97 need to add a line like:-
102 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
111 to work as they may be used to.
113 See DBIMPORT for the importing of existing AK1A format data to databases.
114 See DBSHOW for generic database enquiry
116 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
117 If you want to import or update data in bulk to a database you can use
118 this command. It will either create or update entries into an existing
119 database. For example:-
121 DBIMPORT oblast /tmp/OBLAST.FUL
123 will import the standard OBLAST database that comes with AK1A into the
124 oblast database held locally.
126 === 9^DBREMOVE <dbname>^Delete a database
127 DBREMOVE will completely remove a database entry and also delete any data
128 file that is associated with it.
130 There is no warning, no comeback, no safety net.
136 will remove the oblast database from the system and it will also remove
137 the associated datafile.
141 There is no warning, no comeback, no safety net.
143 You have been warned.
145 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
146 This is the generic user interface to the database to the database system.
147 It is expected that the sysop will add an entry to the local Aliases file
148 so that users can use the more familiar AK1A style of enquiry such as:
152 but if he hasn't and the database really does exist (use DBAVAIL or
153 SHOW/COMMAND to find out) you can do the same thing with:
157 === 9^DEBUG^Set the cluster program into debug mode
158 Executing this command will only have an effect if you are running the cluster
163 It will interrupt the cluster just after the debug command has finished.
164 === 0^DIRECTORY^List messages
165 === 0^DIRECTORY ALL^List all messages
166 === 0^DIRECTORY OWN^List your own messages
167 === 0^DIRECTORY NEW^List all new messages
168 === 0^DIRECTORY TO <call>^List all messages to <call>
169 === 0^DIRECTORY FROM <call>^List all messages from <call>
170 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
171 === 0^DIRECTORY <nn>^List last <nn> messages
172 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
173 List the messages in the messages directory.
175 If there is a 'p' one space after the message number then it is a
176 personal message. If there is a '-' between the message number and the
177 'p' then this indicates that the message has been read.
179 You can use shell escape characters such as '*' and '?' in the <call>
182 You can combine some of the various directory commands together eg:-
186 DIR SUBJECT IOTA 200-250
188 You can abbreviate all the commands to one letter and use ak1a syntax:-
194 Sysops can see all users' messages.
196 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
197 Disconnect any <call> connected locally
199 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
200 This is how you send a DX Spot to other users. You can, in fact, now
201 enter the <freq> and the <call> either way round.
207 will all give the same result. You can add some remarks to the end
208 of the command and they will be added to the spot.
210 DX FR0G 144600 this is a test
212 You can credit someone else by saying:-
214 DX by G1TLH FR0G 144.600 he isn't on the cluster
216 The <freq> is compared against the available bands set up in the
217 cluster. See SHOW/BANDS for more information.
219 === 9^EXPORT <msgno> <filename>^Export a message to a file
220 Export a message to a file. This command can only be executed on a local
221 console with a fully privileged user. The file produced will be in a form
222 ready to be imported back into the cluster by placing it in the import
223 directory (/spider/msg/import).
225 This command cannot overwrite an existing file. This is to provide some
226 measure of security. Any files written will owned by the same user as the
227 main cluster, otherwise you can put the new files anywhere the cluster can
228 access. For example:-
232 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
233 Export the users database to a file in ascii format. If no filename
234 is given then it will export the file to /spider/data/user_asc.
236 If the file already exists it will be renamed to <filename>.o. In fact
237 up to 5 generations of the file can be kept each one with an extra 'o' on the
240 BE WARNED: this will write to any file you have write access to. No check is
241 made on the filename (if any) that you specify.
243 === 1^FORWARD/OPERNAME <call>^Send out information on this <call> to all clusters
244 This command sends out any information held in the user file which can
245 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
246 and Homenode. PC41s are only sent for the information that is available.
248 === 0^HELP^The HELP Command
249 HELP is available for a number of commands. The syntax is:-
253 Where <cmd> is the name of the command you want help on.
255 All commands can be abbreviated, so SHOW/DX can be abbreviated
256 to SH/DX, ANNOUNCE can be shortened to AN and so on.
258 Look at the APROPOS <string> command which will search the help database
259 for the <string> you specify and give you a list of likely commands
260 to look at with HELP.
262 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
263 This command attempts to re-initialise a link to a (usually) AK1A node
264 that has got confused, usually by a protocol loop of some kind. It may
265 work - but you usually will be better off simply disconnecting it (or
266 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
269 Best of luck - you will need it.
271 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
272 Delete a message from the local system. You will only be able to
273 delete messages that you have originated or been sent (unless you are
276 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
277 Delete a message (usually a 'bulletin') from the whole cluster system.
279 This uses the subject field, so any messages that have exactly the
280 same subject will be deleted. Beware!
282 === 0^LINKS^Show which nodes is physically connected
283 This is a quick listing that shows which links are connected and
284 some information about them. See WHO for a list of all connections.
286 === 9^LOAD/ALIASES^Reload the command alias table
287 Reload the /spider/cmd/Aliases file after you have editted it. You
288 will need to do this if you change this file whilst the cluster is
289 running in order for the changes to take effect.
291 === 9^LOAD/BANDS^Reload the band limits table
292 Reload the /spider/data/bands.pl file if you have changed it manually whilst
293 the cluster is running.
295 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
296 Normally, if you change a command file in the cmd or local_cmd tree it
297 will automatially be picked up by the cluster program. Sometimes it
298 can get confused if you are doing a lot of moving commands about or
299 delete a command in the local_cmd tree and want to use the normal one
300 again. Execute this command to reset everything back to the state it
301 was just after a cluster restart.
303 === 9^LOAD/MESSAGES^Reload the system messages file
304 If you change the /spider/perl/Messages file (usually whilst
305 fiddling/writing new commands) you can have them take effect during a
306 cluster session by executing this command. You need to do this if get
309 unknown message 'xxxx' in lang 'en'
311 === 9^LOAD/PREFIXES^Reload the prefix table
312 Reload the /spider/data/prefix_data.pl file if you have changed it
313 manually whilst the cluster is running.
315 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
316 MERGE allows you to bring your spot and wwv database up to date. By default
317 it will request the last 10 spots and 5 WWVs from the node you select. The
318 node must be connected locally.
320 You can request any number of spots or wwv and although they will be appended
321 to your databases they will not duplicate any that have recently been added
322 (the last 2 days for spots and last month for WWV data).
324 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
325 Alter message parameters like To, From, Subject, whether private or bulletin
326 or return receipt (RR) is required or whether to keep this message from timing
329 MSG TO <msgno> <call> - change TO callsign to <call>
330 MSG FRom <msgno> <call> - change FROM callsign to <call>
331 MSG PRrivate <msgno> - set private flag
332 MSG NOPRrivate <msgno> - unset private flag
333 MSG RR <msgno> - set RR flag
334 MSG NORR <msgno> - unset RR flag
335 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
336 MSG NOKEep <msgno> - unset the keep flag
337 MSG SUbject <msgno> <new> - change the subject to <new>
338 MSG WAittime <msgno> - remove any waitting time for this message
339 MSG NOREad <msgno> - mark message as unread
340 MSG REad <msgno> - mark message as read
341 MSG QUeue - queue any outstanding bulletins
342 MSG QUeue 1 - queue any outstanding private messages
344 You can look at the status of a message by using:-
348 This will display more information on the message than DIR does.
350 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
351 Send some arbitrary text to a locally connected callsign. No
352 processing is done on the text. This command allows you to send PC
353 Protocol to unstick things if problems arise (messages get stuck
356 pc gb7djk PC33^GB7TLH^GB7DJK^400^
358 pc G1TLH Try doing that properly!!!
360 === 1^PING <node>^Send a ping command to another cluster
361 This command is used to estimate the quality of the link to another cluster.
362 The time returned is the length of time taken for a PC51 to go to another
363 cluster and be returned.
365 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
366 You can get rid of any message to or originating from your callsign using
367 this command. You can remove more than one message at a time.
369 === 5^KILL <from>-<to>^Remove a range of messages from the system
370 === 5^KILL FROM <call>^Remove all messages from a callsign
371 === 5^KILL TO <call>^Remove all messages to a callsign
372 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
373 Remove this message from the entire cluster system as well as your node.
376 As a sysop you can kill any message on the system.
378 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
379 Send any text you like to the callsign requested. This is used mainly to send
380 PC protocol to connected nodes either for testing or to unstick things.
382 You can also use in the same way as a talk command to a connected user but
383 without any processing, added of "from <blah> to <blah" or whatever.
385 === 1^PING <node call>^Find out the delays an a circuit to another node
386 This command will enable sysops to determine the speed of an inter-cluster
389 Any visible cluster node can be PINGed.
391 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
392 This command allows you to send nearly any command to another DX Cluster
393 node that is connected to the system.
395 Whether you get any output is dependant on a) whether the other system knows
396 that the node callsign of this cluster is in fact a node b) whether the
397 other system is allowing RCMDs from this node and c) whether you have
398 permission to send this command at all.
400 === 0^READ^Read the next unread personal message addressed to you
401 === 0^READ <msgno>^Read the specified message
402 You can read any messages that are sent as 'non-personal' and also any
403 message either sent by or sent to your callsign.
406 As a sysop you may read any message on the system
408 === 0^REPLY^Reply (privately) to the last message that you have read
409 === 0^REPLY <msgno>^Reply (privately) to the specified message
410 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
411 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
412 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
413 You can reply to a message and the subject will automatically have
414 "Re:" inserted in front of it, if it isn't already present.
416 You can also use all the extra qualifiers such as RR, PRIVATE,
417 NOPRIVATE, B that you can use with the SEND command (see SEND
420 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
421 === 0^SEND RR <call>^Send a message and ask for a read receipt
422 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
423 === 0^SEND PRIVATE <call>^Send a personal message
424 === 0^SEND NOPRIVATE <call>^Send a message to all stations
425 All the SEND commands will create a message which will be sent either to
426 an individual callsign or to one of the 'bulletin' addresses.
428 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
429 it will mark the message as personal and send it to the cluster node that
430 that callsign is connected to.
432 You can have more than one callsign in all of the SEND commands.
434 You can have multiple qualifiers so that you can have for example:-
436 SEND RR COPY 123 PRIVATE G1TLH G0RDI
438 which should send a copy of message 123 to G1TLH and G0RDI and you will
439 receive a read receipt when they have read the message.
441 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
442 SP is an alias for SEND PRIVATE
444 === 0^SET/ADDRESS <your address>^Record your postal address
446 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
447 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
449 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
451 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
452 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
454 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
456 === 9^SET/DEBUG <name>^Add a debug level to the debug set
457 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
459 === 0^SET/DX^Allow DX messages to come out on your terminal
460 === 0^UNSET/DX^Stop DX messages coming out on your terminal
462 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
463 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
464 A standard feature which is enabled in version 1.43 and above is
465 that if the spotter's grid square is known it is output on the end
466 of a DX announcement (there is just enough room). Some user programs
467 cannot cope with this. You can use this command to reset (or set)
470 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
472 === 0^SET/ECHO^Make the cluster echo your input
473 === 0^UNSET/ECHO^Stop the cluster echoing your input
474 If you are connected via a telnet session, different implimentations
475 of telnet handle echo differently depending on whether you are
476 connected via port 23 or some other port. You can use this command
477 to change the setting appropriately.
479 The setting is stored in your user profile.
481 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
483 === 0^SET/HERE^Tell the system you are present at your terminal
484 === 0^UNSET/HERE^Tell the system you are absent from your terminal
486 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
487 Tell the cluster system where you normally connect to. Any Messages sent
488 to you will normally find their way there should you not be connected.
492 === 9^SET/ISOLATE^Isolate a node from the rest of the network
493 Connect a node to your system in such a way that you are a full protocol
494 member of its network and can see all spots on it, but nothing either leaks
495 out from it nor goes back into from the rest of the nodes connected to you.
497 You can potentially connect several nodes in this way.
499 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
500 Remove isolation from a node - SET/ISOLATE
502 === 0^SET/LANGUAGE <lang>^Set the language you want to use
503 You can select the language that you want the cluster to use. Currently
504 the languages available are en (english) and nl (dutch).
506 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
507 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
508 In order to get accurate headings and such like you must tell the system
509 what your latitude and longitude is. If you have not yet done a SET/QRA
510 then this command will set your QRA locator for you. For example:-
511 SET/LOCATION 52 22 N 0 57 E
513 === 0^SET/LOGININFO^Inform when a station logs in locally
514 === 0^UNSET/LOGININFO^Inform when a station logs out locally
516 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
517 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
519 === 0^SET/NAME <your name>^Set your name
520 Tell the system what your name is eg:-
523 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
524 Tell the system that the call(s) are to be treated as AK1A cluster and
525 fed PC Protocol rather normal user commands.
527 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
528 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
529 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
530 counter which is decremented on every outgoing ping and then reset to
531 the 'obscount' value on every incoming ping. The default value of this
534 What this means is that a neighbouring node will be pinged twice at
535 (default) 300 second intervals and if no reply has been heard just before
536 what would be the third attempt, that node is disconnected.
538 If a ping is heard then the obscount is reset to the full value. Using
539 default values, if a node has not responded to a ping within 15 minutes,
542 === 0^SET/PAGE <lines per page>^Set the lines per page
543 Tell the system how many lines you wish on a page when the number of line
544 of output from a command is more than this. The default is 20. Setting it
545 explicitly to 0 will disable paging.
549 The setting is stored in your user profile.
551 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
552 As from release 1.35 all neighbouring nodes are pinged at regular intervals
553 in order to determine the rolling quality of the link and, in future, to
554 affect routing decisions. The default interval is 300 secs or 5 minutes.
556 You can use this command to set a different interval. Please don't.
558 But if you do the value you enter is treated as minutes up 60 and seconds
559 for numbers greater than that.
561 This is used also to help determine when a link is down at the far end
562 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
563 for more information.
565 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
566 Set the privilege level on a callsign. The privilege levels that pertain
567 to commands are as default:-
569 1 - allow remote nodes normal user RCMDs
570 5 - various privileged commands (including shutdown, but not disc-
571 connect), the normal level for another node.
572 8 - more privileged commands (including disconnect)
573 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
575 If you are a sysop and you come in as a normal user on a remote connection
576 your privilege will automatically be set to 0.
578 === 9^SET/PASSWORD <callsign> <string>^Set a users password
579 The password for a user can only be set by a full sysop. The string
580 can contain any characters but any spaces are removed (you can type in
581 spaces - but they won't appear in the password). You can see the
582 result with STAT/USER.
584 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
585 Tell the system that the call(s) are to be treated as DXSpider node and
586 fed new style DX Protocol rather normal user commands.
588 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
589 === 0^SET/QRA <locator>^Set your QRA locator
590 Tell the system what your QRA (or Maidenhead) locator is. If you have not
591 done a SET/LOCATION then your latitude and longitude will be set roughly
592 correctly (assuming your locator is correct ;-). For example:-
595 === 0^SET/QTH <your qth>^Set your QTH
596 Tell the system where you are. For example:-
597 SET/QTH East Dereham, Norfolk
599 === 0^SET/TALK^Allow TALK messages to come out on your terminal
600 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
602 === 0^SET/WCY^Allow WCY messages to come out on your terminal
603 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
605 === 0^SET/WWV^Allow WWV messages to come out on your terminal
606 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
608 === 0^SET/WX^Allow WX messages to come out on your terminal
609 === 0^UNSET/WX^Stop WX messages coming out on your terminal
611 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
612 This is very nearly the same as SHOW/TIME, the only difference the format
613 of the date string if no arguments are given.
615 If no prefixes or callsigns are given then this command returns the local
616 time and UTC as the computer has it right now. If you give some prefixes
617 then it will show UTC and UTC + the local offset (not including DST) at
618 the prefixes or callsigns that you specify.
620 === 0^SHOW/DX^Interrogate the spot database
621 If you just type SHOW/DX you will get the last so many spots
622 (sysop configurable, but usually 10).
624 In addition you can add any number of these commands in very nearly
625 any order to the basic SHOW/DX command, they are:-
627 on <band> - eg 160m 20m 2m 23cm 6mm
628 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
630 <number> - the number of spots you want
631 <from>-<to> - <from> spot no <to> spot no in the selected list
633 <prefix> - for a spotted callsign beginning with <prefix>
634 *<suffix> - for a spotted callsign ending in <suffix>
635 *<string>* - for a spotted callsign containing <string>
637 day <number> - starting <number> days ago
638 day <from>-<to> - <from> days <to> days ago
640 info <text> - any spots containing <text> in the info or remarks
642 by <call> - any spots spotted by <call> (spotter <call> is the
645 qsl - this automatically looks for any qsl info on the call
646 held in the spot database.
648 iota [<iota>] - If the iota island number is missing it will look for
649 the string iota and anything which looks like an iota
650 island number. If you specify then it will look for
653 qra [<locator>] - this will look for the specific locator if you specify
654 one or else anything that looks like a locator.
659 SH/DX on 20m info iota
660 SH/DX 9a on vhf day 30
666 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
667 This command takes the <prefix> (which can be a full or partial
668 callsign if desired), looks up which internal country number it is
669 and then displays all the spots as per SH/DX for that country.
671 The options for SHOW/DX also apply to this command.
675 SH/DXCC W on 20m info iota
677 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
678 SHOW/FILES on its own will show you a list of the various fileareas
679 available on the system. To see the contents of a particular file
682 where <filearea> is the name of the filearea you want to see the
685 You can also use shell globbing characters like '*' and '?' in a
686 string to see a selection of files in a filearea eg:-
687 SH/FILES bulletins arld*
689 See also TYPE - to see the contents of a file.
691 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
693 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
695 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
696 Show the Moon rise and set times for a (list of) prefixes or callsigns,
697 together with the azimuth and elevation of the sun currently at those
700 If you don't specify any prefixes or callsigns, it will show the times for
701 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
702 together with the current azimuth and elevation.
704 In addition, it will show the gain or loss dB relative to the nominal
705 distance of 385,000Km due to the ellipsoidal nature of the orbit.
707 If all else fails it will show the Moonrise and set times for the node
708 that you are connected to.
715 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
716 This command allow you to estimate the likelihood of you contacting
717 a station with the prefix you have specified. The output assumes a modest
718 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
720 The result predicts the most likely operating frequencies and signal
721 levels for high frequency (shortwave) radio propagation paths on
722 specified days of the year and hours of the day. It is most useful for
723 paths between 250 km and 6000 km, but can be used with reduced accuracy
724 for paths shorter or longer than this.
726 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
727 used to predict the MUF given the predicted flux, day of the year,
728 hour of the day and geographic coordinates of the transmitter and
729 receiver. This routine is reasonably accurate for the purposes here,
730 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
731 than the programs used by major shortwave broadcasting organizations,
732 such as the Voice of America.
734 The command will display some header information detailing its
735 assumptions, together with the locations, latitude and longitudes and
736 bearings. It will then show UTC (UT), local time at the other end
737 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
738 (Zen) and the likely signal strengths. Then for each frequency for which
739 the system thinks there is a likelihood of a circuit it prints a value.
741 The value is currently a likely S meter reading based on the conventional
742 6dB / S point scale. If the value has a '+' appended it means that it is
743 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
744 there is likely to be much fading and by an 's' that the signal is likely
747 By default SHOW/MUF will show the next two hours worth of data. You
748 can specify anything up to 24 hours worth of data by appending the no of
749 hours required after the prefix. For example:-
755 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
756 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
757 Location Lat / Long Azim
758 East Dereham, Norfolk 52 41 N 0 57 E 47
759 United-States-W 43 0 N 87 54 W 299
760 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
761 18 23 11.5 -35 mS0+ mS2 S3
762 19 0 11.2 -41 mS0+ mS2 S3
764 indicating that you will have weak, fading circuits on top band and
765 80m but usable signals on 40m (about S3).
771 will get you the above display, but with the next 24 hours worth of
777 Gives you an estimate of the long path propagation characterics. It
778 should be noted that the figures will probably not be very useful, nor
779 terrible accurate, but it is included for completeness.
781 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
782 Show the type and version (if connected) of the nodes specified on the
783 command line. If no callsigns are specified then a sorted list of all
784 the non-user callsigns known to the system will be displayed.
786 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
787 This command takes the <callsign> (which can be a full or partial
788 callsign or a prefix), looks up which internal country number
789 it is and then displays all the relevant prefixes for that country
790 together with the internal country no, the CQ and ITU regions.
794 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
795 Show the name and location where every program module was load from. This
796 is useful for checking where you think you have loaded a .pm file from.
798 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
799 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
800 This is a multipurpose command that allows you either to calculate the
801 distance and bearing between two locators or (if only one locator is
802 given on the command line) the distance and beraing from your station
803 to the locator. For example:-
808 The first example will show the distance and bearing to the locator from
809 yourself, the second example will calculate the distance and bearing from
810 the first locator to the second. You can use 4 or 6 character locators.
812 It is also possible to convert a latitude and longitude to a locator by
813 using this command with a latitude and longitude as an argument, for
816 SH/QRA 52 41 N 0 58 E
818 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
819 Show the tracking data from your location to the satellite of your choice
820 from now on for the next few hours.
822 If you use this command without a satellite name it will display a list
823 of all the satellites known currently to the system.
825 If you give a name then you can obtain tracking data of all the passes
826 that start and finish 5 degrees below the horizon. As default it will
827 give information for the next three hours for every five minute period.
829 You can alter the number of hours and the step size, within certain
832 Each pass in a period is separated with a row of '-----' characters
839 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
840 Show the sun rise and set times for a (list of) prefixes or callsigns,
841 together with the azimuth and elevation of the sun currently at those
844 If you don't specify any prefixes or callsigns, it will show the times for
845 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
846 together with the current azimuth and elevation.
848 If all else fails it will show the sunrise and set times for the node
849 that you are connected to.
856 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
857 If no prefixes or callsigns are given then this command returns the local
858 time and UTC as the computer has it right now. If you give some prefixes
859 then it will show UTC and UTC + the local offset (not including DST) at
860 the prefixes or callsigns that you specify.
862 === 0^SHOW/WCY^Show last 10 WCY broadcasts
863 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
864 Display the most recent WCY information that has been received by the system
866 === 0^SHOW/WWV^Show last 10 WWV broadcasts
867 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
868 Display the most recent WWV information that has been received by the system
870 === 5^SHUTDOWN^Shutdown the cluster
871 Shutdown the cluster and disconnect all the users
873 === 5^STAT/DB <dbname>^Show the status of a database
874 Show the internal status of a database descriptor.
876 Depending on your privilege level you will see more or less information.
877 This command is unlikely to be of much use to anyone other than a sysop.
879 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
880 Show the internal status of the channel object either for the channel that
881 you are on or else for the callsign that you asked for.
883 Only the fields that are defined (in perl term) will be displayed.
885 === 5^STAT/MSG <msgno>^Show the status of a message
886 This command shows the internal status of a message and includes information
887 such as to whom it has been forwarded, its size, origin etc etc.
889 === 5^STAT/USER [<callsign>]^Show the full status of a user
890 Shows the full contents of a user record including all the secret flags
893 Only the fields that are defined (in perl term) will be displayed.
895 === 0^SYSOP^Regain your privileges if you login remotely
896 The system automatically reduces your privilege level to that of a
897 normal user if you login in remotely. This command allows you to
898 regain your normal privilege level. It uses the normal system: five
899 numbers are returned that are indexes into the character array that is
900 your assigned password (see SET/PASSWORD). The indexes start from
903 You are expected to return a string which contains the characters
904 required in the correct order. You may intersperse those characters
905 with others to obscure your reply for any watchers. For example (and
906 these values are for explanation :-):
908 password = 012345678901234567890123456789
912 aa2bbbb0ccc5ddd7xxx3n
916 They will all match. If there is no password you will still be offered
917 numbers but nothing will happen when you input a string. Any match is
920 === 0^TALK <call> [<text>]^Send a text message to another station
921 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
922 Send a short message to any other station that is visible on the cluster
923 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
924 command, they don't have to be connected locally.
926 The second form of TALK is used when other cluster nodes are connected
927 with restricted information. This usually means that they don't send
928 the user information usually associated with logging on and off the cluster.
930 If you know that G3JNB is likely to be present on GB7TLH, but you can only
931 see GB7TLH in the SH/C list but with no users, then you would use the
932 second form of the talk message.
934 If you want to have a ragchew with someone you can leave the text message
935 out and the system will go into 'Talk' mode. What this means is that a
936 short message is sent to the recipient telling them that you are in a
937 'Talking' frame of mind and then you just type - everything you send will
938 go to the station that you asked for.
940 All the usual announcements, spots and so on will still come out on your
943 If you want to do something (such as send a spot) you preceed the normal
944 command with a '/' character, eg:-
946 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
949 To leave talk mode type:
953 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
954 Type out the contents of a file in a filearea. So, for example, in
955 filearea 'bulletins' you want to look at file 'arld051' you would
957 TYPE bulletins/arld051
959 See also SHOW/FILES to see what fileareas are available and a
962 === 0^WHO^Show who is physically connected
963 This is a quick listing that shows which callsigns are connected and
964 what sort of connection they have
966 === 0^WX <text>^Send a weather message to local users
967 === 0^WX FULL <text>^Send a weather message to all cluster users
968 === 5^WX SYSOP <text>^Send a weather message to other clusters only
969 Weather messages can sometimes be useful if you are experiencing an extreme
970 that may indicate enhanced conditions