06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

pHILE+ <strong>System</strong> <strong>Calls</strong> lock_f<br />

Error Codes<br />

Notes<br />

See Also<br />

Hex Mnemonic Description<br />

0x2015 E_RO Requested operation not allowed on<br />

this file.<br />

0x201A E_FIDBIG Invalid FID; exceeds maximum.<br />

0x201B E_FIDOFF Invalid FID; file closed.<br />

0x2022 E_LOCKED Data locked.<br />

0x2026 E_BADMS MS-DOS volume; illegal operation.<br />

0x2050 E_BADNFS NFS volume; illegal operation.<br />

0x2060 E_BADCD CD-ROM volume; illegal operation.<br />

1. lock_f() enables the locked region to begin and/or end beyond the current<br />

logical or physical end of the file. In such cases, new data that is appended to<br />

the file in the locked region becomes locked.<br />

2. lock_f() does not move the L_ptr.<br />

3. When initially opened, a file connection has no locks.<br />

4. When a connection to a file is closed, any lock it has on the file is removed.<br />

5. A locked region of a file denies read, write, and truncate access to it by any<br />

other file connection. However, annex_f(), which expands a file’s physical size<br />

without changing its logical size, is allowed.<br />

6. Directory and system files cannot be locked.<br />

annex_f<br />

<strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong> 2-57<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!