EZZ8237I

Explanation
 The Network SLAPM2 subagent was connected to the
SNMP Agent, but the connection  was broken.  
 code is
the return code. The following is a list of the return codes and 
their meaning:  01
The mkDPIopen command failed. 
02
There was a failure parsing DPI open packet. 
03
There was no DPI response
to DPI open.
04
The SNMP agent rejected the Open request.
05
The subagent is not authorized to SNMP Agent.
06
The DPIget_fd_for_handle command failed.
07
There was a failure during mkDPIregister.
08
There was a failure parsing DPI register packet.
09
There was a severe error processing packet.
10
The SNMP Agent rejected the DPI open request from the subagent  because another
subagent has already connected to the Agent using the same  subagent
identifier.
11
The subagent  cannot register this MIB tree or this MIB tree has
been  unregistered.    This action was initiated by a request from
an SNMP Manager.
12
The subagent has received a close packet from the SNMP Agent.
13
There was a failure sending packet to SNMP Agent.
14
The SNMP Agent socket is closed.
15
There was no DPI response
to DPI register.
16
The SNMP agent rejected the Register request.
17
There was an error receiving a packet from SNMP Agent.
18
There was an error processing packets from SNMP Agent.

 tcpName is the procedure
name used to start TCP/IP stack.

System action
 The Network SLAPM2 subagent stops. 

Operator response
 The following is a list of the codes and
their required actions: 05	
Verify that the community name specified for the subagent matches
one  supported by the SNMP Agent.  
 10	
The Network SLAPM2 subagent uses 1.3.6.1.4.1.2.11.7.5 as the subagent
 identifier.   Ensure that no user DPI programs are using this subagent  identifier
and that no Network SLAPM2 subagent instance has already been  started. 
11	
The 1.3.6.1.4.1.2.5.30.1 MIB tree is no longer  available. If
it is acceptable that the specified MIB tree is not available,  then
no action is necessary. Otherwise, contact the system programmer with
 the MIB tree that is no longer available.   Restart the Network SLAPM2
subagent when the MIB tree becomes available. 
For all other error codes
Re-create the problem with the Network SLAPM2  subagent -d 255
trace option. Error information will be written to the Syslog Daemon
(syslogd) output file by default.

 Note: Use of the -o startup option sends all
debug information to stdout.
 Contact the system programmer
with the syslogd output or stdout. See the information on SNMP Agent
 Distributed Protocol Interface Version 2.0 in the z/OS Communications Server: IP Programmer's Guide
and Reference for SNMP Agent error descriptions. Take the
necessary corrective action based on the error code. Restart Network
 SLAPM2 subagent request if necessary.

System programmer response
 If the SNMP Agent job is not active,
restart the SNMP Agent. Restart the  Network SLAPM2 subagent. If the
Network SLAPM2 subagent does not reconnect,  then stop the SNMP Agent
and restart it. If the problem persists, contact IBM® software support center with traces.

Module
 NSLAPM2

Procedure name
  doSNMPConnect,
readSNMPData