The following messages are logged by the Protocol Emulator (PE).

Address !AD must have a '%' seperating the NAP and ethernet address.
Explanation: Error. The network address for the device is incorrect. See Device address format for information on the proper syntax for the network address.
User Action: Modify the network address using the correct syntax.

Address !AD does not contain a valid ethernet address.
Explanation: Error. The ethernet address part of the network address for the device does not contain twelve hexadecimal digits. See Device address format for information on the proper syntax for the network address.
User Action: Construct a network address that contains an ethernet address of twelve hexadecimal digits.

TSAP list must start with a '(' and end with a ')'.
Explanation: Error. The list of TSAPs in the network address for the device is not delineated by parenthesis. See Device address format for information on the proper syntax for the network address.
User Action: Construct a network address that contains a list of TSAPs delineated by parenthesis.

Error deassigning a channel for TSAP !AD.
Explanation: Error. An error occurred when deasigning an OpenVMS device channel assigned to the indicated TSAP.
User Action: Examine the error and take action based on the error found.

Error translating logical name !AD.
Explanation: Error. The DAS expected (based on the network address syntax) to retrieve some or all of the TSAPs from the indicated logical name, but received an error when attempting to do so.
User Action: Verify that the logical name exists and is in a scope that can be resolved by the ILAN$DEVSRV process.

Syntax for TSAP list !AD is not valid.
Explanation: Error. The indicated list of TSAPs is not formatted correctly. Either expected tokens are missing or a TSAP other than R, W, U, C or O has been specified. See Device address format for more information on the proper syntax for the network address.
User Action: Use the proper syntax for the TSAP list when entering the network address.

Error assigning a channel for TSAP !AD.
Explanation: Error. An error occurred when calling SYS$ASSIGN for the OSI pseudo device.
User Action: Examine the error returned from the call and take action based on the error found.

Error getting timeout value from the path.
Explanation: Error. An error occurred when calling ILAN$$SPT_GET_PORT_INFO to retrieve the timeout value from the path definition.
User Action: Examine the error returned from the call and take action based on the error found.

Error in accessing TSAP !AD.
Explanation: Error. An error occurred when calling SYS$QIO IO$_ACCESS for the indicated TSAP. This call attempts to establish a connection to the indicated TSAP.
User Action: Examine the error returned from the call and take action based on the error found. Make sure that TSAPs are properly configured on the device definition and on the programmable controller. Make sure that the programmable controller communication card is properly configured to accept the connection from the indicated TSAP.

QIO error from !AD request.
Explanation: Error. A QIO error when performing the indicated function.
User Action: Examine the error returned from the call and take action based on the error found.

OSIT error on TSAP !AD.
Explanation: Error. A QIO error occurred when performing an operation on the indicated TSAP. The OSI Transport specific error is logged in this message. See DECnet Plus for OpenVMS Programming Appendix A for a list of OSI Transport specific error codes and their meanings.
User Action: Examine the error returned from the call and take action based on the error found.

Error initiating deaccess request, TSAP = !AD.
Explanation: Error. An error occurred when calling SYS$QIO IO$_DEACCESS | IO$M_ABORT for the indicated TSAP.
User Action: Examine the error returned from the call and take action based on the error found.

!AD request, TSAP is not configured.
Explanation: Error. For the indicated request, the corresponding TSAP has not been configured in the device's network address. (For example, a read request requires that the read TSAP be configured.)
User Action: Configure the required TSAP in the network address and in the corresponding programmable controller.

!AD request, TSAP has not been accessed.
Explanation: Error. The TSAP is configured, but has not been accessed (connected). The connection may have disconnected, so the TSAP is no longer available.
User Action: If the connection disconnected, then the DAS will automatically try to reconnect. If the connection fails, then take action based on the connection failure reason.

Unsolicited TSAP !AD set to permanent.
Explanation: Informational. The unsolicited TSAP was configured as a temporary TSAP. The DAS does not allow the unsolicited TSAP to be temporary.
User Action: None.

Disconnect received.
Explanation: Informational. The DAS received a disconnect on one or more of the currently connected TSAPs. The DAS will abort the connection on all TSAPs.
User Action: None.

Network address !AD, connection completed.
Explanation: Informational. All permanently configured TSAPs for the indicated network address have successfully connected.
User Action: None.

Network address !AD, disconnection completed.
Explanation: Informational. All permanently configured TSAPs for the indicated network address have successfully disconnected.
User Action: None.