AM3270 and TR3271 Configuration and Management Manual

SCF Interface to AM3270 and TR3271

AM3270 and TR3271 Configuration and Management Manual—529993-001

4-9

Object-Type Hierarchy

The AM3270 and TR3271 object types supported by SCF, PROCESS, LINE, and SU

are in hierarchical order. The VERSION command implicitly assumes the null object

type. The NAMES command requires no object type. The hierarchy is important when

issuing commands to the AM3270 or TR3271 subsystems for processing. For

example, because the SU object type is subordinate to the LINE object type, any

commands pertaining to an SU object can be issued only when the LINE object is in

the STARTED state.

AM3270 Object Types

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

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

PROCESS Refers to an AM3270 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

AM3270 PROCESS object name might be $AM32.

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, $AM32.

LINE Refers to an AM3270 data communications line controlled by the

AM3270 I/O process and configured on a single system. The LINE

object name is the same as that of the PROCESS object; for example,

$AM32.

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,

$AM32.

SU Refers to an AM3270 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 #TERM1. A subdevice name must always be

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

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