OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-8
TLAM Considerations
Naming TLAM Subdevices
No special service or profile setting is required for TLAM, but the TLAM process must
be in the STARTED state. TSP adds and deletes TLAM ports dynamically in response to
TAPS requests for services.
When interfacing with TLAM, the TSP process builds a TLAM port name by using the
first five characters of its own TSP process name after the dollar sign character ($) as the
prefix, followed by a two-character alphanumeric string that is associated with the
LSAP-selector it uses (normally FE). This method allows for easy identification and
prevents possible duplicate names created by other TSP processes.
Creating TLAM Ports
The first time a connect request or an attach request is received requiring the TLAM
device specified in the NSPDEVICE attribute, the TSP process adds the following:
•
A normal port to the TLAM subdevice
•
A port to receive broadcast messages, if the ESISENABLE attribute is set to ON
While the naming scheme for TLAM ports guarantees that no two TSP processes can
create ports with identical names, the TLAM subsystem can still potentially reject a port
at this stage. This can happen when the LSAP selector (which is an attribute of the ports)
used by the current TSP process is the same as that used by other TSP processes that are
stopped. In such cases, an event message is generated to point to the source of the
problem.
To avoid this problem, always do the following:
•
Abort all transport subdevices before stopping TSP processes. This should be part of
your normal shutdown procedure.
•
Assign the same TLAM IOP to the same TSP process.
Deleting TLAM Ports
TLAM ports can be deleted only by aborting all the TSP subdevices otherwise, TLAM
ports are retained for the lifetime of the TSP process.
If the TLAM device is not operative while a TSP process has the ports opened, the TSP
process attempts to delete them as soon as the error condition is detected. The TSP
process also tries to recreate the TLAM ports during the next attempt to establish a
connection.
Class
Note that when you configure Layer 4 attributes to operate with TLAM processes, you
must specify the transport class 4 protocol.
Note. To change the value of the ESISENABLE attribute you must first abort all the TSP
subdevices. If the TSP subdevices are not first aborted, unpredictable behavior can result.