| Cleanup_events4_DDMConfig_view | No information available
Applies to: Servers
|
| Cleanup_events4_DDMFilters_view | No information available
Applies to: Servers
|
| Cleanup_events4_messages_view | No information available
Applies to: Servers
|
| Cleanup_events4_methods_view | No information available
Applies to: Servers
|
| Cleanup_events4_on_first_night | No information available
Applies to: Servers
|
| Cleanup_events4_stats_view | No information available
Applies to: Servers
|
| Debug_Event | This produces a lot of output, which will show all the notifications being loaded when the Event Monitor starts, show the amount of Event Pool consumed initially, and show what is generating events on the server. You must take steps to capture the output,
Valide since: 5.0
Applies to: Servers
|
| EventSetup |
Valide since: 0
Obsolete since: 0
|
| Event_Pool_Size | The default for Event_Pool_Size in R5 and R6 is 5242880 (5 MB), and that will be the maximum size to which the memory pool can grow for unprocessed events, unprocessed notifications, and event suppression memory. When trying to determine if this is an eve
Valide since: 5.0
|
| Platform_Statistics_Enabled | enables or disable Performance Monitoring Statistics (NT Intel and Solaris Sparc only).
Valide since: 5.0.2
Applies to: Servers
|
