fix sh/contest and add CTY2308 prefixes

[spider.git] / cmd / Commands_en.hlp

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index 8f798b80bc860e0f7ac581fc48524ec01a3c0afd..85143b493e3ce64a516f89b1f0a550b5528808d4 100644 (file)
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -500,8 +500,23 @@ You also use one of these databases in a chain. This may be useful
 locally. 
 
 See DBIMPORT for the importing of existing AK1A format data to databases.
+See DXEXPORT for how to export an AK1A data in a form able to be imported.
 See DBSHOW for generic database enquiry
- 
+
+
+=== 9^DBEXPORT <dbname> <filename>^Export an AK1A data to a file
+Sometimes one needs to export the data from an existing database file,
+maybe for a backup or to send to another node.
+
+  DBEXPORT oblast /tmp/OBLAST.FUL
+
+will export the OBLAST database to /tmp/OBLAST.FUL
+
+There is no protection, it is up to you not to overwrite a file that
+is important to you.
+
+See DBIMPORT for the importing of existing AK1A format data to databases.
+
 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
 If you want to import or update data in bulk to a database you can use
 this command. It will either create or update entries into an existing
@@ -512,6 +527,8 @@ database. For example:-
 will import the standard OBLAST database that comes with AK1A into the
 oblast database held locally.
 
+See DBEXPORT for how to export an AK1A database
+
 === 9^DBREMOVE <dbname>^Delete a database
 DBREMOVE will completely remove a database entry and also delete any data
 file that is associated with it. 
@@ -618,6 +635,41 @@ You can credit someone else by saying:-
 The <freq> is compared against the available bands set up in the 
 cluster.  See SHOW/BANDS for more information.
 
+=== 9^DXQSL_EXPORT <filename>^Export SH/DXSQL information to a file
+The SHOW/DXQSL command shows any QSL managers that have been extracted
+from comments on a DX spot.
+
+Use this command to export the current state of the information to
+a CSV style text file. For example:
+
+   DXQSL_EXPORT /tmp/qsl.csv
+
+NOTE: this command will overwrite any file that you have write
+permission for.
+
+See also DXQSL_IMPORT to import one of these files.
+
+=== 9^DXQSL_IMPORT <filename>^Import SH/DXSQL information from a file
+The SHOW/DXQSL command shows any QSL managers that have been extracted
+from comments on a DX spot.
+
+Use this command to restore a file created by the DXSQL_EXPORT command.
+For example:
+
+   DXQSL_IMPORT /tmp/qsl.csv
+
+The data in this file will UPDATE any information that may already be
+present. This may not be what you want. To make the data the same as
+the import file then you must:
+
+* stop the node
+* remove /spider/data/qsl.v1
+* restart the node
+* login as sysop
+* do the import
+
+Preferably before too many DX spots with qsl manager info come in.
+
 === 0^ECHO <line>^Echo the line to the output
 This command is useful in scripts and so forth for printing the
 line that you give to the command to the output. You can use this
@@ -1986,13 +2038,20 @@ Show all the nodes connected to this node.
 This command shows information on all the active connections known to
 the node. This command gives slightly more information than WHO.
 
-=== 0^SHOW/CONTEST <year and month>^Show all the contests for a month
+=== 0^SHOW/CONTEST [<year>] [<month>]^Show all the contests for a month
 Show all known contests which are maintained at http://www.sk3bg.se/contest/
 for a particular month or year. The format is reasonably flexible.
 For example:-
   
-  SH/CONTEST sep2003
-  SH/CONTEST 03 march
+  SH/CONTEST 
+  SH/CONTEST mar
+  SH/CONTEST mar 13
+  SH/CONTEST 13 march
+
+If there is no month/year then the current month's contests are shown.
+
+Note that it expects ENGLISH (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec)
+month names.
 
 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time 
 This is very nearly the same as SHOW/TIME, the only difference the format