SNMP Configuration and Management Manual

Trap Multiplexer Subagent/Manager
SNMP Configuration and Management Manual—424777-006
12-55
Application Source Code
33. The value of the varbind’s data type is used to determine which statements to
execute in order to extract and display the varbind’s value. For example, if ZTMX-
TKN-TRAP-VARBIND-DATATYPE has a value of ZTMX_TNM_SMI_INTEGER, the
token named ZTMX_TKN_SMI_INTEGER is accessed.
34. The main block initiates communication with an EMS consumer distributor and
then calls getevent_loop() to process trap events.
35. Any EMS collector and filter names passed in the invocation line are identified.
36. The collector name is resolved to a fully qualified file name.
37. The collector name is formatted for use by EMS procedures.
38. The filter name is resolved to a fully qualified file name.
39. The filter name is formatted for use by EMS procedures.
40. The subsystem ID structures are initialized.
41. The buffer for holding a SPI response is allocated by using
ZCOM_VAL_MAX_RSP_BUFLEN to define the largest supported buffer (5120
bytes).
42. An EMS distributor process is started.
43. The process is opened.
44. The process is initialized as a consumer distributor process because event access
is programmatic.
45. The process is closed and then re-opened to initiate SPI command/response
interactions.
46. The function named spi_cmd_set_source() is called to identify the collector from
which trap events are to be received.
47. The function named spi_cmd_load_filter() is called to identify the filter to use.
48. The function getevent_loop() is called to process trap events.