The OS Interface: EC

  This section explains the meaning of each value ec in the set EC. The format of each paragraph is:

ec: OS.errMessage[ec] Brief description of ec.

Recall that a value of type EC accompanies the exception Error. Error and EC are defined in Section 3.2, page .

BadExecutableEC: StartProcess format error

The file passed to StartProcess or StartProcessSearch was not recognizable as an a.out file or as an interpreter script.

BadFileEC: Bad file handle

The file handle passed to a procedure had already been closed.

BadFileNameEC: Bad remote path name syntax

The syntax of a remote path name was incorrect.

BadIOCtlOpEC: Bad IOCtl operation or device

The file supplied to IOCtl was not an unstructured device, or else the operation did not apply to the particular device type.

BadPIDEC: No such process

A PID or PGRP parameter did not specify any existing process.

BadStateForSignalEC: Invalid signal state

An attempt was made to set the signal state for a particular signal to a disallowed value.

CannotLinkToDirectoryEC: HardLink to a directory

The new path name supplied to HardLink was a directory.

CannotWriteADirectoryEC: Write to a directory

The path name to be opened for writing was that of a directory.

CrossDeviceLinkEC: Cross-device link

The parameters to HardLink or Rename would have required creating a link to a file on another logical volume.

DirectoryNotEmptyEC: Directory not empty

An attempt was made to delete a directory that was not empty.

DirectoryUnlinkEC: Remove or Rename of a directory

The path name of a directory was supplied where that of a file was required (Remove, Rename).

FileBusyEC: File or directory in use

An attempt was made to open a file whose exclusive-use flag had been set, or to delete a directory that was the root of a file system or was the mount point for another logical volume.

FileExistsEC: File exists

A name proposed for a new directory entry was already in use.

IOErrorEC: I/O error

A problem occurred reading or writing the storage medium underlying a file or directory. This may result in the volume being marked as needing scavenging. The system should log the specific problem, but isn't currently.

InvalidArgumentEC: Invalid argument

The argument for an operation was invalid, e.g., Seek to a negative position, or use of an invalid process template.

InvalidCredentialsEC: Invalid credentials

The supplied real user name and password did not agree with the authentication database.

InvalidObjectEC: Operation/file mismatch

An attempt was made to do an operation on a type of file that doesn't support it, for example a GetLock, SetLock, or SetExclusiveUse on a pipe or socket. It is also raised when an operation such as Read or Write (or Close) is applied to a TEm window that has been destroyed.

LookUpEC: No such file or directory

A component of the path name was not found in the indicated directory.

MinorDeviceDoesNotExistEC: No such minor device number

An attempt was made to open a device, but the minor device number was not known by the driver determined by the major device number.

NameTooLongEC: Name too long

A component of a path name was longer than 255 characters, or, on Ultrix, an entire path name exceeded 1023 characters.

NoDriverForDeviceEC: No such major device number

An attempt was made to open a device, but no device driver had been registered for the corresponding major device number.

NoMountedVolumesEC: No mounted volumes

An attempt was made to look up a path name before any logical volume had been mounted.

NotADirectoryEC: Not a directory

A component of a path name was not a directory.

NotATerminalEC: Not a terminal

An attempt was made to specify as a control terminal a file other than a terminal device.

NotEnoughRoomEC: Not enough disk space

There was insufficient space to create or extend a file.

NotEnoughVMEC: Not enough VM

Starting a process would have required more virtual memory than allowed by the imposed maximum.

NotImplementedEC: Unimplemented operation

An attempt was made to perform an operation that is not yet implemented but that should be. Consult the wrelease notes for details of a particular version.

NotOwnerEC: Not owner

An attempt was made to perform an operation only permissible by the owner of a file or a process.

NotSuperUserEC: Not super-user

An attempt was made to perform an operation only permissible by the super-user, e.g., supplying an explicit User specification to an operation such as Open.

NotTtyOwnerReadEC: Background write

An attempt was made to read or copy from a device without being in its distinguished process group.

NotTtyOwnerWriteEC: Background read

An attempt was made to write or copy to a device without being in its distinguished process group.

OkEC: No error

No error (never raised).

OperationConflictEC: Operation/open mode mismatch

An attempt was made to do an operation that is not compatible with the way the file was opened, e.g., a Write using a file handle opened for reading.

PipeHasNoReaderEC: Broken pipe

An attempt was made to write to a pipe whose reading end is no longer open.

ProtectionViolationEC: Permission denied

An attempt was made to modify a read-only server set or perform an operation on a file or directory whose current access mode disallowed it.

PvOfflineEC: Physical volume not online

A physical disk volume required to perform the operation was offline. The volume needed should be logged, but isn't currently.

RanOutOfResourcesEC: Ultrix server ran out of file descriptors

An open of a file residing on an Ultrix machine failed because of a lack of file descriptors.

RemoteFileEC: Remote file server call failed

An RPC call to a remote server failed. The reason was logged in the tshell window. The call may have been partially executed on the remote machine.

ServerNotAvailableEC: Server not available

A server needed to look up a remote path name was not available.

ShortExecutableEC: StartProcess header/file mismatch

The a.out file supplied to StartProcess or StartProcessSearch was shorter than its header implied.

TooManyProcessesEC: Too many processes

There were no more address spaces (on Taos) or process table entries (on Ultrix) when StartProcess or StartProcessSearch was called.

TooManySymbolicLinksInPathEC: Too many levels of symbolic links

A possible loop in symbolic links was encountered (more than 5 remote symbolic links or 16 symbolic links per remote file machine).

UnseekableObjectEC: Illegal seek

Seek was called with a pipe.

VolumeNeedsCheckingEC: Volume needs scavenging

An inconsistency was found on a disk volume requiring that it be scavenged.

WouldBlockEC: Advisory lock conflict

SetLock was called with noBlock equal to TRUE, and there was a conflict over the lock. (Read and Write never raise WouldBlockEC.)