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

74 Chapter3
NetIPC Intrinsics
IPCCONNECT
X.25 Considerations
IPCCONNECT used over a switched virtual circuit causes the X.25
protocol to send a call request packet to the node and process described
by the destination socket. Over a permanent virtual circuit (PVC), a
reset packet is sent.
The
opt parameter CUD field is sent as the CUD field in the call
request packet. Based on the setting of the
opt protocol flags “no
address” flag, the user has access to either 12 or 16 bytes in the CUD
field. With fast select, the user has access to either 124 or 128 bytes.
For communication between HP nodes, the first four bytes of the CUD
field are interpreted as an address for incoming call packets (the third
and fourth bytes contain the protocol relative address). The X.25
protocol uses this data to find the proper source socket to route the
incoming call. This corresponds to the relative address parameter
passed when the source socket was created.
Common errors returned by IPCCONNECT in
result are:
SOCKERR 0 Request completed successfully.
SOCKERR 46 Unable to interpret received path
report.
SOCKERR 55 Exceeded protocol module's limit.
SOCKERR 116 Destination unreachable.
SOCKERR 143 Invalid facilities set.
SOCKERR 155 Invalid X.25 flags.
SOCKERR 157 No virtual circuit configured.
SOCKERR 160 Incompatible with protocol state.
SOCKERR 162 X.25 permanent virtual circuit does
not exist.
SOCKERR 163 Permanent virtual circuit already
established.
SOCKERR 170 Error with use of the fast select facility.
SOCKERR 171 Invalid facility field opt record entry.
A complete table of SOCKERRs is included in Appendix C ,
“Error Messages.”
TCP Access
If a call socket descriptor is not supplied, or if the specified value is -1, a
“ghost” socket is created for the purpose of setting up the connection.
This temporary socket is destroyed before the IPCCONNECT call is
complete.
Cross-System Considerations for TCP
The following are cross-system programming considerations for this
intrinsic: