OSI/AS Configuration and Management Manual

Management Environment
OSI/AS Configuration and Management Manual—424119-001
2-22
PROFILE Objects
Note, however, that if two or more TSP processes share the same X25AM line, only the
first four characters after the $ are used by the TSP process to build the SU name and
must be unique.
PROFILE Objects
PROFILE objects allow you to define sets of values for protocol configuration attributes
within the Network Layer, Transport Layer, and Session Layer of your subsystem. You
can define several different PROFILE objects for each layer, each specifying a different
protocol configuration. PROFILE objects are managed exclusively by the OSI manager
process.
PROFILE objects do not define values for all the connections through a layer, but rather
are associated with specific address components. Each network PROFILE object is
associated with a particular SNPA each transport PROFILE object is associated with a
specific NSAP; and each session PROFILE object is associated with a specific TSEL.
Once you associate a PROFILE object with an address component, all connections
through that component are configured by that PROFILE object.
Relationship of PROFILE Objects to SERVICE Objects
At the time a PROFILE object is configured, all service attributes not specified for the
profile default to the attributes defined for the SERVICE object. For example, if you
define values for attributes A, B, and C for a SERVICE object, and you define only a
value for attribute A (for example, A') for the PROFILE object, the profile is registered
in the MIB with the attribute values A', B, and C. These attributes, including the values
taken from the SERVICE object, are permanently retained for the profile unless you
specifically alter them.
After a PROFILE object is configured, if the service attributes are subsequently
changed, the profile attributes do not automatically change. However, if you reconfigure
your subsystem from a command file, the service attributes are taken from that file and
do not reflect any other SERVICE object changes you may have made manually.
Connections using local TSEL addresses, SNPAs, and NSAPs that do not have an
associated profile are configured by the SERVICE object for the respective layer. A
profile assigned to a remote TSEL, SNPA, or NSAP overrides a local profile, which in
turn overrides the local service definition. (See SERVICE Objects
on page 2-25 and
Selection Hierarchy of Object Attributes on page 2-35.)