Tivoli Connection Guide and Reference


Application event definitions

TEC_CLASS:
   Application_Event ISA EVENT
   DEFINES {
   source: default = "Application Name";
   sub_source: default = "Component Name";
   sub_origin: default = "TME Managed Node Name";
   deployment_map: STRING ;
   };
END
TEC_CLASS:
   Application_notice ISA Application_Event
   DEFINES {
   severity: default = HARMLESS;
   };
END
TEC_CLASS:
   Application_warning ISA Application_Event
   DEFINES {
   severity: default = WARNING;
   };
END
TEC_CLASS:
   Application_error ISA Application_Event
   DEFINES {
   severity: default = CRITICAL;
   };
END
TEC_CLASS:
   Application_startup ISA Application_notice;
END
TEC_CLASS:
   Application_idle ISA Application_notice;
END
TEC_CLASS:
   Application_shutdown ISA Application_notice;
END
TEC_CLASS:
   Application_System_error ISA Application_error
   DEFINES {
   error_number: INTEGER;
   };
END
TEC_CLASS:
   Application_SQL_error ISA Application_error
   DEFINES {
   sqlcode: INTEGER;
   database: STRING;
   table: STRING;
   sqlca: STRING;
   };
END

The following event slots are defined for application events:

source
Application Name, as it appears in the "Application Name" attribute of the Global Description File for the application. This field can be overridden in the configuration file.

sub_source
Component Name, as it appears in the "Component Name" attribute of the Component Description File for the component. This field can be overridden in the configuration file.

origin
IP address

sub_origin
operating system and version

hostname
local hostname, as obtained by the gethostname() function or equivalent

The library populates event slots as follows:


[ Top of Page | Previous Page | Next Page | Table of Contents ]