Appendix B: Error Conditions  Appendix C: Using the Command Line-to-DFC Program

Appendix B: Error Conditions

I/O file error conditions

The following list describes the possible error conditions that an I/O file object may encounter during a disk operation, such as reading from or writing to the file. To determine the file error number returned by the operating system when the I/O file object encounters an error, use the errno method.

Table B-1: Error conditions

Mnemonic

Description

FENOERROR

No error.

FEPERM

User needs root permission to access the file.

FENOENT

No such file or directory at the specified location.

FEINTR

A system call was interrupted.

FEIO

An I/O error occurred.

FEBADF

Bad file number. You used the read method on a file before using the open method to open the file.

FENOMEM

Not enough memory available on the system.

FEACCES

Permissions set do not allow access to the file.

FEEXIST

The file or directory exists at the specified location.

FEXDEV

You tried to use the rename method across file systems.

FENOTDIR

Not a directory.

FEISDIR

The I/O file object is referencing a directory.

FEINVAL

You passed an invalid parameter to a method.

FENFILE

The internal table of the number of files open has reached the operating system’s limit. This limit is O/S dependent and may be reconfigurable. Refer to your system’s operating manual for details.

FEMFILE

There are too many files open on the system.

FETXTBSY

You tried to delete a file that is in use.

FEFBIG

The file is too large. How large a file you may open depends upon the operating system’s limit and may be reconfigurable.Refer to your system’s operating manual for details.

FENOSPC

Out of disk space.

FESPIPE

Illegal seek. You read past the end of the file.

FEROFS

Read only file system.

FENOLCK

System record lock table is full.

FEILSEQ

You passed a bad regular expression to the openDir method.

FENOTEMPTY

The directory is not empty.

FENAMETOOLONG

A component of the directory path in the I/O File object’s associated file field is too long, or the entire path is too long. This limit is O/S dependent and may be reconfigurable. Refer to your system’s operating manual for details.

FEUNKNOWN

Unable to determine the error.





Copyright © 2005. Sybase Inc. All rights reserved. Appendix C: Using the Command Line-to-DFC Program

View this book as PDF