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.

TABLE 2-2 Fault Summary (Continued)<br />

Mnemonic Description Hex FN1 FN2 PATH1 PATH2 BN Fixable<br />

VF_BBUSE A bad block is in use. 2129 X X X N<br />

VF_BKFRE A block that is in use is also marked as free<br />

in the volume bitmap.<br />

VF_BBFRE A bad block is marked as free in the volume<br />

bitmap.<br />

VF_BKUSE An unused block is marked as in use in the<br />

volume bitmap.<br />

212A X X X Y<br />

212B X Y<br />

212C X Y<br />

VF_INSUFF Work area too small. 2200 Y<br />

VF_MAXDEPTH Directory depth exceeds maximum. 2201 Y<br />

VF_ABORT Verify routine aborted by user. 2202 Y<br />

a. The file descriptor list, one of the management blocks described in the pHILE+ chapter of <strong>System</strong> Concepts.<br />

b. The root block, one of the management blocks described in the pHILE+ chapter of <strong>System</strong> Concepts.<br />

c. File descriptor.<br />

d. File number.<br />

e. If faultp() so requests, verify_vol() corrects this fault by changing the filename to VFN_xxxxxxxx,<br />

where xxxxxxxx is the hexadecimal representation of the file's FN. For example, if the file has an FN of 29<br />

(decimal), the filename is set to VFN_0000001D.<br />

f. If faultp() so requests, verify_vol() corrects this fault by setting the FN to zero (that frees the entry<br />

for reuse).

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

Saved successfully!

Ooh no, something went wrong!