OSI/AS Configuration and Management Manual

Management Environment
OSI/AS Configuration and Management Manual—424119-001
2-35
Selection Hierarchy of Object Attributes
In its default configuration, OSI/AS looks for TAPS and TSP object code files in the
subvolume from which the OSI manager process was started. The default names for
TAPS and TSP code files are TAPSOBJ and TSPOBJ, respectively.
•
The following example specifies a new location for the MIB file:
ALTER SUBSYS $OSIM, MIB $DATA.OSICONFG.MIB3
The OSI manager process must be in the SUSPENDED state before you can issue
this command. In its default configuration, the subsystem looks for the MIB in the
same subvolume in which the object code for the OSI manager process resides. The
default name for the MIB is ZOSIDB. The default name for the MIB alternate-key
file is ZOSIDB0.
Selection Hierarchy of Object Attributes
The OSI manager process uses the hierarchy shown in Table 2-12, Table 2-13, and
Table 2-14 to determine which attribute values to use and which protocol processes to
select when processing connect requests and attach requests (during the connection-
establishment phase). The OSI manager process begins at the top of each relevant list
and, moving downward, selects the appropriate value from the first existing object.
Table 2-12. Selection Hierarchy of Object Attributes—Layer 3
Attribute Values #L3 Server (NSP Process)
1. L3 PROFILE in remote #APPL ENTRY 1. Local #APPL ENTRY
2. L3 PROFILE in remote #NSAP ENTRY 2. Local #SNPA ENTRY
3. L3 PROFILE in remote #SNPA ENTRY
4. L3 PROFILE in local #APPL ENTRY
5. L# PROFILE in local #NSAP ENTRY
6. L3 PROFILE in local #SNPA entry
7. Local #L3 PROFILE in local #SNPA
ENTRY
8. Default values set by OSI manager or
underlying subsystem (TCP/IP, X25AM, or
TLAM for D-series systems or PAM for G06
and above releases)