=== 9^DBCREATE <name>^Create a database entry
=== 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
=== 9^DBCREATE <name> remote <node>^Create a remote database entry
+=== 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB
DBCREATE allows you to define a database in the system. It doesn't actually
create anything, just defines it.
to work as they may be used to.
+You can also make local commands available as 'pseudo' databases. You
+can therefore make spider special commands available as a database. I
+imagine that this will be primarily useful for remote access from
+legacy nodes. For example:-
+
+ DBCREATE dxqsl cmd show/dxqsl
+
+You also use one of these databases in a chain. This may be useful
+locally.
+
See DBIMPORT for the importing of existing AK1A format data to databases.
See DBSHOW for generic database enquiry
=== 0^SET/DX^Allow DX messages to come out on your terminal
=== 0^UNSET/DX^Stop DX messages coming out on your terminal
+=== 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
+=== 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
+Display both the Spotter's and the Spotted's CQ Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's CQ is on the RHS of the
+time, the Spotted's CQ is on the LHS.
+
+Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
+
+Do a STAT/USER to see which flags you have set if you are confused.
+
+=== 0^SET/DXITU^Show ITU Zones on the end of DX announcements
+=== 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
+Display both the Spotter's and the Spotted's ITU Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's ITU is on the RHS of the
+time, the Spotted's ITU is on the LHS.
+
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
+
+Do a STAT/USER to see which flags you have set if you are confused.
+
=== 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
=== 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is
cannot cope with this. You can use this command to reset (or set)
this feature.
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.
+
=== 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
=== 0^SET/ECHO^Make the cluster echo your input
see also DELETE/USDB
-=== 0^SET/DXSTATE^Allow US State info on the end of DX announcements
-=== 0^UNSET/DXSTATE^Stop US State info on the end of DX announcements
+=== 0^SET/USSTATE^Allow US State info on the end of DX announcements
+=== 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
If the spotter's or spotted's US State is known it is output on the
end of a DX announcement (there is just enough room).
Some user programs cannot cope with this. You can use this command
to reset (or set) this feature.
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.
+
=== 0^SET/WCY^Allow WCY messages to come out on your terminal
=== 0^UNSET/WCY^Stop WCY messages coming out on your terminal
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
+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
+
=== 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format
of the date string if no arguments are given.
See also SHOW/WM7D for an alternative.
+=== 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
+The node collects information from the comment fields in spots (things
+like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
+
+This command allows you to interrogate that database and if the callsign
+is found will display the manager(s) that people have spotted. This
+information is NOT reliable, but it is normally reasonably accurate if
+it is spotted enough times.
+
+For example:-
+
+ sh/dxqsl 4k9w
+
+You can check the raw input spots yourself with:-
+
+ sh/dx 4k9w qsl
+
+This gives you more background information.
+
=== 9^SHOW/REGISTERED [<prefix>]^Show the registered users
=== 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
projects / spider.git / blobdiff