|
|
This section demonstrates how the sample program event2 generates an event and sends an indication (or notification message) to the DMI SP that an event occurred. The SP passes the indication to a management application registered to receive indications, which then processes it.
As rma2 is not registered to receive any indications, this section also introduces the management application, indcons, which is registered to receive indications as defined in the accompanying indcons.inp data file.
The following message should appear:
DmiOriginateEvent() returned status 0x0
Among the files in this directory is defAddr.txt, which holds details of the machine (or indication originator) indcons is to manage, using the following format:
transport_type
rpc_type
IP_address
The file should now look something like:
ncacn_ip_tcp onc 192.168.24.66
In the first window you should see the following output:
DmiOriginateEvent() returned status 0x0
(This is the same message you saw before, generated by event2.)
In the second window you should see a large amount of data, generated by the indcons process, illustrating the kind of data that can be transferred by an indication. An extract is shown below:
... Language : 'en|US|iso8859-1' (len=16) Component Id : 2 Time : 1998:08:11:16:15:19:.:25 :+:000:***: Row Data : (size=1)COMPID : 2 GROUPID : 2001 CLASS NAME : 'EventGeneration|Phone Book|001' (len=31) Key List : (size=1) Id : 5 Value : STRING : 'EventGeneration|Phone Book|001' (len=31)
-----------------------------------
Values List: (size=6) Id : 1 Value : MIF_INTEGER : 0 ...
./event2 -?
You can use these options to generate events of varying severity and type, and for different components.