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