OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-12
Adding and Deleting Processes
Adding and Deleting Processes
You can add more processes (for example, to increase the performance of an OSI/AS
subsystem), or you can delete processes that are no longer needed. The following
subsections describe the procedures you use:
•
Adding and Deleting NSP Processes on this page
•
Adding and Deleting TSP Processes on page 5-13
•
Adding and Deleting TAPS Processes on page 5-13
Adding and Deleting NSP Processes
You can add existing NSP processes to an OSI/AS subsystem whenever the OSI
manager process is in the STARTED state. That is, you can use the SCF ADD command
to register any NSP process that is already running in your NonStop Kernel
environment. You can also delete NSP processes from an OSI/AS subsystem whenever
the OSI manager process is in the STARTED state. Deleting an NSP process from the
subsystem, however, has no effect on its status within your operating system.
NSP processes do not need to be assigned exclusively to OSI/AS to provide the
subsystem with network services. For example, an X25AM process running in your
NonStop system could provide X.25 connections directly to one or more applications
through its programming interface and at the same time provide network services to the
upper layers of OSI/AS. However, the same NSP process cannot provide network
services to more than one OSI/AS subsystem.
If you need to install new NSP I/O processes within your NonStop Kernel operating
system, you can load a new operating system image using SYSGEN or DSM/SCM. For
information about these procedures, see the following manuals:
•
System Generation Manual
•
Dynamic System Configuration Manual
•
X.25 Access Method (X25AM) Manual
•
Multilan/TLAM Management and Operations Manual
•
PAM Configuration and Management Manual
To add an installed NSP process to an OSI/AS subsystem, use the SCF ADD command,
as in the following example:
ADD PROCESS $OSIM.#NSP.L3A, NAME $X25A
The Guardian name following the NAME attribute—in this case, $X25A—must be the
same as the device name assigned to the X25AM process in the SYSGEN configuration
file.
Note that when you add a new NSP process, it can be used by the OSI/AS subsystem
only after you have defined it as the server process for an SNPA address. You make this
assignment by adding a new SNPA ENTRY object or by altering an existing one, as
described later in this section.
The following command deletes an NSP process from an OSI/AS subsystem:
DELETE PROCESS $OSIM.#NSP.L3A