OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-5
X25AM Considerations
•
X25AM provides wide-area, connection-mode subnetwork services over standard
X.25 networks.
•
TLAM (for D-series release) or PAM and SLSA (for G06 and above releases)
provides local-area, connectionless-mode subnetwork services over standard 802.3
and 802.4 networks.
Installation of either of these access methods requires changes to your current operating
system image. You can find detailed information on installing this software in the
manuals listed under Other Useful Manuals
on page 4-3.
Starting Network Lines
After you have installed an access method I/O process into your NonStop Kernel
operating system environment, you need to start the associated communications line.
SCF defines a LINE object corresponding to each access method I/O process that you
install. LINE objects, however, are not part of the SCF interface to OSI/AS and are not
controlled by the OSI manager process.
Use the SCF START command to start LINE objects by referring to the I/O process
directly by its device name:
START LINE $X25X
START LINE $LAMA
$X25X and $LAMA are the device names for I/O processes, defined in the SYSGEN
CONTROLLERS paragraph.
X25AM Considerations
The following points are important for correctly installing X25AM lines to be used by
OSI/AS.
Defining X.25 Subdevices
When you install X25AM as an independent subsystem, you typically need to define
one or more X.25 subdevices, using the SCF ADD SU command. Applications that use
X25AM open these subdevices directly and call Guardian procedures, such as
WRITEREAD, to initiate connections and transfer data across an X.25 network.
However, when X25AM is to be used exclusively by OSI/AS, you do not need to define
any X.25 subdevices. TSP processes add subdevices to and delete subdevices from the
I/O processes dynamically, in response to application requests for services.
Nevertheless, you do need to preconfigure the parameters that the OSI manager uses to
create the X.25 subdevices. You define X.25 subdevice parameters in either of two
ways:
•
By using SCF to alter the Layer 3 SERVICE object for your subsystem
•
By using SCF to add Layer 3 PROFILE objects to your subsystem
Section 5, Routine Management Tasks
, explains how to use these two SCF objects to
define X.25 subdevice parameters. X.25 is a connection-mode subnetwork protocol.
Before transport, session, presentation, or ACSE connections can be set up, an X.25