FILE_INFO

The name of the file.

True (1) if the file exists. False (0) if it does not exist.

True (1) if the file is exists and is readable by the user. False (0) if it is not readable.

True (1) if the file exists and is writable by the user. False (0) if it is not writable.

True (1) if the file exists and is executable by the user. False (0) if it is not executable. The source of this information differs between operating systems:

UNIX: IDL checks the execute bit maintained by the operating system.

Microsoft Windows: The determination is made on the basis of the file name extension (e.g. .exe).

True (1) if the file exists and is a regular disk file and not a directory, pipe, socket, or other special file type. False (0) if it is not a regular disk file (it maybe a directory, pipe, socket, or other special file type).

True (1) if the file exists and is a directory. False (0) if it is not a directory.

True (1) if the file exists and is a UNIX block special device. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and is a UNIX character special device. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and is a UNIX named pipe (fifo) device. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and has its Set-Group-ID bit set. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and has its Set-User-ID bit set. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and is a UNIX domain socket. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and has its sticky bit set. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and is a UNIX symbolic link. On non-UNIX operating systems, this field will always be False (0).

True (1) if the file exists and is a UNIX symbolic link that points at a non-existent file. On non-UNIX operating systems, this field will always be False (0).

The date of last access, date of file status change, and date of last modification given in seconds since 1 January 1970 UTC. Use the SYSTIME function to convert these dates into a textual representation. On Windows platforms the CTIME field will contain the file creation time. On Unix platforms the CTIME field will contain the time of the last file status change.

Note that some file systems do not maintain all of these dates (e.g. MS DOS FAT file systems), and may return 0. On some non-UNIX operating systems, access time is not maintained, and ATIME and MTIME will always return the same date.