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