IPX/SPX Configuration and Management Manual

Managing NonStop™ IPX/SPX With the Subsystem
Control Facility (SCF)
IPX/SPX Configuration and Management Manual—425731-001
3-15
ADD Command
unresponsive SPX connection is disconnected after the fifth ping. The default is five
minutes.
For example, if SPXKEEPALIVETIMER is set to 7, SPX sends up to five pings at
one-minute intervals if an SPX connection has not received a packet for seven
minutes.
SPXMAXBINDS integer
is the number of concurrent, explicit binds to this particular IPXPROTO process. An
explicit bind is the result of a socket BIND call by an SPX application, typically
caused by a server process listening on the socket. The bind is terminated when the
application closes the socket. Set SPXMAXBINDS to a value equal to or greater than
the upper bound on the expected number of concurrent binds. The range is 10 to 500
binds; the default is 25.
SPXMAXCONN integer
is the number of SPX connections allowed open simultaneously. The recommended
value is the maximum number of concurrent SPX user sessions, including sessions
established by higher-level protocols, such as Telserv, Remote Server Call (RSC),
and Open Database Connectivity (ODBC).
SPXMAXRESEND integer
specifies the maximum number of times that SPX resends a data packet.
Retransmission time is approximately five seconds between retries. The range is 1 to
256. The default is 65 retries.
Examples
The following command defines an IPXPROTO process, named $ZNV2, to the
subsystem $ZMGR:
-> ADD PROCESS $ZMGR.$ZNV2, &
CODEFILE $system.zipxpro.ipxproto, &
IOPORTNAME "L018.IPX8023", &
SPXMAXBINDS 30
After issuing the ADD PROCESS command, you only need to specify the process name
when entering subsequent commands; you no longer need to enter the fully qualified
process name.
To start the new process, use the SCF START command:
-> START PROCESS $ZNV2
For more information, see START PROCESS on page 3-32.
Note. SPXMAXBINDS significantly affects memory usage; you should set this value as low as
possible.