06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Conventions Using This Manual<br />

Description<br />

Provides a description of the call.<br />

Arguments<br />

Provides descriptions of all arguments used in the call.<br />

Target<br />

Where applicable, provides processor-specific information about the call. The<br />

information appears next to an icon representing the processor in question, as<br />

below:<br />

68K<br />

If the information is also specific to a set of host tools, a host tool icon appears next<br />

to the processor icon, as below:<br />

68K pRISM<br />

Return Value<br />

Lists the possible return values of the call. For example, pSOS+ system calls always<br />

return a 0 to indicate a successful call, and pREPC+ calls can return either a nonzero<br />

value if the test result is true, or 0 if it is false. The Error Codes section lists<br />

possible errors returned by each call.<br />

Error Codes<br />

On 68K processors, a signal is passed to the ASR in the D0.L register.<br />

For 68K processors with pRISM host tools, the formula is the following:<br />

SIZE = 32 + (4 * VSIZE) + (16 * NFD) + (42 * MAXDEPTH)<br />

Provides a list of the error codes that the call can generate. For pSOS+ and pHILE+<br />

system calls, an error code returns as a system call return value. For other components,<br />

such as the pREPC+ component/library and the pNA+ network manager, error<br />

codes are loaded into an internal variable that can be read through the macro<br />

errno. Appendix B contains a complete list of error codes for each software component.<br />

x <strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong>

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

Saved successfully!

Ooh no, something went wrong!