1 # Email gateway - general kernel resources
2 # $Id: default.res,v 1.28 1995/07/20 08:16:36 adam Exp $
4 # Important directories, programs, etc.
5 gw.reply.mta: /usr/lib/sendmail
6 gw.reply.tmp.prefix: gwr
8 #gw.path: /home/adam/egate/kernel
22 gw.hostname: localhost
23 gw.bibset: default.bib
24 gw.target.loc: loc.res
25 gw.target.drewdb: drewdb.res
26 gw.target.dimitris: dimitris.res
27 gw.target.danbib: dimitris.res
30 # Language definitions
31 gw.lang.dk: lang.dk.res
32 gw.lang.uk: lang.uk.res
35 gw.msg.subject: Your Z39.50 Query...
36 gw.msg.greeting: Europagate Email-Z39.50 gateway
37 gw.msg.cont: Session continued...
38 gw.msg.from: Email-gateway
39 gw.err.nullbody: Empty body
40 ccl.command.find: find f
41 ccl.command.show: show s
42 ccl.command.base: base b
43 ccl.command.help: help h
44 ccl.command.info: info i
45 ccl.command.continue: continue
46 ccl.command.status: status
48 ccl.command.account: account
51 ccl.token.not: not andnot
54 # Diagnostic Conditions
55 gw.bib1.diag.1: Permanent system error
56 gw.bib1.diag.2: Temporary system error
57 gw.bib1.diag.3: Unsupported search
58 gw.bib1.diag.4: Terms only exclusion (stop) words
59 gw.bib1.diag.5: Too many argument words
60 gw.bib1.diag.6: Too many boolean operators
61 gw.bib1.diag.7: Too many truncated words
62 gw.bib1.diag.8: Too many incomplete subfields
63 gw.bib1.diag.9: Truncated words too short
64 gw.bib1.diag.10: Invalid format for record number (search term)
65 gw.bib1.diag.11: Too many characters in search statement
66 gw.bib1.diag.12: Too many records retrieved
67 gw.bib1.diag.13: Present request out of range
68 gw.bib1.diag.14: System error in presenting records
69 gw.bib1.diag.15: Record no authorized to be sent intersystem
70 gw.bib1.diag.16: Record exceeds Preferred-message-size
71 gw.bib1.diag.17: Record exceeds Maximum-record-size
72 gw.bib1.diag.18: Result set not supported as a search term
73 gw.bib1.diag.19: Only single result set as search term supported
74 gw.bib1.diag.20: Only ANDing of a single result set as search term supported
75 gw.bib1.diag.21: Result set exists and replace indicator off
76 gw.bib1.diag.22: Result set naming not supported
77 gw.bib1.diag.23: Combination of specified databases not supported
78 gw.bib1.diag.24: Element set names not supported
79 gw.bib1.diag.25: Specified element set name not valid for specified database
80 gw.bib1.diag.26: Only a single element set name supported
81 gw.bib1.diag.27: Result set no longer exists - unilaterally deleted by target
82 gw.bib1.diag.28: Result set is in use
83 gw.bib1.diag.29: One of the specified databases is locked
84 gw.bib1.diag.30: Specified result set does not exist
85 gw.bib1.diag.31: Resources exhausted - no results available
86 gw.bib1.diag.32: Resources exhausted - unpredictable partial results available
87 gw.bib1.diag.33: Resources exhausted - valid subset of results available
88 gw.bib1.diag.100: Unspecified error
89 gw.bib1.diag.101: Access-control failure
90 gw.bib1.diag.102: Security challenge required but could not be
91 issued - request terminated
92 gw.bib1.diag.103: Security challenge required but could not be
93 issued - record not included
94 gw.bib1.diag.104: Security challenge failed - record not included
95 gw.bib1.diag.105: Terminated by negative continue response
96 gw.bib1.diag.106: No abstract syntaxes agreed to for this record
97 gw.bib1.diag.107: Query type not supported
98 gw.bib1.diag.108: Malformed query
99 gw.bib1.diag.109: Database unavailable
100 gw.bib1.diag.110: Operator unsupported
101 gw.bib1.diag.111: Too many databases specified
102 gw.bib1.diag.112: Too many result sets created
103 gw.bib1.diag.113: Unsupported attribute type
104 gw.bib1.diag.114: Unsupported Use attribute
105 gw.bib1.diag.115: Unsupported value for Use attribute
106 gw.bib1.diag.116: Use attribute required but not supplied
107 gw.bib1.diag.117: Unsupported Relation attribute
108 gw.bib1.diag.118: Unsupported Structure attribute
109 gw.bib1.diag.119: Unsupported Position attribute
110 gw.bib1.diag.120: Unsupported Truncation attribute
111 gw.bib1.diag.121: Unsupported Attribute Set
112 gw.bib1.diag.122: Unsupported Completeness attribute
113 gw.bib1.diag.123: Unsupported attribute combination
114 gw.bib1.diag.124: Unsupported coded value for term
115 gw.bib1.diag.125: Malformed search term
116 gw.bib1.diag.126: Illegal term value for attribute
117 gw.bib1.diag.127: Unparsable format for un-normalized value
118 gw.bib1.diag.128: Illegal result set name
119 gw.bib1.diag.129: Proximity search of sets not supported
120 gw.bib1.diag.130: Illegal result set in proximity search
121 gw.bib1.diag.131: Unsupported proximity relation
122 gw.bib1.diag.132: Unsupported proximity unit code
125 gw.help.target: Command:\n
126 \ttarget <host>[:<port>]\n
128 The target command selects exactly one target <host>. The <host>
129 is a normal internet domain hostname. The optional <port> argument
130 specifies the port number to use. Normally, this does not need to be
133 gw.help.base: Command:\n
134 \tbase <base1> <base2> ...\n
136 The base command selects one or more databases. However, some
137 targets do not allow the selection of more than one database.
139 gw.help.find: Command:\n
141 The find command issues a search request based on the specified
142 <query>. A query consists of one or more <search-element>s separated
143 by boolean operators <bool-operator>, i.e.:\n
144 \tquery = search-element bool-operator search-element ...\n\n
145 There are three boolean operators (| means or):\n
146 \tbool-operator = and | or | not\n\n
147 A search-element has three forms. The first and simplest is
148 when it consists of one or more search-terms as in:\n
149 \t<search-element> = <search-term> ...\n\n
150 In the second form, qualifiers are specified:\n
151 \t<search-element> = <qualifier> <relation> <search-term> ...\n\n
152 A qualifier directs the search to a specified index register. The
154 \t<relation> = > | < | >= | <= | = | <>\n\n
155 The third type of <search-element> is the result-set reference:\n
156 \t<search-element> = s=<name>\n\n
157 Parentheses may be used to create recursive definitions.\n\n
158 Some examples, may be in order:\n
160 This query consists of one <search-element>, which in turn consists of
161 one <search-term>. The query searches for the word "network".\n\n
162 \tfind computer network\n
163 This is the same as above, but there are two search terms. The
164 phrase "computer network" is searched.\n\n
165 \tfind ti=computer and au=knuth or donald\n
166 There are three <search-element>s. The first and second <search-element>
167 use qualifiers; the last one doesn't. The search is equivalent to:\n
168 \tfind (ti=computer and au=knuth) or donald\n
169 If the 'or' is to be applied to "knuth" and "donald", one could use:\n
170 \tfind ti=computer and (au=knuth or donald)\n\n
171 \tfind computer and s=2\n
172 Here, the <search-term> "computer" is and'ed with result-set "2".\n
173 gw.help.show: Command:\n
174 \tshow <show-spec> ...\n\n
175 The show command retrieves records. A <show-spec> is a combination
176 of record position specifications and a presentation format
177 specification. A show command with no <show-spec> retrieves
178 10 records and displays them in the full format. A show-spec
181 sets the the format to <type>. Currently, there are three formats:
182 0 - full, 1 - medium, 2 compact format. Record positions can
183 be specified by the form:\n
184 \tp = <from> - <to>\n
185 Here <from> and <to> are two integers specifying the record
188 \tshow p=2-7 p=9-10 f=1\n
189 Records 2 through 7 and 9-10 are shown in format 1.\n
191 \tdef <setting> <value>\n
192 The def command sets/gets various settings. Setting is one of:
193 \tf - display format to be used in show\n
194 \tautoshow - number of records to show after a find\n
195 \tdefaultshow - number of records to retrieve in a show command\n
196 \tlang - conversation language\n
198 \treset - resets the settings to their defaults values\n
199 \tshow - show current settings\n
201 \taccount <account>\n
202 Sets authentication string. Necessary for some targets.\n
204 have triggered the "help"-information on the Email gateway. \n\n
205 This preliminary service is a very early alpha release of a Email service
206 which acts as a Z39.50-client (origin). \n\n
207 With this service you can connect to several Z39.50-targets. Your Email
208 body consists of one or more commands. Each command must start on column
209 zero; otherwise it will be ignored. Also, everything AFTER the first
210 empty line in your body is ignored. Thus, you probably do not have to
211 delete your signature in the end.\n\n
212 All your requests will be logged. Hopefully you will get a reply with
213 the result of your queries in a minute or two. If you don't something
214 probably went wrong. Hopefully, we will be able to see what went wrong
215 by examining the log files.\n\n
216 This is what you do:\n
217 * First you must select a target (i.e. a host with a Z39.50-interface
218 to one or more databases) with the "target" command. For example:\n
219 \ttarget dranet.dra.com\n
220 * Second, select the databases in which you wish to search, with the
221 "base" command. For example:\n
223 * Now you are ready to issue real queries by using the "find"-command.
224 The query consists of one or more search words. You can perform boolean
225 searches by using the operators "and", "or" and "not". For example:\n
226 \tfind computer and knuth\n
227 If the target supports it, you may also direct the search to special
228 indexes by using qualfiers. For example, the following query will search
229 for "computer" in the "title"-index and "knuth" in the "normal" index:\n
230 \tfind ti=computer and knuth\n\n
231 * If the query succeeds, you will be informed with the number of hits.
232 To display the records use the "show"-command.\n