NetIPC 3000/XL Programmer's Reference Manual (5958-8600)

Appendix A 173
IPC Interpreter (IPCINT)
Comparison of IPCINT to Programmatic NetIPC
Comparison of IPCINT to Programmatic
NetIPC
The following examples show the difference between programmatic
access and IPCINT used to execute the IPCCREATE intrinsic.
Example: Programmatic Access to X.25
For a program using direct access to X.25 level 3, a call to IPCCREATE
can be specified as follows:
IPCCREATE (3,2,,opt,calldesc,result)
The value 3 for parameter socketkind specifies a call socket. The value
2 (for parameter
protocol ) indicates the protocol access is X.25. At a
minimum, the
opt array would contain the X.25 network name, and
optionally either define a catch-all socket (
opt code 144, bit 2) or specify
a protocol relative address (
opt code 128). The calldesc will contain
the call socket descriptor, and result will contain an error (if any).
Example: IPCINT for X.25 Direct Access
For example, to execute the IPCCREATE intrinsic using IPCINT, enter CR
from the IPCINT prompt (see example below). You are prompted for the
IPCCREATE X.25 parameters. In this example, no catch-all socket is
specified; therefore, a protocol relative address is specified. The network
name is a required parameter. The network name X25NET is used in
this example. After the required parameters are entered, press
[RETURN] and the IPCCREATE intrinsic is executed.
CR
Protocol: 2
Catch All Socket (Y/N)? N
Protocol Relative Address: 3100
Network name (8 chars): X25NET
-----> Executing: IPCCREATE
CALL = 6