# Email gateway - general kernel resources # $Id: default.res,v 1.32 2001/02/26 14:32:36 adam Exp $ # # Important directories, programs, etc. gw.reply.mta: /usr/lib/sendmail gw.reply.tmp.prefix: gwr gw.reply.tmp.dir: /tmp #gw.path: /home/adam/egate/kernel gw.marc.log: marc.log gw.timeout: 30 gw.resultset: 1 gw.persist: 1 gw.max.process: 3 # Retrieval settings gw.ignore.which: 0 gw.default.show: 10 gw.max.show: 100 # Target definitions gw.portno: 210 gw.hostname: localhost gw.bibset: default.bib gw.target.loc: loc.res gw.target.drewdb: drewdb.res gw.target.bagel: bagel.res gw.databases: # Language definitions gw.lang.dk: lang.dk.res gw.lang.uk: lang.uk.res # Messages gw.msg.subject: Your Z39.50 Query... gw.msg.greeting: Europagate Email-Z39.50 gateway gw.msg.cont: Session continued... gw.msg.from: Email-Z39.50 gateway gw.err.nullbody: Empty body ccl.command.find: find f ccl.command.show: show s ccl.command.base: base b ccl.command.help: help h ccl.command.info: info i ccl.command.continue: continue ccl.command.status: status ccl.command.def: def ccl.command.account: account ccl.token.and: and ccl.token.or: or ccl.token.not: not andnot ccl.token.set: set s # Diagnostic Conditions gw.bib1.diag.1: Permanent system error gw.bib1.diag.2: Temporary system error gw.bib1.diag.3: Unsupported search gw.bib1.diag.4: Terms only exclusion (stop) words gw.bib1.diag.5: Too many argument words gw.bib1.diag.6: Too many boolean operators gw.bib1.diag.7: Too many truncated words gw.bib1.diag.8: Too many incomplete subfields gw.bib1.diag.9: Truncated words too short gw.bib1.diag.10: Invalid format for record number (search term) gw.bib1.diag.11: Too many characters in search statement gw.bib1.diag.12: Too many records retrieved gw.bib1.diag.13: Present request out of range gw.bib1.diag.14: System error in presenting records gw.bib1.diag.15: Record no authorized to be sent intersystem gw.bib1.diag.16: Record exceeds Preferred-message-size gw.bib1.diag.17: Record exceeds Maximum-record-size gw.bib1.diag.18: Result set not supported as a search term gw.bib1.diag.19: Only single result set as search term supported gw.bib1.diag.20: Only ANDing of a single result set as search term supported gw.bib1.diag.21: Result set exists and replace indicator off gw.bib1.diag.22: Result set naming not supported gw.bib1.diag.23: Combination of specified databases not supported gw.bib1.diag.24: Element set names not supported gw.bib1.diag.25: Specified element set name not valid for specified database gw.bib1.diag.26: Only a single element set name supported gw.bib1.diag.27: Result set no longer exists - unilaterally deleted by target gw.bib1.diag.28: Result set is in use gw.bib1.diag.29: One of the specified databases is locked gw.bib1.diag.30: Specified result set does not exist gw.bib1.diag.31: Resources exhausted - no results available gw.bib1.diag.32: Resources exhausted - unpredictable partial results available gw.bib1.diag.33: Resources exhausted - valid subset of results available gw.bib1.diag.100: Unspecified error gw.bib1.diag.101: Access-control failure gw.bib1.diag.102: Security challenge required but could not be issued - request terminated gw.bib1.diag.103: Security challenge required but could not be issued - record not included gw.bib1.diag.104: Security challenge failed - record not included gw.bib1.diag.105: Terminated by negative continue response gw.bib1.diag.106: No abstract syntaxes agreed to for this record gw.bib1.diag.107: Query type not supported gw.bib1.diag.108: Malformed query gw.bib1.diag.109: Database unavailable gw.bib1.diag.110: Operator unsupported gw.bib1.diag.111: Too many databases specified gw.bib1.diag.112: Too many result sets created gw.bib1.diag.113: Unsupported attribute type gw.bib1.diag.114: Unsupported Use attribute gw.bib1.diag.115: Unsupported value for Use attribute gw.bib1.diag.116: Use attribute required but not supplied gw.bib1.diag.117: Unsupported Relation attribute gw.bib1.diag.118: Unsupported Structure attribute gw.bib1.diag.119: Unsupported Position attribute gw.bib1.diag.120: Unsupported Truncation attribute gw.bib1.diag.121: Unsupported Attribute Set gw.bib1.diag.122: Unsupported Completeness attribute gw.bib1.diag.123: Unsupported attribute combination gw.bib1.diag.124: Unsupported coded value for term gw.bib1.diag.125: Malformed search term gw.bib1.diag.126: Illegal term value for attribute gw.bib1.diag.127: Unparsable format for un-normalized value gw.bib1.diag.128: Illegal result set name gw.bib1.diag.129: Proximity search of sets not supported gw.bib1.diag.130: Illegal result set in proximity search gw.bib1.diag.131: Unsupported proximity relation gw.bib1.diag.132: Unsupported proximity unit code # Help messages gw.help.target: Command:\n \ttarget [:]\n \n The target command selects exactly one target . The is a normal internet domain hostname. The optional argument specifies the port number to use. Normally, this does not need to be specified. \n gw.help.base: Command:\n \tbase ...\n \n The base command selects one or more databases. However, some targets do not allow the selection of more than one database. \n gw.help.find: Command:\n \tfind \n\n The find command issues a search request based on the specified . A query consists of one or more s separated by boolean operators , i.e.:\n \tquery = search-element bool-operator search-element ...\n\n There are three boolean operators (| means or):\n \tbool-operator = and | or | not\n\n A search-element has three forms. The first and simplest is when it consists of one or more search-terms as in:\n \t = ...\n\n In the second form, qualifiers are specified:\n \t = ...\n\n A qualifier directs the search to a specified index register. The relation is:\n \t = > | < | >= | <= | = | <>\n\n The third type of is the result-set reference:\n \t = s=\n\n Parentheses may be used to create recursive definitions.\n\n Some examples, may be in order:\n \tfind network\n This query consists of one , which in turn consists of one . The query searches for the word "network".\n\n \tfind computer network\n This is the same as above, but there are two search terms. The phrase "computer network" is searched.\n\n \tfind ti=computer and au=knuth or donald\n There are three s. The first and second use qualifiers; the last one doesn't. The search is equivalent to:\n \tfind (ti=computer and au=knuth) or donald\n If the 'or' is to be applied to "knuth" and "donald", one could use:\n \tfind ti=computer and (au=knuth or donald)\n\n \tfind computer and s=2\n Here, the "computer" is and'ed with result-set "2".\n gw.help.show: Command:\n \tshow ...\n\n The show command retrieves records. A is a combination of record position specifications and a presentation format specification. A show command with no retrieves 10 records and displays them in the full format. A show-spec of the form:\n \tf = \n sets the the format to . Currently, there are three formats: 0 - full, 1 - medium, 2 compact format. Record positions can be specified by the form:\n \tp = - \n Here and are two integers specifying the record positions.\n Example:\n \tshow p=2-7 p=9-10 f=1\n Records 2 through 7 and 9-10 are shown in format 1.\n gw.help.def:\n \tdef \n The def command sets/gets various settings. Setting is one of: \tf - display format to be used in show\n \tautoshow - number of records to show after a find\n \tdefaultshow - number of records to retrieve in a show command\n \tlang - conversation language\n \n \treset - resets the settings to their defaults values\n \tshow - show current settings\n gw.help.account:\n \taccount \n Sets authentication string. Necessary for some targets.\n gw.help.status:\n \tstatus\n Displays information about previous result sets and how they were obtained.\n gw.help.general: You have triggered the "help"-information on the Email gateway. \n\n This service is the first official release of a Email service which acts as a Z39.50-client (origin). \n\n With this service you can connect to several Z39.50-targets. Your Email body consists of one or more commands. Each command must start on column zero; otherwise it will be ignored. Also, everything AFTER the first empty line in your body is ignored. Thus, you probably do not have to delete your signature in the end.\n\n All your requests will be logged. Hopefully you will get a reply with the result of your queries in a minute or two. If you don't something probably went wrong. Hopefully, we will be able to see what went wrong by examining the log files.\n\n This is what you do:\n * First you must select a target (i.e. a host with a Z39.50-interface to one or more databases) with the "target" command. For example:\n \ttarget dranet.dra.com\n * Second, select the databases in which you wish to search, with the "base" command. For example:\n \tbase drewdb\n\n * Now you are ready to issue real queries by using the "find"-command. The query consists of one or more search words. You can perform boolean searches by using the operators "and", "or" and "not". For example:\n \tfind computer and knuth\n If the target supports it, you may also direct the search to special indexes by using qualfiers. For example, the following query will search for "computer" in the "title"-index and "knuth" in the "normal" index:\n \tfind ti=computer and knuth\n\n * If the query succeeds, you will be informed with the number of hits. To display the records use the "show"-command.\n