sys_local(2) DG/UX R4.11MU05 sys_local(2)
NAME
sys_local - invoke an extended system call (88k only)
SYNOPSIS
#include <m88kbcs.h>
int syslocal (vendorid, functionid, arg1,arg2 .. arg10 )
int vendorid;
int functionid;
int arg1,arg2 .. arg10;
DESCRIPTION
The 88open Binary Compatibility Standard (BCS) defines syslocal as
the mechanism for accessing an extended system service on a BCS-
compliant platform. For example, you might be using DG/UX to develop
a program that you expect to run on one or more different 88open
platforms. Using syslocal, you can invoke an extended system call
supported by a platform, even if that system call is not supported by
DG/UX.
vendorid is the vendor identifier: 1 selects functions defined in
88open Binary Compatibility Standard Networking
Supplement: 2 selects the symlink and stkexec extensions
defined in the 88open Binary Compatibility Standard,
revision 1.1A. To select functions defined by a specific
88open system, enter the vendor's identifier.
functionid is the function identifier within the set of functions
defined for the given vendor-id.
arg1,arg2.. arg10
are any arguments required by the function indicated by
functionid. Note that you must supply 10 arguments (see
the example, below).
DG/UX supports no syslocal-accessible system calls except those
defined in the 88open standards.
In case of failure, -1 is returned and errno is set to ENOSYS. This
result indicates that the specified syslocal system call is not
implemented on the target system.
EXAMPLE
Implement symlink(2) using the sys-local mechanism:
int symlink (contents, path)
char *contents;/* the 2 arguments required by symlink(2) */
char *path;
{
int vendorid=2;/* symlink is specified under BCS vendorid 2*/
int functionid=4;/* the BCS id of symlink is 4 */
return syslocal
(vendorid,functionid,contents,path,0,0,0,0,0,0,0,0);
}
SEE ALSO
88open Binary Compatibility Standard and 88open Binary Compatibility
Standard Networking Supplement
Licensed material--property of copyright holder(s)