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

Chapter 3 87
NetIPC Intrinsics
IPCCREATE
If no match is found, the incoming call is routed to the catch-all socket if
one has been defined. If the CUD address does not match any of the call
sockets and no catch-all socket has been defined, the incoming call is
cleared. the cause field of the clear packet is set to 0 and the diagnostic
is 64.
The catch-all socket can be defined by setting the
opt protocol flags
catch-all socket flag (bit 2). Only one catch-all socket can be defined per
directly-connected network.
The catch-all socket and address option (protocol relative address) only
apply to switched virtual circuits (SVCs).
Common errors returned by IPCCREATE in result are:
SOCKERR 0 Successful completion.
SOCKERR 4 Transport has not been initialized.
SOCKERR 9 Protocol is not active.
SOCKERR 55 Exceeded protocol module's limit.
SOCKERR 106 Address currently in use by another
socket.
SOCKERR 107 Transport is going down.
SOCKERR 153 Socket is already in use.
A complete table of SOCKERRs is included in Appendix C ,
“Error Messages.”
TCP
for TCP access, only the
socketkind and calldesc parameters are
required.
Cross-System Considerations for TCP
The following are HP 3000 to HP 1000, HP 3000 to HP 9000, and
HP 3000 to PC programming considerations for this intrinsic:
TCP protocol address — Although the ranges of protocol addresses
for each computer system are different, the recommended range for
cross-system user applications is from 30767 to 32767 decimal (%74057
to %77777).