OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
Format D is not administered by OSF and can be used freely within the cell. These event
numbers may not be unique across cells and should not be used by application servers
that are installed in more than one cell.
Format E is reserved for future use.
The event number formats are illustrated in Figure 33-1.
Figure 33-1. Event Number Formats
Format A
Format B
Format C
Format D
Format E
0 1 2 3 4 8 16 24 31
0 set–id event–id
1 0 set–id event–id
1 1 0 set–id event–id
1 1 1 0 event–id
1 1 1 1 reserved
33.3.3.3 Sample Event Numbers for DCE Servers
Following are examples of event numbers in the security and time servers, as defined in a
header file used by the security server and time server programs, respectively.
/* Event numbers 0x00000100 to 0x000001FF are assigned to the
security server. */
#define AS_Request 0x00000100
#define TGS_TicketReq 0x00000101
#define TGS_RenewReq 0x00000102
#define TGS_ValidateReq 0x00000103
...
/* Event numbers 0x00000200 to 0x000002FF are
assigned to the time server. */
#define CNTRL_Create 0x00000200
#define CNTRL_Delete 0x00000201
#define CNTRL_Enable 0x00000202
#define CNTRL_Disable 0x00000203
...
33.3.3.4 Sample Event Numbers for Application Servers
The following is an example of the event numbers in a banking server application, as
defined in the application’s header file.
33−4 Tandem Computers Incorporated 124245