pSOSystem System Calls - Read

Error Codes pHILE+ Error Codes
TABLE B-3 pHILE+ Error Codes (Continued)
Hex Mnemonic and Description System Call(s)
0x2015 E_RO: Requested operation not allowed on this
file. This error implies one of the following:
■ An attempt was made to write to or lock
BITMAP.SYS,
file.
FLIST.SYS, or a directory
■ Attempted to remove a system file.
■ Attempted to annex to
FLIST.SYS.
BITMAP.SYS or
■ Attempted to write to a volume mounted
with sync_mode set to SM_READ_ONLY. *
0x2016 E_DIFDEV: move_f() across volumes. The old
and new pathnames specified on a move_f()
call are not on the same device.
0x2017 E_NOTREE: move_f() would destroy directorytree
structure. Attempted to move a directory file
to a location within its own sub-tree. If allowed,
the volume's file system hierarchy would no
longer be a tree structure.
0x2018 E_OFULL: Too many files open for task. A task
attempted to open more files than specified by
the pHILE+ Configuration Table parameter
fc_ncfile.
0x2019 E_NOFCB: Too many files open in system. An
open_f() attempt will exceed the maximum
number of open files allowed in the system as
specified by the pHILE+ Configuration Table parameter
fc_nfcb.
0x201A E_FIDBIG: Invalid FID, out of range. The FID
provided on a pHILE+ call has a value that could
not have been returned by an open_f() call.
close_dir() will return this error code only if
dd_fn in the XDIR has been corrupted.
annex_f, chmod_f,
chown_f, create_f,
fchmod_f, fchown_f,
ftruncate_f, link_f,
lock_f, make_dir,
move_f, remove_f,
truncate_f, utime_f,
write_f, write_vol
move_f
move_f
open_dir, open_f,
open_fn,
open_dir, open_f,
open_fn,
annex_f, close_dir,
close_f, fchmod_f,
fchown_f, fstat_f,
fstat_vfs,
ftruncate_f, lock_f,
lseek_f, read_f,
write_f
pSOSystem System Calls B-19
B