Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Configuration entry considerations z/OS Communications Server: IP Programmer's Guide and Reference SC27-3659-02 |
|
Configuration entries represent either SNMP agents to which requests are to be sent, or notification receivers. The snmpInitialize() function, which is the first function your SNMP manager must invoke, can create configuration entries if you specify a configuration file to be processed by this function. The function returns the configuration entries as a linked-list of SnmpConfigEntry structures, which are built from the information in the configuration file. If you do not specify a configuration file, your SNMP manager application must manually create the configuration entries by using the SnmpConfigEntry structure. This structure is required by other SNMP manager API functions. It is defined in the SNMP manager API header file, <snmpmgr.h>, which is available in the /usr/include directory. This structure supports both community-based and SNMPv3 user-based security. Requirement: If your SNMP manager
application manually creates the SnmpConfigEntry structures and the
application sets the functionsRequested input parameter to the snmpInitialize()
function to request the functional support of the current release,
then the application must perform the following tasks:
A sample manager implementation, snmpSMgr.c, is found in the usr/lpp/tcpip/samples directory. Note: The functions snmpValueCreateBits, snmpValueCreateUnsignedInteger32,
and snmpValueCreateNSApAddr have been removed. If these functions
are used, SNMP_MGR_RC_DEPRECATED is returned.
|
Copyright IBM Corporation 1990, 2014
|