|
|
|
Table 2-2 "NetIPC Calls Affecting the Remote
Process" lists the NetIPC calls affecting communication with the remote
process.
Table 2-2 NetIPC Calls Affecting the Remote Process
| HP 3000 |
HP 1000 |
HP 9000 |
PC |
| IPCCONNECT | IPCConnect |
ipcconnect() | IPCConnect |
| IPCDEST | IPCDest |
ipcdest() | IPCDest |
| IPCLOOKUP | IPCLookUp |
ipclookup() | Not implemented |
| IPCRECV | IPCRecv |
ipcrecv() | IPCRecv |
| IPCRECVCN | IPCRecvCn |
ipcrecvcn() | IPCRecvCn |
| IPCSEND | IPCSend |
ipcsend() | IPCSend |
| IPCSHUTDOWN | IPCShutDown |
ipcshutdown() | IPCShutDown |
HP 3000 to HP 1000 NetIPC
The NetIPC calls affecting cross-system communication with the remote process
have the following differences: checksumming, send and receive sizes, range of
permitted TCP protocol addresses for users, and socket sharing.
Table 2-3 "Cross-System Calls (HP 3000 —
HP 1000)" summarizes the cross-system considerations.
Table 2-3 Cross-System Calls (HP 3000 — HP 1000)
| NetIPC Call |
Cross-System Considerations |
| IPCCONNECT |
Checksumming — TCP checksumming will be enabled for both
sides of the connection if it is enabled by either side for HP 3000 to HP
1000 cross-system communication. On both the HP 3000 and HP 1000
checksumming can be enabled by setting bit 21 in the flags
parameter. |
| Send and receive sizes — The HP 3000 send and receive size
range is 1 to 30,000 bytes. The HP 1000 send and receive size range is 1
to 8,000 bytes. For example, if the HP 3000 node sends 16,000 bytes, the
HP 1000 node can call IPCRECV twice, receiving the first 8,000
bytes the first time and the second 8,000 bytes the second time. |
| Note that the default send and receive sizes are different on different HP
systems. On the HP 3000, the default send and receive size is less than or
equal to 1,024 bytes. On the HP 1000 the default send and receive size is
100 bytes. |
| IPCCREATE IPCDEST |
TCP protocol address — The recommended range of TCP addresses
for cross-system user applications is from 30767 to 32767 decimal (%74057
to%77777). |
| IPCLOOKUP |
No differences that affect-cross-system operations. |
| IPCRECV |
Receive size (dlen parameter) — Range for the
HP 3000 is 1 to 30,000 bytes. Range for the HP 1000 is 1 to 8,000 bytes.
Although the ranges are different, cross-system communication is not
affected. If you specify a send or receive size, be sure it is within the
correct range for the respective system. |
| Data wait flag — The HP 1000 IPCRecv call supports a
"DATA_WAIT" flag. This flag, when set, specifies that the call will not
complete until the amount of data specified by the dlen
parameter has been received. This flag is not available on the HP 3000,
meaning that the call may complete before all the data is received.
However, the HP 3000 IPCRECV supports other flags such as the
"more data" and "destroy data" flags. Refer to the description of
IPCRECV in Chapter 3 "NetIPC Intrinsics"
for more information. |
| IPCRECVCN |
Checksumming — TCP checksumming will be enabled for both
sides of the connection if it is enabled by either side for HP 3000 to HP
1000 connections. On both the HP 3000 and HP 1000 checksumming can be
enabled by setting bit 21 in the flags parameter. |
| Send and receive sizes — The HP 3000 send and receive size range is
1 to 30,000 bytes. The HP 1000 send and receive size range is 1 to 8,000
bytes. For example, if the HP 3000 node sends 16,000 bytes, the HP 1000
node can call IPCRECV twice, receiving 8,000 bytes the first time
and the second 8,000 bytes the second time. |
| Note that the default send and receive sizes are different on different HP
systems. On the HP 3000, the default send and receive size is less than or
equal to 1,024 bytes. On the HP 1000 the default send and receive size is
100 bytes. |
| IPCSEND |
Send size — The HP 3000 send size range is 1 to 30,000 bytes.
The HP 1000 send size is 1 to 8,000 bytes. Although the ranges are
different, cross-system communication is not affected. If you specify a
send or receive size, be sure it is within the correct range for the
respective system. Note that the urgent data bit is not supported on the
HP 1000; however, if this bit is set by the HP 3000 program, it will be
ignored by the receiving process on the HP 1000. |
| IPCSHUTDOWN |
Socket shut down — The HP 3000 provides a graceful release
flag (flag 17) that is not available on the HP 1000. Do not set
the graceful release flag on the HP 3000. Otherwise, the HP 1000 will not
perform a normal shutdown. |
HP 3000 to HP 9000 NetIPC
The NetIPC calls affecting cross-system communication with the remote process
have the following differences. Checksumming, send and receive sizes, range of
permitted TCP protocol addresses for users, and socket sharing.
Table 2-4 "Cross-System Calls (HP 3000 —
HP 9000" lists the NetIPC calls affecting the remote process and
summarizes the cross-system considerations.
Table 2-4 Cross-System Calls (HP 3000 — HP9000
| NetIPC Call |
Cross-System Consideration |
| IPCCONNECT |
Checksumming — When the ipcconnect() call is
executed on the HP 9000 node, checksumming is always enabled. Therefore
checksumming is always enabled for the HP 3000-to-HP 9000 connection.
|
| Send and receive sizes — The HP 3000 send and receive size
range is 1 to 30,000 bytes. The HP 9000 send and receive size range is 1
to 32,767 bytes. Although the ranges are different, cross-system
communication is not affected. If you specify a send or receive size, be
sure it is within correct range for the respective system. |
| Note that the default send and receive sizes are different on different HP
systems. On the HP 3000, the default send and receive size is less than or
equal to 1,024 bytes. On the HP 9000, the default send and receive size is
100 bytes. |
| IPCCREATE IPCDEST |
TCP protocol address — The recommended range of TCP addresses
for cross-system user applications is from 30767 to 32767 decimal (%74057
to %77777). Addresses outside of this range require privileged mode
access. |
| IPCLOOKUP |
No differences that affect cross-system operations. |
| IPCRECV |
Receive size (dlen parameter) — Range for the
HP 3000 is 1 to 30,000 bytes. Range for the HP 9000 is 1 to 32,767 bytes.
Although the ranges are different, cross-system communication is not
affected. If you specify a send or receive size, be sure it is within the
correct range for the respective system. |
| Data wait flag — The HP 9000 IPCRECV call supports a
"DATA_WAIT" flag. This flag, when set, specifies that the call will not
complete until the amount of data specified by the dlen
parameter has been received. This flag is not available on the HP 3000,
meaning that the call may complete before all the data is received.
However, the HP 3000 IPCRECV supports other flags such as the
"more data" and "destroy data" flags. Refer to the description of
IPCRECV in Chapter 3 "NetIPC Intrinsics"
for more information. |
| IPCRECVCN |
Checksumming — When the ipcrecvcn() call is executed
on the HP 9000 node, checksumming is always enabled. |
| Send and receive sizes — The HP 3000 send and receive size
range is 1 to 30,000 bytes. The HP 9000 send and receive size range is 1
to 32,767 bytes. Although the ranges are different, cross-system
communication is not affected. If you specify a send or receive size, be
sure it is within the correct range for the respective system. |
| Note that the default send and receive sizes are different on different HP
systems. On the HP 3000, the default send and receive size is less than or
equal to 1,024 bytes. On the HP 9000, the default send and receive size is
100 bytes. |
| IPCSEND |
Send size — The HP 3000 send size range is 1
to 30,000 bytes. The HP 9000 send size is 32,767 bytes, although the
ranges are different, cross-system communication is not affected. If you
specify a send or receive size, be sure it is within the correct range for
the respective system. |
| Note that the urgent data bit is not supported on the HP 9000; however, if
this bit is set by the HP 3000 program, it will be ignored by the
receiving process on the HP 9000. For differences in send and receive size
see the discussion for IPCRECVCN. |
| IPCSHUTDOWN |
Socket shut down — The HP 3000 provides a graceful release flag that
is not available on the HP 9000. If the graceful release flag
(flag 17) is set on the HP 3000, the HP 9000 will respond
as though it were a normal shutdown. The HP 3000 does not support shared
sockets; the HP 9000 does. Shared sockets are destroyed only when the
descriptor being released is the sole descriptor for the socket. Therefore,
the HP 9000 process may take longer to close the connection than
expected. |
HP 3000 to PC NetIPC
The NetIPC calls affecting cross-system communication with the remote process
have the following differences: checksumming, send and receive sizes, range of
permitted TCP protocol addresses for users, and socket sharing.
Table 2-5 "Cross-System Calls (HP 3000 —
PC)" lists the NetIPC calls affecting the remote process and summarizes
the cross-system considerations.
Table 2-5 Cross-System Calls (HP 3000 — PC)
| NetIPC Call |
Cross-System Considerations |
| IPCCONNECT |
Checksumming — With PC NetIPC, the TCP checksum option cannot
be turned on. But if the HP 3000 requires it, the TCP checksum is in
effect on both sides of the connection. |
| Send and receive sizes — The HP 3000 send and receive size
range is 1 to 30,000 bytes. The PC send and receive size range is 1 to
65,535 bytes. Although the ranges are different, cross-system
communication is not affected. If you specify a send or receive size, be
sure it is within the correct range for the respective system. For
example, if the PC node sends 60,000 bytes, the HP 3000 node can call
IPCRECV twice, receiving the first 30,000 bytes the first time
and the second 30,000 bytes the second time. |
| Note that the default send and receive sizes are different on different HP
systems. On the HP 3000, the default send and receive size is less than or
equal to 1,024 bytes. |
| IPCCREATE IPCDEST |
TCP protocol address — The recommended range of TCP addresses
for cross-system user applications is from 30767 to 32767 decimal (%74057
to %77777). |
| IPCRECV |
Receive size (dlen parameter) — Range for the
HP 3000 is 1 to 30,000 bytes. The PC send and receive size is 1 to 65,535
bytes. Although the ranges are different, cross-system communication is
not affected. If you specify a send or receive size, be sure it is within
the correct range for the respective system. |
| On the PC, you can specify the maximum receive size of the data buffer
through the got array in the IPCCONNECT call.
This determines what the maximum value for dlen can be for
any IPCRECV call. PC NetIPC has no option array defined in
IPCCONNECT. This does not affect cross-system communication. The
maximum receive size of the data in the buffer on the HP 3000 will
determine the receive size buffer on the PC. |
| IPCRECVCN |
Checksumming — With PC NetIPC, the TCP
checksum option cannot be turned on. But if the HP 3000 requires it, the
TCP checksum is in effect on both sides of the connection. |
| Send and receive sizes — The HP 3000 send and receive size
range is 1 to 30,000 bytes. The PC send and receive size range is 1 to
65,535 bytes. Although the ranges are different, cross-system
communication is not affected. If you specify a send or receive size, be
sure it is within the correct range for the respective system. For
example, if the PC node sends 60,000 bytes, the HP 3000 node can call
IPCRECV twice, receiving 30,000 bytes the first time and the
second 30,000 bytes the second time. |
| Note that the default send and receive sizes are different on different HP
systems. On the HP 3000, the default send and receive size is less than or
equal to 1,024 bytes. |
IPCSEND |
Send size — The PC send and receive size range is 1 to 65,635
bytes. Although the ranges are different, cross-system communication is
not affected. If you specify a send or receive size, be sure it is within
the correct range for the respective system. |
| On the PC, you can specify the maximum receive size of the data buffer
through the got array in the IPCCONNECT call.
This determines what the maximum value the dlen parameter
can be for any IPCRECV call. PC NetIPC has no option array
defined for IPCCONNECT. This does not affect cross-system
communication. The maximum receive size of the data in the buffer on the
HP 3000 will determine the receive size buffer on the PC. |
| IPCSHUTDOWN |
Socket shut down — The HP 3000 provides a graceful release
flag that is not available on the PC. If the graceful release flag
(flags 17) is set on the HP 3000, the PC will respond as
though it were a normal shutdown. |
|
