|
|
|
Table of Contents
- NetIPC Concepts
- Sockets
- Connections
- Using NetIPC for Interprocess Communication
- Establishing a Level 4 Connection
- Sending and Receiving Data Over a
Connection
- Shutting Down Sockets and Connections
- Additional NetIPC Functions
- Direct Access to Level 3 (X.25)
- Features
- Limitations
- Switched Virtual Circuits (SVCs)
- Permanent Virtual Circuits (PVCs)
- Access to the Call User Data (CUD)
Field
- Fast Select Facility
- Facility Field
- Access to X.25 Protocol Features
- NetIPC Between MPE-XL and MPE-V Systems
Network Interprocess Communication (NetIPC) is a facility that enables
processes on the same or different nodes to communicate with each other using
a series of programmatic calls.
NetIPC 3000/XL can be purchased as part of any NS 3000/XL link product. It
provides access to the Transmission Control Protocol (TCP), the Transport
Layer protocol used in NS 3000/XL link products. Over an NS X.25 network,
NetIPC provides access to X.25 protocol features at level 3.
To communicate by means of NetIPC, processes must be executing concurrently.
One or more users (or programs) can run these processes independently, or one
process can initiate the execution of another by using the Remote Process
Management (RPM) Network Service. In conjunction with NetIPC, RPM can be used
to manage distributed applications. Refer to the
Using NS 3000/XL Network
Services manual for information about RPM.
Processes that use NetIPC calls gain access to the communication services
provided by the network protocols of NS 3000/XL. NetIPC does not encompass a
protocol of its own; rather, it acts as a generic interface to the protocols
underlying the NS 3000/XL network services.
This chapter is organized into the following major sections:
- NetIPC Concepts
- Using NetIPC for Interprocess Communication
- Direct Access to Level 3, X.25
- Considerations for using NetIPC between MPE-V and MPE XL HP 3000
systems.
|
