TCP/IP Programming Manual

Usage Guidelines
• Use socket_get_open_info after creating a socket using the socket or socket_nw
functions. Then, immediately checkpoint the data.
• Use socket_get_open_info to checkpoint state information to a backup process after a
call to AWAITIOX and before subsequent AWAITIOX calls.
• The user application must fill in the filenum, flags and sync variables in the
open_info_message structure before calling this function. Flags and sync must have the
same values that were used in the call to socket()/socket_nw() that resulted in the
opening of the socket identified by filenum. Immediately after the call to
socket_get_open_info(), the user application must checkpoint the information by
whatever means is being employed (passive or active) to its backup process.
socket_ioctl, socket_ioctl_nw
The socket_ioctl and socket_ioctl_nw functions perform a control operation on a socket.
NOTE: In CIP, certain socket_ioctl and socket_ioctl_nw operations are not supported, may have
different defaults, or have different behavior. See the Cluster I/O Protocols (CIP) Configuration
and Management Manual for details.
C Synopsis
#include <socket.h>
#include <in.h>
#include <in6.h> /* for IPv6 use */
#include <if.h>
#include <route.h>
#include <mbuf.h>
#include <ioctl.h>
#include <netdb.h>
error = socket_ioctl (socket, command, arg_ptr);
error = socket_ioctl_nw (socket, command, arg_ptr, tag);
int error, socket, command;
long tag;
char *arg_ptr;
TAL Synopsis
?NOLIST, SOURCE SOCKDEFT
?NOLIST, SOURCE SOCKPROC
error := socket_ioctl (socket, command, arg_ptr);
error := socket_ioctl_nw (socket, command, arg_ptr, tag);
INT(32) error,
socket,
command;
STRING .EXT arg_ptr;
INT(32) tag;
error
return value; f the call is successful, a zero is returned. If the call is not successful, –1 is returned.
If the call failed, the external variable errno is set as indicated in Errors (page 198).
socket_ioctl, socket_ioctl_nw 197