X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=b5c10c19255ce7c6e87176c4072e3c1e194d2472;hb=51fc2b9134d2e3bf91daf970c36bb8a80590e34f;hp=5a2c33451f2ff6de9adcda78e05604a58b24b23f;hpb=97ed91562320bf23d3ca62194a732fb9d89bb8ba;p=spider.git

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index 5a2c3345..b5c10c19 100644
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -378,6 +378,7 @@ in the system. It is also aliased to SHOW/COMMAND.
 === 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.
 
@@ -430,6 +431,16 @@ to allow
 
 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