NetIPC 3000/XL Programmer's Reference Manual (5958-8600)

Table Of Contents
Chapter 3 81
NetIPC Intrinsics
IPCCONTROL
Description
The IPCCONTROL intrinsic is used to perform various special operations
on sockets. This intrinsic is option variable. All requests require the
descriptor
and
request
parameters except
request
14 which
requires
request
and
readdata
only. The timeout requests (code 3 or
262) also require the
wrtdata
parameter. For tracing, socket address
requests, and the local node name, information may be returned in the
readdata
buffer.
Request code 3 is used to set a receive timeout value as specified in
wrtdata
(two bytes). Zero (0) may be used to indicate no timeout. The
timeout value is measured in tenths of a second. The default value is
60 seconds with the timeout enabled.
Request code 3 and the no activity timeout for X.25 (code 13) are
independent timers. Setting one has no influence on the other. Both
timers can be operational at the same time.
Request code 262 is used to set a send timeout value as specified in
wrtdata
(two bytes). Zero (0) may be used to indicate no timeout. If
timeouts are enabled, the timer will expire the number of timeout
seconds (as specified in
wrtdata
) after completion of the last send. The
default value is timeout NOT enabled. There is only one send timer per
connection. It will be running any time there is an outstanding send.
That is, if nowait I/O is used, it will run until IOWAIT completes for all
sends.
For a waited send, the timer will run until the intrinsic completes. If
multiple nowait sends are issued, the timer will be restarted for each
send initiated and for each IOWAIT completed with sends still
outstanding. If a send timer expires before a send completes, the
connection must be shutdown.
Request codes 9 and 15 allow the user to accept or reject a connection
that is in the deferred-connection state (see IPCRECVCN). If the
connection request is accepted, the connection can receive and send
data upon the completion of IPCCONTROL. If the connection is rejected,
all resources allocated for the connection are returned and the
requestor is notified of the rejection.
When requesting the descriptor’s address (request code 514),
readdata
has the meanings shown in Table 3-3.