Chapter 63 NSDS (NonStop Directory Services) Messages

Table of Contents

APS Error Codes

The messages in this chapter are sent by the NonStop Directory Services (NSDS) subsystem that provides an X.500 standard directory service. The subsystem ID displayed by these messages includes NSDS as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

managername DSA SC Process eventsubject: terminateinfo

managername

identifies the name of the Pathmon process that manages the NSDS subsystem.

eventsubject

identifies the event subject or subjects.

terminateinfo

identifies the reason for the termination. The DSA storage-component process is about to terminate itself or is being terminated by the operating system. The possible causes and their associated meanings are as follows:

Termination Cause	Meaning
Process calls exit	STOPPED
Process calls abort	ABORTED
Instruction failure trap	Instruction Failure
Arithmetic overflow trap	Arithmetic Overflow
Illegal address reference trap	Illegal Address Reference
Stack overflow trap	Stack Overflow
Loop-timer timeout trap	Loop-timer Timeout
Termination request	Termination Request

Cause The DSA storage-component process terminated. The termination cause is indicated in the message as terminateinfo.

Effect If the termination is due to an error reported in a previous operator message, investigate the problem associated with the error. Usually, a new process instance is started immediately to take over. If a restart is successful, a message announcing the restart is issued.

Recovery None. The NUMSTATIC parameter in the Pathway server class configuration establishes the number of DSA storage-component processes that run continuously. During normal processing, additional DSA storage-component processes are dynamically started to handle any increased load and then stopped when they are no longer needed. NSDS generates an operator message 1 each time one such additional processes is stopped. If you receive a great number of these operator messages, you might want to increase the value of NUMSTATIC.

managername DSA SC Process eventsubject: STARTED

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem..
`eventsubject`	identifies the event subject or subjects.

Cause The DSA storage-component process is started and is ready for use.

Effect None.

Recovery None. This is an informational message.

managername DSA SC Process eventsubject: File System Error filesyserror File Name filename, addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`filesyserror`	indicates the file‑system error.
`filename`	indicates the name of the file for which the error is reported.
`addlinfo`	indicates any additional information about the error.

Cause The DSA storage-component process encountered an I/O file system error. Possible causes are the following:

The database was not correctly configured.
The alternate collector used to collect accounting messages has terminated.

Effect This error may prevent NSDS from functioning.

Recovery Follow the recovery for the specific error encountered.

managername DSA SC Process eventsubject: Out of Memory

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The DSA storage-component process ran out of available memory. An internal resource management problem is the most likely cause.

Effect This error may prevent NSDS from functioning. The system might be able to correct the situation itself, or it may subsequently fail; in this case, additional messages are issued.

Recovery None. If no operator message 1 is reported for the same eventsubject following this operator message, the process successfully recovered from the error. If, however, an additional operator message 1 is reported for the same eventsubject, the process terminated. In this case, an operator message 2 is issued, indicating that a new process has been started.

managername DSA SC Process eventsubject: Internal Error addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The DSA storage-component process encountered an internal error or unexpected logic error.

Effect This error may lead to subsequent process failure. In this case, additional messages are issued.

managername DSA SC Process eventsubject: Initialization Error addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause Either the schema file has been corrupted, or an invalid DSA name was specified in the installation macros.

Effect The DSA SC process will automatically stop.

Recovery Reinstall the NSDS subsystem with a new DSA name, or change the schema definition file to accept the given name as a valid DSA name.

managername DSA SC Process eventsubject: Attribute Error attrerror addlinfo or managername DSA SC Process eventsubject: Name Error nameerror addlinfo or managername DSA SC Process eventsubject: Security Error secerror addlinfo or managername DSA SC Process eventsubject: Service Error serverror addlinfo or managername DSA SC Process eventsubject: Update Error updateerror addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`attrerror`	identifies the X.500 attribute that is in error.
`addlinfo`	indicates any additional information about the error.
`nameerror`	identifies the X.500 name that is in error.
`secerror`	identifies the security error.
`serverror`	identifies the service error.
`updateerror`	identifies the update error.

Cause An X.500 request has been rejected for the specified reason.

Effect None.

Recovery None. This is an informational message.

101

managername DSA Access Process eventsubject terminateinfo

managername

identifies the name of the Pathmon process that manages the NSDS subsystem.

eventsubject

identifies the event subject or subjects.

terminateinfo

identifies the reason for the termination. The DSA access process is about to terminate itself or is being terminated by the operating system. The possible causes and their associated meanings are as follows:

Termination Cause	Meaning
Process calls exit	STOPPED
Process calls abort	“ABORTED”
Instruction failure trap	Instruction Failure
Arithmetic overflow trap	Arithmetic Overflow
Illegal address reference trap	Illegal Address Reference
Stack overflow trap	Stack Overflow
Loop-timer timeout trap	Loop-timer Timeout
Termination request	Termination Request

Cause The termination cause is indicated in the message as terminateinfo.

Recovery None. If the NSDS subsystem is not being shut down, watch for a subsequent operator message 102 indicating that a new DSA access process has been started. If you receive this message during the normal operation of NSDS, contact the the Global Mission Critical Solution Center (GMCSC).

102

managername DSA Access Process eventsubject: STARTED

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The process is started and is ready for use.

Effect None.

Recovery None. This is an informational message.

103

managername DSA Access Process eventsubject: File System Error filesyserror File Name filename addlinfo or managername DSA Access Process eventsubject: APS Error apserror Subcode apserror, addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`filesyserror`	indicates the file system error. For a list of these codes, see Appendix B.
`filename`	indicates the name of the file for which the error is reported.
`addlinfo`	indicates any additional information about the error.
`apserror`	identifies the APS error code and subcode. For a list of these codes, see “APS Error Codes” and the Tandem OSI/AS Programming Manual.

Cause The DSA access process encountered an I/O error; either a file-system error or an APS procedure call error. For errors from underlying subsystems, the most likely cause is that the subsystem (OSI/AS, OSI/TS, X25AM, or TLAM) was not configured correctly. For file-system errors, the most likely causes are the following:

NSDS was incorrectly installed.
An NSDS file has become corrupted.

Effect This error may prevent NSDS from functioning.

Recovery Recovery is error-dependent. For errors from underlying subsystems, check the subsystem configuration by obtaining a trace of the DSM records or by using the OSI/AS CHECK ENTRY command. For file-system errors, follow the recovery for the specific error encountered.

104

managername DSA Access Process eventsubject: Out of Memory

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The DSA access process ran out of available memory. The most likely cause is an internal resource management problem.

Effect This error may prevent NSDS from functioning. The system might be able to correct the situation itself or it may subsequently fail; in this case, additional operator messages are issued.

Recovery None. If no operator message 101 is reported for the same eventsubject following this operator message, the process successfully recovered from the error. If, however, an additional operator message 101 is reported for the same eventsubject, the process terminated. In this case, an operator message 102 is issued, indicating that a new process has been started.

105

managername DSA Access Process eventsubject: Internal Error addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The process encountered an internal error or unexpected logic error.

Effect This error may lead to subsequent process failure. In this case, additional operator messages are issued.

201

managername DUA Access Process eventsubject: terminateinfo

managername

identifies the name of the Pathmon process that manages the NSDS subsystem.

eventsubject

identifies the event subject or subjects.

terminateinfo

identifies the reason for the termination. The DUA access process is about to terminate itself or is being terminated by the operating system. The possible causes and their associated meanings are as follows:

Termination Cause	Meaning
Process calls exit	STOPPED
Process calls abort	ABORTED
Instruction failure trap	Instruction Failure
Arithmetic overflow trap	Arithmetic Overflow
Illegal address reference trap	Illegal Address Reference
Stack overflow trap	Stack Overflow
Loop-timer timeout trap	Loop-timer Timeout
Termination request	Termination Request

Cause The termination cause is indicated in the message as terminateinfo.

Recovery None. If the NSDS subsystem is not being shut down, watch for a subsequent operator message 202 indicating that a new DUA access process has been started. If you receive this message during the normal operation of NSDS, contact the the Global Mission Critical Solution Center (GMCSC).

202

managername DUA Access Process eventsubject: STARTED

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The DUA access process is started and is ready for use.

Effect None.

Recovery None. This is an informational message.

203

managername DUA Access Process eventsubject: File System Error filesyserror File Name filename addlinfo or managername DUA Access Process eventsubject: APS error apserror Subcode apserror, addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`filesyserror`	indicates the file‑system error. For a list of these codes, see Appendix B.
`filename`	indicates the name of the file for which the error is reported.
`addlinfo`	indicates any additional information about the error.
`apserror`	identifies the APS error code and subcode. For a list of these codes, see “APS Error Codes” and the Tandem OSI/AS Programming Manual.

Cause The DUA access process encountered an I/O error, either a file system error or an APS procedure-call error. For errors from underlying subsystems, the most likely cause is that the subsystem (OSI/AS, OSI/TS, X25AM, or TLAM) was not configured correctly. For file-system errors, the most likely causes are the following:

NSDS was incorrectly installed.
An NSDS file has become corrupted.

Effect This error may prevent NSDS from functioning.

Recovery Recovery is error-dependent. For errors from underlying subsystems, check the subsystem configuration by obtaining a trace of the DSM records or by using the OSI/AS CHECK ENTRY command. For file system errors, follow the recovery for the specific error encountered.

204

managername DUA Access Process eventsubject: Out of Memory

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The DUA access process ran out of available memory. The most likely cause is that there is an internal resource management problem.

Effect This error may prevent NSDS from functioning. The system might be able to correct the situation itself or it may subsequently fail; in this case, additional messages are issued.

Recovery None. If no operator message 201 is reported for the same eventsubject following this operator message, the process successfully recovered from the error. If, however, an additional operator message 201 is reported for the same eventsubject, the process terminated. In this case, an operator message 202 is issued, indicating that a new process has been started.

205

managername DUA Access Process eventsubject: Internal Error addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The DUA access process encountered an internal error or unexpected logic error.

Effect This error may lead to subsequent process failure. In this case, additional messages are issued.

206

managername DUA Access Process eventsubject: Connection Lost

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The requester process died unexpectedly, and the access process was able to detect this condition.

Effect None.

Recovery None. This is an informational message.

Check the requester for reason of the unexpected termination. The requestor process is likely to be an XOM/XDS application process.

207

managername DUA Access Process eventsubject: Initialization Warning addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The DUA access process encountered a problem during initialization. It was able to recover from the problem and continue executing.

Effect The error might have left the process disabled in some way. For example, the process might no longer be able to perform NSAP mapping. The text in addlinfo explains the problem.

Recovery Correct the problem indicated by addlinfo. For example, the NSAPMAP file might require correction. When the necessary corrections are made, stop and restart the process.

301

managername DSA Chaining Process eventsubject: terminateinfo

managername

identifies the name of the Pathmon process that manages the NSDS subsystem.

eventsubject

identifies the event subject or subjects.

terminateinfo

identifies the reason for the termination. The DSA chaining process is about to terminate itself or is being terminated by the operating system. The possible causes and their associated meanings are as follows:

Termination Cause	Meaning
Process calls exit	STOPPE"
Process calls abort	ABORTED
Instruction failure trap	Instruction Failure
Arithmetic overflow trap	Arithmetic Overflow
Illegal address reference trap	Illegal Address Reference
Stack overflow trap	Stack Overflow
Loop-timer timeout trap	Loop-timer Timeout
Termination request	Termination Request

Cause The termination cause is indicated in the message as terminateinfo.

Recovery None. If the NSDS subsystem is not being shut down, watch for a subsequent operator message 302 indicating that a new DSA chaining process has been started. If you receive this message during the normal operation of NSDS, contact the the Global Mission Critical Solution Center (GMCSC).

302

managername DSA Chaining Process eventsubject: STARTED

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The DSA chaining process is started and is ready for use.

Effect None.

Recovery None. This is an informational message.

303

managername DSA Chaining Process eventsubject : File System Error filesyserror File Name filename addlinfo or managername DSA Chaining Process eventsubject: APS Error apserror Subcode apserror, addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`filesyserror`	indicates the file‑system error. For a list of these codes, see Appendix B.
`filename`	indicates the name of the file for which the error is reported.
`addlinfo`	indicates any additional information about the error.
`apserror`	identifies the APS error code and subcode. For a list of these codes, see “APS Error Codes” and the Tandem OSI/AS Programming Manual.

Cause The DSA chaining process encountered an I/O error, either a file system error or an APS procedure-call error. For errors from underlying subsystems, the most likely cause is that the subsystem (OSI/AS, OSI/TS, X25AM, or TLAM) was not configured correctly. For file-system errors, the most likely causes are the following:

NSDS was incorrectly installed.
An NSDS file has become corrupted.

Effect This error may prevent NSDS from functioning.

304

managername DSA Chaining Process eventsubject: Out of Memory

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The DSA chaining process ran out of available memory. The most likely cause is that there is an internal resource-management problem.

Effect This error may prevent NSDS from functioning. The system might be able to correct the situation itself, or it may subsequently fail; in this case, additional messages are issued.

Recovery None. If no operator message 301 is reported for the same eventsubject following this operator message, the process successfully recovered from the error. If, however, an additional operator message 301 is reported for the same eventsubject, the process terminated. In this case, an operator message 302 is issued, indicating that a new process has been started.

305

managername DSA Chaining Process eventsubject: Internal Error addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The DSA chaining process encountered an internal error or unexpected logic error.

Effect This error may lead to subsequent process failure. In this case, additional events are issued.

306

managername DSA Chaining Process eventsubject: Connection Lost

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The requester process died unexpectedly, and the access process was able to detect this condition.

Effect None.

Recovery None. This is an informational message.

Other Considerations. The requester of the chaining process is the DSA storage-component process, so this message may signal a problem with the DSA storage-component process. Normally, additional events concerning the termination of the DSA storage-component process will also be issued by the storage-component process or the operating system.

307

managername DSA Chaining Process eventsubject: Initialization Warning addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The DSA chaining process encountered a problem during initialization. It was able to recover from the problem and continue executing.

Effect The error might have left the process disabled in some way. For example, the process might no longer be able to perform NSAP mapping. The text in addlinfo explains the problem.

Recovery Correct the problem indicated by addlinfo. For example, the NSAPMAP file might require correction. When the necessary corrections are made, stop and restart the process.

501

managername View Access Process eventsubject: terminateinfo

managername

identifies the name of the Pathmon process that manages the NSDS subsystem.

eventsubject

identifies the event subject or subjects.

terminateinfo

identifies the reason for the termination. The view access process is about to terminate itself or is being terminated by the operating system. The possible causes and their associated meanings are as follows:

Termination Cause	Meaning
Process calls exit	STOPPED
Process calls abort	ABORTED
Instruction failure trap	Instruction Failure
Arithmetic overflow trap	Arithmetic Overflow
Illegal address reference trap	Illegal Address Reference
Stack overflow trap	Stack Overflow
Loop-timer timeout trap	Loop-timer Timeout
Termination request	Termination Request

Cause The termination cause is indicated in the message as terminateinfo.

Recovery None. The NUMSTATIC parameter in the Pathway server class configuration establishes the number of view access processes that run continuously. During normal processing, additional view access processes are dynamically started to handle any increased load and then stopped when they are no longer needed. NSDS generates an operator message 1 each time one such additional processes is stopped. If you receive a great number of these operator messages, you might want to increase the value of NUMSTATIC.

502

managername View Access Process eventsubject: STARTED

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The view access process is started and is ready for use.

Effect None.

Recovery None. This is an informational message.

503

managername View Access Process eventsubject: File System Error filesyserror File Error filename addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`filesyserror`	indicates the file‑system error.
`filename`	indicates the name of the file for which the error is reported.
`addlinfo`	indicates any additional information about the error.

Cause The view access process encountered an file system I/O error.

Effect This error may prevent NSDS from functioning.

Recovery Follow the recovery for the specific error encountered.

504

managername View Access Process eventsubject: Out of Memory

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The view access process ran out of available memory. The most likely cause is an internal resource-management problem.

Effect This error may prevent NSDS from functioning. The system might be able to correct the situation itself, or it may subsequently fail; in this case, additional messages are issued.

Recovery None. If no operator message 501 is reported for the same eventsubject following this operator message, the process successfully recovered from the error. If, however, an additional operator message 501 is reported for the same eventsubject, the process terminated. In this case, an operator message 502 is issued, indicating that a new process has been started.

505

managername View Access Process eventsubject: Internal Error addlinfo

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`addlinfo`	indicates any additional information about the error.

Cause The view access process encountered an internal error or unexpected logic error.

Effect This error may lead to subsequent process failure. In this case, additional messages are issued.

506

managername View Access Process eventsubject: Connection Lost

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.

Cause The view access process maintains resources on behalf of a client process. If the connection with that client is lost, the view access process releases all resources. This event is issued when such forced closure of connections occurs. Possible cause include one or more of the following:

TCP/IP terminated
A problem occurred in the TCP/IP stack.
A problem occurred within a remote work station.
A physical loss of link occurred.

Effect None.

Recovery None. This is an informational message.

Other Consideations. Check the relevant Tandem processes, the physical link, and the remote work station to find the source of the connection loss.

551

managername View Listener Process eventsubject: PORT portnumber is in-use by another process

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`portnumber`	identifies the port number assigned to the TCP/IP port.

Cause The view listener process tried to listen on a port that another process is monitoring.

Effect The view listener process cannot function. Thus, no NSDS Viewer client process can bind to the directory that has this view listener process configured as a listener.

Recovery Take either of the following actions:

Change the port number configured for the view listener process and restart the process.
Stop the process that is currently listening on the specified port.

552

managername View Listener Process eventsubject: PORT portnumber is in-use by this process

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`portnumber`	identifies the port number assigned to the TCP/IP port.

Cause The view listener process is now successful in listening on the configured port.

Effect The view listener process is now functional: an NSDS Viewer client process can bind to the directory by means of this view listener process.

Recovery None. This message is an acknowledgement that the the necessary task has been performed.

553

managername View Listener Process eventsubject: Pathsend Error filesyserror to View Access server.

`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.
`eventsubject`	identifies the event subject or subjects.
`filesyserror`	indicates the Pathsend error. For a list of Pathsend errors, see the NonStop TS/MP Pathsend and Server Programming Manual. (Before the D30.02 release, this information was contained in the Pathway Application Programming Guide.)

Cause The view listener process attempted to send a Pathsend request to the view access server process. The attempt failed. Possible reasons for the failure include:

The view access process is not started.
The maximum number of view access servers allowed are currently running and busy servicing other clients. The maximum number of allowed servers is determined by the MAXSERVERS parameter specified during PATHMON configuration.

Effect No NSDS Viewer client process can connect to the directory.

Recovery If the view access process is not running, it should be started.

If the MAXSERVERS limit had been exceeded, the user should continue to issue Connect requests at the PC until a server becomes available. If this problem recurs, specify a higher value for MAXSERVERS in the PATHMON configuration.

901

Operator attention need for eventsubject please , event number: 901 , action ID: actionID , manager: managername

`eventsubject`	identifies the name of the alternate collector process.
`actionID`	identifies the action ID for this request. It is used to associate this request with the corresponding Operator Attention Completed operator message (NSDS operator message 902).
`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.

Cause The NSDS subsystem failed to write an accounting event to the alternate collector process because the alternate collector process is not available.

Effect Accounting events are discarded until the alternate collector process is started.

Recovery Restart the alternate collector process.

902

Operator attention completed for eventsubject thank you , event number: 902 , action ID: actionID , manager: managername

`eventsubject`	identifies the name of the alternate collector process.
`actionID`	identifies the action ID that was specified in the original Operator Action Needed request (NSDS operator message 901).
`managername`	identifies the name of the Pathmon process that manages the NSDS subsystem.

Cause The alternate collector is available again, and the NSDS subsystem is logging accounting events to it.

Effect Accounting events are once again collected.

Recovery None. This message is an acknowledgement that the operator has performed the required task.

1001

Bind attempt: result, direction protocol, AssocID: assocID.

`result`	indicates whether the association attempt was successful. The values are either Success or Failure.
`direction`	indicates whether the local system is the association initiator or responder. Inbound signifies that the local system is the responder. Outbound signifies that the local system is the initiator.
`protocol`	indicates the protocol used for this association. Values are either DAP or DSP.
`assocID`	is the correlation identifier that identifies this particular association. It is displayed only when a Bind attempt is successful. The correlation identifier value also appears in operator messages 1002 and 1003. This value allows you to correlate specific operations described in operator message 1003 with a specific association. A correlation identifier uniquely identifies an association only for the duration of that association. The same identifier value can be reused repeatedly for other associations at later times.

Cause A requesting process has attempted to establish an association by means of a Bind operation. For inbound requests (in which a local process is the responder), NSDS generates this message because:

A local XDS application that incorporates the DUA library attempted to bind to a DSA storage-component process and access the local DIB.
A remote DUA or DSA , using the services of the DSA access process, attempted to bind to a DSA storage-component process and establish an association.

For outbound requests (in which a remote process is the responder), NSDS generates this message because a DSA storage-component process has attempted to bind to a remote DSA through the DSA chaining process.

Effect None.

Recovery None. This is a informational accounting message.

1002

UNBIND: normal, AssocId: assocID.

assocID

is the correlation identifier that identifies this particular association. A correlation identifier uniquely identifies an association only for the duration of that association. The same identifier value can be reused repeatedly for other associations at later times.

Cause The association (specified by AssocID) has ended by means of an Unbind operation.

Effect None.

Recovery This is a informational accounting message.

1003

optype: result size was resultsize bytes in responseentries entries. AssocID: AssocID.

optype

identifies the Directory Access Protocol (DAP) or Directory System Protocol (DSP) operation performed. Values are:

Value	Meaning
Read Operation	The operation is either a DAP Read or a DSP Chained Read. These operations read information from a single directory entry.
Compare Operation	The operation is either a DAP Compare or a DSP Chained Compare. These operations compare a value asserted in the request.
Abandon Operation	The operation is either a DAP Abandon or a DSP Chained Abandon. These operations indicate to the directory that a DUA no longer wants the result of an operation.
List Operation	The operation is either a DAP List or a DSP Chained List. These operations list the names of the immediate subordinates of particular entry.
Search Operation	The operation is either a DAP Search or a DSP Chained Search. These operations retrieve information from all entries, within a section of the DIT, that match the specified filter (s).
Add Entry Operation	The operation is either a DAP Add Entry or a DSP Chained Add Entry. These operations add a leaf entry to the DIT.
Remove Entry Operation	The operation is either a DAP Remove Entry or a DSP Chained Remove Entry. These operations remove a leaf entry from the DIT.
Modify Entry Operation	The operation is either a DAP Modify Entry or a DSP Chained Modify Entry. These operations modify the attributes of a particular entry.
Modify Rdn Operation	The operation is either a DAP Modify RDN or a DSP Chained Modify RDN These operations modify the relative distinguished name of a leaf entry.

resultsize

indicates the size of the operation result in bytes.

responseentries

indicates the number of directory entries returned in the result.

AssocID

is the correlation identifier that identifies this particular association. It allows you to correlate the operation reported in this message with a specific association.

A correlation identifier uniquely identifies an association only for the duration of that association. The same identifier value can be reused repeatedly for other associations at later times.

Cause A protocol operation has completed during the particular association indicated by AssocID.

Effect None.

Recovery This is an informational accounting message.

APS Error Codes

NSDS uses Open System Interconnection (OSI) protocols for communication with remote NSDS subsystems and with other DSAs. The upper three layers of OSI (Application, Presentation, and Session) are implemented in the Tandem OSI/AS product. NSDS uses only the Session Layer of OSI/AS.

A set of APS procedure calls are included as part of the OSI/AS subsystem. These procedure calls provide NSDS with access to the Session Layer. The APS procedures return status codes indicating the success or failure of a procedure call.

Following is a list of these status codes and a brief description of each. For information about correcting APS errors, see the Tandem OSI/AS Programming Manual.

Number	Description
0	Operation succeeded.
1	You have received an event.
2	Operation failed; don’t retry.
3	Operation failed; retry immediately.
4	Operation failed; retry after a delay.
5	Operation failed;get operator; retry.
6	Operation failed; abort connection.
7	Operation failed; discard connection.
8	Operation failed; status unknown.