NAME

errors − DECnet-ULTRIX Secondary Error Messages

DESCRIPTION

This is a list and description of the error text that can appear at the end of diagnostic messages for the commands dcat, dcp, dlogin, dls, drm, and the subroutine dnet__conn. These errors fall into the following categories:

Connect Errors Connect errors document failures to establish a DECnet logical link by either the local or remote system. 

General Errors General errors document all other error conditions other than DECnet connect errors. 

Note that DECnet-ULTRIX secondary error messages can also include standard Ultrix errors. 

Connect Errors

Connect failed, connection rejected by object
The logical link connection was rejected by the remote object.

Connect failed, insufficient network resources
The logical link connection was rejected because of insufficient network resources on either the local or the remote node.

Connect failed, unrecognized node name
The logical link could not be connected because the local node could not map the destination node name to any known node address.

Connect failed, remote node shutting down
The logical link could not be connected because the remote node was shutting down.

Connect failed, unrecognized object
The remote node has not defined the object you specified.

Connect failed, invalid object name format
The remote node did not understand the object name format you specified.

Connect failed, object too busy
The logical link connection was rejected by the network partner because the remote object was too busy handling other logical links.

Connect failed, invalid node name format
The logical link could not be connected because the host node name format was incorrect.  A node name is invalid if it contains illegal characters or is too long.   Node names can consist of 1 to 6 alphanumeric characters.

Connect failed, local node shutting down
The logical link could not be connected because the network on the local node was shutting down.

Connect failed, access control rejected
The logical link connection was rejected because the network partner could not successfully validate the access control information it received.

Connect failed, no response from object
The logical link could not be connected because the remote object did not respond.  The object either responded too slowly or terminated abnormally.

Connect failed, node unreachable
The logical link could not be connected because no path exists to the remote node.

General Errors

No such device
The device you specified does not exist on the remote system.

No such file
The file you specified does not exist on the remote system.

Unsupported operation
The remote system does not support the operation you requested.

Bad format DAP message received
An incorrect Data Access Protocol (DAP) message was exchanged with the remote file access listener (fal).  This error can be caused by an internal dcp or fal programming error, or by an incompatibility in DAP version numbers.

DAP message received out of order
A Data Access Protocol (DAP) message was received out of order. This error can be caused by an internal dcp or fal programming error or by an incompatibility in DAP version numbers.

Data type not supported
You attempted to copy a file whose data type is not supported by either the local or the remote system.

File organization not supported
You attempted to copy a file whose organization was not sequential. DECnet-ULTRIX systems support only sequential files.

Record format not supported
You attempted to copy a file whose record format is not supported by either the local or the remote system.

Record attributes not supported
You attempted to copy a file whose record attributes are not supported by either the local or the remote system.

Link to partner broken
The DECnet logical link to the remote file access listener (fal) was broken.  This error can result from a change in the path to the remote node, such as problems with hardware or transmission facilities between the local and the remote node.

Node name format error

The node name you specified was invalid; that is, the name contained illegal characters or was too long.  Node names can consist of 1 to 6 alphanumeric characters. 

Record too big for user’s buffer
You attempted to copy a file which contained a record that is larger than dcp’s or the remote fal’s internal buffer.  This error is frequently the result of an attempt to transfer a non-ASCII file in ASCII mode, which is the default transfer mode to non-ULTRIX systems.

Unspecified access error
An error occurred at the remote system in accessing a file.  For an explanation, see the Data Access Protocol (DAP) error code in /usr/lib/dnet_shared/dap.errors.

File is locked
The file you are attempting to access is locked by the remote system. This error can be caused by a remote system disallowing concurrent reading and writing of a file or by two users simultaneously attempting to write to a file.

Error in file name
The file name you specified does not conform to the syntax of the remote system.  See the DECnet-ULTRIX User’s and Programmer’s Guide for a definition of all DECnet file name specifications. 

Device is write locked
You attempted to to write to a file on a device that was write protected.

Directory is full
The output file you specified cannot be created because there is no room available in the specified directory.

Device not in system
The device you specified is not known to the remote system.

Network operation failed
An operation to the network failed at the remote system.

Operation not supported locally
You attempted to perform an operation that is not supported by your local DECnet-ULTRIX system.  For example, you cannot use dls to list a local directory.

DAP error code (macro:micro)
This message appears when no other specific error message can be provided.  For an explanation, see the Data Access Protocol (DAP) error code in /usr/lib/dnet_shared/dap.errors.