OSI/AS Configuration and Management Manual
Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-37
Step-by-Step Configuration Example
1. Your application must first define LOCAL as the name used to identify the
application name (or the APPL ENTRY object) and define OSIM as the name of the
OSI manager process.
2. Add the APPL ENTRY object, $OSIM.#APPL.LOCAL. Identify the PSEL, SSEL,
TSEL, and NSAP addresses to go with that application name. TSELs and NSAPs
must represent the actual addresses that will be added later as the names for the
ENTRY objects in the other layers.
This step completes the configuration of the application.
3. At the Session Layer, add the TAPS process $OSIM.#TAPS.TAP1. Associate this
TAPS process with a unique process name, $TAPA, by which it will be known to the
NonStop Kernel operating system and, optionally, specify the location of the code
file for the process.
4. Add the TSEL ENTRY object, $OSIM.#TSEL.444401, specifying the same TSEL
value as that in the APPL ENTRY configuration. The Layer 5 server,
$OSIM.#TAPS.TAP1, was added in step 3 and points to the process to be used by
this TSEL. The L5PROFILE object can optionally be used to select the specific
session services required.
5. Add the Layer 5 PROFILE object, $OSIM.#L5.L5VSN2, if you specified it in step
4. An example set of attributes for the Layer 5 profile might be VSN1 OFF, VSN2
ON.
This step completes the configuration of the Session Layer.
6. At the Transport Layer, add the TSP process $OSIM.#TSP.TSP1. Associate this TSP
process with a unique process name, $TSPA, by which it will be known to the
NonStop Kernel operating system and, optionally, specify the location of the code
file for the process.
7. Add the NSAP ENTRY object, $OSIM.#NSAP.30104085551212, specifying the
same NSAP value as that in the APPL ENTRY configuration. This must also be the
actual address for the entry into the Transport Layer entity #TSP. The Layer 4
server, $OSIM.#TSP.TSP1, was added in step 6 and points to the process to be used
by this NSAP. The L4PROFILE can optionally be used to select the specific
transport services required.
An SNPA address must also be configured under this entry. For X.25 networks using
the 1980 addressing standards, this field is not used, but it still must be specified.
For TLAM networks on D-series releases (or PAM networks on G06 and above
releases), this field must contain the 6-byte controller address, as configured by the
manufacturer, with an OSI link selector address of FE in front, for a total of 14
hexadecimal digits—for example, SNPA FE08008E000024.
Since this example configuration connects to an X.25 network that implements the
1980 X.25 standard, the clause NETADDR-MODE X25-1980 is also required.