1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Administration Manual v1.47: The DXSpider command set</TITLE>
6 <LINK HREF="adminmanual-8.html" REL=previous>
7 <LINK HREF="adminmanual.html#toc9" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-8.html">Previous</A>
13 <A HREF="adminmanual.html#toc9">Contents</A>
15 <H2><A NAME="s9">9. The DXSpider command set</A></H2>
17 <P>Below is a complete list of commands available from the cluster prompt.
18 Most maintenance tasks are automatic but there are some commands that are useful
19 for a sysop. These are listed below in alphabetical order. The number in
20 brackets following the command name is the permissions level needed to use
23 <H2><A NAME="ss9.1">9.1 accept/announce (0)</A>
26 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
27 line for announce</CODE>
29 <P>Create an 'accept this announce' line for a filter.
30 <P>An accept filter line means that if the announce matches this filter it is
31 passed onto the user. See HELP FILTERS for more info. Please read this
32 to understand how filters work - it will save a lot of grief later on.
33 <P>You can use any of the following things in this line:-
37 info <string> eg: iota or qsl
38 by <prefixes> eg: G,M,2
40 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
41 origin_itu <numbers>
42 origin_zone <numbers>
47 wx 1 filter WX announces
48 dest <prefixes> eg: 6MUK,WDX (distros)
56 acc/ann 2 by_zone 14,15,16
57 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
67 <P>This filter would only allow announces that were posted buy UK stations.
68 You can use the tag 'all' to accept everything eg:
75 <P>but this probably for advanced users...
77 <H2><A NAME="ss9.2">9.2 accept/announce (extended for sysops) (8)</A>
80 <P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
82 <P>This version allows a sysop to set a filter for a callsign as well as the
83 default for nodes and users eg:-
88 accept/ann input node_default by G,M,2
89 accept/ann user_default by G,M,2
93 <H2><A NAME="ss9.3">9.3 accept/spots (0)</A>
96 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter line for spots</CODE>
98 <P>Create an 'accept this spot' line for a filter.
100 <P>An accept filter line means that if the spot matches this filter it is
101 passed onto the user. See HELP FILTERS for more info. Please read this
102 to understand how filters work - it will save a lot of grief later on.
103 <P>You can use any of the following things in this line:-
107 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
108 on <range> same as 'freq'
109 call <prefixes> eg: G,PA,HB9
110 info <string> eg: iota or qsl
112 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
113 call_itu <numbers>
114 call_zone <numbers>
119 channel <prefixes>
123 <P>For frequencies, you can use any of the band names defined in
124 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
125 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
126 this is more efficient than saying simply: freq HF (but don't get
127 too hung up about that)
133 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
136 <P>You can use the tag 'all' to accept everything, eg:
143 <P>but this probably for advanced users...
145 <H2><A NAME="ss9.4">9.4 accept/spots (extended for sysops) (8)</A>
148 <P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
150 <P>This version allows a sysop to set a filter for a callsign as well as the
151 default for nodes and users eg:-
155 accept/spot db0sue-7 1 by_zone 14,15,16
156 accept/spot node_default all
157 set/hops node_default 10
159 accept/spot user_default by G,M,2
163 <H2><A NAME="ss9.5">9.5 accept/wcy (0)</A>
166 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
168 <P>It is unlikely that you will want to do this, but if you do then you can
169 filter on the following fields:-
173 by <prefixes> eg: G,M,2
175 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
176 origin_itu <numbers>
177 origin_zone <numbers>
181 channel <prefixes>
185 <P>There are no examples because WCY Broadcasts only come from one place and
186 you either want them or not (see UNSET/WCY if you don't want them).
187 <P>This command is really provided for future use.
188 <P>See HELP FILTER for information.
190 <H2><A NAME="ss9.6">9.6 accept/wcy (extended for sysops) (8)</A>
193 <P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
194 WCY filter sysop version</CODE>
196 <P>This version allows a sysop to set a filter for a callsign as well as the
197 default for nodes and users eg:-
201 accept/wcy node_default all
202 set/hops node_default 10
206 <H2><A NAME="ss9.7">9.7 accept/wwv (0)</A>
209 <P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
211 <P>It is unlikely that you will want to do this, but if you do then you can
212 filter on the following fields:-
216 by <prefixes> eg: G,M,2
218 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
219 origin_itu <numbers>
220 origin_zone <numbers>
224 channel <prefixes>
234 <P>is probably the only useful thing to do (which will only show WWV broadcasts
235 by stations in the US).
236 <P>See HELP FILTER for information.
238 <H2><A NAME="ss9.8">9.8 accept/wwv (extended for sysops) (8)</A>
241 <P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
242 WWV filter sysop version</CODE>
244 <P>This version allows a sysop to set a filter for a callsign as well as the
245 default for nodes and users eg:-
249 accept/wwv db0sue-7 1 by_zone 4
250 accept/wwv node_default all
251 set/hops node_default 10
253 accept/wwv user_default by W,K
257 <H2><A NAME="ss9.9">9.9 announce (0)</A>
260 <P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
262 <P>Send an announcement to LOCAL users only, where <text> is the text
263 of the announcement you wish to broadcast
265 <H2><A NAME="ss9.10">9.10 announce full (0)</A>
268 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
270 <P>This command will send your announcement across the whole cluster
274 <H2><A NAME="ss9.11">9.11 announce sysop (5)</A>
277 <P><CODE><B>announce sysop <text></B></CODE>
279 <P>Send an announcement to Sysops only
281 <H2><A NAME="ss9.12">9.12 apropos (0)</A>
284 <P><CODE><B>apropos <string></B> Search the help database</CODE>
286 <P>Search the help database for <string> (it isn't case sensitive),
287 and print the names of all the commands that may be relevant.
289 <H2><A NAME="ss9.13">9.13 bye (0)</A>
292 <P><CODE><B>bye</B> Exit from the cluster</CODE>
294 <P>This will disconnect you from the cluster
296 <H2><A NAME="ss9.14">9.14 catchup (5)</A>
299 <P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
301 <P>When you send messages the fact that you have forwarded it to another node
302 is remembered so that it isn't sent again. When you have a new partner
303 node and you add their callsign to your /spider/msg/forward.pl file, all
304 outstanding non-private messages will be forwarded to them. This may well
305 be ALL the non-private messages. You can prevent this by using these
311 catchup GB7DJK 300 301 302 303 500-510
314 <P>and to undo what you have just done:-
319 uncatchup GB7DJK 300 301 302 303 500-510
322 <P>which will arrange for them to be forward candidates again.
323 <P>Order is not important.
325 <H2><A NAME="ss9.15">9.15 clear/spots (0)</A>
328 <P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
330 <P>This command allows you to clear (remove) a line in a spot filter or to
331 remove the whole filter.
332 <P>If you have a filter:-
337 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
347 <P>you will be left with:-
351 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
361 <P>the filter will be completely removed.
364 <H2><A NAME="ss9.16">9.16 connect (5) </A>
367 <P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
369 <P>Start a connection process that will culminate in a new connection to the
370 DX cluster <callsign>. This process creates a new 'client' process which will
371 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
372 necessary to traverse the network(s) to logon to the cluster <callsign>.
374 <H2><A NAME="ss9.17">9.17 dbavail (0)</A>
377 <P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
379 <P>The title says it all really, this command lists all the databases defined
380 in the system. It is also aliased to SHOW/COMMAND.
382 <H2><A NAME="ss9.18">9.18 dbcreate (9)</A>
385 <P><CODE><B>dbcreate <name></B> Create a database entry<BR>
386 <B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
387 <B>dbcreate <name> remote <node></B> Create a remote database
390 <P>DBCREATE allows you to define a database in the system. It doesn't actually
391 create anything, just defines it.
392 <P>The databases that are created are simple DB_File hash databases, they are
393 therefore already 'indexed'.
394 <P>You can define a local database with the first form of the command eg:
396 <P>You can also chain databases with the addition of the 'chain' keyword.
397 This will search each database one after the other. A typical example
399 <P>DBCREATE sdx_qsl chain sql_ad
400 <P>No checking is done to see if the any of the chained databases exist, in
401 fact it is usually better to do the above statement first then do each of
402 the chained databases.
403 <P>Databases can exist offsite. To define a database that lives on another
405 <P>DBCREATE buckmaster remote gb7dxc
406 <P>Remote databases cannot be chained; however, the last database in a
407 a chain can be a remote database eg:
408 <P>DBCREATE qsl chain gb7dxc
409 <P>To see what databases have been defined do:
410 <P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
411 <P>It would be normal for you to add an entry into your local Aliases file
412 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
413 need to add a line like:-
420 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
428 <P>to work as they may be used to.
429 <P>See DBIMPORT for the importing of existing AK1A format data to databases.
430 See DBSHOW for generic database enquiry
432 <H2><A NAME="ss9.19">9.19 dbimport (9)</A>
435 <P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
437 <P>If you want to import or update data in bulk to a database you can use
438 this command. It will either create or update entries into an existing
439 database. For example:-
440 <P>DBIMPORT oblast /tmp/OBLAST.FUL
441 <P>will import the standard OBLAST database that comes with AK1A into the
442 oblast database held locally.
444 <H2><A NAME="ss9.20">9.20 dbremove (9)</A>
447 <P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
449 <P>DBREMOVE will completely remove a database entry and also delete any data
450 file that is associated with it.
451 <P>There is no warning, no comeback, no safety net.
454 <P>will remove the oblast database from the system and it will also remove
455 the associated datafile.
457 <P>There is no warning, no comeback, no safety net.
458 <P>You have been warned.
460 <H2><A NAME="ss9.21">9.21 dbshow (0)</A>
463 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
465 <P>This is the generic user interface to the database to the database system.
466 It is expected that the sysop will add an entry to the local Aliases file
467 so that users can use the more familiar AK1A style of enquiry such as:
474 <P>but if he hasn't and the database really does exist (use DBAVAIL or
475 SHOW/COMMAND to find out) you can do the same thing with:
484 <H2><A NAME="ss9.22">9.22 debug (9)</A>
487 <P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
489 <P>Executing this command will only have an effect if you are running the cluster
497 <P>It will interrupt the cluster just after the debug command has finished.
499 <H2><A NAME="ss9.23">9.23 directory (0)</A>
502 <P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
503 <B>directory own</B> List your own messages<BR>
504 <B>directory new</B> List all new messages<BR>
505 <B>directory to <call></B> List all messages to <call><BR>
506 <B>directory from <call></B> List all messages from <call><BR>
507 <B>directory subject <string></B> List all messages with <string> in subject<BR>
508 <B>directory <nn></B> List last <nn> messages<BR>
509 <B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
511 <P>List the messages in the messages directory.
512 <P>If there is a 'p' one space after the message number then it is a
513 personal message. If there is a '-' between the message number and the
514 'p' then this indicates that the message has been read.
515 <P>You can use shell escape characters such as '*' and '?' in the <call>
517 <P>You can combine some of the various directory commands together eg:-
523 DIR SUBJECT IOTA 200-250
526 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-
536 <H2><A NAME="ss9.24">9.24 directory (extended for sysops) (5)</A>
539 <P>Works just like the user command except that sysops can see ALL messages.
541 <H2><A NAME="ss9.25">9.25 disconnect (8)</A>
544 <P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
546 <P>Disconnect any <call> connected locally
548 <H2><A NAME="ss9.26">9.26 dx (0)</A>
551 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
553 <P>This is how you send a DX Spot to other users. You can, in fact, now
554 enter the <freq> and the <call> either way round.
563 <P>will all give the same result. You can add some remarks to the end
564 of the command and they will be added to the spot.
568 DX FR0G 144600 this is a test
571 <P>You can credit someone else by saying:-
575 DX by G1TLH FR0G 144.600 he isn't on the cluster
578 <P>The <freq> is compared against the available bands set up in the
579 cluster. See SHOW/BANDS for more information.
581 <H2><A NAME="ss9.27">9.27 export (9)</A>
584 <P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
586 <P>Export a message to a file. This command can only be executed on a local
587 console with a fully privileged user. The file produced will be in a form
588 ready to be imported back into the cluster by placing it in the import
589 directory (/spider/msg/import).
590 <P>This command cannot overwrite an existing file. This is to provide some
591 measure of security. Any files written will owned by the same user as the
592 main cluster, otherwise you can put the new files anywhere the cluster can
593 access. For example:-
594 <P>EXPORT 2345 /tmp/a
596 <H2><A NAME="ss9.28">9.28 export_users (9)</A>
599 <P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
601 <P>Export the users database to a file in ascii format. If no filename
602 is given then it will export the file to /spider/data/user_asc.
603 <P>If the file already exists it will be renamed to <filename>.o. In fact
604 up to 5 generations of the file can be kept each one with an extra 'o' on the
606 <P>BE WARNED: this will write to any file you have write access to. No check is
607 made on the filename (if any) that you specify.
609 <H2><A NAME="ss9.29">9.29 forward/latlong (8)</A>
612 <P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
614 <P>This command sends all the latitude and longitude information that your
615 cluster is holding against callsigns. One advantage of recieving this
616 information is that more locator information is held by you. This
617 means that more locators are given on the DX line assuming you have
618 <EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
619 it is not recommended on slow links.
621 <H2><A NAME="ss9.30">9.30 forward/opername (1)</A>
624 <P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
626 <P>This command sends out any information held in the user file which can
627 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
628 and Homenode. PC41s are only sent for the information that is available.
630 <H2><A NAME="ss9.31">9.31 help (0)</A>
633 <P><CODE><B>help <cmd></B> Get help on a command</CODE>
635 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
636 to SH/DX, ANNOUNCE can be shortened to AN and so on.
637 <P>Look at the APROPOS <string> command which will search the help database
638 for the <string> you specify and give you a list of likely commands
639 to look at with HELP.
641 <H2><A NAME="ss9.32">9.32 init (5)</A>
644 <P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
646 <P>This command attempts to re-initialise a link to a (usually) AK1A node
647 that has got confused, usually by a protocol loop of some kind. It may
648 work - but you usually will be better off simply disconnecting it (or
649 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
651 <P>Best of luck - you will need it.
653 <H2><A NAME="ss9.33">9.33 kill (0)</A>
656 <P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
658 <P>Delete a message from the local system. You will only be able to
659 delete messages that you have originated or been sent (unless you are
662 <H2><A NAME="ss9.34">9.34 kill (5)</A>
665 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
666 <B>kill from <call></B> Remove all messages from a callsign<BR>
667 <B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
669 <P>You can get rid of any message to or originating from your callsign using
670 this command. You can remove more than one message at a time.
671 <P>As a sysop you can kill any message on the system.
673 <H2><A NAME="ss9.35">9.35 kill full (5)</A>
676 <P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
678 <P>Delete a message (usually a 'bulletin') from the whole cluster system.
679 <P>This uses the subject field, so any messages that have exactly the same subject
680 will be deleted. Beware!
682 <H2><A NAME="ss9.36">9.36 links (0)</A>
685 <P><CODE><B>links</B> Show which nodes are physically connected</CODE>
687 <P>This is a quick listing that shows which links are connected and
688 some information about them. See WHO for a list of all connections.
691 <H2><A NAME="ss9.37">9.37 load/aliases (9)</A>
694 <P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
696 <P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
697 do this if you change this file whilst the cluster is running in order for the
698 changes to take effect.
701 <H2><A NAME="ss9.38">9.38 load/baddx (9)</A>
704 <P><CODE><B>load/baddx</B> Reload the bad DX table</CODE>
706 <P>Reload the /spider/data/baddx.pl file if you have changed it manually whilst
707 the cluster is running. This table contains the DX Calls that, if spotted,
708 will not be passed on. FR0G and TEST are classic examples.
710 <H2><A NAME="ss9.39">9.39 load/badmsg (9)</A>
713 <P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
715 <P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
716 the cluster is running. This table contains a number of perl regular
717 expressions which are searched for in the fields targetted of each message.
718 If any of them match then that message is immediately deleted on receipt.
720 <H2><A NAME="ss9.40">9.40 load/badwords (9)</A>
723 <P><CODE><B>load/badwords</B> Reload the badwords file</CODE>
725 <P>Reload the /spider/data/badwords file if you have changed it manually whilst
726 the cluster is running. This file contains a list of words which, if found
727 on certain text portions of PC protocol, will cause those protocol frames
728 to be rejected. It will all put out a message if any of these words are
729 used on the announce, dx and talk commands. The words can be one or
730 more on a line, lines starting with '#' are ignored.
732 <H2><A NAME="ss9.41">9.41 load/bands (9)</A>
735 <P><CODE><B>load/bands</B> Reload the band limits table</CODE>
737 <P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
738 the cluster is running.
740 <H2><A NAME="ss9.42">9.42 load/cmd_cache (9)</A>
743 <P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
745 <P>Normally, if you change a command file in the cmd or local_cmd tree it will
746 automatially be picked up by the cluster program. Sometimes it can get confused
747 if you are doing a lot of moving commands about or delete a command in the
748 local_cmd tree and want to use the normal one again. Execute this command to
749 reset everything back to the state it was just after a cluster restart.
751 <H2><A NAME="ss9.43">9.43 load/forward (9)</A>
754 <P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
755 <P>Reload the /spider/msg/forward.pl file if you have changed it
756 manually whilst the cluster is running.
758 <H2><A NAME="ss9.44">9.44 load/messages (9)</A>
761 <P><CODE><B>load/messages</B> Reload the system messages file</CODE>
763 <P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
764 commands) you can have them take effect during a cluster session by executing this
765 command. You need to do this if get something like :-
766 <P>unknown message 'xxxx' in lang 'en'
768 <H2><A NAME="ss9.45">9.45 load/prefixes (9)</A>
771 <P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
773 <P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
774 whilst the cluster is running.
776 <H2><A NAME="ss9.46">9.46 merge (5)</A>
779 <P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
781 <P>MERGE allows you to bring your spot and wwv database up to date. By default
782 it will request the last 10 spots and 5 WWVs from the node you select. The
783 node must be connected locally.
784 <P>You can request any number of spots or wwv and although they will be appended
785 to your databases they will not duplicate any that have recently been added
786 (the last 2 days for spots and last month for WWV data).
788 <H2><A NAME="ss9.47">9.47 msg (9)</A>
791 <P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
793 <P>Alter message parameters like To, From, Subject, whether private or bulletin
794 or return receipt (RR) is required or whether to keep this message from timing
799 MSG TO <msgno> <call> - change TO callsign to <call>
800 MSG FRom <msgno> <call> - change FROM callsign to <call>
801 MSG PRrivate <msgno> - set private flag
802 MSG NOPRrivate <msgno> - unset private flag
803 MSG RR <msgno> - set RR flag
804 MSG NORR <msgno> - unset RR flag
805 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
806 MSG NOKEep <msgno> - unset the keep flag
807 MSG SUbject <msgno> <new> - change the subject to <new>
808 MSG WAittime <msgno> - remove any waitting time for this message
809 MSG NOREad <msgno> - mark message as unread
810 MSG REad <msgno> - mark message as read
811 MSG QUeue - queue any outstanding bulletins
812 MSG QUeue 1 - queue any outstanding private messages
815 <P>You can look at the status of a message by using:-
816 <P>STAT/MSG <msgno>
817 <P>This will display more information on the message than DIR does.
819 <H2><A NAME="ss9.48">9.48 pc (8)</A>
822 <P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
824 <P>Send some arbitrary text to a locally connected callsign. No processing is done on
825 the text. This command allows you to send PC Protocol to unstick things if problems
826 arise (messages get stuck etc). eg:-
827 <P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
828 <P>You can also use in the same way as a talk command to a connected user but
829 without any processing, added of "from <blah> to <blah>" or whatever.
830 <P>pc G1TLH Try doing that properly!!!
832 <H2><A NAME="ss9.49">9.49 ping (1)</A>
835 <P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
837 <P>his command allows you to send a frame to another cluster node on
838 the network and get a return frame. The time it takes to do this
839 is a good indication of the quality of the link. The actual time
840 it takes is output to the console in seconds.
841 Any visible cluster node can be PINGed.
844 <H2><A NAME="ss9.50">9.50 rcmd (1)</A>
847 <P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
849 <P>This command allows you to send nearly any command to another DX Cluster
850 node that is connected to the system.
851 <P>Whether you get any output is dependant on a) whether the other system knows
852 that the node callsign of this cluster is in fact a node b) whether the
853 other system is allowing RCMDs from this node and c) whether you have
854 permission to send this command at all.
856 <H2><A NAME="ss9.51">9.51 read (0)</A>
859 <P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
860 <B>read <msgno></B> Read the specified message<BR></CODE>
862 <P>You can read any messages that are sent as 'non-personal' and also any
863 message either sent by or sent to your callsign.
866 <H2><A NAME="ss9.52">9.52 read (extended for sysops) (5) </A>
869 <P><CODE><B>read <msgno></B> Read a message on the system</CODE>
871 <P>As a sysop you may read any message on the system
873 <H2><A NAME="ss9.53">9.53 reject/announce</A>
876 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
879 <P>Create an 'reject this announce' line for a filter.
880 <P>An reject filter line means that if the announce matches this filter it is
881 passed onto the user. See HELP FILTERS for more info. Please read this
882 to understand how filters work - it will save a lot of grief later on.
883 <P>You can use any of the following things in this line:-
887 info <string> eg: iota or qsl
888 by <prefixes> eg: G,M,2
890 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
891 origin_itu <numbers>
892 origin_zone <numbers>
896 channel <prefixes>
897 wx 1 filter WX announces
898 dest <prefixes> eg: 6MUK,WDX (distros)
905 rej/ann by_zone 14,15,16 and not by G,M,2
908 <P>You can use the tag 'all' to reject everything eg:
915 <P>but this probably for advanced users...
917 <H2><A NAME="ss9.54">9.54 reject/announce (extended for sysops) (8)</A>
920 <P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
922 <P>This version allows a sysop to set a filter for a callsign as well as the
923 default for nodes and users eg:-
928 reject/ann input node_default by G,M,2
929 reject/ann user_default by G,M,2
933 <H2><A NAME="ss9.55">9.55 reject/spots (0)</A>
936 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
938 <P>Create a 'reject this spot' line for a filter.
939 <P>A reject filter line means that if the spot matches this filter it is
940 dumped (not passed on). See HELP FILTERS for more info. Please read this
941 to understand how filters work - it will save a lot of grief later on.
942 <P>You can use any of the following things in this line:-
946 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
947 on <range> same as 'freq'
948 call <prefixes> eg: G,PA,HB9
949 info <string> eg: iota or qsl
951 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
952 call_itu <numbers>
953 call_zone <numbers>
958 channel <prefixes>
961 <P>For frequencies, you can use any of the band names defined in
962 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
963 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
964 this is more efficient than saying simply: on HF (but don't get
965 too hung up about that)
971 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
974 <P>You can use the tag 'all' to reject everything eg:
981 <P>but this probably for advanced users...
983 <H2><A NAME="ss9.56">9.56 reject/spots (extended for sysops) (8)</A>
986 <P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
987 Reject spot filter sysop version </CODE>
989 <P>This version allows a sysop to set a filter for a callsign as well as the
990 default for nodes and users eg:-
994 reject/spot db0sue-7 1 by_zone 14,15,16
995 reject/spot node_default all
996 set/hops node_default 10
998 reject/spot user_default by G,M,2
1000 </CODE></BLOCKQUOTE>
1002 <H2><A NAME="ss9.57">9.57 reject/wcy (0)</A>
1005 <P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
1007 <P>It is unlikely that you will want to do this, but if you do then you can
1008 filter on the following fields:-
1012 by <prefixes> eg: G,M,2
1013 origin <prefixes>
1014 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1015 origin_itu <numbers>
1016 origin_zone <numbers>
1017 by_dxcc <numbers>
1019 by_zone <numbers>
1020 channel <prefixes>
1022 </CODE></BLOCKQUOTE>
1023 <P>There are no examples because WCY Broadcasts only come from one place and
1024 you either want them or not (see UNSET/WCY if you don't want them).
1025 <P>This command is really provided for future use.
1026 <P>See HELP FILTER for information.
1028 <H2><A NAME="ss9.58">9.58 reject/wcy (extended for sysops) (8)</A>
1031 <P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
1032 WCY reject filter sysop version</CODE>
1034 <P>This version allows a sysop to set a filter for a callsign as well as the
1035 default for nodes and users eg:-
1036 <P>reject/wcy gb7djk all
1038 <H2><A NAME="ss9.59">9.59 reject/wwv (0)</A>
1041 <P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
1043 <P>It is unlikely that you will want to do this, but if you do then you can
1044 filter on the following fields:-
1048 by <prefixes> eg: G,M,2
1049 origin <prefixes>
1050 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1051 origin_itu <numbers>
1052 origin_zone <numbers>
1053 by_dxcc <numbers>
1055 by_zone <numbers>
1056 channel <prefixes>
1058 </CODE></BLOCKQUOTE>
1063 reject/wwv by_zone 14,15,16
1065 </CODE></BLOCKQUOTE>
1066 <P>is probably the only useful thing to do (which will only show WWV broadcasts
1067 by stations in the US).
1068 <P>See HELP FILTER for information.
1070 <H2><A NAME="ss9.60">9.60 reject/wwv (extended for sysops) (8)</A>
1073 <P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
1074 WWV reject filter sysop version</CODE>
1076 <P>This version allows a sysop to set a filter for a callsign as well as the
1077 default for nodes and users eg:-
1081 reject/wwv db0sue-7 1 by_zone 4
1082 reject/wwv node_default all
1084 reject/wwv user_default by W
1086 </CODE></BLOCKQUOTE>
1088 <H2><A NAME="ss9.61">9.61 reply (0)</A>
1091 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
1092 <B>reply <msgno></B> Reply (privately) to the specified message<BR>
1093 <B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
1094 <B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
1096 <B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
1098 <P>You can reply to a message and the subject will automatically have
1099 "Re:" inserted in front of it, if it isn't already present.
1100 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
1101 NOPRIVATE, B that you can use with the SEND command (see SEND
1102 for further details)
1104 <H2><A NAME="ss9.62">9.62 send (0)</A>
1107 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
1108 <B>send RR <call></B> Send a message and ask for a read receipt<BR>
1109 <B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
1110 <B>send PRIVATE <call></B> Send a personal message<BR>
1111 <B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
1113 <P>All the SEND commands will create a message which will be sent either to
1114 an individual callsign or to one of the 'bulletin' addresses.
1115 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1116 it will mark the message as personal and send it to the cluster node that
1117 that callsign is connected to.
1118 <P>You can have more than one callsign in all of the SEND commands.
1119 <P>You can have multiple qualifiers so that you can have for example:-
1123 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1125 </CODE></BLOCKQUOTE>
1126 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
1127 receive a read receipt when they have read the message.
1128 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1129 SP is an alias for SEND PRIVATE
1131 <H2><A NAME="ss9.63">9.63 set/address (0)</A>
1134 <P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
1136 <P>Literally, record your address details on the cluster.
1138 <H2><A NAME="ss9.64">9.64 set/announce (0)</A>
1141 <P><CODE><B>set/announce</B> Allow announce messages</CODE>
1143 <P>Allow announce messages to arrive at your terminal.
1145 <H2><A NAME="ss9.65">9.65 set/arcluster (5)</A>
1148 <P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
1149 the node_call an AR-Cluster type node</CODE>
1151 <P>Set the node_call as an AR-Cluster type node
1153 <H2><A NAME="ss9.66">9.66 set/baddx (8)</A>
1156 <P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
1157 of a dx spot being propagated</CODE>
1159 <P>Setting a word as 'baddx' will prevent spots with that word in the callsign
1160 field of a DX spot from going any further. They will not be displayed and they
1161 will not be sent onto other nodes.
1162 <P>The word must be wriiten in full, no wild cards are allowed eg:-
1166 set/baddx FORSALE VIDEO FR0G
1168 </CODE></BLOCKQUOTE>
1169 <P>To allow a word again, use the following command ...
1175 </CODE></BLOCKQUOTE>
1177 <H2><A NAME="ss9.67">9.67 set/badnode (6)</A>
1180 <P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
1181 being propagated</CODE>
1183 <P>Setting a callsign as a 'badnode' will prevent spots from that node
1184 going any further. They will not be displayed and they will not be
1185 sent onto other nodes.
1186 <P>The call can be a full or partial call (or a prefix), eg:-
1192 </CODE></BLOCKQUOTE>
1193 <P>will stop anything from K1TTT (including any SSID's)
1199 </CODE></BLOCKQUOTE>
1200 <P>will allow spots from him again.
1201 <P>Use with extreme care. This command may well be superceded by FILTERing.
1203 <H2><A NAME="ss9.68">9.68 set/badspotter (8)</A>
1206 <P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
1208 <P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
1209 going any further. They will not be displayed and they will not be
1210 sent onto other nodes.
1211 <P>The call must be written in full, no wild cards are allowed eg:-
1215 set/badspotter VE2STN
1217 </CODE></BLOCKQUOTE>
1218 <P>will stop anything from VE2STN. If you want SSIDs as well then you must
1219 enter them specifically.
1223 unset/badspotter VE2STN
1225 </CODE></BLOCKQUOTE>
1226 <P>will allow spots from him again.
1227 <P>Use with extreme care. This command may well be superceded by FILTERing.
1229 <H2><A NAME="ss9.69">9.69 set/beep (0)</A>
1232 <P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
1234 <P>Add a beep to DX and other terminal messages.
1236 <H2><A NAME="ss9.70">9.70 set/clx (5)</A>
1239 <P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
1240 the node_call a CLX type node</CODE>
1242 <P>Set the node_call as a CLX type node
1244 <H2><A NAME="ss9.71">9.71 set/debug (9)</A>
1247 <P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
1249 <P>You can choose to log several different levels. The levels are
1255 <P>You can show what levels you are logging with the <EM>show/debug</EM>
1257 <P>You can remove a debug level with unset/debug <name>
1259 <H2><A NAME="ss9.72">9.72 set/dx (0)</A>
1262 <P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
1264 <P>You can stop DX messages with the <EM>unset/dx</EM> command
1266 <H2><A NAME="ss9.73">9.73 set/dxgrid (0)</A>
1269 <P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
1271 <P>Some logging programs do not like the additional information at
1272 the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
1273 command to remove the grid squares.
1275 <H2><A NAME="ss9.74">9.74 set/dxnet (5)</A>
1278 <P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
1279 the node_call a DXNet type node</CODE>
1281 <P>Set the node_call as a DXNet type node
1283 <H2><A NAME="ss9.75">9.75 set/echo (0)</A>
1286 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
1288 <P>If you are connected via a telnet session, different implimentations
1289 of telnet handle echo differently depending on whether you are
1290 connected via port 23 or some other port. You can use this command
1291 to change the setting appropriately.
1292 <P>You can remove the echo with the <EM>unset/echo</EM> command
1293 <P>The setting is stored in your user profile.
1294 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1296 <H2><A NAME="ss9.76">9.76 set/here (0)</A>
1299 <P><CODE><B>set/here</B> Set the here flag</CODE>
1301 <P>Let others on the cluster know you are here by only displaying your
1302 callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
1303 command to let people know you are away. This simply puts brackets
1304 around your callsign to indicate you are not available.
1306 <H2><A NAME="ss9.77">9.77 set/homenode (0)</A>
1309 <P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
1311 <P>Tell the cluster system where you normally connect to. Any Messages sent
1312 to you will normally find their way there should you not be connected.
1319 </CODE></BLOCKQUOTE>
1321 <H2><A NAME="ss9.78">9.78 set/hops (8)</A>
1324 <P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
1325 Set hop count</CODE>
1327 <P>Set the hop count for a particular type of broadcast for a node.
1328 <P>This command allows you to set up special hop counts for a node
1329 for currently: announce, spots, wwv and wcy broadcasts.
1334 set/hops gb7djk ann 10
1335 set/hops gb7mbc spots 20
1337 </CODE></BLOCKQUOTE>
1338 <P>Set SHOW/HOPS for information on what is already set. This command
1339 creates a filter and works in conjunction with the filter system.
1341 <H2><A NAME="ss9.79">9.79 set/isolate (9)</A>
1344 <P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
1346 <P>Connect a node to your system in such a way that you are a full protocol
1347 member of its network and can see all spots on it, but nothing either leaks
1348 out from it nor goes back into from the rest of the nodes connected to you.
1349 <P>You can potentially connect several nodes in this way.
1350 <P>You can see which nodes are isolated with the show/isolate (1) command.
1351 <P>You can remove the isolation with the command unset/isolate.
1353 <H2><A NAME="ss9.80">9.80 set/language (0)</A>
1356 <P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
1358 <P>You can select the language that you want the cluster to use. Currently
1359 the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
1361 <H2><A NAME="ss9.81">9.81 set/location (0)</A>
1364 <P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
1366 <P>You can set your latitude and longitude manually or alternatively use the
1367 <EM>set/qra</EM> command which will do the conversion for you.
1371 set/location 54 04 N 2 02 E
1373 </CODE></BLOCKQUOTE>
1376 <H2><A NAME="ss9.82">9.82 set/sys_location (9)</A>
1379 <P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
1381 <P>In order to get accurate headings and such like you must tell the system
1382 what your latitude and longitude is. If you have not yet done a SET/QRA
1383 then this command will set your QRA locator for you. For example:-
1387 SET/LOCATION 52 22 N 0 57 E
1389 </CODE></BLOCKQUOTE>
1391 <H2><A NAME="ss9.83">9.83 set/logininfo (0)</A>
1394 <P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
1396 <P>Show users and nodes when they log in and out of the local cluster. You
1397 can stop these messages by using the <EM>unset/logininfo</EM> command.
1400 <H2><A NAME="ss9.84">9.84 set/lockout (9)</A>
1403 <P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
1405 <P>You can show who is locked out with the <EM>show/lockout</EM> command.
1406 To allow the user to connect again, use the <EM>unset/lockout</EM> command.
1408 <H2><A NAME="ss9.85">9.85 set/name (0)</A>
1411 <P><CODE><B>set/name <your_name></B> Set your name</CODE>
1413 <P>Tell the cluster what your name is, eg:-
1419 </CODE></BLOCKQUOTE>
1421 <H2><A NAME="ss9.86">9.86 set/node (9)</A>
1424 <P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
1426 <P>Tell the system that the call(s) are to be treated as AK1A cluster and
1427 fed PC Protocol rather normal user commands.
1428 <P>From version 1.41 you can also set the following types of cluster
1437 </CODE></BLOCKQUOTE>
1438 <P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
1440 <H2><A NAME="ss9.87">9.87 set/obscount (9)</A>
1443 <P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
1445 <P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1446 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1447 counter which is decremented on every outgoing ping and then reset to
1448 the 'obscount' value on every incoming ping. The default value of this
1450 <P>What this means is that a neighbouring node will be pinged twice at
1451 (default) 300 second intervals and if no reply has been heard just before
1452 what would be the third attempt, that node is disconnected.
1453 <P>If a ping is heard then the obscount is reset to the full value. Using
1454 default values, if a node has not responded to a ping within 15 minutes,
1457 <H2><A NAME="ss9.88">9.88 set/page (0)</A>
1460 <P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
1462 <P>Tell the system how many lines you wish on a page when the number of lines
1463 of output from a command is more than this. The default is 20. Setting it
1464 explicitly to 0 will disable paging.
1471 </CODE></BLOCKQUOTE>
1472 <P>The setting is stored in your user profile.
1475 <H2><A NAME="ss9.89">9.89 set/password (9)</A>
1478 <P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
1480 <P>The password for a user can only be set by a full sysop. The string
1481 can contain any characters but any spaces are removed (you can type in
1482 spaces - but they won't appear in the password). You can see the
1483 result with STAT/USER. The password is the usual 30 character baycom
1486 <H2><A NAME="ss9.90">9.90 set/pinginterval (9)</A>
1489 <P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
1491 <P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
1492 in order to determine the rolling quality of the link and, in future, to
1493 affect routing decisions. The default interval is 300 secs or 5 minutes.
1494 <P>You can use this command to set a different interval. Please don't.
1495 <P>But if you do the value you enter is treated as minutes up 60 and seconds
1496 for numbers greater than that.
1497 <P>This is used also to help determine when a link is down at the far end
1498 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1499 for more information.
1501 <H2><A NAME="ss9.91">9.91 set/privilege (9)</A>
1504 <P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
1506 <P>Set the privilege level on a callsign. The privilege levels that pertain
1507 to commands are as default:-
1512 1 - allow remote nodes normal user RCMDs
1513 5 - various privileged commands (including shutdown, but not disc-
1514 connect), the normal level for another node.
1515 8 - more privileged commands (including disconnect)
1516 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1519 </CODE></BLOCKQUOTE>
1520 <P>If you are a sysop and you come in as a normal user on a remote connection
1521 your privilege will automatically be set to 0.
1523 <H2><A NAME="ss9.92">9.92 set/spider (5)</A>
1526 <P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
1527 the node_call a DXSpider type node</CODE>
1529 <P>Set the node_call as a DXSpider type node
1531 <H2><A NAME="ss9.93">9.93 set/sys_qra (9)</A>
1534 <P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
1536 <H2><A NAME="ss9.94">9.94 set/qra (0)</A>
1539 <P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
1541 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
1542 done a SET/LOCATION then your latitude and longitude will be set roughly
1543 correctly (assuming your locator is correct ;-). For example:-
1549 </CODE></BLOCKQUOTE>
1551 <H2><A NAME="ss9.95">9.95 set/qth (0)</A>
1554 <P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
1556 <P>Tell the system where your are. For example:-
1560 set/qth East Dereham, Norfolk
1562 </CODE></BLOCKQUOTE>
1564 <H2><A NAME="ss9.96">9.96 set/talk (0)</A>
1567 <P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
1569 <P>Allow talk messages to arrive at your console. You can switch off
1570 talks with the <EM>unset/talk</EM> command.
1572 <H2><A NAME="ss9.97">9.97 set/wcy (0)</A>
1575 <P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
1577 <P>Allow WCY information to be seen at your console. You can switch off
1578 WCY messages with the <EM>unset/wcy</EM> command.
1580 <H2><A NAME="ss9.98">9.98 set/wwv (0)</A>
1583 <P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
1585 <P>Allow WWV information to be seen at your console. You can switch off
1586 WWV messages with the <EM>unset/wwv</EM> command.
1588 <H2><A NAME="ss9.99">9.99 set/wx (0)</A>
1591 <P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
1593 <P>Allow WX information to be seen at your console. You can switch off
1594 WX messages with the <EM>unset/wx</EM> command.
1596 <H2><A NAME="ss9.100">9.100 show/baddx (1)</A>
1599 <P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
1601 <P>Display all the bad dx callsigns in the system, see SET/BADDX
1602 for more information.
1604 <H2><A NAME="ss9.101">9.101 show/badnode (6)</A>
1607 <P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
1609 <P>Display all the bad node callsigns in the system, see SET/BADNODE
1610 for more information.
1612 <H2><A NAME="ss9.102">9.102 show/badspotter (1)</A>
1615 <P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
1617 <P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1618 for more information.
1620 <H2><A NAME="ss9.103">9.103 show/configuration (0)</A>
1623 <P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
1625 <P>This command allows you to see all the users that can be seen
1626 and the nodes to which they are connected. With the optional <EM>node</EM>,
1627 you can specify a particular node to look at.
1628 <P>This command is normally abbreviated to: sh/c
1629 <P>BE WARNED: the list that is returned can be VERY long
1631 <H2><A NAME="ss9.104">9.104 show/configuration/node (0)</A>
1634 <P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
1636 <P>Show all the nodes connected locally and the nodes they have connected.
1638 <H2><A NAME="ss9.105">9.105 show/connect (1)</A>
1641 <P><CODE><B>show/connect</B> Show all the active connections</CODE>
1643 <P>This command shows information on all the active connections known to
1644 the node. This command gives slightly more information than WHO.
1646 <H2><A NAME="ss9.106">9.106 show/date (0)</A>
1649 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
1650 the local time</CODE>
1652 <P>This is very nearly the same as SHOW/TIME, the only difference the format
1653 of the date string if no arguments are given.
1654 <P>If no prefixes or callsigns are given then this command returns the local
1655 time and UTC as the computer has it right now. If you give some prefixes
1656 then it will show UTC and UTC + the local offset (not including DST) at
1657 the prefixes or callsigns that you specify.
1659 <H2><A NAME="ss9.107">9.107 show/debug (9)</A>
1662 <P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
1664 <P>The levels can be set with <EM>set/debug</EM>
1666 <H2><A NAME="ss9.108">9.108 show/dx (0)</A>
1669 <P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
1671 <P>If you just type SHOW/DX you will get the last so many spots
1672 (sysop configurable, but usually 10).
1673 <P>In addition you can add any number of these options in very nearly
1674 any order to the basic SHOW/DX command, they are:-
1679 on <band> - eg 160m 20m 2m 23cm 6mm
1680 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1682 <number> - the number of spots you want
1683 <from>-<to> - <from> spot no <to> spot no in
1686 <prefix> - for a spotted callsign beginning with <prefix>
1687 *<suffix> - for a spotted callsign ending in <suffix>
1688 *<string>* - for a spotted callsign containing <string>
1690 day <number> - starting <number> days ago
1691 day <from>-<to> - <from> days <to> days ago
1693 info <text> - any spots containing <text> in the info or remarks
1695 by <call> - any spots spotted by <call> (spotter <call>
1698 qsl - this automatically looks for any qsl info on the call
1699 held in the spot database.
1701 iota [<iota>] - If the iota island number is missing it will
1702 look for the string iota and anything which looks like
1703 an iota island number. If you specify then it will look
1706 qra [<locator>] - this will look for the specific locator if
1707 you specify one or else anything that looks like a locator.
1709 </CODE></BLOCKQUOTE>
1716 SH/DX on 20m info iota
1717 SH/DX 9a on vhf day 30
1723 </CODE></BLOCKQUOTE>
1725 <H2><A NAME="ss9.109">9.109 show/dxcc (0)</A>
1728 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
1730 <P>This command takes the <prefix> (which can be a full or partial
1731 callsign if desired), looks up which internal country number it is
1732 and then displays all the spots as per SH/DX for that country.
1733 <P>The options for SHOW/DX also apply to this command.
1740 SH/DXCC W on 20m info iota
1742 </CODE></BLOCKQUOTE>
1744 <H2><A NAME="ss9.110">9.110 show/files (0)</A>
1747 <P><CODE><B>show/files [<filearea> [<string>]]</B> List
1748 the contents of a filearea</CODE>
1750 <P>SHOW/FILES on its own will show you a list of the various fileareas
1751 available on the system. To see the contents of a particular file
1756 SH/FILES <filearea>
1758 </CODE></BLOCKQUOTE>
1759 <P>where <filearea> is the name of the filearea you want to see the
1761 <P>You can also use shell globbing characters like '*' and '?' in a
1762 string to see a selection of files in a filearea eg:-
1766 SH/FILES bulletins arld*
1768 </CODE></BLOCKQUOTE>
1769 <P>See also TYPE - to see the contents of a file.
1771 <H2><A NAME="ss9.111">9.111 show/filter (0)</A>
1774 <P><CODE><B>show/filter</B> Show the filters you have set</CODE>
1776 <P>Show the contents of all the filters that are set by you. This command
1777 displays all the filters set - for all the various categories.
1779 <H2><A NAME="ss9.112">9.112 show/filter (extended for sysops) (5)</A>
1782 <P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
1784 <P>A sysop can look at any filters that have been set.
1786 <H2><A NAME="ss9.113">9.113 show/hops (8)</A>
1789 <P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
1791 <P>This command shows the hop counts set up for a node. You can specify
1792 which category you want to see. If you leave the category out then
1793 all the categories will be listed.
1795 <H2><A NAME="ss9.114">9.114 show/isolate (1)</A>
1798 <P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
1800 <P>Show which nodes are currently set to be isolated.
1802 <H2><A NAME="ss9.115">9.115 show/lockout (9)</A>
1805 <P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
1807 <P>Show a list of callsigns that have been excluded (locked out) of the
1808 cluster locally with the <EM>set/lockout</EM> command
1810 <H2><A NAME="ss9.116">9.116 show/log (8)</A>
1813 <P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
1815 <P>This command outputs a short section of the system log. On its own
1816 it will output a general logfile. With the optional callsign it will
1817 show output from the log associated with that callsign.
1819 <H2><A NAME="ss9.117">9.117 show/moon (0)</A>
1822 <P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
1823 rise and set times</CODE>
1825 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
1826 together with the azimuth and elevation of the sun currently at those
1828 <P>If you don't specify any prefixes or callsigns, it will show the times for
1829 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1830 together with the current azimuth and elevation.
1831 <P>In addition, it will show the gain or loss dB relative to the nominal
1832 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1833 <P>If all else fails it will show the Moonrise and set times for the node
1834 that you are connected to.
1842 </CODE></BLOCKQUOTE>
1844 <H2><A NAME="ss9.118">9.118 show/muf (0)</A>
1847 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
1848 the likely propagation to <prefix></CODE>
1850 <P>This command allow you to estimate the likelihood of you contacting
1851 a station with the prefix you have specified. The output assumes a modest
1852 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1853 <P>The result predicts the most likely operating frequencies and signal
1854 levels for high frequency (shortwave) radio propagation paths on
1855 specified days of the year and hours of the day. It is most useful for
1856 paths between 250 km and 6000 km, but can be used with reduced accuracy
1857 for paths shorter or longer than this.
1858 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1859 used to predict the MUF given the predicted flux, day of the year,
1860 hour of the day and geographic coordinates of the transmitter and
1861 receiver. This routine is reasonably accurate for the purposes here,
1862 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1863 than the programs used by major shortwave broadcasting organizations,
1864 such as the Voice of America.
1865 <P>The command will display some header information detailing its
1866 assumptions, together with the locations, latitude and longitudes and
1867 bearings. It will then show UTC (UT), local time at the other end
1868 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1869 (Zen) and the likely signal strengths. Then for each frequency for which
1870 the system thinks there is a likelihood of a circuit it prints a value.
1871 <P>The value is currently a likely S meter reading based on the conventional
1872 6dB / S point scale. If the value has a '+' appended it means that it is
1873 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1874 there is likely to be much fading and by an 's' that the signal is likely
1876 <P>By default SHOW/MUF will show the next two hours worth of data. You
1877 can specify anything up to 24 hours worth of data by appending the no of
1878 hours required after the prefix. For example:-
1884 </CODE></BLOCKQUOTE>
1889 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1890 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1891 Location Lat / Long Azim
1892 East Dereham, Norfolk 52 41 N 0 57 E 47
1893 United-States-W 43 0 N 87 54 W 299
1894 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1895 18 23 11.5 -35 mS0+ mS2 S3
1896 19 0 11.2 -41 mS0+ mS2 S3
1898 </CODE></BLOCKQUOTE>
1899 <P>indicating that you will have weak, fading circuits on top band and
1900 80m but usable signals on 40m (about S3).
1907 </CODE></BLOCKQUOTE>
1908 <P>will get you the above display, but with the next 24 hours worth of
1916 </CODE></BLOCKQUOTE>
1917 <P>Gives you an estimate of the long path propagation characterics. It
1918 should be noted that the figures will probably not be very useful, nor
1919 terrible accurate, but it is included for completeness.
1921 <H2><A NAME="ss9.119">9.119 show/node (1)</A>
1924 <P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
1925 number of nodes</CODE>
1927 <P>Show the type and version (if connected) of the nodes specified on the
1928 command line. If no callsigns are specified then a sorted list of all
1929 the non-user callsigns known to the system will be displayed.
1931 <H2><A NAME="ss9.120">9.120 show/prefix (0)</A>
1934 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
1936 <P>This command takes the <callsign> (which can be a full or partial
1937 callsign or a prefix), looks up which internal country number
1938 it is and then displays all the relevant prefixes for that country
1939 together with the internal country no, the CQ and ITU regions.
1940 <P>See also SHOW/DXCC
1943 <H2><A NAME="ss9.121">9.121 show/program (5)</A>
1946 <P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
1948 <P>Show the name and location where every program module was load from. This
1949 is useful for checking where you think you have loaded a .pm file from.
1951 <H2><A NAME="ss9.122">9.122 show/qra (0)</A>
1954 <P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
1955 between locators<BR>
1956 <B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
1958 <P>This is a multipurpose command that allows you either to calculate the
1959 distance and bearing between two locators or (if only one locator is
1960 given on the command line) the distance and beraing from your station
1961 to the locator. For example:-
1968 </CODE></BLOCKQUOTE>
1969 <P>The first example will show the distance and bearing to the locator from
1970 yourself, the second example will calculate the distance and bearing from
1971 the first locator to the second. You can use 4 or 6 character locators.
1972 <P>It is also possible to convert a latitude and longitude to a locator by
1973 using this command with a latitude and longitude as an argument, for
1978 SH/QRA 52 41 N 0 58 E
1980 </CODE></BLOCKQUOTE>
1982 <H2><A NAME="ss9.123">9.123 show/qrz (0)</A>
1985 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
1987 <P>This command queries the QRZ callbook server on the internet
1988 and returns any information available for that callsign. This service
1989 is provided for users of this software by http://www.qrz.com
1991 <H2><A NAME="ss9.124">9.124 show/route (0)</A>
1994 <P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
1996 <P>This command allows you to see to which node the callsigns specified are
1997 connected. It is a sort of inverse sh/config.
2003 </CODE></BLOCKQUOTE>
2005 <H2><A NAME="ss9.125">9.125 show/satellite (0)</A>
2008 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
2009 Show satellite tracking data</CODE>
2011 <P>Show the tracking data from your location to the satellite of your choice
2012 from now on for the next few hours.
2013 <P>If you use this command without a satellite name it will display a list
2014 of all the satellites known currently to the system.
2015 <P>If you give a name then you can obtain tracking data of all the passes
2016 that start and finish 5 degrees below the horizon. As default it will
2017 give information for the next three hours for every five minute period.
2018 <P>You can alter the number of hours and the step size, within certain
2020 <P>Each pass in a period is separated with a row of '-----' characters
2026 SH/SAT FENGYUN1 12 2
2028 </CODE></BLOCKQUOTE>
2030 <H2><A NAME="ss9.126">9.126 show/sun (0)</A>
2033 <P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
2034 sun rise and set times</CODE>
2036 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
2037 together with the azimuth and elevation of the sun currently at those
2039 <P>If you don't specify any prefixes or callsigns, it will show the times for
2040 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2041 together with the current azimuth and elevation.
2042 <P>If all else fails it will show the sunrise and set times for the node
2043 that you are connected to.
2049 SH/SUN G1TLH K9CW ZS
2051 </CODE></BLOCKQUOTE>
2053 <H2><A NAME="ss9.127">9.127 show/time (0)</A>
2056 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
2057 the local time</CODE>
2059 <P>If no prefixes or callsigns are given then this command returns the local
2060 time and UTC as the computer has it right now. If you give some prefixes
2061 then it will show UTC and UTC + the local offset (not including DST) at
2062 the prefixes or callsigns that you specify.
2064 <H2><A NAME="ss9.128">9.128 show/wcy (0)</A>
2067 <P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
2068 <B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
2070 <P>Display the most recent WCY information that has been received by the system
2072 <H2><A NAME="ss9.129">9.129 show/wwv (0)</A>
2075 <P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
2076 <B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
2078 <P>Display the most recent WWV information that has been received by the system
2081 <H2><A NAME="ss9.130">9.130 shutdown (5)</A>
2084 <P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
2086 <P>Shutdown the cluster and disconnect all the users. If you have Spider
2087 set to respawn in /etc/inittab it will of course restart.
2089 <H2><A NAME="ss9.131">9.131 spoof (9)</A>
2092 <P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
2094 <P>This is a very simple yet powerful command for the sysop. It allows you to
2095 issue commands as if you were a different user. This is very useful for the
2096 kind of things that users seem to always get wrong.. like home_node for
2099 <H2><A NAME="ss9.132">9.132 stat/db (5)</A>
2102 <P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
2104 <P>Show the internal status of a database descriptor.
2105 <P>Depending on your privilege level you will see more or less information.
2106 This command is unlikely to be of much use to anyone other than a sysop.
2108 <H2><A NAME="ss9.133">9.133 stat/channel (5)</A>
2111 <P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
2113 <P>Show the internal status of the channel object either for the channel that
2114 you are on or else for the callsign that you asked for.
2115 <P>Only the fields that are defined (in perl term) will be displayed.
2117 <H2><A NAME="ss9.134">9.134 stat/msg (5)</A>
2120 <P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
2122 <P>This command shows the internal status of a message and includes information
2123 such as to whom it has been forwarded, its size, origin etc etc.
2125 <H2><A NAME="ss9.135">9.135 stat/user (5)</A>
2128 <P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
2130 <P>Shows the full contents of a user record including all the secret flags
2132 <P>Only the fields that are defined (in perl term) will be displayed.
2134 <H2><A NAME="ss9.136">9.136 sysop (0)</A>
2137 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
2139 <P>The system automatically reduces your privilege level to that of a
2140 normal user if you login in remotely. This command allows you to
2141 regain your normal privilege level. It uses the normal system: five
2142 numbers are returned that are indexes into the character array that is
2143 your assigned password (see SET/PASSWORD). The indexes start from
2145 <P>You are expected to return a string which contains the characters
2146 required in the correct order. You may intersperse those characters
2147 with others to obscure your reply for any watchers. For example (and
2148 these values are for explanation :-):
2152 password = 012345678901234567890123456789
2156 </CODE></BLOCKQUOTE>
2161 aa2bbbb0ccc5ddd7xxx3n
2165 </CODE></BLOCKQUOTE>
2166 <P>They will all match. If there is no password you will still be offered
2167 numbers but nothing will happen when you input a string. Any match is
2170 <H2><A NAME="ss9.137">9.137 talk (0)</A>
2173 <P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
2174 <B>talk <callsign> <text></B> Send a text message to <callsign><BR>
2175 <B>talk <callsign> > <node_call> [<text>]</B>
2176 Send a text message to <callsign> via <node_call></CODE>
2178 <P>Send a short message to any other station that is visible on the cluster
2179 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2180 command, they don't have to be connected locally.
2181 <P>The second form of TALK is used when other cluster nodes are connected
2182 with restricted information. This usually means that they don't send
2183 the user information usually associated with logging on and off the cluster.
2184 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
2185 see GB7TLH in the SH/C list but with no users, then you would use the
2186 second form of the talk message.
2187 <P>If you want to have a ragchew with someone you can leave the text message
2188 out and the system will go into 'Talk' mode. What this means is that a
2189 short message is sent to the recipient telling them that you are in a 'Talking'
2190 frame of mind and then you just type - everything you send will go to the
2191 station that you asked for.
2192 <P>All the usual announcements, spots and so on will still come out on your
2194 <P>If you want to do something (such as send a spot) you precede the normal
2195 command with a '/' character, eg:-
2199 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2202 </CODE></BLOCKQUOTE>
2203 <P>To leave talk mode type:
2209 </CODE></BLOCKQUOTE>
2211 <H2><A NAME="ss9.138">9.138 type (0)</A>
2214 <P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
2216 <P>Type out the contents of a file in a filearea. So, for example, in
2217 filearea 'bulletins' you want to look at file 'arld051' you would
2222 TYPE bulletins/arld051
2224 </CODE></BLOCKQUOTE>
2225 <P>See also SHOW/FILES to see what fileareas are available and a
2228 <H2><A NAME="ss9.139">9.139 who (0)</A>
2231 <P><CODE><B>who</B> Show who is physically connected locally</CODE>
2233 <P>This is a quick listing that shows which callsigns are connected and
2234 what sort of connection they have
2236 <H2><A NAME="ss9.140">9.140 wx (0)</A>
2239 <P><CODE><B>wx <text></B> Send a weather message to local users<BR>
2240 <B>wx full <text> </B> Send a weather message to all cluster users</CODE>
2242 <P>Weather messages can sometimes be useful if you are experiencing an extreme
2243 that may indicate enhanced conditions
2245 <H2><A NAME="ss9.141">9.141 wx (enhanced for sysops) (5)</A>
2248 <P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
2250 <P>Send a weather message only to other cluster nodes and not to general users.
2256 <A HREF="adminmanual-8.html">Previous</A>
2257 <A HREF="adminmanual.html#toc9">Contents</A>
projects / spider.git / blob