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

Appendix D 209
Migration From PTOP to NetIPC and RPM
Creating Remote Processes
20000) for the socket name and the local node name. (These will be
used by the slave program to set up the virtual circuit connection.) If
any process-creation options are included in the POPEN call
(
entryname
,
param
,
flags
,
stacksize
,
dlsize
, or
maxdata
),
include them in the opt array with the corresponding RPM opt codes:
• Call RPMCREATE to create the slave process on the remote node. Use
the
progname
and
location
parameters as they appear in the
POPEN call, although you will have to supply the (byte) lengths of
progname
and location. You should set the dependent bit of the
flag
parameter, so the slave will terminate if the master does. Save
the program descriptor, returned by RPMCREATE, for a future
RPMKILL.
NOTE
RPMCREATE requires the program to be linked with Process Handling
(PH) capability. PTOP does not require PH capability.
• Call IPCRECVCN to wait for the connection request from the slave.
Save the returned virtual-circuit descriptor for subsequent IPCSEND
and IPCRECV calls.
• Now that the virtual-circuit connection has been set up, call
IPCSHUTDOWN to delete the master’s call socket and IPCNAMERASE
to delete the socket name.
• If a tag is specified, call IPCSEND to send the tag on the virtual
circuit to the slave.
• If the slave could respond to the POPEN with either an ACCEPT or a
REJECT, call IPCRECV to receive a one-byte accept or reject
indication from the slave.
• If a tag is specified, call IPCRECV to receive the tag from the slave
(but see the comment on IPCRECV under “Exchanging Data”).
Parameter Opt Code
entry name 22001
param 22002
flags 22003
stacksize 22004
dlsize 22005
maxdata 22006