OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-14
Altering Process Attributes
Since the ADD command in this example does not include the CPU or BACKUPCPU
attributes, the values assigned are the same as the values specified for the OSI manager
process.
Note that when you add a TAPS process, it can be used by the subsystem only after you
have defined it as the server process for a TSEL identifier. You make this assignment by
adding a new TSEL ENTRY object, or by altering an existing one, as described later in
this section. In the case where you add a new TSEL ENTRY object, you may also need
to alter or add new APPL ENTRY objects (as described later) so that applications can
use the new TSEL identifier.
To stop a TAPS process and delete it from the MIB, use commands like the following:
STOP PROCESS $OSIM.#TAPS.L5A
DELETE PROCESS $OSIM.#TAPS.L5A
Before you delete a TAPS process, you should make sure that it is not assigned as the
server process to any active TSEL identifier. Thus, you should also delete or alter any
TSEL ENTRY objects that refer to the TAPS process you have deleted. In cases where
you have deleted TSEL ENTRY objects, you may also need to delete or alter any APPL
ENTRY objects that refer to the deleted TSEL identifier.
Altering Process Attributes
You can alter the Guardian configuration attributes of OSI/AS subsystem processes.
These are configuration attributes that do not relate directly to OSI protocols. Rather,
they relate to the overall configuration of your subsystem and to the operating system
environment in which NSP processes run. Included in this category are attributes that
allow you to determine the Expand or FOX node in which the process runs, the process's
primary and backup CPUs, the Guardian filename of the process, the priority of the
process, and the like. The kinds of attributes that you can alter and the procedure you
must use to alter them differ according to the type of process.
Altering NSP Processes
Since the NSP processes in your subsystem are privileged I/O processes, they have
special configuration requirements. Most of the Guardian configuration attributes that
apply to NSP processes are those that can be defined in the SYSGEN PERIPHERALS
paragraph. Thus, to alter attributes of an NSP process, you typically have to edit the
SYSGEN configuration file, bring your operating system down, and perform a cold
load. However, you can also alter some of the configuration attributes for these
processes using the DSC utility and, to a much more limited extent, using SCF.
One of the major restrictions on NSP processes is that the primary and the backup
process must run in the CPUs to which the associated hardware controller board is
attached. Thus, you usually have to make changes to the hardware configuration of your
system to move an NSP process from one CPU pair to another, or from one Expand or
FOX node to another.
It is not possible to start, stop, or abort NSP processes in the same way you manage TSP
processes. However, associated with each NSP process is a LINE object that allows you