Changed header a bit.

[egate.git] / kernel / default.res

diff --git a/kernel/default.res b/kernel/default.res
index fe79d7e..de4759a 100644 (file)
--- a/kernel/default.res
+++ b/kernel/default.res
@@ -1,5 +1,5 @@
 # Email gateway - general kernel resources
 # Email gateway - general kernel resources

-# $Id: default.res,v 1.13 1995/03/03 17:19:11 adam Exp $
+# $Id: default.res,v 1.30 1996/02/07 16:48:10 adam Exp $

 #
 # Important directories, programs, etc.
 gw.reply.mta: /usr/lib/sendmail
 #
 # Important directories, programs, etc.
 gw.reply.mta: /usr/lib/sendmail

@@ -7,9 +7,13 @@ gw.reply.tmp.prefix: gwr
 gw.reply.tmp.dir: /tmp
 #gw.path: /home/adam/egate/kernel
 gw.marc.log: marc.log
 gw.reply.tmp.dir: /tmp
 #gw.path: /home/adam/egate/kernel
 gw.marc.log: marc.log

+gw.timeout: 30
+gw.resultset: 1
+gw.persist: 1
+gw.max.process: 3

 
 # Retrieval settings
 
 # Retrieval settings

-gw.ignore.which: 1
+gw.ignore.which: 0

 gw.default.show: 10
 gw.max.show: 100
 
 gw.default.show: 10
 gw.max.show: 100
 

@@ -19,6 +23,8 @@ gw.hostname: localhost
 gw.bibset: default.bib
 gw.target.loc: loc.res
 gw.target.drewdb: drewdb.res
 gw.bibset: default.bib
 gw.target.loc: loc.res
 gw.target.drewdb: drewdb.res

+gw.target.dimitris: dimitris.res
+gw.target.danbib: dimitris.res

 gw.databases:
 
 # Language definitions
 gw.databases:
 
 # Language definitions

@@ -28,6 +34,7 @@ gw.lang.uk: lang.uk.res
 # Messages
 gw.msg.subject: Your Z39.50 Query...
 gw.msg.greeting: Europagate Email-Z39.50 gateway
 # Messages
 gw.msg.subject: Your Z39.50 Query...
 gw.msg.greeting: Europagate Email-Z39.50 gateway

+gw.msg.cont: Session continued...

 gw.msg.from: Email-gateway
 gw.err.nullbody: Empty body
 ccl.command.find: find f
 gw.msg.from: Email-gateway
 gw.err.nullbody: Empty body
 ccl.command.find: find f

@@ -37,11 +44,12 @@ ccl.command.help: help h
 ccl.command.info: info i
 ccl.command.continue: continue
 ccl.command.status: status
 ccl.command.info: info i
 ccl.command.continue: continue
 ccl.command.status: status

-ccl.command.cancel: cancel
+ccl.command.def: def
+ccl.command.account: account

 ccl.token.and: and
 ccl.token.or: or
 ccl.token.and: and
 ccl.token.or: or

-ccl.token.not: not
-ccl.token.set: set
+ccl.token.not: not andnot
+ccl.token.set: set s

 
 # Diagnostic Conditions
 gw.bib1.diag.1: Permanent system error
 
 # Diagnostic Conditions
 gw.bib1.diag.1: Permanent system error

@@ -115,75 +123,89 @@ gw.bib1.diag.132: Unsupported proximity unit code
 
 # Help messages
 gw.help.target: Command:\n
 
 # Help messages
 gw.help.target: Command:\n

- \ttarget host[:port]\n
+ \ttarget <host>[:<port>]\n

  \n
  The target command selects exactly one target <host>. The <host>
  is a normal internet domain hostname. The optional <port> argument
  specifies the port number to use. Normally, this does not need to be
  specified.
  \n
  \n
  The target command selects exactly one target <host>. The <host>
  is a normal internet domain hostname. The optional <port> argument
  specifies the port number to use. Normally, this does not need to be
  specified.
  \n

-gw.help.database: Command:\n
- \tbase base1 base2 ...\n
+gw.help.base: Command:\n
+ \tbase <base1> <base2> ...\n

  \n
  The base command selects one or more databases. However, some 
  targets do not allow the selection of more than one database.
  \n
 gw.help.find: Command:\n
  \n
  The base command selects one or more databases. However, some 
  targets do not allow the selection of more than one database.
  \n
 gw.help.find: Command:\n

- \tfind query\n\n
+ \tfind <query>\n\n

  The find command issues a search request based on the specified
  <query>. A query consists of one or more <search-element>s separated
  The find command issues a search request based on the specified
  <query>. A query consists of one or more <search-element>s separated

- by boolean operators <bool-operator>, i.e.:\n\n
+ by boolean operators <bool-operator>, i.e.:\n

  \tquery = search-element bool-operator search-element ...\n\n
  There are three boolean operators (| means or):\n
  \tbool-operator = and | or | not\n\n
  A search-element has three forms. The first and simplest is
  when it consists of one or more search-terms as in:\n
  \tquery = search-element bool-operator search-element ...\n\n
  There are three boolean operators (| means or):\n
  \tbool-operator = and | or | not\n\n
  A search-element has three forms. The first and simplest is
  when it consists of one or more search-terms as in:\n

- \tsearch-element = search-term ...\n\n
+ \t<search-element> = <search-term> ...\n\n

  In the second form, qualifiers are specified:\n
  In the second form, qualifiers are specified:\n

- \tsearch-element = qualifier relation search-term ...\n\n
+ \t<search-element> = <qualifier> <relation> <search-term> ...\n\n

  A qualifier directs the search to a specified index register. The
  relation is:\n
  A qualifier directs the search to a specified index register. The
  relation is:\n

- \trelation = > | < | >= | <= | = | <>\n\n
+ \t<relation> = > | < | >= | <= | = | <>\n\n

  The third type of <search-element> is the result-set reference:\n
  The third type of <search-element> is the result-set reference:\n

- \tsearch-element = s = name\n\n
+ \t<search-element> = s=<name>\n\n

  Parentheses may be used to create recursive definitions.\n\n
  Some examples, may be in order:\n
  \tfind network\n
  This query consists of one <search-element>, which in turn consists of
  Parentheses may be used to create recursive definitions.\n\n
  Some examples, may be in order:\n
  \tfind network\n
  This query consists of one <search-element>, which in turn consists of

- one <search-term>. The query search for the token "network".\n\n
+ one <search-term>. The query searches for the word "network".\n\n

  \tfind computer network\n
  This is the same as above, but there are two search terms. The
  phrase "computer network" is searched.\n\n
  \tfind computer network\n
  This is the same as above, but there are two search terms. The
  phrase "computer network" is searched.\n\n

- \tfind ti=computer and au=knuth or donald
+ \tfind ti=computer and au=knuth or donald\n

  There are three <search-element>s. The first and second <search-element>
  use qualifiers; the last one doesn't. The search is equivalent to:\n
  \tfind (ti=computer and au=knuth) or donald\n
  If the 'or' is to be applied to "knuth" and "donald", one could use:\n
  \tfind ti=computer and (au=knuth or donald)\n\n
  \tfind computer and s=2\n
  There are three <search-element>s. The first and second <search-element>
  use qualifiers; the last one doesn't. The search is equivalent to:\n
  \tfind (ti=computer and au=knuth) or donald\n
  If the 'or' is to be applied to "knuth" and "donald", one could use:\n
  \tfind ti=computer and (au=knuth or donald)\n\n
  \tfind computer and s=2\n

- Here, the <search-term> "computer" is and'ed with result-set "2".
- Note: The result-set reference faclility is unavailable at the moment.
- \n
+ Here, the <search-term> "computer" is and'ed with result-set "2".\n

 gw.help.show: Command:\n
 gw.help.show: Command:\n

- \tshow show-spec ...\n\n
+ \tshow <show-spec> ...\n\n

  The show command retrieves records. A <show-spec> is a combination
  of record position specifications and a presentation format
  specification. A show command with no <show-spec> retrieves
  10 records and displays them in the full format. A show-spec
  of the form:\n
  The show command retrieves records. A <show-spec> is a combination
  of record position specifications and a presentation format
  specification. A show command with no <show-spec> retrieves
  10 records and displays them in the full format. A show-spec
  of the form:\n

- \tf = type\n
+ \tf = <type>\n

  sets the the format to <type>. Currently, there are three formats:
  0 - full, 1 - medium, 2 compact format. Record positions can
  be specified by the form:\n
  sets the the format to <type>. Currently, there are three formats:
  0 - full, 1 - medium, 2 compact format. Record positions can
  be specified by the form:\n

- \tp = from - to\n
+ \tp = <from> - <to>\n

  Here <from> and <to> are two integers specifying the record
  positions.\n
  Example:\n
  \tshow p=2-7 p=9-10 f=1\n
  Records 2 through 7 and 9-10 are shown in format 1.\n
  Here <from> and <to> are two integers specifying the record
  positions.\n
  Example:\n
  \tshow p=2-7 p=9-10 f=1\n
  Records 2 through 7 and 9-10 are shown in format 1.\n

+gw.help.def:\n
+ \tdef <setting> <value>\n
+ The def command sets/gets various settings. Setting is one of:
+ \tf - display format to be used in show\n
+ \tautoshow - number of records to show after a find\n
+ \tdefaultshow - number of records to retrieve in a show command\n
+ \tlang - conversation language\n
+ \n
+ \treset - resets the settings to their defaults values\n
+ \tshow - show current settings\n
+gw.help.account:\n
+ \taccount <account>\n
+ Sets authentication string. Necessary for some targets.\n
+gw.help.status:\n
+ \tstatus\n
+ Displays information about previous result sets and how they were obtained.\n

 gw.help.general: You 
  have triggered the "help"-information on the Email gateway. \n\n
 gw.help.general: You 
  have triggered the "help"-information on the Email gateway. \n\n

- This preliminary service is a very early alpha release of a Email service
+ This service is the first official release of a Email service

  which acts as a Z39.50-client (origin). \n\n
  With this service you can connect to several Z39.50-targets. Your Email
  body consists of one or more commands. Each command must start on column
  which acts as a Z39.50-client (origin). \n\n
  With this service you can connect to several Z39.50-targets. Your Email
  body consists of one or more commands. Each command must start on column