OSI/AS SCF Reference Manual

OSI/AS SCF Commands
OSI/AS SCF Reference Manual—424121-001
2-8
PROCESS Objects
ENTRY Object-Name Examples
The following are valid object-names for the ENTRY object:
$OSIM.#APPL.GLOBAL_DSA
$OSIM.#APPL.FILE_SERVER*
$OSIM.#TSEL.000?
$OSIM.#TSEL.0002
$OSIM.#NSAP.9A*
$OSIM.#NSAP.9A0002
$OSIM.#SNPA.FE08008E000013 (for LAN)
$OSIM.#SNPA.* (for X.25)
PROCESS Objects
A PROCESS object identifies a specific process. Use the PROCESS object to define
processes that provide data communications and subsystem-management services.
Four kinds of PROCESS objects can be specified:
•
Tandem application, presentation, and session service provider (TAPS) processes
•
Transport service provider (TSP) processes
•
Network service provider (NSP) processes
•
OSI manager process
Note that only TAPS processes and the OSI manager process are part of the OSI/AS
subsystem; TSP and NSP processes belong to lower-level subsystems that are used by
the OSI/AS subsystem.
This manual describes only operations supported by the TAPS processes and the OSI
manager process. This support includes a full range of operations on TAPS processes
and on the OSI manager process itself, a more limited number of operations on TSP
processes, and a minimal set of operations on NSP processes.
A larger set of management operations can be performed on TSP processes using the
commands described in the OSI/TS SCF Reference Manual. Likewise, a larger set of
operations can also be performed on NSP processes by using the commands described in
the SCF Reference Manual for X25AM, the TCP/IP Configuration and Management
Manual, or the SCF Reference Manual for Multilan/TLAM (for D-series releases), or
the PAM Configuration and Management Manual (for G06 and later releases).
The
object-name for the PROCESS object can be either indirect-process-name
or
process-name (these are described on the next page). When the
indirect-process-name format is used, the command is directed through the OSI
manager process first, then on to the specified process type. The OSI manager process
will update the MIB accordingly. When the
process-name format is used, the
command bypasses the OSI manager process, SCF and SCP pass the command directly
to the appropriate lower-level subsystem [OSI/TS for TSP processes; X25AM, TCP/IP,
or TLAM (for D-series releases), or PAM (for G06 and later releases), for NSP
processes], and the command must follow the rules for that subsystem rather than those
described in this manual. The MIB will not be updated.