Purpose of Status Feeder Client

This example shows how a client can send attribute changes for Operations Sentinel Console to the Event Server. This client does not request notification of events.

Code

main(
   int argc,
   char **argv
)
{
   char *attr[] = {"MYATTR"};
   char *value[] = {"myvalue"};
 
   /* Initialize the API.
      Application name = "Status feeder"
      No application qualifier.
   */
   SPD_InitClient("Status feeder", NULL);
 
   /* client processing... */
 
   /* Report a change in value of an attribute of an object 
      being monitored by the Status application:
      The class is "disk".
      The instance is "disk01".
      The host on which the instance resides is "HOST1".
      The application name and qualifier are set to NULL.  This
      causes the default values to be used (i.e., "Status feeder"
      for the name and NULL for the qualifier).
      No time stamp.
      One attribute is updated.  Its name (from the attr array) is
      "MYATTR" and its new value (from the value array) is "myvalue".
   */
   SPD_ReportValue("disk", "disk01", "HOST1", NULL, NULL, 0, 1,
       attr, value);
 
   /*  more client processing... */
    
   /*  no event loop required if events are only sent,
       but not received.
   */
}

Data Flow Diagram

This illustration shows the flow of information for the Status Feeder client.