 |
» |
|
|
|
NetIPC applications can be written to communicate between
MPE-V and MPE XL-based HP 3000s with the following considerations: In addition to the X.25 features supported
on MPE-V, NetIPC on MPE XL systems supports the following: Ability to append, generate and examine the facility
field in call packets Directly specifying the remote host X.25 address
or PVC number.
There are additional differences between
the MPE-V and MPE XL X.25 implementations that can affect NetIPC
programming: On MPE XL, IPCCONTROL request 12, reason for error or event only returns 10 (clear),
11 (reset), or 12 (interrupt). On MPE-V, in addition to returning
10, 11, 12, IPCCONTROL returns 14 (network shutdown), 15 (restart sent
by local network), 16 (level 2 failure), 17(restart sent by local
protocol module), and 18 (restart packet received). On MPE XL, IPCSHUTDOWN completes immediately, while on MPE-V it does
not complete until a clear confirmation arrives. On MPE XL, PAD calls are sent to the catch-all socket
while on MPE-V PAD calls are sent to socket #2563. On MPE XL a reset is not sent to initialize or clear
a PVC, while on MPE-V a reset is sent. MPE-V has a timeout for interrupt collisions, MPE
XL does not. On MPE XL, the IPCCREATE parameter network name must be padded with blanks while on MPE-V, the network
name is padded with nulls.
|
