OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-10
Creating the MIB Database
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 PAM to the same TSP process.
Deleting PAM Ports
PAM ports can be deleted only by aborting all the TSP subdevices; otherwise, PAM
ports are retained for the lifetime of the TSP process.
If the PAM 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 PAM ports during the next attempt to establish a
connection.
Class
Note that when you configure Layer 4 attributes to operate with PAM processes, you
must specify the transport class 4 protocol.
Maximum TPDU Size
The maximum TPDU size to be used for Transport Layer connections over PAM is
limited to the maximum I/O size supported by TLAM, as specified by the
MAXREQUESTSIZE attribute; the MAXREQUESTSIZE default is 32000. Ordinarily,
the OSI/TS subsystem automatically determines each TLAM line’s maximum I/O size.
However, you can override the TLAM MAXREQUESTSIZE value by doing one of the
following:
•
Using the TSP^LANIOSIZE PARAM parameter to set the desired size when starting
the TSP process.
•
Altering the OSI/TS LANIOSIZE attribute of the process object.
Creating the MIB Database
The Management Information Base (MIB) is a file that the OSI manager process uses to
store and retrieve configuration information on your subsystem. You need to create this
file before you install the OSI manager process.
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.