OSI/AS SCF Reference Manual

OSI/AS SCF Commands
OSI/AS SCF Reference Manual—424121-001
2-51
Considerations for the ADD Command
1. The OSI manager verifies the required entries. The OSI manager locates the servers
and profiles from the #APPL or other OSI address components supplied in the
attach or connect request call. Servers and profiles are associated with the following
MIB entries:
#APPL entry
#NSAP entry
#SNPA entry
#TSEL entry
2. The OSI manager selects the TAPS, TSP, and NSP server process:
3. The OSI manager determines which set of protocol-related attributes will be used to
define connection parameters for TAPS and TSP subdevices:
a. The OSI manager searches the MIB for a profile entry (the composite profile).
After selecting the correct entry, it adds to it the service values that aren't present
in the profile attributes (for example, the attribute ESISCHECKSUM would be
added to a Layer 3 composite profile as this attribute is present in ALTER
SERVICE #L3, but not in ADD or ALTER PROFILE #L3). Additionally, as
stated in a previous consideration, at connection establishment time, any missing
values in the composite profile may be defaulted to a corresponding value in the
underlying subsystem.
b. If no profile entry exists, the OSI manager selects the service entry.
Note. The following discussion explains how the OSI manager process selects
information from the MIB. In the tables that accompany this discussion, the OSI manager
process uses a hierarchical approach in selecting one item from each of the tables below.
The OSI manager process begins at the top of each list and moves downward, selecting
the first existing item.
Also, in the tables, the words local and remote refer to the two endpoints of a connection
and there are two cases to consider as to how these terms are used.
In the context of a connect request, the application that makes the request is the calling or
local address and the called application is the remote address. In this case, profiles
associated with the called (remote) address take precedence over profiles associated with
the calling (local) address. Server specifications are unnecessary for remote entries and
are ignored.
In the context of an attach request, the application that issues an attach request is the
called address and is considered to be the local address—the remote entries in the table
are ignored.
#L5 Server
(TAPS Process)
#L4 Server
(TSP Protocol)
#L3 Server
(NSP Process)
1. Local #APPL ENTRY 1. Local #APPL ENTRY 1. Local #APPL ENTRY
2. Local #TSEL ENTRY 2. Local #NSAP ENTRY 2. Local #SNPA ENTRY