NetIPC 3000/XL Programmer's Reference Manual (5958-8600)
Table Of Contents
- 1 NetIPC Fundamentals
- 2 Cross-System NetIPC
- 3 NetIPC Intrinsics
- 4 NetIPC Examples
- A IPC Interpreter (IPCINT)
- B Cause and Diagnostic Codes
- C ErrorMessages
- D Migration From PTOP to NetIPC and RPM
- E C Program Language Considerations

210 AppendixD
Migration From PTOP to NetIPC and RPM
Creating Remote Processes
Creating Remote Processes: In the Slave Program
To convert the PTOP intrinsic listed below, perform the following steps.
Syntax
ifun := GET [([
itag
][
il
][,
ionumber
]
• Call RPMGETSTRING twice to get the master’s socket name and node
name.
• Create a TCP call socket by using the IPCCREATE intrinsic.
• Call IPCLOOKUP to look up the master’s socket, using the master
socket name and node name passed in the RPM strings. This returns
a destination descriptor to be used in the IPCCONNECT call.
• Set up a virtual-circuit connection between the master and the slave
sockets, using IPCCONNECT. Call IPCRECV to wait for the connection
acknowledgment from the slave. Save the returned virtual-circuit
descriptor for subsequent IPCSEND and IPCRECV calls.
• After setting up the connection, delete the call socket and
destination descriptor using IPCSHUTDOWN.
• If a tag is specified, call IPCRECV to receive the master’s tag on the
virtual circuit (see the comment on IPCRECV under Data Exchange).
To convert the PTOP intrinsic listed below, perform the following steps.
Syntax
ACCEPT [([
itag
][,
target
][,
tcount
])]
• If the slave can call either ACCEPT or REJECT in response to the
POPEN, send a one byte accept or reject indication on the virtual
circuit to the master.
• If a tag is specified, call IPCSEND to send the slave’s tag on the
virtual circuit back to the master.