OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
The name of an event class is the same as its filename. Each event class is defined within
an event class file.
You can define new event classes by removing or adding event numbers in the event
class files, or by creating new event class files.
42.3.5.2 Event Class Names
Each event class has a symbolic name assigned to it. Following is the suggested name
format of event classes that vendors should follow:
ec_ org_product_class
where:
org Is the name of the organization or company that defines the event class.
product Is the name of the product for which the event class is defined.
class Is the characterization of the event class.
The following are two examples of event class names:
• ec_osf_dce_authentication—Defines an authentication event class for OSF’s DCE
core components.
• ec_transarc_encina_update—Defines an update event class for Transarc’s Encina.
You can also define event classes to meet your own auditing needs. The following is the
suggested name format for these event classes:
dce_server-name_class
where class is a characterization of the event class.
42.3.5.3 Event Class Numbers
If you define your own event classes, you must associate it with an event class number.
Event class numbers are 32-bit integers. Each event class number is a tuple made up of a
set ID and the class ID. The set ID corresponds to a set of event classes and is assigned
by OSF to an organization or vendor. The class ID identifies an event class within the set
of event classes. The organization or vendor manages the issuance of the class ID
numbers to generate an event class number.
The structure and administration of event class numbers can be likened to the structure
and administration of IP addresses. Recall that an IP address is a tuple of a network ID
(analogous to the set ID) and a host ID (analogous to the class ID).
42 − 4 Tandem Computers Incorporated 124243