OSI/FTAM and OSI/APLMGR SCF Reference Manual

Attributes for Tandem FTAM
OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001
4-2
Attribute Descriptions
Attribute Descriptions
Attributes are the configurable characteristics of objects—characteristics that are
intentionally assigned rather than those that change outside the user’s control (such as
reset time or the current number of openers). They are used in Tandem FTAM as
parameters in, and display fields returned by, SCF commands.
The following attributes are used in the Subsystem Control Facility (SCF) commands
described in Section 3, SCF Commands for Tandem FTAM
.
address
address specifies the default OSI address of an initiator process or VFS profile.
Although address is a variable (only the address components are the true attributes),
it is included in this list because the components are generally configured at the same
time, as a whole. The address variable serves as a contrast to COMNAME.
Relationship to COMNAME
You must specify either address or COMNAME "character-string". If you
specify address in the ADD command, you must specify all four parts of the address
(although you can modify the fields independently using the ALTER command). If all
attributes are not provided, the ADD command is rejected. See the OSI/AS SCF
Reference Manual for details on how to add address components to the OSI manager
MIB or to view those already defined. The four address components are also described
in this section.
Relationship to OSI MIB
If you specify address instead of a common name, address must match an OSI
address defined in the OSI manager MIB. Whenever an application requests an FTAM
association without specifying an OSI address or common name, the OSI manager uses
the OSI address that was specified for the initiator selected by the APLMGR process.
When a Tandem FTAM responder is started, the OSI manager uses the OSI address in
the associated profile for the responder. For details on how to add an address to the OSI
manager MIB or to view addresses already defined, see the OSI/AS Configuration and
Management Manual.
Note that SCF does not check for the existence of a matching application name in the
OSI manager MIB; such an error is not detected until run time, when the associated
responder process is started or a connection is initiated through the initiator. For more
information on the common name and how it is used, see the OSI/FTAM Configuration
and Management Manual.
Default: None; see description
Value: See specific address components
Objects: PROCESS, PROFILE, SU