OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-34
Adding APPL ENTRY Objects
matter, administered within your NonStop system environment and not by any external
OSI network administration authority.
The first attribute-spec assigns the NSAP address 9A0001 to both local
applications:
NSAP 9A0001
NSAP 9A0001
Although both applications in this example use the same NSAP address, this need not be
the case. You can assign different NSAP addresses to different applications. However,
OSI/AS does not allow different NSAP addresses to be assigned to the same application.
NSAP addresses are globally administered. You must register the local NSAP addresses
used by your local applications with the OSI manager process. You do this by adding
NSAP ENTRY objects.
Remote NSAP addresses must also be registered with the OSI manager process. You
also do this by adding NSAP ENTRY objects. The NSAP ENTRY object for remote
NSAP addresses associates an SNPA address with the NSAP and enters this information
into the MIB. Remote NSAP ENTRY objects do not have TSP or NSP servers.
Local NSAP ENTRY objects determine which TSP and NSP processes service requests
by the applications assigned to the corresponding NSAP address. (See “Registering
Local NSAP Addresses,” earlier in this section.)
The second attribute-spec assigns a distinct TSEL identifier to each application:
TSEL 0001
TSEL 0002
The choice of local TSEL identifiers is a local matter, administered within your OSI
environment. You must register each local TSEL identifier with the OSI manager
process by adding a corresponding TSEL ENTRY object. TSEL ENTRY objects
determine which TAPS processes will service requests by the applications assigned to
the corresponding TSEL identifiers. (See Adding TSEL ENTRY Objects
on page 4-32.)
The third attribute-spec assigns a distinct SSEL identifier to each application:
SSEL 0001
SSEL 0002
These are optional address elements that TAPS processes use for routing during
connection establishment. The choice of local SSEL identifiers is a local matter that is
administered within your OSI application environment.
The fourth attribute-spec assigns a distinct PSEL identifier to each application:
PSEL 0001
PSEL 0002
These are optional address elements that TAPS processes use for routing during
connection establishment. The choice of local PSEL identifiers is a local matter that is
administered within your OSI application environment.