OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-31
Adding NSAP ENTRY Objects
The command and object-spec register the remote NSAP address 9A1112 with the OSI
manager process $OSIM:
ADD ENTRY $OSIM.#NSAP.9A1112
The first attribute-spec associates the SNPA address FE08008E00024 with the
NSAP address you identified in the first part:
SNPA FE08008E000024
In cases where the remote application runs on an open system attached to a subnetwork
other than your own, the SNPA address you enter is the address of a gateway system that
routes messages between the two subnetworks.
The second attribute-spec associates a Layer-4 PROFILE object called TPFILE5
to the remote NSAP address 9A1112:
L4PROFILE $OSIM.#L4.TPFILE5
The OSI manager process uses the configuration values contained in this L4PROFILE
object to configure Transport Layer subdevices, even if a different L4PROFILE object is
assigned to the corresponding local NSAP address.
The last attribute-spec defines the addressing mode used by the network accessed
through this NSAP:
NETADDR-MODE NORMAL
This example gives the default setting, indicating addressing for any LAN or for an X.25
network that is implemented to 1984 X.25 standards. NETADDR-MODE X25-1980
would indicate addressing for an X.25 network implemented to 1980 standards; for such
networks, that clause is required.
Example 2: 1980 X.25
The following command registers two different remote NSAP addresses on an X.25
WAN and assigns them to the same SNPA. The command also specifies addressing for a
network that implements the 1980 X.25 standard:
ADD ENTRY $OSIM.#NSAP.9A1112, SNPA 543219 &
, NETADDR-MODE X25-1980
ADD ENTRY $OSIM.#NSAP.9A1113, SNPA 543219 &
, NETADDR-MODE X25-1980
Considerations
•
Note that you do not assign a TSP server process when you add remote NSAP
ENTRY objects. If you do assign a TSP server process, it is ignored when you set up
a connection using that entry as the remote entry.
•
You can assign L4PROFILE objects to remote NSAP addresses, as in the first
example. In this case, connections to the remote address are configured with the
protocol values specified by the assigned L4PROFILE object. If you do not assign
an L4PROFILE object to a remote NSAP address, as in the second example,