OSI/AS Configuration and Management Manual

Management Environment

OSI/AS Configuration and Management Manual—424119-001

2-33

Sensitive Command Examples

The following examples illustrate the sensitive commands you can use with SU objects:

ABORT SU $TAPS1.#Z123456

STOP SU $X25X.#ZAD1234

Of these two commands, ABORT is the stronger—and the more dangerous, since it

deletes a subdevice immediately, even when it is currently in use. Before you issue an

ABORT SU command, make sure that you will not disrupt critical application

communications.

SUBSYS (Subsystem) Objects

SUBSYS (subsystem) objects allow you to collect general configuration information on

your OSI/AS subsystem or to modify certain configuration attributes. Using the

SUBSYS object, you can do the following:

•

Find out where the subsystem looks for code files used to start TAPS, TSP, and the

OSI manager processes. You can also specify new locations where the subsystem

can find code files for TAPS and TSP processes.

•

Find out the names of all the objects configured in your subsystem.

•

Set the maximum number of TAPS, TSP, and NSP processes that can be started

within the subsystem, or find out the maximum number that has already been set.

You can also find out the number of TAPS and TSP processes that are currently

started.

•

Find out the name the subsystem uses to identify the MIB, or specify a new MIB

name to the subsystem.

•

Find out the software version of the subsystem.

•

Find out the current status of the subsystem.

•

Find out statistics information for the subsystem.

Note. The PORT object for TLAM lines (for D-series releases) or PAM lines (for G06 and

above releases) is equivalent to the SU object for X25AM lines. For example, for a TLAM

line you might give the following NAMES command to find out the names of the current

PORT objects:

NAMES PORT $LAM1.*

This command is automatically passed to TLAM (or PAM), which recognizes the PORT

object.