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