This is the MIB module for objects used to
manage network devices with APPN capabilities.    

Administratively assigned network name for this node.    

The total number of HPR route setups received for routes
passing through this node since the node was last
reinitialized.    

The number of HPR route setups rejected by this node for
routes passing through it since the node was last
reinitialized.    

The total number of HPR route setups sent for routes
originating in this node since the node was last
reinitialized.    

The number of HPR route setups rejected by other nodes for
routes originating in this node since the node was last
reinitialized.    

The total number of HPR route setups received for routes
ending in this node since the node was last reinitialized.    

The number of HPR route setups rejected by this node for
routes ending in it since the node was last reinitialized.    

The value of the sysUpTime object the last time the APPN node
was reinitialized.    

Possible values are:


other, noAnr, anrForLocalNces, allAnr
                

Indicates which ANR traffic, if any, the node includes in the
counts returned by the APPN link station counters
appnLsInXidBytes, appnLsInMsgBytes, appnLsInXidFrames,
appnLsInMsgFrames, appnLsOutXidBytes, appnLsOutMsgBytes,
appnLsOutXidFrames, and appnLsOutMsgFrames.  These counters
are always incremented for ISR traffic.

The following values are defined:

other(1)             - the node does something different
from all the options listed below
noAnr(2)             - the node does not include any ANR
traffic in these counts
anrForLocalNces(3)   - the node includes in these counts
ANR traffic for RTP connections
that terminate in this node, but
not ANR traffic for RTP connections
that pass through this node without
terminating in it
allAnr(4)            - the node includes all ANR traffic
in these counts.    

Indicates whether this node is currently configured as a
branch network node.

Note:  throughout the remainder of this MIB module, branch
network node is treated as a third node type, parallel to
network node and end node.  This is not how branch network
nodes are treated in the base APPN architecture, but it

increases clarity to do it here.    

DEPRECATED
The value of LAST-UPDATED from this module's MODULE-IDENTITY
macro.  This object gives a Management Station an easy way of
determining the level of the MIB supported by an agent.

Since this object incorporates the Year 2000-unfriendly
2-digit year specified in SMI for the LAST-UPDATED field, and



since it was not found to be particularly useful, it has been
deprecated.  No replacement object has been defined.    

This node's Node Identification, which it sends in bytes
2-5 of XID.    

Possible values are:


networkNode, endNode, t21len
                

Type of APPN node:

networkNode(1) - APPN network node
endNode(2)     - APPN end node
t21len(4)      - LEN end node

Note:  A branch network node SHALL return endNode(2)
as the value of this object.  A management application

can distinguish between a branch network node and an
actual end node by retrieving the appnNodeBrNn object.    

Amount of time (in hundredths of a second) since the APPN node
was last reinitialized.    

Indicates whether this node supports parallel TGs.    

Indicates whether this node supports adaptive bind pacing for
dependent LUs.    

Possible values are:


noHprSupport, hprBaseOnly, rtpTower, 
controlFlowsOverRtpTower

Indicates this node's level of support for high-performance
routing (HPR):

noHprSupport(1)             - no HPR support
hprBaseOnly(2)              - HPR base (option set 1400)
supported
rtpTower(3)                 - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported

This object corresponds to cv4580, byte 9, bits 3-4.    

This object represents a configuration parameter indicating
the maximum number of sessions that the APPN node is to put on
any HPR connection.  The value is zero if not applicable.    

Indicates whether this node supports central directory
services.

This object corresponds to cv4580, byte 8, bit 1.    

Resource sequence number for this node, which it assigns and
controls.

This object corresponds to the numeric value in cv4580, bytes
2-5.    

Indicates whether this node is congested.  Other network nodes
stop routing traffic to this node while this flag is on.

This object corresponds to cv4580, byte 7, bit 0.    

Indicate whether intermediated session routing resources are
depleted.  Other network nodes stop routing traffic through
this node while this flag is on.

This object corresponds to cv4580, byte 7, bit 1.    

Indicates whether the node is quiescing.

This object corresponds to cv4580, byte 7, bit 5.    

Indicates whether the node has gateway services support.

This object corresponds to cv4580, byte 8, bit 0.    

Possible values are:


noCache, cacheNoIncrUpdate, 
cacheWithIncrUpdate

Indicates this node's level of support for caching of route
trees.  Three levels are specified:

noCache(1)             - caching of route trees is not
supported
cacheNoIncrUpdate(2)   - caching of route trees is
supported, but without incremental
updates
cacheWithIncrUpdate(3) - caching of route trees with
incremental updates is supported    

Route addition resistance.

This administratively assigned value indicates the relative
desirability of using this node for intermediate session
traffic.  The value, which can be any integer 0-255, is used
in route computation.  The lower the value, the more
desirable the node is for intermediate routing.

This object corresponds to cv4580, byte 6.    

Indicates whether the node supports intermediate session
routing.

This object corresponds to cv4580, byte 8, bit 2.    

The last flow-reduction sequence number (FRSN) sent by this
node in a topology update to an adjacent network node.    

Indicates whether this node has peripheral border node
support.

This object corresponds to cv4580, byte 9, bit 0.    

Indicates whether this node has interchange node support.

This object corresponds to cv4580, byte 9, bit 1.    

Indicates whether this node has extended border node support.

This object corresponds to cv4580, byte 9, bit 2.    

The topology safe store frequency.

If this number is not zero, then the topology database is saved
each time the total number of topology database updates (TDUs)
received by this node increases by this number.  A value of
zero indicates that the topology database is not being saved.    

Indicates whether this end node supports mode name to COS name
mapping.    

The fully qualified name of the current NN server for this end
node.  An NN server is identified using the format specified in
the SnaControlPointName textual convention.  The value is a
zero-length string when there is no active NN server.

A branch network node shall also implement this object.    

Indicates whether the node is to be searched for LUs as part
of a network broadcast search.

A branch network node shall also implement this object.    

The Port table describes the configuration and current status
of the ports used by APPN.  When it is known to the APPN
component, an OBJECT IDENTIFIER pointing to additional
information related to the port is included.  This may, but
need not, be a RowPointer to an ifTable entry for a DLC
interface immediately 'below' the port.    

The port name is used as the index to this table.    

Administratively assigned name for this APPN port.    

Maximum Basic Transmission Unit (BTU) size that a link station
on this port can receive.

This object corresponds to bytes 21-22 of XID3.    

Maximum number of I-frames that can be received by the XID
sender before an acknowledgement is received.    

The total number of successful XID exchanges that have
occurred on all defined link stations on this port since the
last time this port was started.    

The total number of unsuccessful XID exchanges that have
occurred on all defined link stations on this port since the
last time this port was started.    

The total number of successful XID exchanges that have
occurred on all dynamic link stations on this port since the
last time this port was started.    

The total number of unsuccessful XID exchanges that have
occurred on all dynamic link stations on this port since the
last time this port was started.    

Identifies the object, e.g., one in a DLC-specific MIB, that
can provide additional information related to this port.

If the agent is unable to identify such an object, the value
0.0 is returned.    

The value of the sysUpTime object the last time the port was
started.    

Possible values are:


deactivate, activate, recycle, ready
                

Object by which a Management Station can activate, deactivate,
or recycle (i.e., cause to be deactivated and then immediately
activated) a port, by setting the value to activate(1),
deactivate(2), or recycle(3), respectively.  The value ready(4)
is returned on GET operations until a SET has been processed;
after that the value received on the most recent SET is
returned.    

Possible values are:


inactive, pendactive, active, pendinact
                

Indicates the current state of this port:

inactive(1)   - port is inactive
pendactive(2) - port is pending active
active(3)     - port is active
pendinact(4)  - port is pending inactive    

The type of DLC interface, distinguished according to the
protocol immediately 'below' this layer.    

Possible values are:


leased, switched, 
sharedAccessFacilities
                

Identifies the type of line used by this port:

leased(1)                 - leased line
switched(2)               - switched line
sharedAccessFacilities(3) - shared access facility, such
as a LAN.    

Indicates whether Set Initialization Mode (SIM) and Receive
Initialization Mode (RIM) are supported for this port.    

Possible values are:


primary, secondary, negotiable, abm
                

Initial role for link stations activated through this port.
The values map to the following settings in the initial XID,
where 'ABM' indicates asynchronous balanced mode and 'NRM'
indicated normal response mode:

primary(1):     ABM support = 0     ( = NRM)
role = 01           ( = primary)
secondary(2):   ABM support = 0     ( = NRM)
role = 00           ( = secondary)
negotiable(3):  ABM support = 0     ( = NRM)
role = 11           ( = negotiable)
abm(4):         ABM support = 1     ( = ABM)
role = 11           ( = negotiable)    

Indicates whether the node supports negotiable link stations
for this port.    

Indicates whether this node allows call-in on this port from
nodes not defined locally.    

This table contains detailed information about the link
station configuration and its current status.    

This table is indexed by the link station name.    

Administratively assigned name for the link station.
The name can be from one to ten characters.    

Indicates whether the link station is a limited resource.  A
link station that is a limited resource is deactivated when it
is no longer in use.    

Indicates whether the link station is activatable on demand.

Such a link station is reported in the topology as active
regardless of its actual state, so that it can be considered in
route calculations.  If the link station is inactive and is
chosen for a route, it will be activated at that time.    

Indicates whether this link station will be used for
connections to down-level or migration partners.

In general, migration nodes do not append their CP names on
XID3.  Such nodes:  (1) will not support parallel TGs, (2)
should be sent an ACTIVATE PHYSICAL UNIT (ACTPU), provided that
the partner supports ACTPUs, and (3) should not be sent
segmented BINDs.  However, if this node receives an XID3 with
an appended CP name, then the partner node will not be treated
as a migration node.

In the case of DYNAMIC TGs this object should be set to 'no'.    

The partner's Node Identification, from bytes 2-5 of the XID
received from the partner.  If this value is not available,
then the characters '00000000' are returned.    

Indicates whether CP-CP sessions are supported by this
link station.  For a dynamic link, this object represents
the default ('Admin') value.    

Numeric value between 99 and 32767 inclusive indicating the
maximum number of bytes in a Basic Transmission Unit (BTU) sent
on this link.

When the link state (returned by the appnLsOperState object) is
inactive or pending active, the value configured at this node
is returned.  When the link state is active, the value that was
negotiated for it is returned.  This negotiated value is the
smaller of the value configured at this node and the partner's
maximum receive BTU length, received in XID.    

Number of XID bytes received.  All of the bytes in the SNA
basic transmission unit (BTU), i.e., all of the bytes in the
DLC XID Information Field, are counted.    

Number of message (I-frame) bytes received.  All of the bytes
in the SNA basic transmission unit (BTU), including the
transmission header (TH), are counted.    

Possible values are:


deactivate, activate, recycle, ready
                

Object by which a Management Station can activate, deactivate,
or recycle (i.e., cause to be deactivated and then immediately
reactivated) a link station, by setting the value to
activate(1), deactivate(2), or recycle(3), respectively.  The
value ready(4) is returned on GET operations until a SET has
been processed; after that the value received on the most
recent SET is returned.    

Number of XID bytes sent.  All of the bytes in the SNA basic
transmission unit (BTU), i.e., all of the bytes in the DLC XID
Information Field, are counted.    

Number of message (I-frame) bytes sent.  All of the bytes
in the SNA basic transmission unit (BTU), including the
transmission header (TH), are counted.    

Number of echo responses returned from adjacent link station.
A response should be returned for each test frame sent by this
node.  Test frames are sent to adjacent nodes periodically to
verify connectivity and to measure the actual round trip time,
that is, the time interval from when the test frame is sent
until when the response is received.    

The time that it took for the last test signal to be sent and
returned from this link station to the adjacent link station.
This time is represented in milliseconds.    

The longest time it took for a test signal to be sent and
returned from this link station to the adjacent link station.

This time is represented in milliseconds .

The value 0 is returned if no test signal has been sent and
returned.    

The shortest time it took for a test signal to be sent and
returned from this link station to the adjacent link station.
This time is represented in milliseconds.

The value 0 is returned if no test signal has been sent and
returned.    

The time when the longest delay occurred.  This time can be
used to identify when this high water mark occurred in relation
to other events in the APPN node, for example, the time at
which an APPC session was either terminated or failed to be
established.  This latter time is available in the
appcHistSessTime object in the APPC MIB.

The value 00000000 is returned if no test signal has been sent
and returned.    

The total number of successful XID exchanges that have
occurred on this link station since the time it was started.    

Possible values are:


inactive, sentConnectOut, pendXidExch, 
sendActAs, sendSetMode, 
otherPendingActive, active, 
sentDeactAsOrd, sentDiscOrd, 
sentDiscImmed, otherPendingInact

State of this link station.  The comments map these more
granular states to the 'traditional' four states for SNA
resources.  Values (2) through (5) represent the normal
progression of states when a link station is being activated.
Value (6) represents some other state of a link station in
the process of being activated.  Values (8) through (10)
represent different ways a link station can be deactivated.
Value (11) represents some other state of a link station in
the process of being deactivated.    

The total number of unsuccessful XID exchanges that have
occurred on this link station since the time it was started.    

Identifies the object, e.g., one in a DLC-specific MIB, that
can provide additional information related to this link
station.

If the agent is unable to identify such an object, the value
0.0 is returned.    

The cumulative amount of time since the node was last
reinitialized, measured in hundredths of a second, that this
link station has been in the active state.  A zero value
indicates that the link station has never been active since
the node was last reinitialized.    

The amount of time, measured in hundredths of a second, that

the link station has been in its current state.    

Possible values are:


noHprSupport, hprBaseOnly, rtpTower, 
controlFlowsOverRtpTower

Indicates the level of high performance routing (HPR) support
over this link:

noHprSupport(1)             - no HPR support
hprBaseOnly(2)              - HPR base (option set 1400)
supported
rtpTower(3)                 - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported

If the link is not active, the defined value is returned.    

Indicates whether the link station is supporting
HPR link-level error recovery.    

The forward Automatic Network Routing (ANR) label for this
link station.  If the link does not support HPR or the value is
unknown, a zero-length string is returned.    

The reverse Automatic Network Routing (ANR) label for this
link station.  If the link does not support HPR or the value is
unknown, a zero-length string is returned.    

The network connection endpoint identifier (NCE ID) for CP-CP
sessions if this node supports the HPR transport tower, a
zero-length string if the value is unknown or not meaningful
for this node.    

The network connection endpoint identifier (NCE ID) for Route
Setup if this node supports the HPR transport tower, a zero-
length string if the value is unknown or not meaningful for
this node.    

Administratively assigned name for the port associated with

this link station.  The name can be from one to ten
characters.    

The network connection endpoint identifier (NCE ID) for the
APPN/HPR boundary function if this node supports the HPR
transport tower, a zero-length string if the value is unknown
or not meaningful for this node.    

Address of the remote link station on this link.    

Remote link station discovered from the XID exchange.
The name can be from one to ten characters.  A zero-length
string indicates that the value is not known.    

The value of the sysUpTime object the last time the link
station was started.    

Indicates whether the link is a member of a multi-link TG.  If
the link's TG has been brought up as a multi-link TG, then the
link is reported as a member of a multi-link TG, even if it is

currently the only active link in the TG.    

The type of DLC interface, distinguished according to the
protocol immediately 'below' this layer.    

Identifies whether this is a dynamic link station.  Dynamic
link stations are created when links that have not been locally
defined are established by adjacent nodes.    

Fully qualified name of the adjacent node for this link
station.  An adjacent node is identified using the format
specified in the SnaControlPointName textual convention.

The value of this object is determined as follows:

1. If the adjacent node's name was received on XID, it
is returned.

2. If the adjacent node's name was not received on XID,
but a locally-defined value is available, it is
returned.

3. Otherwise a string of length 0 is returned, indicating
that no name is known for the adjacent node.    

Possible values are:


networkNode, endNode, t21len, unknown
                

Node type of the adjacent node on this link:

networkNode(1) - APPN network node
endNode(2)     - APPN end node
t21len(4)      - LEN end node
unknown(255)   - the agent does not know the node type
of the adjacent node

Number associated with the TG to this link station, with a
range from 0 to 256.  A value of 256 indicates that the TG
number has not been negotiated and is unknown at this time.    

This table contains information related to exceptional and
potentially exceptional conditions that occurred during the
activation, XID exchange, and termination of a connection.  No
entries are created when these activities proceed normally.

It is an implementation option when entries are removed from
this table.    

This table is indexed by the LsStatusIndex, which is an
integer that is continuously updated until it eventually
wraps.    

Table index.  The value of the index begins at zero
and is incremented up to a maximum value of 2**31-1
(2,147,483,647) before wrapping.    

The sense data associated with the rejection of the XID.

This is the sense data that came from the local node (this
node) when it built the XID Negotiation Error control vector
(cv22) to send to the remote node.    

The sense data the adjacent node returned to this node
indicating the reason the XID was rejected.

This is the sense data that came from the remote node in the
XID Negotiation Error control vector (cv22) it sent to the
local node (this node).    

This object identifies the actual byte in the XID that caused
the error.  The value 65536 indicates that the object has no
meaning.

For values in the range 0-65535, this object corresponds to
bytes 2-3 of the XID Negotiation (X'22') control vector.    

This object identifies the actual bit in error (0 through 7)
within the errored byte of the XID.  The value 8 indicates that
this object has no meaning.

For values in the range 0-7, this object corresponds to byte 4
of the XID Negotiation (X'22') control vector.    

The type of DLC interface, distinguished according to the
protocol immediately 'below' this layer.    

Address of the remote link station on this link.    

Time when the exception condition occurred.  This time can be
used to identify when this event occurred in relation to other
events in the APPN node, for example, the time at which an APPC
session was either terminated or failed to be established.
This latter time is available in the appcHistSessTime object in
the APPC MIB.    

Administratively assigned name for the link station
experiencing the condition.    

Fully qualified name of the adjacent node for this link
station.  An adjacent node is identified using the format
specified in the SnaControlPointName textual convention.

The value of this object is determined as follows:

1. If the adjacent node's name was received on XID, it
is returned.

2. If the adjacent node's name was not received on XID,
but a locally-defined value is available, it is
returned.

3. Otherwise a string of length 0 is returned, indicating
that no name is known for the adjacent node.    

The partner's Node Identification, from bytes 2-5 of the XID
received from the partner.  If this value is not available,
then the characters '00000000' are returned.    

Number associated with the TG to this link station, with a
range from 0 to 256.  A value of 256 indicates that the TG
number was unknown at the time of the failure.    

The error sense data associated with the start sequence of
activation of a link up to the beginning of the XID sequence.

This is the sense data that came from Configuration Services
whenever the link did not activate or when it went inactive.    

Indicates whether the node will retry the start request to
activate the link.    

The sense data associated with the termination of the link
connection to adjacent node.

This is the sense data that came from the DLC layer.    

This table relates a virtual routing node to an APPN port.    

This table is indexed by the virtual routing node name, TG
number, and port name.  There will be a matching entry in the
appnLocalTgTable to represent status and characteristics of the
TG representing each virtual routing node definition.    

Administratively assigned name of the virtual routing node.
This is a fully qualified name, and matches the appnLocalTgDest
name in the appnLocalTgTable.    

Number associated with the transmission group representing
this virtual routing node definition.    

The name of the port this virtual routing node definition is
defined to.    

Maximum number of node entries allowed in the APPN topology

database.  It is an implementation choice whether to count only
network-node entries, or to count all node entries.  If the
number of node entries exceeds this value, APPN will issue an
Alert and the node can no longer participate as a network node.
The value 0 indicates that the local node has no defined limit,
and the number of node entries is bounded only by memory.    

Current number of node entries in this node's topology
database.  It is an implementation choice whether to count only
network-node entries, or to count all node entries, but an
implementation must make the same choice here that it makes for
the appnNnTopoMaxNodes object.  If this value exceeds the
maximum number of nodes allowed (appnNnTopoMaxNodes, if that
field in not 0), APPN Alert CPDB002 is issued.    

Total number of topology node records purged from this node's
topology database since the node was last reinitialized.    

Total number of topology TG records purged from this node's
topology database since the node was last reinitialized.    

Number of TDU wars detected by this node since its last
initialization.    

Portion of the APPN topology database that describes all of
the APPN network nodes and virtual routing nodes known to this
node.    

The FRSN and the fully qualified node name are used to index
this table.    

Flow reduction sequence numbers (FRSNs) are associated with
Topology Database Updates (TDUs) and are unique only within
each APPN network node.  A TDU can be associated with multiple
APPN resources.  This FRSN indicates the last relative time
this resource was updated at the agent node.    

Indicates whether the node provide gateway services.

This object corresponds to cv4580, byte 8, bit 0.    

Indicates whether the node supports central directory
services.

This object corresponds to cv4580, byte 8, bit 1.    

Indicates whether the node supports intermediate session
routing (ISR).

This object corresponds to cv4580, byte 8, bit 2.    

Indicates whether the node has been marked for garbage
collection (deletion from the topology database) upon the next
garbage collection cycle.

This object corresponds to cv4580, byte 7, bit 3.    

Possible values are:


noHprSupport, hprBaseOnly, rtpTower, 
controlFlowsOverRtpTower

Indicates the node's level of support for high-performance
routing (HPR):

noHprSupport(1)             - no HPR support
hprBaseOnly(2)              - HPR base (option set 1400)
supported
rtpTower(3)                 - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported

This object corresponds to cv4580, byte 9, bits 3-4.    

Indicates whether this node has peripheral border node
support.

This object corresponds to cv4580, byte 9, bit 0.    

Indicates whether this node has interchange node support.

This object corresponds to cv4580, byte 9, bit 1.    

Indicates whether this node has extended border node
support.

This object corresponds to cv4580, byte 9, bit 2.    

Indicates whether this node supports branch awareness.

This object corresponds to cv4580, byte 8, bit 4.    

Administratively assigned network name that is locally defined
at each network node.    

Number of days before deletion of this network node entry.    

Possible values are:


networkNode, virtualRoutingNode
                

Resource sequence number, which is assigned and controlled by
the network node that owns this resource.  An odd number
indicates that information about the resource is inconsistent.

This object corresponds to the numeric value in cv4580, bytes
2-5.    

Route addition resistance.

This administratively assigned value indicates the relative
desirability of using this node for intermediate session
traffic.  The value, which can be any integer 0-255, is used
in route computation.  The lower the value, the more
desirable the node is for intermediate routing.

This object corresponds to cv4580, byte 6.    

Indicates whether this node is congested.  This node is not be
included in route selection by other nodes when this congestion
exists.

This object corresponds to cv4580, byte 7, bit 0.    

Indicates whether intermediate session routing resources are
depleted.  This node is not included in intermediate route
selection by other nodes when resources are depleted.

This object corresponds to cv4580, byte 7, bit 1.    

Indicates whether the node is quiescing.  This node is not
included in route selection by other nodes when the node is
quiescing.

This object corresponds to cv4580, byte 7, bit 5.    

Portion of the APPN topology database that describes all of
the APPN transmissions groups between nodes in the database.    

This table is indexed by four columns:  FRSN, TG owner fully
qualified node name, TG destination fully qualified node name,
and TG number.    

Flow reduction sequence numbers (FRSNs) are associated with
Topology Database Updates (TDUs) and are unique only within
each APPN network node.  A TDU can be associated with multiple
APPN resources.  This FRSN indicates the last time this
resource was updated at this node.    

Indicates whether the transmission group is quiescing.

If the TG owner is either an extended border node or a
branch-aware network node (indicated, respectively, by
the appnNnNodeFRExteBorderSup and appnNnNodeFRBranchAwareness
objects in the corresponding appnNnTopologyFREntry), then
this indicator is artificially set to TRUE in the APPN

topology database, to remove the TG from other nodes'
route calculations.  A management application can
determine whether the TG is actually quiescing by
examining its appnLocalTgQuiescing object at the TG owner.

This object corresponds to cv47, byte 6, bit 2.    

Possible values are:


supportedUnknownStatus, supportedActive, 
notSupported, supportedNotActive

Indicates whether CP-CP sessions are supported on this TG, and
whether the TG owner's contention-winner session is active on
this TG.  Some nodes in the network are not able to
differentiate support and status of CP-CP sessions, and thus
may report the 'supportedUnknownStatus' value.

This object corresponds to cv47, byte 6, bits 3-4.    

Cost per connect time.

This is an administratively assigned value representing the
relative cost per unit of time to use this TG.  Range is from

0, which means no cost, to 255, which indicates maximum cost.

This object corresponds to cv47, byte 13.    

Cost per byte transmitted.

This is an administratively assigned value representing the
relative cost of transmitting a byte over this TG.  Range is
from 0, which means no cost, to 255, which indicates maximum
cost.

This object corresponds to cv47, byte 14.    

Administratively assigned security level of this TG.

This object corresponds to cv47, byte 16.    

Administratively assigned delay associated with this TG.

This object corresponds to cv47, byte 17.    

First user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.

This object corresponds to cv47, byte 19.    

Second user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.

This object corresponds to cv47, byte 20.    

Third user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.

This object corresponds to cv47, byte 21.    

Administratively assigned name for the originating node for
this TG.  This is the same name specified in the node table.    

Indicates whether the TG has been marked for garbage
collection (deletion from the topology database) upon the next
garbage collection cycle.

This object corresponds to cv47, byte 6, bit 1.    

The subarea number associated with this TG.

This object corresponds to cv4680, bytes m+2 through m+5.    

Indicates whether high performance routing (HPR)
is supported over this TG.

This object corresponds to cv4680, byte m+1, bit 2.    

Indicates whether the destination node supports
high performance routing (HPR) transport tower.

This object corresponds to cv4680, byte m+1, bit 7.    

Possible values are:


unknown, appnOrBfTg, interchangeTg, 
virtualRouteTg

Indicates the type of the TG.

This object corresponds to cv4680, byte m+1, bits 3-4.    

Indicates whether the transmission group is an intersubnet TG,
which defines a border between subnetworks.

This object corresponds to cv4680, byte m+1, bit 5.    

This object indicates whether the transmission group is a
multi-link TG.  A TG that has been brought up as a multi-link
TG is reported as one, even if it currently has only one link
active.

This object corresponds to cv47, byte 6, bit 5.    

Indicates whether the transmission group is a branch TG
(equivalently, whether the destination of the transmission
group is a branch network node).

This object corresponds to cv4680, byte m+1, bit 1.    

Administratively assigned fully qualified network name for the
destination node for this TG.    

Number associated with this transmission group.  Range is
0-255.    

Number of days before deletion of this network node TG entry
if it is not operational or has an odd (inconsistent) RSN.    

Indicates whether the destination node is a virtual routing
node.    

DLC-specific data related to a link connection network.    

Current owning node's resource sequence number for this
resource.  An odd number indicates that information about the
resource is inconsistent.

This object corresponds to the numeric value in cv47, bytes
2-5    

Indicates whether the transmission group is operational.

This object corresponds to cv47, byte 6, bit 0.    

TG Table describes all of the TGs owned by this node.  The TG
destination can be a virtual node, network node, LEN node, or
end node.    

This table is indexed by the destination CpName and the TG
number.    

Administratively assigned name of the destination node for
this TG.  This is the fully qualified name of a network node,
end node, LEN node, or virtual routing node.    

Cost per connect time:  a value representing the relative cost
per unit of time to use the TG.  Range is from 0, which means
no cost, to 255.    

Relative cost of transmitting a byte over this link.
Range is from 0 (lowest cost) to 255.    

Administratively assigned security level of this TG.    

Administratively assigned delay associated with this TG.    

First user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.    

Second user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.    

Third user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.    

Possible values are:


noHprSupport, hprBaseOnly, rtpTower, 
controlFlowsOverRtpTower

Indicates the level of high performance routing (HPR) support
over this TG :

noHprSupport(1)             - no HPR support
hprBaseOnly(2)              - HPR base (option set 1400)
supported
rtpTower(3)                 - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported    

Indicates whether the transmission group is an intersubnet TG,
which defines a border between subnetworks.    

This object indicates whether the transmission group is a
multi-link TG.  A TG that has been brought up as a multi-link
TG is reported as one, even if it currently has only one link
active.    

Number associated with this transmission group.    

Possible values are:


other, uplink, downlink, 
downlinkToBranchNetworkNode, none, 
unknown

Branch link type of this TG:
other(1)             = the agent has determined the TG's
branch link type to be a value other
than branch uplink or branch
downlink.  This is the value used
for a connection network TG owned by
a branch network node.
uplink(2)            = the TG is a branch uplink.
downlink(3)          = the TG is a branch downlink to an
end node.
downlinkToBranchNetworkNode(4) = the TG is a branch
downlink to a cascaded branch

network node.
none(5)              = the TG is not a branch TG.
unknown(255)         = the agent cannot determine the
branch link type of the TG.    

Indicates whether the destination node for this TG is a
virtual routing node.    

DLC-specific data related to a link connection network.    

Administratively assigned name for the local port associated
with this TG.  A zero-length string indicates that this value
is unknown.    

Indicates whether the transmission group is quiescing.    

Indicates whether the transmission group is operational.    

Possible values are:


supportedUnknownStatus, supportedActive, 
notSupported, supportedNotActive

Indicates whether CP-CP sessions are supported on this TG, and
whether the TG owner's contention-winner session is active on
this TG.  Some nodes in the network are not able to
differentiate support and status of CP-CP sessions, and thus
may report the 'supportedUnknownStatus' value.    

Table describing all of the TGs owned by the end nodes known
to this node via TG registration.  This node does not represent
its own view of the TG on behalf of the partner node in this
table.  The TG destination can be a virtual routing node,
network node, or end node.    

This table requires multiple indexes to uniquely identify each
TG.  They are originating CPname, destination CPname, and the
TG number.    

Administratively assigned name of the origin node for this
TG.  This is a fully qualified network name.    

Cost per connect time:  a value representing the relative cost
per unit of time to use the TG.  Range is from 0, which means
no cost, to 255.    

Relative cost of transmitting a byte over this link.
Range is from 0, which means no cost, to 255.    

Administratively assigned security level of this TG.    

Administratively assigned delay associated with this TG.    

First user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.    

Second user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.    

Third user-defined TG characteristic for this TG.  This is
an administratively assigned value associated with the TG.    

This object indicates whether the transmission group is a
multi-link TG.  A TG that has been brought up as a multi-link
TG is reported as one, even if it currently has only one link
active.    

Administratively assigned name of the destination node for
this TG.  This is the fully qualified name of a network node,
end node, LEN node, or virtual routing node.    

Number associated with this transmission group.    

Number of days before deletion of this end node TG entry.    

Indicates whether the destination node is a virtual routing
node.    

DLC-specific data related to a link connection network.    

Indicates whether the transmission group is operational.    

Possible values are:


supportedUnknownStatus, supportedActive, 
notSupported, supportedNotActive

Indicates whether CP-CP sessions are supported on this TG, and
whether the TG owner's contention-winner session is active on
this TG.  Some nodes in the network are not able to

differentiate support and status of CP-CP sessions, and thus
may report the 'supportedUnknownStatus' value.    

Maximum number of cache entries allowed.  This is an
administratively assigned value.    

Number of broadcast Locates returned with a 'not found' since
the node was last reinitialized.    

Current number of outstanding Locates, both directed and
broadcast.  This value varies.  A value of zero indicates
that no Locates are unanswered.    

Number of directed Locates received since the node was last
reinitialized.    

Number of broadcast Locates received since the node was last
reinitialized.    

Number of directed Locates sent since the node was last
reinitialized.    

Number of broadcast Locates sent since the node was last
reinitialized.    

Number of directed Locates returned with a 'not found' since
the node was last reinitialized.    

Table containing information about all known LUs.    

Fully qualified network LU name in the domain of the
serving network node.  Entries take one of three forms:

- Explicit entries do not contain the character '*'.
- Partial wildcard entries have the form 'ccc*', where
'ccc' represents one to sixteen characters in a
legal SNA LuName.
- A full wildcard entry consists of the single
character '*    

Fully qualified control point (CP) name of the network node
server.  For unassociated end node entries, a zero-length
string is returned.    

Fully qualified CP name of the node at which the LU is
located.  This name is the same as the serving NN name when
the LU is located at a network node.  It is also the same as
the fully qualified LU name when this is the control point
LU for this node.    

Possible values are:


local, domain, xdomain
                

Specifies the location of the LU with respect to the local
node.    

Possible values are:


home, cache, registered
                

Directory types are:
1 - Home
The LU is in the domain of the local node, and the LU
information has been configured at the local node.

2 - Cache
The LU has previously been located by a broadcast
search, and the location information has been saved.

3 - Registered
The LU is at an end node that is in the domain
of the local network node.  Registered entries
are registered by the served end node.    

Fully qualified CP name of the node at which the LU appears to
be located.  This object and the appnDirLuOwnerName object are
related as follows:

Implementations that support this object save in their
directory database information about an LU's owning control
point that was communicated in two control vectors:

-  an Associated Resource Entry (X'3C') CV with resource
type X'00F4' (ENCP)

-  a Real Owning Control Point (X'4A') CV.

The X'4A' CV is created by a branch network node to preserve
the name of the real owning control point for an LU below the
branch network node, before it overwrites this name with its
own name in the X'3C' CV.  The X'4A' CV is not present for LUs
that are not below branch network nodes.

If the information a node has about an LU's owning CP came only
in a X'3C' CV, then the name from the X'3C' is returned in the
appnDirLuOwnerName object, and a null string is returned in
this object.

If the information a node has about an LU's owning CP came in
both X'3C' and X'4A' CVs, then the name from the X'4A' is
returned in the appnDirLuOwnerName object, and the name from
the X'3C' (which will be the branch network node's name) is
returned in this object.    

Table representing all of the defined mode names for this
node.  The table contains the matching COS name for each
mode name.    

Administratively assigned name for this mode.    

Administratively assigned name for this class of service.    

Table mapping all of the defined class-of-service names for
this node to their network transmission priorities.    

Administratively assigned name for this class of service.    

Possible values are:


low, medium, high, network
                

Transmission priority for this class of service:

low(1)     - (X'01'):  low priority
medium(2)  - (X'02'):  medium priority
high(3)    - (X'03'):  high priority
network(4) - (X'04'):  network priority    

This table contains all node-row information for all classes
of service defined in this node.    

Administratively assigned name for this class of service.    

Subindex under appnCosNodeRowName, corresponding to a row in
the node table for the class of service identified in
appnCosNodeRowName.

For each class of service, this subindex orders rows in the
appnCosNodeRowTable in the same order as that used for route
calculation in the APPN node.    

Weight to be associated with the nodes that fit the criteria
specified by this node row.

This value can either be a character representation of an
integer, or a formula for calculating the weight.    

Minimum route addition resistance value for this node.

Range of values is 0-255.  The lower the value, the more
desirable the node is for intermediate routing.    

Maximum route addition resistance value for this node.
Range of values is 0-255.  The lower the value, the more
desirable the node is for intermediate routing.    

Indicates whether low congestion will be tolerated.  This
object and appnCosNodeRowMaxCongestAllow together delineate a
range of acceptable congestion states for a node.  For the
ordered pair (minimum congestion allowed, maximum congestion
allowed), the values are interpreted as follows:

- (0,0):  only low congestion is acceptable
- (0,1):  either low or high congestion is acceptable
- (1,1):  only high congestion is acceptable.

Note that the combination (1,0) is not defined, since it
would identify a range whose lower bound was high congestion
and whose upper bound was low congestion.    

Indicates whether low congestion will be tolerated.  This
object and appnCosNodeRowMinCongestAllow together delineate a
range of acceptable congestion states for a node.  For the
ordered pair (minimum congestion allowed, maximum congestion
allowed), the values are interpreted as follows:

- (0,0):  only low congestion is acceptable
- (0,1):  either low or high congestion is acceptable
- (1,1):  only high congestion is acceptable.

Note that the combination (1,0) is not defined, since it
would identify a range whose lower bound was high congestion
and whose upper bound was low congestion.    

Table containing all the TG-row information for all classes of
service defined in this node.    

Administratively assigned name for this class of service.    

Minimum acceptable security for this class of service.    

Maximum acceptable security for this class of service.    

Minimum acceptable propagation delay for this class of

service.    

Maximum acceptable propagation delay for this class of
service.    

Minimum acceptable value for this user-defined
characteristic.    

Maximum acceptable value for this user-defined
characteristic.    

Minimum acceptable value for this user-defined
characteristic.    

Maximum acceptable value for this user-defined
characteristic.    

Minimum acceptable value for this user-defined
characteristic.    

Maximum acceptable value for this user-defined
characteristic.    

Subindex under appnCosTgRowName, corresponding to a row in the
TG table for the class of service identified in
appnCosTgRowName.

For each class of service, this subindex orders rows in the
appnCosTgRowTable in the same order as that used for route
calculation in the APPN node.    

Weight to be associated with the TGs that fit the criteria
specified by this TG row.

This value can either be a character representation of an
integer, or a formula for calculating the weight.    

Minimum acceptable capacity for this class of service.    

Maximum acceptable capacity for this class of service.    

Minimum acceptable cost per connect time for this class of
service.

Cost per connect time:  a value representing the relative
cost per unit of time to use this TG.  Range is from 0, which
means no cost, to 255.    

Maximum acceptable cost per connect time for this class of
service.

Cost per connect time:  a value representing the relative
cost per unit of time to use this TG.  Range is from 0, which
means no cost, to 255.    

Minimum acceptable cost per byte transmitted for this class
of service.

Cost per byte transmitted:  a value representing the relative
cost per unit of time to use this TG.  Range is from 0, which
means no cost, to 255.    

Maximum acceptable cost per byte transmitted for this class
of service.

Cost per byte transmitted:  a value representing the relative
cost of transmitting a byte over this TG.  Range is from 0,
which means no cost, to 255.    

Possible values are:


notActive, active, ready
                

Object by which a Management Station can deactivate or
activate capture of intermediate-session counts and names, by
setting the value to notActive(1) or active(2), respectively.
The value ready(3) is returned on GET operations until a SET
has been processed; after that the value received on the most
recent SET is returned.

The counts referred to here are the eight objects in the
AppnIsInTable, from appnIsInP2SFmdPius through
appnIsInS2PNonFmdBytes.  The names are the four objects in this
table, from appnIsInPriLuName through appnIsInCosName.

Setting this object to the following values has the following
effects:

notActive(1)  stop collecting count data.  If a count
is queried, it returns the value 0.
Collection of names may, but need not be,
disabled.
active(2)     start collecting count data.  If it is
supported, collection of names is enabled.    

Possible values are:


notActive, active
                

Indicates whether or not the intermediate session counts
are active.  The counts referred to here are the eight
objects in the AppnIsInTable, from appnIsInP2SFmdPius through
appnIsInS2PNonFmdBytes.  These eight counts are of type
Unsigned32 rather than Counter32 because when this object
enters the notActive state, either because a Management
Station has set appnInInGlobeCtrAdminStatus to notActive or
because of a locally-initiated transition, the counts are
all reset to 0.

The values for this object are:

notActive(1):  collection of counts is not active; if it
is queried, a count returns the value 0.
active(2):     collection of counts is active.    

The time since the appnIsInGlobeCtrOperStatus object last
changed, measured in hundredths of a second.  This time can be
used to identify when this change occurred in relation to other
events in the agent, such as the last time the APPN node was
reinitialized.    

Possible values are:


notActive, active
                

Indicates the current route selection control vector (RSCV)
collection option in effect, and allows a Management Station to
change the option.

The values for this object are:

notActive(1): collection of route selection control vectors
is not active.
active(2):    collection of route selection control vectors
is active.    

The time since the appnIsInGlobeRscv object last changed,
measured in hundredths of a second.  This time can be used to
identify when this change occurred in relation to other events
in the agent, such as the last time the APPN node was
reinitialized.    

The number of currently active intermediate sessions.    

The number of currently active HPR intermediate sessions.    

Entry of Intermediate Session Information Table.    

The network-qualified control point name of the node at which
the session and PCID originated.  For APPN and LEN nodes, this
is either CP name of the APPN node at which the origin LU is
located or the CP name of the NN serving the LEN node at which
the origin LU is located.  For resources served by a dependent
LU requester (DLUR), it is the name of the owning system
services control point (SSCP).    

Length of time the session has been active, measured in
hundredths of a second.    

Length of time the session counters have been active, measured
in hundredths of a second.    

Number of function management data (FMD) path information
units (PIUs) sent from the Primary LU to the Secondary LU since
the counts were last activated.    

Number of FMD PIUs sent from the Secondary LU to the Primary
LU since the counts were last activated.    

Number of non-FMD PIUs sent from the Primary LU to the
Secondary LU since the counts were last activated.    

Number of non-FMD PIUs sent from the Secondary LU to the
Primary LU since the counts were last activated.    

Number of FMD bytes sent from the Primary LU to the Secondary
LU since the counts were last activated.    

Number of FMD bytes sent from the Secondary LU to the Primary
LU since the counts were last activated.    

Number of non-FMD bytes sent from the Primary LU to the
Secondary LU since the counts were last activated.    

Number of non-FMD bytes sent from the Secondary LU to the
Primary LU since the counts were last activated.    

The procedure correlation identifier (PCID) of a session.  It
is an 8-byte value assigned by the primary LU.    

The primary stage adjacent CP name of this session.  If the
session stage traverses an RTP connection, the CP name of the
remote RTP endpoint is returned.    

The primary stage adjacent transmission group (TG) number
associated with this session.  If the session stage traverses
an RTP connection, the value 256 is returned.

Values between 257 and 300 are available for other possible
TG 'stand-ins' that may be added to APPN in the future.    

The primary stage maximum basic transmission unit (BTU) size
for sending data.    

Possible values are:


fixed, adaptive
                

The primary stage type of pacing being used for sending data.    

The primary stage send residual pace count.  This represents
the primary stage number of message units (MUs) that can still
be sent in the current session window.    

The primary stage size of the next window which will be used
to send data.    

Possible values are:


fixed, adaptive
                

The primary stage type of pacing being used for receiving
data.    

The primary stage receive residual pace count.  This
represents the primary stage number of message units (MUs) that
can still be received in the current session window.    

The primary stage size of the next window which will be used
to receive data.    

The secondary stage adjacent CP name of this session.  If the
session stage traverses an RTP connection, the CP name of the
remote RTP endpoint is returned.    

Possible values are:


inactive, pendactive, active, pendinact
                

Indicates the state of the session:

inactive(1)   - session is inactive
pendactive(2) - session is pending active
active(3)     - session is active
pendinact(4)  - session is pending inactive

Active sessions can be deactivated by setting this object
to inactive(1).    

The secondary stage adjacent transmission group (TG) number
associated with this session.  If the session stage traverses
an RTP connection, the value 256 is returned.

Values between 257 and 300 are available for other possible
TG 'stand-ins' that may be added to APPN in the future.    

The secondary stage maximum basic transmission unit (BTU) size
for sending data.    

Possible values are:


fixed, adaptive
                

The secondary stage type of pacing being used for sending
data.    

The secondary stage send residual pace count.  This represents
the secondary stage number of message units (MUs) that can
still be sent in the current session window.    

The secondary stage size of the next window which will be used
to send data.    

Possible values are:


fixed, adaptive
                

The secondary stage type of pacing being used for receiving
data.    

The secondary stage receive residual pace count.  This
represents the secondary stage number of message units (MUs)
that can still be received in the current session window.    

The secondary stage size of the next window which will be used
to receive data.    

The route selection control vector (RSCV X'2B') used for this
session.  It is present for APPN nodes; but is not present for
LEN nodes.  The format of this vector is described in SNA
Formats.  If no RSCV is available, a zero-length string is
returned.    

The HPR local Network Connection Endpoint of the session.    

The primary LU name of the session.  A zero-length
string indicates that this name is not available.    

The RTP connection local TCID of the session.    

The secondary LU name of the session.  A zero-length
string indicates that this name is not available.    

The Class of Service (COS) name used for this session.    

Possible values are:


low, medium, high, network
                

Transmission priority for this class of service.  Values are:

low(1)     - (X'01'):  low priority
medium(2)  - (X'02'):  medium priority
high(3)    - (X'03'):  high priority
network(4) - (X'04'):  network priority    

Possible values are:


unknown, lu62, lu0thru3, lu62dlur, 
lu0thru3dlur

The type of intermediate session.  Defined values are

unknown      The session type is not known.

lu62         A session between LUs of type 6.2
(as indicated by the LU type in Bind)

lu0thru3     A session between LUs of type 0, 1, 2, or 3
(as indicated by the LU type in Bind)

lu62dlur     A session between LUs of type 6.2
(as indicated by the LU type in Bind).
One of the LUs is a dependent LU supported
by the dependent LU requester (DLUR)
function at this node.

lu0thru3dlur A session between LUs of type 0, 1, 2, or 3
(as indicated by the LU type in Bind)
One of the LUs is a dependent LU supported
by the dependent LU requester (DLUR)
function at this node.    

A table indicating how many ISR sessions are transported by
each RTP connection.    

The local Network Connection Endpoint of the RTP connection.    

The number of intermediate sessions using this RTP
connection.    

Values are:


alertIdNumber, affectedObject
                

This trap carries a 32-bit SNA Management Services (SNA/MS)
Alert ID Number, as specified in SNA/MS Formats.    

A 32-bit SNA Management Services (SNA/MS) Alert ID Number, as
specified in SNA/MS Formats.    

The MIB object associated with the Alert condition, if there
is an object associated with it.  If no associated object can
be identified, the value 0.0 is passed in the trap.    

DEPRECATED
The compliance statement for the SNMPv2 entities that
implement the APPN MIB.

This is the compliance statement for the RFC 2155-level version
of the APPN MIB.  It was deprecated as new objects were added
to the MIB for MLTG, branch network node, and other extensions
to the APPN architecture.    

The compliance statement for the SNMPv2 entities that
implement the APPN MIB.

In the descriptions for the conditionally mandatory groups that
follow, the branch network node is treated as a third node type,
parallel to network node and end node.  This is not how branch
network nodes are treated in the base APPN architecture, but it
increases clarity here to do it.    

Values are:


appnNodeCpName, appnNodeMibVersion, 
appnNodeId, appnNodeType, 
appnNodeUpTime, appnNodeParallelTg, 
appnNodeAdaptiveBindPacing, 
appnNodeHprSupport, 
appnNodeCounterDisconTime

DEPRECATED
A collection of objects providing the instrumentation of
APPN general information and capabilities.

This RFC 2155-level group was deprecated when the
appnNodeMibVersion object was removed and the
appnNodeLsCounterType and appnNodeBrNn objects were added.    

Values are:


appnLocalEnTgEntryTimeLeft, 
appnLocalEnTgDestVirtual, 
appnLocalEnTgDlcData, 
appnLocalEnTgOperational, 
appnLocalEnTgCpCpSession, 
appnLocalEnTgEffCap, 
appnLocalEnTgConnCost, 
appnLocalEnTgByteCost, 
appnLocalEnTgSecurity, 
appnLocalEnTgDelay, appnLocalEnTgUsr1, 
appnLocalEnTgUsr2, appnLocalEnTgUsr3

DEPRECATED
The appnLocalEnTopoConfGroup is mandatory only for network
nodes.

This RFC 2155-level group was deprecated when the
appnLocalEnTgMltgLinkType object was added.    

Values are:


appnDirMaxCaches, appnDirCurCaches, 
appnDirCurHomeEntries, 
appnDirRegEntries, appnDirInLocates, 
appnDirInBcastLocates, 
appnDirOutLocates, 
appnDirOutBcastLocates, 
appnDirNotFoundLocates, 
appnDirNotFoundBcastLocates, 
appnDirLocateOutstands

The appnLocalDirPerfConfGroup is mandatory only for APPN
network nodes and end nodes.    

Values are:


appnCosModeCosName, 
appnCosTransPriority, appnCosNodeRowWgt, 
appnCosNodeRowResistMin, 
appnCosNodeRowResistMax, 
appnCosNodeRowMinCongestAllow, 
appnCosNodeRowMaxCongestAllow, 
appnCosTgRowWgt, appnCosTgRowEffCapMin, 
appnCosTgRowEffCapMax, 
appnCosTgRowConnCostMin, 
appnCosTgRowConnCostMax, 
appnCosTgRowByteCostMin, 
appnCosTgRowByteCostMax, 
appnCosTgRowSecurityMin, 
appnCosTgRowSecurityMax, 
appnCosTgRowDelayMin, 
appnCosTgRowDelayMax, 
appnCosTgRowUsr1Min, 
appnCosTgRowUsr1Max, 
appnCosTgRowUsr2Min, 
appnCosTgRowUsr2Max, 
appnCosTgRowUsr3Min, 
appnCosTgRowUsr3Max

The appnCosConfGroup is mandatory only for APPN network
nodes and end nodes.    

Values are:


appnIsInGlobeCtrAdminStatus, 
appnIsInGlobeCtrOperStatus, 
appnIsInGlobeCtrStatusTime, 
appnIsInGlobeRscv, 
appnIsInGlobeRscvTime, 
appnIsInGlobeActSess, appnIsInSessState, 
appnIsInPriLuName, appnIsInSecLuName, 
appnIsInModeName, appnIsInCosName, 
appnIsInTransPriority, appnIsInSessType, 
appnIsInSessUpTime, appnIsInCtrUpTime, 
appnIsInP2SFmdPius, appnIsInS2PFmdPius, 
appnIsInP2SNonFmdPius, 
appnIsInS2PNonFmdPius, 
appnIsInP2SFmdBytes, 
appnIsInS2PFmdBytes, 
appnIsInP2SNonFmdBytes, 
appnIsInS2PNonFmdBytes, 
appnIsInPsAdjCpName, appnIsInPsAdjTgNum, 
appnIsInPsSendMaxBtuSize, 
appnIsInPsSendPacingType, 
appnIsInPsSendRpc, 
appnIsInPsSendNxWndwSize, 
appnIsInPsRecvPacingType, 
appnIsInPsRecvRpc, 
appnIsInPsRecvNxWndwSize, 
appnIsInSsAdjCpName, appnIsInSsAdjTgNum, 
appnIsInSsSendMaxBtuSize, 
appnIsInSsSendPacingType, 
appnIsInSsSendRpc, 
appnIsInSsSendNxWndwSize, 
appnIsInSsRecvPacingType, 
appnIsInSsRecvRpc, 
appnIsInSsRecvNxWndwSize, 
appnIsInRouteInfo

The appnIntSessConfGroup is mandatory only for network
nodes.    

Values are:


appnNodeHprIntRteSetups, 
appnNodeHprIntRteRejects, 
appnLsErrRecoSup, appnLsForAnrLabel, 
appnLsRevAnrLabel

The appnHprBaseConfGroup is mandatory only for nodes that
implement the HPR base (APPN option set 1400).    

Values are:


appnNodeMaxSessPerRtpConn, 
appnNodeHprOrgRteSetups, 
appnNodeHprOrgRteRejects, 
appnNodeHprEndRteSetups, 
appnNodeHprEndRteRejects, appnLsBfNceId

The appnHprRtpConfGroup is mandatory only for nodes that
implement the HPR RTP tower (APPN option set 1401).