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 === 1^FORWARD/OPERNAME <call>^Send out information on this <call> to all clusters
220 This command sends out any information held in the user file which can
221 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
222 and Homenode. PC41s are only sent for the information that is available.
224 === 0^HELP^The HELP Command
225 HELP is available for a number of commands. The syntax is:-
229 Where <cmd> is the name of the command you want help on.
231 All commands can be abbreviated, so SHOW/DX can be abbreviated
232 to SH/DX, ANNOUNCE can be shortened to AN and so on.
234 Look at the APROPOS <string> command which will search the help database
235 for the <string> you specify and give you a list of likely commands
236 to look at with HELP.
238 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
239 Delete a message from the local system. You will only be able to delete messages
240 that you have originated or been sent (unless you are the sysop).
242 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
243 Delete a message (usually a 'bulletin') from the whole cluster system.
245 This uses the subject field, so any messages that have exactly the same subject
246 will be deleted. Beware!
248 === 9^LOAD/ALIASES^Reload the command alias table
249 Reload the /spider/cmd/Aliases file after you have editted it. You will need to
250 do this if you change this file whilst the cluster is running in order for the
251 changes to take effect.
253 === 9^LOAD/BANDS^Reload the band limits table
254 Reload the /spider/data/bands.pl file if you have changed it manually whilst
255 the cluster is running.
257 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
258 Normally, if you change a command file in the cmd or local_cmd tree it will
259 automatially be picked up by the cluster program. Sometimes it can get confused
260 if you are doing a lot of moving commands about or delete a command in the
261 local_cmd tree and want to use the normal one again. Execute this command to
262 reset everything back to the state it was just after a cluster restart.
264 === 9^LOAD/MESSAGES^Reload the system messages file
265 If you change the /spider/perl/Messages file (usually whilst fiddling/writing new
266 commands) you can have them take effect during a cluster session by executing this
267 command. You need to do this if get something like :-
269 unknown message 'xxxx' in lang 'en'
271 === 9^LOAD/PREFIXES^Reload the prefix table
272 Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst
273 the cluster is running.
275 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
276 MERGE allows you to bring your spot and wwv database up to date. By default
277 it will request the last 10 spots and 5 WWVs from the node you select. The
278 node must be connected locally.
280 You can request any number of spots or wwv and although they will be appended
281 to your databases they will not duplicate any that have recently been added
282 (the last 2 days for spots and last month for WWV data).
284 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
285 Alter message parameters like To, From, Subject, whether private or bulletin
286 or return receipt (RR) is required or whether to keep this message from timing
289 MSG TO <msgno> <call> - change TO callsign to <call>
290 MSG FRom <msgno> <call> - change FROM callsign to <call>
291 MSG PRrivate <msgno> - set private flag
292 MSG NOPRrivate <msgno> - unset private flag
293 MSG RR <msgno> - set RR flag
294 MSG NORR <msgno> - unset RR flag
295 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
296 MSG NOKEep <msgno> - unset the keep flag
297 MSG SUbject <msgno> <new> - change the subject to <new>
298 MSG WAittime <msgno> - remove any waitting time for this message
299 MSG QUeue - queue any outstanding bulletins
300 MSG QUeue 1 - queue any outstanding private messages
302 You can look at the status of a message by using:-
306 This will display more information on the message than DIR does.
308 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
309 Send some arbitrary text to a locally connected callsign. No processing is done on
310 the text. This command allows you to send PC Protocol to unstick things if problems
311 arise (messages get stuck etc). eg:-
312 pc gb7djk PC33^GB7TLH^GB7DJK^400^
314 pc G1TLH Try doing that properly!!!
316 === 1^PING <node>^Send a ping command to another cluster
317 This command is used to estimate the quality of the link to another cluster.
318 The time returned is the length of time taken for a PC51 to go to another
319 cluster and be returned.
321 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
322 You can get rid of any message to or originating from your callsign using
323 this command. You can remove more than one message at a time.
325 === 5^KILL <from>-<to>^Remove a range of messages from the system
326 === 5^KILL FROM <call>^Remove all messages from a callsign
327 === 5^KILL TO <call>^Remove all messages to a callsign
328 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
329 Remove this message from the entire cluster system as well as your node.
332 As a sysop you can kill any message on the system.
334 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
335 Send any text you like to the callsign requested. This is used mainly to send
336 PC protocol to connected nodes either for testing or to unstick things.
338 You can also use in the same way as a talk command to a connected user but
339 without any processing, added of "from <blah> to <blah" or whatever.
341 === 1^PING <node call>^Find out the delays an a circuit to another node
342 This command will enable sysops to determine the speed of an inter-cluster
345 Any visible cluster node can be PINGed.
347 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
348 This command allows you to send nearly any command to another DX Cluster
349 node that is connected to the system.
351 Whether you get any output is dependant on a) whether the other system knows
352 that the node callsign of this cluster is in fact a node b) whether the
353 other system is allowing RCMDs from this node and c) whether you have
354 permission to send this command at all.
356 === 0^READ^Read the next unread personal message addressed to you
357 === 0^READ <msgno>^Read the specified message
358 You can read any messages that are sent as 'non-personal' and also any
359 message either sent by or sent to your callsign.
362 As a sysop you may read any message on the system
364 === 0^REPLY^Reply (privately) to the last message that you have read
365 === 0^REPLY <msgno>^Reply (privately) to the specified message
366 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
367 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
368 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
369 You can reply to a message and the subject will automatically have
370 "Re:" inserted in front of it, if it isn't already present.
372 You can also use all the extra qualifiers such as RR, PRIVATE,
373 NOPRIVATE, B that you can use with the SEND command (see SEND
376 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
377 === 0^SEND RR <call>^Send a message and ask for a read receipt
378 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
379 === 0^SEND PRIVATE <call>^Send a personal message
380 === 0^SEND NOPRIVATE <call>^Send a message to all stations
381 All the SEND commands will create a message which will be sent either to
382 an individual callsign or to one of the 'bulletin' addresses.
384 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
385 it will mark the message as personal and send it to the cluster node that
386 that callsign is connected to.
388 You can have more than one callsign in all of the SEND commands.
390 You can have multiple qualifiers so that you can have for example:-
392 SEND RR COPY 123 PRIVATE G1TLH G0RDI
394 which should send a copy of message 123 to G1TLH and G0RDI and you will
395 receive a read receipt when they have read the message.
397 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
398 SP is an alias for SEND PRIVATE
400 === 0^SET/ADDRESS <your address>^Record your postal address
402 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
403 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
405 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
406 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
408 === 9^SET/DEBUG <name>^Add a debug level to the debug set
409 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
411 === 0^SET/DX^Allow DX messages to come out on your terminal
412 === 0^UNSET/DX^Stop DX messages coming out on your terminal
414 === 0^SET/HERE^Tell the system you are present at your terminal
415 === 0^UNSET/HERE^Tell the system you are absent from your terminal
417 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
418 Tell the cluster system where you normally connect to. Any Messages sent
419 to you will normally find their way there should you not be connected.
423 === 9^SET/ISOLATE^Isolate a node from the rest of the network
424 Connect a node to your system in such a way that you are a full protocol
425 member of its network and can see all spots on it, but nothing either leaks
426 out from it nor goes back into from the rest of the nodes connected to you.
428 You can potentially connect several nodes in this way.
430 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
431 Remove isolation from a node - SET/ISOLATE
433 === 0^SET/LANGUAGE <lang>^Set the language you want to use
434 You can select the language that you want the cluster to use. Currently
435 the languages available are en (english) and nl (dutch).
437 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
438 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
439 In order to get accurate headings and such like you must tell the system
440 what your latitude and longitude is. If you have not yet done a SET/QRA
441 then this command will set your QRA locator for you. For example:-
442 SET/LOCATION 52 22 N 0 57 E
444 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
445 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
447 === 0^SET/NAME <your name>^Set your name
448 Tell the system what your name is eg:-
451 === 9^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
452 Tell the system that the call(s) are to be treated as AK1A cluster and
453 fed PC Protocol rather normal user commands.
455 === 0^SET/PAGE <lines per page>^Set the lines per page
456 Tell the system how many lines you wish on a page when the number of line
457 of output from a command is more than this. The default is 20. Setting it
458 explicitly to 0 will disable paging.
462 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
463 Set the privilege level on a callsign. The privilege levels that pertain
464 to commands are as default:-
466 1 - allow remote nodes normal user RCMDs
467 5 - various privileged commands (including shutdown, but not disc-
468 connect), the normal level for another node.
469 8 - more privileged commands (including disconnect)
470 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
472 If you are a sysop and you come in as a normal user on a remote connection
473 your privilege will automatically be set to 0.
475 === 9^SET/PASSWORD <callsign> <string>^Set a users password
476 The password for a user can only be set by a full sysop. The string
477 can contain any characters but any spaces are removed (you can type in
478 spaces - but they won't appear in the password). You can see the
479 result with STAT/USER.
481 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
482 === 0^SET/QRA <locator>^Set your QRA locator
483 Tell the system what your QRA (or Maidenhead) locator is. If you have not
484 done a SET/LOCATION then your latitude and longitude will be set roughly
485 correctly (assuming your locator is correct ;-). For example:-
488 === 0^SET/QTH <your qth>^Set your QTH
489 Tell the system where you are. For example:-
490 SET/QTH East Dereham, Norfolk
492 === 0^SET/TALK^Allow TALK messages to come out on your terminal
493 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
495 === 0^SET/WWV^Allow WWV messages to come out on your terminal
496 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
498 === 0^SET/WX^Allow WX messages to come out on your terminal
499 === 0^UNSET/WX^Stop WX messages coming out on your terminal
501 === 0^SHOW/DX^Interrogate the spot database
502 If you just type SHOW/DX you will get the last so many spots
503 (sysop configurable, but usually 10).
505 In addition you can add any number of these commands in very nearly
506 any order to the basic SHOW/DX command, they are:-
508 on <band> - eg 160m 20m 2m 23cm 6mm
509 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
511 <number> - the number of spots you want
512 <from>-<to> - <from> spot no <to> spot no in the selected list
514 <prefix> - for a spotted callsign beginning with <prefix>
515 *<suffix> - for a spotted callsign ending in <suffix>
516 *<string>* - for a spotted callsign containing <string>
518 day <number> - starting <number> days ago
519 day <from>-<to> - <from> days <to> days ago
521 info <text> - any spots containing <text> in the info or remarks
523 by <call> - any spots spotted by <call> (spotter <call> is the
526 qsl - this automatically looks for any qsl info on the call
527 held in the spot database.
529 iota [<iota>] - If the iota island number is missing it will look for
530 the string iota and anything which looks like an iota
531 island number. If you specify then it will look for
534 qra [<locator>] - this will look for the specific locator if you specify
535 one or else anything that looks like a locator.
540 SH/DX on 20m info iota
541 SH/DX 9a on vhf day 30
547 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
548 This command takes the <prefix> (which can be a full or partial
549 callsign if desired), looks up which internal country number it is
550 and then displays all the spots as per SH/DX for that country.
552 The options for SHOW/DX also apply to this command.
556 SH/DXCC W on 20m info iota
558 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
559 SHOW/FILES on its own will show you a list of the various fileareas
560 available on the system. To see the contents of a particular file
563 where <filearea> is the name of the filearea you want to see the
566 You can also use shell globbing characters like '*' and '?' in a
567 string to see a selection of files in a filearea eg:-
568 SH/FILES bulletins arld*
570 See also TYPE - to see the contents of a file.
572 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
573 This command allow you to estimate the likelihood of you contacting
574 a station with the prefix you have specified. The output assumes a modest
575 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
577 The result predicts the most likely operating frequencies and signal
578 levels for high frequency (shortwave) radio propagation paths on
579 specified days of the year and hours of the day. It is most useful for
580 paths between 250 km and 6000 km, but can be used with reduced accuracy
581 for paths shorter or longer than this.
583 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
584 used to predict the MUF given the predicted flux, day of the year,
585 hour of the day and geographic coordinates of the transmitter and
586 receiver. This routine is reasonably accurate for the purposes here,
587 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
588 than the programs used by major shortwave broadcasting organizations,
589 such as the Voice of America.
591 The command will display some header information detailing its
592 assumptions, together with the locations, latitude and longitudes and
593 bearings. It will then show UTC (UT), local time at the other end
594 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
595 (Zen) and the likely signal strengths. Then for each frequency for which
596 the system thinks there is a likelihood of a circuit it prints a value.
598 The value is currently a likely S meter reading based on the conventional
599 6dB / S point scale. If the value has a '+' appended it means that it is
600 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
601 there is likely to be much fading and by an 's' that the signal is likely
604 By default SHOW/MUF will show the next two hours worth of data. You
605 can specify anything up to 24 hours worth of data by appending the no of
606 hours required after the prefix. For example:-
612 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
613 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
614 Location Lat / Long Azim
615 East Dereham, Norfolk 52 41 N 0 57 E 47
616 United-States-W 43 0 N 87 54 W 299
617 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
618 18 23 11.5 -35 mS0+ mS2 S3
619 19 0 11.2 -41 mS0+ mS2 S3
621 indicating that you will have weak, fading circuits on top band and
622 80m but usable signals on 40m (about S3).
628 will get you the above display, but with the next 24 hours worth of
634 Gives you an estimate of the long path propagation characterics. It
635 should be noted that the figures will probably not be very useful, nor
636 terrible accurate, but it is included for completeness.
638 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
639 This command takes the <callsign> (which can be a full or partial
640 callsign or a prefix), looks up which internal country number
641 it is and then displays all the relevant prefixes for that country
642 together with the internal country no, the CQ and ITU regions.
646 === 0^SHOW/SUN [<callsign>|<prefix>]^Display sunrise and sunset times
647 Show the sunrise and sunset times for a callsign (if it is known to the
648 cluster), a prefix or, if nothing is specified, at your QTH (if you have
649 remembered to set your location using SET/LOCATION or SET/QRA). If all else
650 fails it will show the sunrise and set times for the node that you are
653 You can enter more than one prefix or callsign:-
655 SH/SUN G1TLH G8TIC W9
657 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
658 Show the name and location where every program module was load from. This
659 is useful for checking where you think you have loaded a .pm file from.
661 === 0^SHOW/WWV^Show last 10 WWV broadcasts
662 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
663 Display the most recent WWV information that has been received by the system
665 === 5^SHUTDOWN^Shutdown the cluster
666 Shutdown the cluster and disconnect all the users
668 === 5^STAT/DB <dbname>^Show the status of a database
669 Show the internal status of a database descriptor.
671 Depending on your privilege level you will see more or less information.
672 This command is unlikely to be of much use to anyone other than a sysop.
674 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
675 Show the internal status of the channel object either for the channel that
676 you are on or else for the callsign that you asked for.
678 Only the fields that are defined (in perl term) will be displayed.
680 === 5^STAT/MSG <msgno>^Show the status of a message
681 This command shows the internal status of a message and includes information
682 such as to whom it has been forwarded, its size, origin etc etc.
684 === 5^STAT/USER [<callsign>]^Show the full status of a user
685 Shows the full contents of a user record including all the secret flags
688 Only the fields that are defined (in perl term) will be displayed.
690 === 0^SYSOP^Regain your privileges if you login remotely
691 The system automatically reduces your privilege level to that of a
692 normal user if you login in remotely. This command allows you to
693 regain your normal privilege level. It uses the normal system: five
694 numbers are returned that are indexes into the character array that is
695 your assigned password (see SET/PASSWORD). The indexes start from
698 You are expected to return a string which contains the characters
699 required in the correct order. You may intersperse those characters
700 with others to obscure your reply for any watchers. For example (and
701 these values are for explanation :-):
703 password = 012345678901234567890123456789
707 aa2bbbb0ccc5ddd7xxx3n
711 They will all match. If there is no password you will still be offered
712 numbers but nothing will happen when you input a string. Any match is
715 === 0^TALK <call> <text>^Send a text message to another station
716 === 0^TALK <call> > <node> <text>^Send a text message to another station via a node
717 Send a short message to any other station that is visible on the cluster
718 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
719 command, they don't have to be connected locally.
721 The second form of TALK is used when other cluster nodes are connected
722 with restricted information. This usually means that they don't send
723 the user information usually associated with logging on and off the cluster.
725 If you know that G3JNB is likely to be present on GB7TLH, but you can only
726 see GB7TLH in the SH/C list but with no users, then you would use the
727 second form of the talk message.
729 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
730 Type out the contents of a file in a filearea. So, for example, in
731 filearea 'bulletins' you want to look at file 'arld051' you would
733 TYPE bulletins/arld051
735 See also SHOW/FILES to see what fileareas are available and a
738 === 0^WHO^Show who is physically connected
739 This is a quick listing that shows which callsigns are connected and
740 what sort of connection they have
742 === 0^WX <text>^Send a weather message to local users
743 === 0^WX FULL <text>^Send a weather message to all cluster users
744 === 5^WX SYSOP <text>^Send a weather message to other clusters only
745 Weather messages can sometimes be useful if you are experiencing an extreme
746 that may indicate enhanced conditions