AM3270 and TR3271 Configuration and Management Manual

SCF Interface to AM3270 and TR3271

AM3270 and TR3271 Configuration and Management Manual—529993-001

4-10

TR3271 Object Types

The TR3271 subsystem supports the PROCESS, LINE, and SU object types. The null

object type is supported only for the NAMES command and the VERSION command.

null The null object is not an actual object type. The term null is used to

represent the lack of a specified object. Any SCF command that

supports the null object type is issued without the specification of an

object type. Commands support the null object type if an object type

is irrelevant (as is the case with the VERSION command), or if they

refer to a collection of objects (as is the case with the NAMES

command).

PROCESS Refers to a TR3271 line-handler process running on a NonStop

S-series server or on an Integrity NonStop NS-series server. A

process name is the same as the name of the line it controls. A

typical TR3271 PROCESS object name might be $TR3271.

When you assign a name to a PROCESS object, you must

make sure that the name conforms to the NonStop Kernel

conventions for process names. The recommended form for

AM3270 and TR3271 is $identifier, where identifier

consists of a letter followed by zero to six alphanumeric

characters with no embedded blanks; for example, $TR32.

LINE Refers to a TR3271 data communications line controlled by the

TR3271 I/O process and configured on a single system. A line

name must be unique within the system. It must be preceded

by a dollar sign ($) and must begin with an alphabetic character,

which can be followed by up to six alphanumeric characters. A

typical line name might be $TR3271.

LINE object names refer to data communications lines

connected through a modem to an AM3270 or TR3271 network.

The LINE object name is the same as that of the PROCESS

object name; for example, $TR32.

SU Refers to a TR3271 subdevice. A subdevice name identifies a

specific subdevice configured on a single line. A subdevice

name must be unique within the line with which it is associated.

It must be preceded by a pound sign (#) and begin with an

alphabetic character, which can be followed by up to six

alphanumeric characters. A typical subdevice name might be

$TR32.#TERM1. A subdevice name must always be qualified

with its line name (for example, $TR3271.#TERM1). To avoid

using a fully-qualified object name, use the ASSUME command.