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-13
ADD Command
Considerations
•
The object-name template (wildcard notation) is supported for the ABORT
command. (See Object-Name Templates and Wildcards on page 3-6.)
•
All activities being performed by the specified objects are stopped immediately.
Files may be left in an inconsistent or incomplete state.
•
To reinitiate the operation of an aborted process, use the START command.
•
After ABORT SUBSYS is executed, the IPXPROTO process is still running but is
not available for use. Only the IPXMGR process can communicate with the
IPXPROTO process.
•
Use the STOP command if you want to stop the operation of objects in a controlled
manner. The STOP command does not abruptly terminate activities in progress.
•
ABORT is a sensitive command. See Sensitive and Nonsensitive SCF Commands
on page 3-8 for additional information on sensitive commands.
•
When the ABORT command is completed, the subordinate processes are in the
STOPPED summary state.
•
You can abort only the PROCESS object without restriction. Specify the SUB
option when you use the SUBSYS object. You cannot abort the IPXMGR process.
ADD Command
The ADD command defines a process and its associated attributes to the NonStop™
IPX/SPX subsystem. Enter an IOPORTNAME value for each process you add. (See
Specifying Processes, LIF Names, and Filter Protocols in SCF Commands on page 3-8
for more information.) The other attributes are optional and assume default values if you
do not specify them. ADD is a sensitive command.
ADD PROCESS
ADD PROCESS creates an IPXPROTO process.
Command Syntax
ADD [ / OUT file-spec / ] PROCESS $manager-name.$process-
name
, CODEFILE filename
, IOPORTNAME LIF-name.filter-protocol
[ , IPXMAXSOCKETS integer ]
[ , QIOLIMIT integer ]
[ , SPXKEEPALIVETIMER integer ]
[ , SPXMAXBINDS integer ]
[ , SPXMAXCONN integer ]
[ , SPXMAXRESEND integer ]