EZZ3213I

Explanation
 One of the following events occured:  The SNMP TCP/IP subagent attempted to register the specified MIB
tree, mib_tree, but another DPI subagent had already registered
the requested MIB tree with a higher priority.  
The TCP/IP subagent had successfully registered the specified
MIB tree, but the Agent received a later registration from another
subagent that requested a higher priority than that with which the
TCP/IP subagent was currently registered. 

As a result, the Agent sends SNMP requests for the MIB tree to
the subagent that registered with the higher priority, instead of
to the TCP/IP subagent.
 If the mib_tree value
is 1.3.6.1.2.1.10.7.2. (which is the SNMP dot3StatsTable table from
RFC 2665), the message was probably issued because the OSA-Express
Direct subagent is active.  The dot3StatsTable table is supported
by both the TCP/IP subagent and the OSA-Express Direct subagent. 
The OSA-Express Direct subagent, started by procedure IOBSNMP, supports
more types of OSA features in the dot3StatsTable table than the TCP/IP
subagent.  Therefore, if the OSA-Express Direct subagent is active,
it supports the dot3StatsTable table.  If any SNMP requests are received
for data from the dot3StatsTable table, the SNMP Agent passes the
requests on to the OSA-Express Direct subagent to be processed. If
the OSA-Express Direct subagent is active, the TCP/IP subagent writes
message EZZ3213I to the syslog daemon, to indicate that it is currently
waiting to support the dot3StatsTable table.  This is normal processing
and does not indicate a problem.  If the OSA-Express Direct subagent
ends, then the TCP/IP subagent supports the dot3StatsTable table and
the SNMP Agent will send SNMP requests for this table to the TCP/IP
subagent.

System action
 The  TCP/IP subagent continues to process for
the other MIB trees supported by the  TCP/IP subagent.  If the MIB
tree becomes available at a later time, the  TCP/IP subagent will
begin processing for that MIB tree.

Operator response
 If it is acceptable that a DPI subagent program other than
the SNMP TCP/IP subagent provides the processing for the MIB variables
in the specified MIB tree, than no action is necessary.  Otherwise,
the other DPI subagent
must be ended for the SNMP TCP/IP subagent to provide the processing
for the variables in the specified MIB tree. If the mib_tree value
is 1.3.6.1.2.1.10.7.2., then the message was probably issued because
the OSA-Express Direct subagent is active and supporting the dot3StatsTable
table.  Because the OSA-Express Direct subagent is the preferred supporter
of the dot3StatsTable table, this does not indicate a problem.
 If
you need to determine which DPI subagent is currently providing the processing
for the mib_tree value, you can use the following z/OS® UNIX snmp
commands:  snmp -h host -v walk saTindex
Find the entries whose index value starts with the mib_tree value
from the message.  In the case of the dot3StatsTable table, the entries
could appear as:  saTindex.1.3.6.1.2.1.10.7.2.0 = 4  
saTindex.1.3.6.1.2.1.10.7.2.1 = 2
  The .0 at
the end of the index value indicates that a DPI subagent registered for the
MIB tree value with a priority of 0.  This is the highest priority.
 Use this entry's saTindex value of 4 in the next snmp command.
snmp -h host -v get saDescription.4
This command returns:  saDescription.4 = OSA subagent  This
information enables you to determine that the OSA-Express Direct subagent
is the DPI agent
that registered for the MIB tree with a higher priority.

System programmer response
 None.

Module
 EZASADPI.C

Procedure name
  do_register,
do_unreg 