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