Z39.50 Implementor Agreement 5:
Returning diagnostics in an InitResponse
May 2, 1997
A target may supply one or more diagnostics in an InitResponse APDU, within
UserInfo-1, within userInformationField.
When the target wishes to return one or more bib-1 diagnostics, it may do so
using the Diag-1 diagnostic format, selecting defaultDiagRec as the CHOICE for
'diagnostic', and may include multiple bib-1 diagnostics within a single
instance of the format, as it is defined to be a SEQUENCE OF SEQUENCE.
The Diag-1 format may then be included within UserInfo-1,
which is the EXTERNAL to be referenced by userInformationField.
See related agreement Use of Init
Parameters for Negotiation and User Information.
Examples of bib-1 diagnostics meaningful in an Init response are:
- 1010: Init/AC: Bad Userid
- 1011: Init/AC: Bad Userid and/or Password
- 1012: Init/AC: No searches remaining (pre-purchased searches exhausted)
- 1013: Init/AC: Incorrect interface type
(specified id valid only when used with a particular access method
or client)
- 1014: Init/AC: Authentication System error
- 1015: Init/AC: Maximum number of simultaneous sessions for Userid
- 1016: Init/AC: Blocked network address
- 1017: Init/AC: No databases available for specified userId
- 1018: Init/AC: System temporarily out of resources
- 1019: Init/AC: System not available due to maintenance
(Addinfo: when it's expected back up)
- 1020: Init/AC: System temporarily unavailable
(Addinfo: when it's expected back up)
- 1021: Init/AC: Account has expired
- 1022: Init/AC: Password has expired so a new one must be supplied
- 1023: Init/AC: Password has been changed by an administrator so a new
one must be supplied
Library
of Congress