OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-16
Managing Protocol Services
Some of the important attributes of TSP and TAPS processes that you can change using
the SCF ALTER PROCESS command are the following:
•
The Guardian process name
•
The network node in which the process runs
•
The primary and backup CPUs in which the process runs
•
The priority at which the process runs
•
The code file from which the process is run
•
The location of the process swap file
•
The maximum number of simultaneous connections that the process is permitted to
handle
The following sequence of SCF commands could be used to start a TSP process on
another network node:
STOP PROCESS $OSIM.#TSP.L4A
ALTER PROCESS $OSIM.#TSP.L4A, NAME \MARS.$TSP3 &
, CODEFILE \MARS.$SYSTEM.OSIFILES.TSPCODE &
, SWAP \MARS.$DATA &
, CPU 8, BACKUPCPU 4
START PROCESS $OSIM.#TSP.L4A
Notice that in the ALTER command, the NAME attribute specifies a system name as
well as the process name. The effect is that the OSI manager starts the TSP process
$OSIM.#TSP.L4A on the system \MARS. The process pair runs in CPUs 8 and 4 and
has the process name $TSP3 in the specified system. Note that if you specify a remote
system, the code file and swap volume have to be on that system too.
The following sequence of commands could be used to alter the priority of a TAPS
process:
STOP PROCESS $OSIM.#TAPS.L5A
ALTER PROCESS $OSIM.#TAPS.L5A, PRIORITY 149
START PROCESS $OSIM.#TAPS.L5A
Managing Protocol Services
This subsection discusses how you use OSI/AS SERVICE and PROFILE objects to
manage Layer 3, Layer 4, Layer 5, Layer 6, and ACSE protocol services. The discussion
is divided into the following topics:
•
Altering SERVICE Objects on this page
•
Adding PROFILE Objects on this page
•
Adding PROFILE Objects on page 5-17
•
Altering PROFILE Objects on page 5-20