SNMP DPI Version 2.0 API

DPI Version 2.0 is intended for use with UNIX System Services sockets and is not for use with other socket libraries. A DPI subagent must include the snmp_dpi.h header in any C part that intends to use DPI. The path for snmp_dpi.h is /usr/lpp/tcpip/snmp/include. By default, when you include the snmp_dpi.h include file, you will be exposed to the DPI Version 2.0 API. For a list of the functions provided, read more about the The snmp_dpi.h include file. This is the recommended use of the SNMP DPI API.

When you prelink your object code into an executable file, you must use the DPI Version 2.0 functions as provided in the snmp_lDPI.o, snmp_mDPI.o, and snmp_qDPI.o object files in /usr/lpp/tcpip/snmp/build/libdpi20.

Notes:

The object files are located only in a z/OS® UNIX file system. Files in a z/OS UNIX file system can be accessed from JCL using the path parameter on an explicit DD definition.
Together the snmp_dpi.h include file and the dpi_mvs_sample.c file comprise an example of the DPI Version 2.0 API.
Debugging information (resulting from the DPIdebug function) is routed to SYSLOGD. Ensure the SYSLOG daemon is active.
Compile your subagent code using the DEF(MVS™) compiler option.
Waiting for a DPI packet depends on the platform and how the chosen transport protocol is implemented. In addition, some subagents want to control the sending of and waiting for packets themselves, because they might need to be driven by other interrupts as well.
There is a set of DPI transport-related functions that are implemented on all platforms to hide the platform-dependent issues for those subagents that do not need detailed control for the transport themselves.

For more information about SNMP, see the Simple Network Management Protocol (SNMP) information in z/OS Communications Server: IP Configuration Guide or the Managing TCP/IP network resources with SNMP information in z/OS Communications Server: IP System Administrator's Commands.