Appendix B
Diagnostics:
Suggested User Display and Message Logging Using Bib-1 Diagnostic Set
2. Messages - grouped by Response and Case
2.1. General
Messages
2.2. Init
2.3. Search - General
problems with the search statement
2.4. Search - Messages
relating to Database Selection
2.5. Search - Messages
relating to Search Attributes
2.6. Search -
Messages relating to Search Term or Terms
2.7.
Search - Messages relating to Element Set Names and Element Specification
2.8. Search - Messages
relating to Results Set Names
2.9. Search - Messages
relating to Piggyback Present
2.10. Search - Messages
relating to Proximity
2.11. Search - Messages
relating to Search Results
2.12. Present - General messages
2.13. Present - Messages
relating to Results Sets
2.14. Present - Messages
relating to Record Syntax
2.15. Present - Messages relating to Segmentation
2.16. Present -
Messages relating to Individual Records
2.17. Scan - General Messages
2.18. Scan - Messages
relating to Database Selection
2.19. Scan - Messages
relating to Scan attributes
2.20. Explain
2.21. Sort
3. Messages - Numeric Sequence
The tables below indicate the messages that are appropriate for various Z39.50 responses with suggested displays to users. Clients are encouraged to take remedial steps where they are possible without displaying messages. It is recommended that clients log diagnostic messages, particularly those masked, so that a system administrator can use it to:
Some messages are marked specifically "Do not display - origin should correct error". If the origin's program cannot correct the error, then the message "Protocol error (ref. {diagnostic number})" should be displayed, preceded by "Message received from {target name}".
Where there are no possible remedial steps, the client should clearly indicate the source of the message. This is particularly important in the case of multi-target searches. Example:
Message received from {target name}: Cannot sort by {sequence} (ref. 207)
In other cases, remedial steps involve the user in the reconstruction of the message. In this case, the message should be presented along with a list of valid options from which the user may choose. Example:
Message retrieved from {target name}: Cannot perform Periodic Query Schedule as requested (ref. 1057). Your choice was "fortnight". Please make a different selection - weekly, monthly, quarterly.
The suggested displays have been created for a user proficient in searching but not necessarily in Z39.50. The messages have been generalized, avoiding Z39.50 specific technical concepts, however the Bib-1 diagnostic message number has been included in brackets after the message, so that the actual message can be traced. If the client interface is aimed at novice searchers, then it is recommended that the messages be simplified further.
2. Messages - grouped by Response and Case
| Number | Description | Recommended display |
| 1 | Permanent system error | System unavailable - Permanent system error (ref. 1) |
| 2 | Temporary system error | System temporarily unavailable (ref. 2.) |
| 100 | (unspecified) error | Unspecified error (ref. 100) |
| 1001 | Malformed APDU. | Do not display - origin should correct error or display "Protocol error (ref. 1001)" |
| 1025 | Service not supported for this database | Selected database {database} does not support {service} (ref. 1025) |
| 1030 | Currently unassigned | Unknown message (ref. 1030) |
| 1031 | Currently unassigned | Unknown message (ref. 1031) |
| 1032 | Currently unassigned | Unknown message (ref. 1032) |
| 1033 | Currently unassigned | Unknown message (ref. 1033) |
| 1034 | Currently unassigned | Unknown message (ref. 1034) |
| 1035 | Currently unassigned | Unknown message (ref. 1035) |
| 1036 | Currently unassigned | Unknown message (ref. 1036) |
| 1037 | Currently unassigned | Unknown message (ref. 1037) |
| 1038 | Currently unassigned | Unknown message (ref. 1038) |
| 1039 | Currently unassigned | Unknown message (ref. 1039) |
| Number | Description | Recommended display |
| 1010 | Init/AC: Bad Userid | Unknown user identification (ref. 1010) |
| 1011 | Init/AC: Bad Userid and/or Password | Unknown user identification or invalid password (ref. 1011) |
| 1012 | Init/AC: No searches remaining (pre-purchased searches exhausted) | No searches remaining (pre-purchased searches exhausted) (ref. 1012) |
| 1013 | Init/AC: Incorrect interface type (specified id valid only when used with a particular access method or client) | User identifier not valid for this operation ref. 1013) |
| 1014 | Init/AC: Authentication System error | Unknown user identification or invalid password (ref. 1014) |
| 1015 | Init/AC: Maximum number of simultaneous sessions for Userid | System temporarily unavailable (ref. 1015) |
| 1016 | Init/AC: Blocked network address | System temporarily unavailable (ref. 1016) |
| 1017 | Init/AC: No databases available for specified userId | User identifier not valid for any available databases (ref. 1017) |
| 1018 | Init/AC: System temporarily out of resources | System temporarily unavailable (ref. 1018) |
| 1019 | Init/AC: System not available due to maintenance | System temporarily unavailable (ref. 1019) |
| 1020 | Init/AC: System temporarily unavailable | System temporarily available (ref. 1020) |
| 1021 | Init/AC: Account has expired | Access denied - Account has expired (ref. 1021) |
| 1022 | Init/AC: Password has expired so a new one must be supplied | Password expired - please supply new password (ref. 1022) |
| 1023 | Init/AC: Password has been changed by an administrator so a new one must be supplied | Password changed - please supply new password (ref. 1023) |
| 1054 | Init: Required negotiation record not included | Access denied - transaction incomplete (ref. 1054) |
| 1055 | Init: negotiation option required | Access denied - transaction incomplete (ref. 1055) |
For diagnostics 1054 and 1055, it is recommended that the origin should take remedial action instead of displaying this message.
2.3. Search - General problems with the search statement
| Number | Description | Recommended display |
| 3 | Unsupported search | Unsupported search for this database (ref. 3) |
| 11 | Too many characters in search statement | Search cannot be performed - Too long (too many characters in the search) (ref. 11) |
| 101 | Access-control failure | Security failure (ref. 101) |
| 102 | Challenge required, could not be issued - operation terminated | Target protocol error (ref. 102) - (all targets should support search once init successful.) |
| 107 | Query type not supported | Origin should send a type 1 query. If the message is still received, origin should display "Target protocol error (ref. 107)". |
| 108 | Malformed query | Cannot perform search - malformed query (ref. 108) |
2.4. Search - Messages relating to Database Selection
| Number | Description | Recommended display |
| 3 | Unsupported search | Unsupported search for this database (ref. 3) |
| 23 | Specified combination of databases not supported | Specific combination of databases not supported (ref. 23) |
| 29 | One of the specified databases is locked | {Database name} currently unavailable (ref. 29) |
| 109 | Database unavailable | {Database name} currently unavailable (ref. 109) |
| 111 | Too many databases specified | Cannot perform search - too many databases (ref. 111) |
| 235 | Database does not exist | Database does not exist (ref. 235) |
| 236 | Access to specified database denied | Access to {database name} denied (ref. 236) |
| 1025 | Service not supported for this database | Target Protocol error (ref. 1025) |
2.5. Search - Messages relating to Search Attributes
| Number | Description | Recommended display |
| 113 | Unsupported attribute type | Cannot perform search as requested (ref. 113) |
| 114 | Unsupported use attribute | Cannot perform search - {use attribute} not supported (ref. 114) |
| 115 | Unsupported term value for use attribute | Cannot perform search - structure of term not supported (ref. 115) |
| 116 | Use attribute required but not supplied | Do not display - origin should correct error |
| 117 | Unsupported relation attribute | Cannot perform search - {relation attribute} not supported (ref. 117) |
| 118 | Unsupported structure attribute | Cannot perform search - {structure attribute} not supported (ref. 118) |
| 119 | Unsupported position attribute | Cannot perform search - {position attribute} not supported (ref. 119) |
| 120 | Unsupported truncation attribute | Cannot truncate search as requested (ref. 120) |
| 121 | Unsupported attribute set | Cannot search by {attribute set / attribute} (ref. 121) |
| 122 | Unsupported completeness attribute | Cannot perform search - {completeness attribute} not supported (ref. 122) |
| 123 | Unsupported attribute combination | Cannot search {attribute} with {attribute} as requested (ref. 123) |
| 126 | Illegal term value for attribute | Cannot perform search - incorrect construction (ref. 126) |
| 245 | Type-1 query: restriction ('resultAttr') operand not supported | Cannot perform search as requested (ref. 245) |
| 246 | Type-1 query: 'complex' attributeValue not supported | Cannot perform search as requested (ref. 246) |
| 247 | Type-1 query: 'attributeSet' as part of AttributeElement nor supported | Cannot perform search as requested (ref. 247) |
| 1024 | Unsupported Attribute. | Cannot perform search as requested (ref. 1024) |
| 1056 | Attribute not supported for database | Cannot perform search as requested (ref. 1056) |
2.6. Search - Messages relating to Search Term or Terms
| Number | Description | Recommended display |
| 4 | Terms only exclusion (stop) words | Search cannot be performed - only contains common words that are not indexed (ref. 4) |
| 5 | Too many argument words | Search cannot be performed - Too many words or phrases in the search (ref. 5) |
| 6 | Too many boolean operators | Search cannot be performed - Too many words or phrases in the search (ref. 6) |
| 7 | Too many truncated words | Search cannot be performed - Too many truncated words or phrases in the search (ref. 7) |
| 8 | Too many incomplete subfields | Search cannot be performed (ref. 8) |
| 9 | Truncated words too short | Search cannot be performed - Truncated words are too short (ref. 9) |
| 10 | Invalid format for record number (search term) | Search cannot be performed - Invalid format of record number (ref. 10) |
| 110 | Operator unsupported | Cannot perform search - {operator} not supported (ref. 110) |
| 124 | Unsupported coded value for term | Cannot search by {term} (ref. 124) |
| 125 | Malformed search term | Cannot search by {term} (ref. 125) |
| 127 | Unparsable format for unnormalized value | {Unnormalised value} cannot be processed (ref. 127) |
| 1027 | SQL error | Cannot perform search - incorrect construction (ref. 1027) - to be displayed if SQL created by user, else, display "SQL error (ref. 1027)" |
2.7. Search - Messages relating to Element Set Names and Element Specification
| Number | Description | Recommended display |
| 24 | Element set names not supported | Origin should send a present request with an element set name of F or B and give message "Unable to specify record content as requested". If the message is still received, origin should display "Target protocol error (ref. 24)". |
| 25 | Specified element set name not valid for specified database | Origin should send a present request with an element set name of F or B and give message "Unable to specify record content as requested". If the message is still received, origin should display "Target protocol error (ref. 25)". |
| 26 | Only generic form of element set name supported | Origin should send a present request with an element set name of F or B and give message "Unable to specify record content as requested". |
2.8. Search - Messages relating to Results Set Names
| Number | Description | Recommended display |
| 18 | Result set not supported as a search term | Cannot search by {result set name} (ref. 18) |
| 19 | Only single result set as search term supported | Cannot search by more than one named results set (ref. 19) |
| 20 | Only ANDing of a single result set as search term | Cannot perform search - {operator} not valid with a results set. Valid search = {Results set name} AND {term} - Perform search? (ref. 20) |
| 21 | Result set exists and replace indicator off | Cannot create a results set with this name because it already exists - Delete existing results set? (ref. 21) |
| 22 | Result set naming not supported | Naming of search results not supported (ref. 22) |
| 112 | Too many results sets created | Too many results sets already exist, select one or more from the following list to delete (ref. 112) |
| 128 | Illegal result set name | {Results set name} is an illegal name (ref. 128) |
2.9. Search - Messages relating to Piggyback Present
| Number | Description | Recommended display |
Messages relating to Individual Records |
||
| 14 | System error in presenting records | System error - cannot retrieve record or records (ref. 14) |
| 15 | Record not authorized to be sent intersystem | Cannot retrieve requested record - security failure (ref. 15) |
| 16 | Record exceeds Preferred-message-size | Oversized record, cannot be retrieved (ref. 16) |
| 17 | Record exceeds Exceptional-record -size | Oversized record, cannot be retrieved (ref. 17) |
| 103 | Challenge required, could not be issued - record not included | Record could not be retrieved - security failure (ref. 103) |
| 104 | Challenge failed - record not included | Record could not be retrieved - security failure (ref. 104) |
| 1026 | Record cannot be opened because it is locked | Cannot retrieve record, currently locked (ref. 1026) |
| 1028 | Record deleted | Cannot retrieve record - record deleted (ref. 1028) |
Messages relating to Record Syntax |
||
| 106 | No abstract syntaxes agreed to for this record | Cannot retrieve record, record syntax not displayable (ref. 106) |
| 227 | No data available in requested record syntax | Cannot retrieve record, record syntax not displayable (ref. 227) |
| 238 | Record not available in requested syntax | Cannot retrieve record, record syntax not displayable (ref. 238) |
| 239 | Record syntax not supported | Cannot retrieve record, record syntax not displayable (ref. 239) |
Messages relating to Piggyback Present |
||
| 1005 | Response records in Search response not supported. | Do not display - perform a present request |
| 1006 | Response records in Search response not possible for specified database (or database combination). | Do not display - perform a present request |
2.10 Search - Messages relating to Proximity
| Number | Description | Recommended display |
| 129 | Proximity search of sets not supported | Cannot do a proximity search of a results set (ref. 129) |
| 130 | Illegal result set in proximity search | Do not display - origin should correct error |
| 131 | Unsupported proximity relation | Cannot do a proximity search using {relation type} (ref. 131) |
| 132 | Unsupported proximity unit code | Cannot do a proximity search based on {known proximity unit} (ref. 132) |
| 201 | Proximity not supported with this attribute combination | Cannot do a proximity search with {attribute} combined with {attribute} (ref. 201) |
| 202 | Unsupported distance for proximity | Cannot do a proximity search with a distance of {distance} and {known proximity unit} (ref. 202) |
| 203 | Ordered flag not supported for proximity | Do not display - origin should retry without the ordered flag. |
Note that if the origin did not prompt for the proximity parameters then it should not present these messages to the user. In preference, the origin should attempt to construct a proximity search that will be accepted by the target or should revert to a boolean AND combination in the search.
2.11. Search - Messages relating to Search Results
| Number | Description | Recommended display |
| 12 | Too many records retrieved | Too many records retrieved (ref. 12) |
| 31 | Resources exhausted - no results available | Search has not completed - No results available (ref. 31) |
| 32 | Resources exhausted - unpredictable partial results available | Search has not completed - Partial results available, quality unknown (ref. 32) |
| 33 | Resources exhausted - valid subset of results available | Search has not completed - Partial results available (ref. 33) |
2.12. Present - General messages
| Number | Description | Recommended display |
| 13 | Present request out of range | No more records to display ( ref. 13) |
| 101 | Access-control failure | Security failure (ref. 101) |
| 102 | Challenge required, could not be issued - operation terminated | Target protocol error (ref. 102) - (all targets should support present once init successful.) |
| 243 | Present: additional-ranges parameter not supported | Cannot retrieve more than one range of records at once (ref. 243) |
| 244 | Present: comp-spec parameter not supported | Cannot retrieve record with contents as specified (ref. 244) |
| 1066 | CompSpec: Unknown schema, or schema not supported. | Cannot retrieve record with contents as specified (ref. 1066) |
2.13. Present - Messages relating to Results Sets
| Number | Description | Recommended display |
| 27 | Result set no longer exists - unilaterally deleted by target | Cannot retrieve records - results set was deleted (ref. 27) |
| 28 | Result set is in use | Cannot retrieve records - results set currently in use (ref. 28) |
| 30 | Specified result set does not exist | Cannot retrieve records - results set not found (ref. 30) |
2.14. Present - Messages relating to Record Syntax
| Number | Description | Recommended display |
| 106 | No abstract syntaxes agreed to for this record | Cannot retrieve record, record syntax not displayable (ref. 106) |
| 227 | No data available in requested record syntax | Cannot retrieve record, record syntax not displayable (ref. 227) |
| 238 | Record not available in requested syntax | Cannot retrieve record, record syntax not displayable (ref. 238) |
| 239 | Record syntax not supported | Cannot retrieve record, record syntax not displayable (ref. 239) |
2.15. Present - Messages relating to Segmentation
| Number | Description | Recommended display |
| 217 | Segmentation: Cannot guarantee records will fit in specified segments | Oversized record or records, cannot guarantee quality of results (ref. 217) |
| 242 | Segmentation: max-segment-size too small to segment record | Cannot retrieve record - oversized (ref. 242) |
2.16. Present - Messages relating to Individual Records
| Number | Description | Recommended display |
| 14 | System error in presenting records | System error - cannot retrieve record or records (ref. 14) |
| 15 | Record not authorized to be sent intersystem | Cannot retrieve requested record - security failure (ref. 15) |
| 16 | Record exceeds Preferred-message-size | Oversized record, cannot be retrieved (ref. 16) |
| 17 | Record exceeds Exceptional-record -size | Oversized record, cannot be retrieved (ref. 17) |
| 103 | Challenge required, could not be issued - record not included | Record could not be retrieved - security failure (ref. 103) |
| 104 | Challenge failed - record not included | Record could not be retrieved - security failure (ref. 104) |
| 1026 | Record cannot be opened because it is locked | Cannot retrieve record, currently locked (ref. 1026) |
| 1028 | Record deleted | Cannot retrieve record - record deleted (ref. 1028) |
| Number | Description | Recommended display |
| 101 | Access-control failure | Security failure (ref. 101) |
| 102 | Challenge required, could not be issued - operation terminated | Security failure (ref. 102) |
| 205 | Only zero step size supported for scan | Cannot skip records when scanning, can only scan one by one (ref. 205) |
| 206 | Specified step size not supported for scan | Cannot skip {step size} records when scanning (ref. 206) |
| 228 | Scan: malformed scan | Do not display - origin should correct error |
| 229 | Term type not supported | Cannot scan by {term type} (ref. 229). Preferably, origin should retry scan using "general" type |
| 232 | Scan: term list not supported | Cannot perform scan as requested (ref. 232) Preferably origin should perform multiple scans. |
| 233 | Scan: unsupported value of position-in-response | Do not display - origin should resubmit scan without position in response. |
| 234 | Too many index terms processed | Cannot perform scan as requested (ref. 234) Preferably origin should perform multiple scans. |
| 240 | Scan: Resources exhausted looking for satisfying terms | Scan not completed - resources exhausted (ref. 240) |
| 241 | Scan: Beginning or end of term list | Cannot scan any further - beginning or end reached (ref. 241) |
| 1029 | Scan: too many terms requested | Cannot perform scan as requested (ref. 1029) Preferably origin should perform multiple scans. |
2.18. Scan - Messages relating to Database Selection
| Number | Description | Recommended display |
| 109 | Database unavailable | {Database name} currently unavailable (ref. 109) |
| 111 | Too many databases specified | Cannot perform scan - too many databases (ref. 111) |
| 235 | Database does not exist | Database does not exist (ref. 235) |
| 236 | Access to specified database denied | Access to {database name} denied (ref. 236) |
| 1025 | Service not supported for this database | Scan not available for {database name} (ref. 1025) |
2.19. Scan - Messages relating to Scan attributes
| Number | Description | Recommended display |
| 113 | Unsupported attribute type | Cannot perform scan as requested (ref. 113) |
| 114 | Unsupported use attribute | Cannot perform scan - {use attribute} not supported (ref. 114) |
| 115 | Unsupported term value for use attribute | Cannot perform scan - structure of term not supported (ref. 115) |
| 116 | Use attribute required but not supplied | Do not display - origin should correct error |
| 117 | Unsupported relation attribute | Cannot perform scan - {relation attribute} not supported (ref. 117) |
| 118 | Unsupported structure attribute | Cannot perform scan - {structure attribute} not supported (ref. 118) |
| 119 | Unsupported position attribute | Cannot perform scan - {position attribute} not supported (ref. 119) |
| 120 | Unsupported truncation attribute | Cannot truncate scan as requested (ref. 120) |
| 121 | Unsupported attribute set | Cannot scan by {attribute set / attribute} (ref. 121) |
| 122 | Unsupported completeness attribute | Cannot perform scan - {completeness attribute} not supported (ref. 122) |
| 123 | Unsupported attribute combination | Cannot scan {attribute} with {attribute} as requested (ref. 123) |
| 126 | Illegal term value for attribute | Cannot perform scan - incorrect construction (ref. 126) |
| 1024 | Unsupported Attribute. | Cannot perform scan as requested (ref. 1024) |
| 1051 | Scan: Attribute set id required -- not supplied | Do not display - origin should correct error |
| Number | Description | Recommended display |
| 102 | Challenge required, could not be issued - operation terminated | Security failure (ref. 102) |
| 1007 | No Explain server. | Message not displayed - origin should redirect explain request. |
| Number | Description | Recommended display |
| 102 | Challenge required, could not be issued - operation terminated | Security failure (ref. 102) |
| 207 | Cannot sort according to sequence | Cannot sort by {sequence} (ref. 207) |
| 208 | No result set name supplied in sort | Do not display - origin should correct error |
| 209 | Generic sort not supported (database-specific sort only supported) | Can only sort the results from one database (ref. 209) |
| 210 | Database specific sort not supported | Cannot sort results from {Database name} (ref. 210) |
| 211 | Too many sort keys | Unable to sort - too many sort keys (ref. 211) |
| 212 | Duplicate sort keys | Do not display - origin should correct error |
| 213 | Unsupported missing data action | Do not display - origin should correct error |
| 214 | Illegal sort relation | Do not display - origin should correct error |
| 215 | Illegal case value | Do not display - origin should correct error |
| 216 | Illegal missing data action | Do not display - origin should correct error |
| 230 | Sort: too many input results | Too many records to sort (ref. 230) |
| 231 | Sort: incompatible record formats | Unable to sort as requested (ref. 231) |
| 237 | Sort: illegal sort | Do not display - origin should correct error |
3. Messages - Numeric Sequence
| Number | Description | Recommended display |
| 1 | Permanent system error | System unavailable - Permanent system error (ref. 1) |
| 2 | Temporary system error | System temporarily unavailable (ref. 2.) |
| 3 | Unsupported search | Unsupported search for this database (ref. 3) |
| 4 | Terms only exclusion (stop) words | Search cannot be performed - only contains common words that are not indexed (ref. 4) |
| 5 | Too many argument words | Search cannot be performed - Too many words or phrases in the search (ref. 5) |
| 6 | Too many boolean operators | Search cannot be performed - Too many words or phrases in the search (ref. 6) |
| 7 | Too many truncated words | Search cannot be performed - Too many truncated words or phrases in the search (ref. 7) |
| 8 | Too many incomplete subfields | Search cannot be performed (ref. 8) |
| 9 | Truncated words too short | Search cannot be performed - Truncated words are too short (ref. 9) |
| 10 | Invalid format for record number (search term) | Search cannot be performed - Invalid format of record number (ref. 10) |
| 11 | Too many characters in search statement | Search cannot be performed - Too long (too many characters in the search) (ref. 11) |
| 12 | Too many records retrieved | Too many records retrieved (ref. 12) |
| 13 | Present request out of range | No more records to display ( ref. 13) |
| 14 | System error in presenting records | System error - cannot retrieve record or records (ref. 14) |
| 15 | Record not authorized to be sent intersystem | Cannot retrieve requested record - security failure (ref. 15) |
| 16 | Record exceeds Preferred-message-size | Oversized record, cannot be retrieved (ref. 16) |
| 17 | Record exceeds Exceptional-record -size | Oversized record, cannot be retrieved (ref. 17) |
| 18 | Result set not supported as a search term | Cannot search by {result set name} (ref. 18) |
| 19 | Only single result set as search term supported | Cannot search by more than one named results set (ref. 19) |
| 20 | Only ANDing of a single result set as search term | Cannot perform search - {operator} not valid with a results set. Valid search = {Results set name} AND {term} - Perform search? (ref. 20) |
| 21 | Result set exists and replace indicator off | Cannot create a results set with this name because it already exists - Delete existing results set? (ref. 21) |
| 22 | Result set naming not supported | Naming of search results not supported (ref. 22) |
| 23 | Specified combination of databases not supported | Specific combination of databases not supported (ref. 23) |
| 24 | Element set names not supported | Origin should send a present request with an element set name of F or B and give message "Unable to specify record content as requested". If the message is still received, origin should display "Target protocol error (ref. 24)". |
| 25 | Specified element set name not valid for specified database | Origin should send a present request with an element set name of F or B and give message "Unable to specify record content as requested". If the message is still received, origin should display "Target protocol error (ref. 25)". |
| 26 | Only generic form of element set name supported | Origin should send a present request with an element set name of F or B and give message "Unable to specify record content as requested". |
| 27 | Result set no longer exists - unilaterally deleted by target | Cannot retrieve records - results set was deleted (ref. 27) |
| 28 | Result set is in use | Cannot retrieve records - results set currently in use (ref. 28) |
| 29 | One of the specified databases is locked | {Database name} currently unavailable (ref. 29) |
| 30 | Specified result set does not exist | Cannot retrieve records - results set not found (ref. 30) |
| 31 | Resources exhausted - no results available | Search has not completed - No results available (ref. 31) |
| 32 | Resources exhausted - unpredictable partial results available | Search has not completed - Partial results available, quality unknown (ref. 32) |
| 33 | Resources exhausted - valid subset of results available | Search has not completed - Partial results available (ref. 33) |
| 100 | (unspecified) error | Unspecified error (ref. 100) |
| 101 | Access-control failure | Security failure (ref. 101) |
| 102 | Challenge required, could not be issued - operation terminated | For
Search and Present: Target protocol error (ref. 102) For other services: Security failure (ref. 102) |
| 103 | Challenge required, could not be issued - record not included | Record could not be retrieved - security failure (ref. 103) |
| 104 | Challenge failed - record not included | Record could not be retrieved - security failure (ref. 104) |
| 105 | Terminated at origin request | Terminated as requested (ref. 105) (if user initiated the request) |
| 106 | No abstract syntaxes agreed to for this record | Cannot retrieve record, record syntax not displayable (ref. 106) |
| 107 | Query type not supported | Origin should send a type 1 query. If the message is still received, origin should display "Target protocol error (ref. 107)". |
| 108 | Malformed query | Cannot perform search - malformed query (ref. 108) |
| 109 | Database unavailable | {Database name} currently unavailable (ref. 109) |
| 110 | Operator unsupported | Cannot perform search - {operator} not supported (ref. 110) |
| 111 | Too many databases specified | Cannot perform search/scan - too many databases (ref. 111) |
| 112 | Too many results sets created | Too many results sets already exist, select one or more from the following list to delete (ref. 112) |
| 113 | Unsupported attribute type | Cannot perform search/scan as requested (ref. 113) |
| 114 | Unsupported use attribute | Cannot perform search/scan - {use attribute} not supported (ref. 114) |
| 115 | Unsupported term value for use attribute | Cannot perform search/scan - structure of term not supported (ref. 115) |
| 116 | Use attribute required but not supplied | Do not display - origin should correct error |
| 117 | Unsupported relation attribute | Cannot perform search/scan - {relation attribute} not supported (ref. 117) |
| 118 | Unsupported structure attribute | Cannot perform search/scan - {structure attribute} not supported (ref. 118) |
| 119 | Unsupported position attribute | Cannot perform search/scan - {position attribute} not supported (ref. 119) |
| 120 | Unsupported truncation attribute | Cannot truncate search/scan as requested (ref. 120) |
| 121 | Unsupported attribute set | Cannot search/scan by {attribute set / attribute} (ref. 121) |
| 122 | Unsupported completeness attribute | Cannot perform search/scan - {completeness attribute} not supported (ref. 122) |
| 123 | Unsupported attribute combination | Cannot search/scan {attribute} with {attribute} as requested (ref. 123) |
| 124 | Unsupported coded value for term | Cannot search by {term} (ref. 124) |
| 125 | Malformed search term | Cannot search by {term} (ref. 125) |
| 126 | Illegal term value for attribute | Cannot perform search/scan - incorrect construction (ref. 126) |
| 127 | Unparsable format for unnormalized value | {Unnormalised value} cannot be processed (ref. 127) |
| 128 | Illegal result set name | {Results set name} is an illegal name (ref. 128) |
| 129 | Proximity search of sets not supported | Cannot do a proximity search of a results set (ref. 129) |
| 130 | Illegal result set in proximity search | Do not display - origin should correct error |
| 131 | Unsupported proximity relation | Cannot do a proximity search using {relation type} (ref. 131) |
| 132 | Unsupported proximity unit code | Cannot do a proximity search based on {known proximity unit} (ref. 132) |
| 201 | Proximity not supported with this attribute combination | Cannot do a proximity search with {attribute} combined with {attribute} (ref. 201) |
| 202 | Unsupported distance for proximity | Cannot do a proximity search with a distance of {distance} and {known proximity unit} (ref. 202) |
| 203 | Ordered flag not supported for proximity | Do not display - origin should retry without the ordered flag. |
| 205 | Only zero step size supported for scan | Cannot skip records when scanning, can only scan one by one (ref. 205) |
| 206 | Specified step size not supported for scan | Cannot skip {step size} records when scanning (ref. 206) |
| 207 | Cannot sort according to sequence | Cannot sort by {sequence} (ref. 207) |
| 208 | No result set name supplied in sort | Do not display - origin should correct error |
| 209 | Generic sort not supported (database-specific sort only supported) | Can only sort the results from one database (ref. 209) |
| 210 | Database specific sort not supported | Cannot sort results from {Database name} (ref. 210) |
| 211 | Too many sort keys | Unable to sort - too many sort keys (ref. 211) |
| 212 | Duplicate sort keys | Do not display - origin should correct error |
| 213 | Unsupported missing data action | Do not display - origin should correct error |
| 214 | Illegal sort relation | Do not display - origin should correct error |
| 215 | Illegal case value | Do not display - origin should correct error |
| 216 | Illegal missing data action | Do not display - origin should correct error |
| 217 | Segmentation: Cannot guarantee records will fit in specified segments | Oversized record or records, cannot guarantee quality of results (ref. 217) |
| 218 | ES: Package name already in use | Do not display - client should assign a different name |
| 219 | ES: no such package, on modify / delete | Cannot perform {extended service} cannot find task reference number (ref. 219) |
| 220 | ES: quota exceeded | Cannot perform {extended service}, quota exceeded (ref. 220) |
| 221 | ES: extended service type not supported | Cannot perform {extended service}, service not supported (ref. 221) |
| 222 | ES: permission denied on ES - id not authorized | Cannot perform {extended service}, not authorized (ref. 222) |
| 223 | ES: permission denied on ES - cannot modify or delete | Cannot change or delete {extended service}, not authorized (ref. 223) |
| 224 | ES: immediate execution failed | Cannot perform {extended service} interactively (ref. 224) |
| 225 | ES: immediate execution not supported for this service | Cannot perform {extended service} interactively (ref. 225) |
| 226 | ES: immediate execution not supported for these parameters | Cannot perform this {extended service} interactively (ref. 226) |
| 227 | No data available in requested record syntax | Cannot retrieve record, record syntax not displayable (ref. 227) |
| 228 | Scan: malformed scan | Do not display - origin should correct error |
| 229 | Term type not supported | Cannot scan by {term type} (ref. 229). Preferably, origin should retry scan using "general" type |
| 230 | Sort: too many input results | Too many records to sort (ref. 230) |
| 231 | Sort: incompatible record formats | Unable to sort as requested (ref. 231) |
| 232 | Scan: term list not supported | Cannot perform scan as requested (ref. 232) Preferably origin should perform multiple scans. |
| 233 | Scan: unsupported value of position-in-response | Do not display - origin should resubmit scan without position in response. |
| 234 | Too many index terms processed | Cannot perform scan as requested (ref. 234) Preferably origin should perform multiple scans. |
| 235 | Database does not exist | Database does not exist (ref. 235) |
| 236 | Access to specified database denied | Access to {database name} denied (ref. 236) |
| 237 | Sort: illegal sort | Do not display - origin should correct error |
| 238 | Record not available in requested syntax | Cannot retrieve record, record syntax not displayable (ref. 238) |
| 239 | Record syntax not supported | Cannot retrieve record, record syntax not displayable (ref. 239) |
| 240 | Scan: Resources exhausted looking for satisfying terms | Scan not completed - resources exhausted (ref. 240) |
| 241 | Scan: Beginning or end of term list | Cannot scan any further - beginning or end reached (ref. 241) |
| 242 | Segmentation: max-segment-size too small to segment record | Cannot retrieve record - oversized (ref. 242) |
| 243 | Present: additional-ranges parameter not supported | Cannot retrieve more than one range of records at once (ref. 243) |
| 244 | Present: comp-spec parameter not supported | Cannot retrieve record with contents as specified (ref. 244) |
| 245 | Type-1 query: restriction ('resultAttr') operand not supported | Cannot perform search as requested (ref. 245) |
| 246 | Type-1 query: 'complex' attributeValue not supported | Cannot perform search as requested (ref. 246) |
| 247 | Type-1 query: 'attributeSet' as part of AttributeElement nor supported | Cannot perform search as requested (ref. 247) |
| 1001 | Malformed APDU. | Do not display - origin should correct error or display "Protocol error (ref. 1001)" |
| 1002 | ES: EXTERNAL form of Item Order request not supported. | Cannot accept Item Order request as formatted (ref. 1002) |
| 1003 | ES: Result set item form of Item Order request not supported. | Cannot accept Item Order request as formatted (ref. 1003) |
| 1004 | ES: Extended services not supported unless access control is in effect. | Cannot perform {extended service} - security procedures not met (ref. 1004) |
| 1005 | Response records in Search response not supported. | Do not display - perform a present request |
| 1006 | Response records in Search response not possible for specified database (or database combination). | Do not display - perform a present request |
| 1007 | No Explain server. | Message not displayed - origin should redirect explain request. |
| 1008 | ES: missing mandatory parameter for specified function | Cannot perform {extended service} - missing data (ref. 1008) |
| 1009 | ES: Item Order, unsupported OID in itemRequest. | Cannot accept Item Order request as formatted (ref. 1009) |
| 1010 | Init/AC: Bad Userid | Unknown user identification (ref. 1010) |
| 1011 | Init/AC: Bad Userid and/or Password | Unknown user identification or invalid password (ref. 1011) |
| 1012 | Init/AC: No searches remaining (pre-purchased searches exhausted) | No searches remaining (pre-purchased searches exhausted) (ref. 1012) |
| 1013 | Init/AC: Incorrect interface type (specified id valid only when used with a particular access method or client) | User identifier not valid for this operation ref. 1013) |
| 1014 | Init/AC: Authentication System error | Unknown user identification or invalid password (ref. 1014) |
| 1015 | Init/AC: Maximum number of simultaneous sessions for Userid | System temporarily unavailable (ref. 1015) |
| 1016 | Init/AC: Blocked network address | System temporarily unavailable (ref. 1016) |
| 1017 | Init/AC: No databases available for specified userId | User identifier not valid for any available databases (ref. 1017) |
| 1018 | Init/AC: System temporarily out of resources | System temporarily unavailable (ref. 1018) |
| 1019 | Init/AC: System not available due to maintenance | System temporarily unavailable (ref. 1019) |
| 1020 | Init/AC: System temporarily unavailable | System temporarily available (ref. 1020) |
| 1021 | Init/AC: Account has expired | Access denied - Account has expired (ref. 1021) |
| 1022 | Init/AC: Password has expired so a new one must be supplied | Password expired - please supply new password (ref. 1022) |
| 1023 | Init/AC: Password has been changed by an administrator so a new one must be supplied | Password changed - please supply new password (ref. 1023) |
| 1024 | Unsupported Attribute. | Cannot perform search as requested (ref. 1024) |
| 1025 | Service not supported for this database | For Search and
Present - Target Protocol error (ref. 1025) For other services : Selected database {database} does not support {service} (ref. 1025) |
| 1026 | Record cannot be opened because it is locked | Cannot retrieve record, currently locked (ref. 1026) |
| 1027 | SQL error | Cannot perform search - incorrect construction (ref. 1027) - to be displayed if SQL created by user, else, display "SQL error (ref. 1027)" |
| 1028 | Record deleted | Cannot retrieve record - record deleted (ref. 1028) |
| 1029 | Scan: too many terms requested | Cannot perform scan as requested (ref. 1029) Preferably origin should perform multiple scans. |
| 1030 | Currently unassigned | Unknown message (ref. 1030) |
| 1031 | Currently unassigned | Unknown message (ref. 1031) |
| 1032 | Currently unassigned | Unknown message (ref. 1032) |
| 1033 | Currently unassigned | Unknown message (ref. 1033) |
| 1034 | Currently unassigned | Unknown message (ref. 1034) |
| 1035 | Currently unassigned | Unknown message (ref. 1035) |
| 1036 | Currently unassigned | Unknown message (ref. 1036) |
| 1037 | Currently unassigned | Unknown message (ref. 1037) |
| 1038 | Currently unassigned | Unknown message (ref. 1038) |
| 1039 | Currently unassigned | Unknown message (ref. 1039) |
| 1040 | ES: Invalid function | Do not display - origin should correct error |
| 1041 | ES: Error in retention time | Cannot perform {extended service} - invalid transaction data (ref. 1041) |
| 1042 | ES: Permissions data not understood | Cannot perform {extended service} - invalid transaction data (ref. 1042) |
| 1043 | ES: Invalid OID for task specific parameters | Do not display - origin should correct error |
| 1044 | ES: Invalid action | Do not display - origin should correct error |
| 1045 | ES: Unknown schema | Cannot perform {extended service} - {schema} schema unknown (ref. 1045) |
| 1046 | ES: Too many records in package | Do not display - origin should break into two or more packages. If only one record in package, treat as if message 1052. |
| 1047 | ES: Invalid wait action | Do not display - origin should correct error |
| 1048 | ES: Cannot create task package -- exceeds maximum permissible size (see note 4) | Do not display - origin should break into two or more packages. If only one record in package, treat as if message 1052. |
| 1049 | ES: Cannot return task package -- exceeds maximum permissible size for ES response (see note 5) | Not displayed (but may be logged). Origin should search the task package or the database directly. |
| 1050 | ES: Extended services request too large (see note 6) | Do not display - origin should break into two or more packages. If only one record in package, treat as if message 1052. |
| 1051 | ES: Extended services request too large (see note 6) | Do not display - origin should correct error |
| 1052 | ES: Cannot process task package record -- exceeds maximum permissible record size for ES (see note 7) | Cannot update this record - too large (ref. 1052) |
| 1053 | ES: Cannot return task package record -- exceeds maximum permissible record size for ES response (see note 8) | Not displayed (but may be logged). Origin should search the task package or the database directly. |
| 1054 | Init: Required negotiation record not included | Access denied - transaction incomplete (ref. 1054) |
| 1055 | Init: negotiation option required | Access denied - transaction incomplete (ref. 1055) |
| 1056 | Attribute not supported for database | Cannot perform search as requested (ref. 1056) |
| 1057 | ES: Unsupported value of task package parameter | Cannot perform {extended service} as requested (ref. 1057) |
| 1058 | Duplicate Detection: Cannot dedup on requested record portion | Results may contain duplicates (ref. 1058) |
| 1059 | Duplicate Detection: Requested detection criterion not supported | Results may contain duplicates (ref. 1059) |
| 1060 | Duplicate Detection: Requested level of match not supported | Results may contain duplicates (ref. 1060) |
| 1061 | Duplicate Detection: Requested regular expression not supported | Results may contain duplicates (ref. 1061) |
| 1062 | Duplicate Detection: Cannot do clustering | Results may contain duplicates (ref. 1062) |
| 1063 | Duplicate Detection: Retention criterion not supported | Results may contain duplicates (ref. 1063) |
| 1064 | Duplicate Detection: Requested number (or percentage) of entries for retention too large | Results may contain duplicates (ref. 1064) |
| 1065 | Duplicate Detection: Requested sort criterion not supported | Results may contain duplicates (ref. 1065) |
| 1066 | CompSpec: Unknown schema, or schema not supported. | Cannot retrieve record with contents as specified (ref. 1066) |