OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-9
PAM Considerations
Maximum TPDU Size
The maximum TPDU size to be used for Transport Layer connections over TLAM is
limited to the maximum I/O size supported by TLAM, as specified by the MAXIOSIZE
attribute the MAXIOSIZE default is 32000. Ordinarily, the OSI/TS subsystem
automatically determines each TLAM line’s maximum I/O size. However, you can
override the TLAM MAXIOSIZE value by doing one of the following:
•
Use the TSP^LANIOSIZE PARAM parameter to set the desired size when starting
the TSP process.
•
Alter the OSI/TS LANIOSIZE attribute of the PROCESS object.
PAM Considerations
The Port Access Method (PAM) is a system process that provides an interface to the
SLSA subsystem for local-area, connectionless-mode subnetwork service over standard
802.2, 802.3, and 802.4 networks. PAM has an application interface and an interface
with SLSA, which interfaces to an intelligent controller that runs the data-link protocols
(logical link control and CSMA/CD). The PAM subsystem can be used only on an
S-series system with G06 and above releases.
Naming PAM Subdevices
No special service or profile setting is required for PAM, but the PAM process must be
in the STARTED state. TSP adds and deletes PAM ports dynamically in response to
TAPS requests for services.
When interfacing with PAM, the TSP process builds a PAM port name by using the first
five characters of its own TSP process name after the $ sign 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 PAM Ports
The first time a connect request or an attach request is received requiring the PAM
device specified in the NSPDEVICE attribute, the TSP process adds the following:
•
A normal port to the PAM subdevice
•
A port to receive broadcast messages, if the ESISENABLE attribute is set to ON
While the naming scheme for PAM ports guarantees that no two TSP processes can
create ports with identical names, the PAM subsystem can still potentially reject a port at
this stage. This can happen when the port is being used by other TSP processes that are
stopped. In such cases, an event message is generated to point to the source of the
problem.