OSI/AS SCF Reference Manual

Table Of Contents

OSI/AS SCF Commands

OSI/AS SCF Reference Manual—424121-001

2-14

SU Objects

Use the SU (subdevice) object to define a data communications subdevice to a process.

There are two types of SUs: static and dynamic. A dynamic SU object is temporary, it is

added dynamically by a TAPS, TSP, or NSP process and lasts only as long as the

connection exists. A static SU object is not temporary, it is added by a TAPS, TSP, or

NSP process, is saved when the connection is finished and can be reused by another

connection if that connection desires the same addresses and configuration used by the

first connection. Specify the SU type with the DELETETIME attribute.

The

object-name for the SU object is su-name, and it has the following format:

$process-name

is the name of the TAPS process as follows:

Local TAPS process names can be up to six characters (the $ sign followed by five

characters). For example:

$TAPS1

$TAPS5

Remote TAPS process names can be up to five characters (the $ sign followed by

four characters). For example:

$TAP1

$TAP5

#su-name

is a Guardian subdevice name indicating the desired subdevice.

SU Object Wildcard Support

Wildcards are supported for the ABORT SU, CHECK SU, LISTOPENS SU, NAMES

SU, STATS SU, STATUS SU, and STOP SU commands, Specify wildcards in the

su-name field. Examples of the su-name field with wildcards are

.#*

.#G00000?

.#ABC*

.#A?C*

$process-name.#su-name

Note. For the NAMES command, see NAMES Command Syntax on page 2-174, as wildcard

support for this command does not follow the above rules.