Universal Event Monitor Server configuration options
Universal Event Monitor Server configuration options
This page provides links to detailed information on the configuration options available for use with the Universal Event Monitor Server.
The options are listed alphabetically, without regard to any specific operating system.
Configuration Options Information
For each configuration option, these pages provide the following information.
Description
Describes the option and how it is used.
Usage
Provides a table of the following information:
Method | Syntax | IBM i | HP NonStop | UNIX | Windows | z/OS |
---|---|---|---|---|---|---|
Configuration File Keyword | <Format / Value> | |||||
UEM Load Override | <Format / Value> | |||||
UEM Manager Override | <Format / Value> |
Method
Identifies the different methods used to specify Universal Event Monitor Server configuration options:
- Configuration File Keyword
- UEMLoad Override
- UEM Manager Override
Note
Each option can be specified using one or more methods.
Syntax
Identifies the syntax of each method that can be used to specify the option:
- Format: Specific characters that identify the option.
- Value: Type of value(s) to be supplied for this method.
Note
If a Method is not valid for specifying the option, the Syntax field contains n/a.
(Operating System)
Identifies (with a ?) the operating systems for which each method of specifying the option is valid:
- IBM i
- HP NonStop
- UNIX
- Windows
- z/OS
Values
Identifies all possible values for the specified value type.
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="cb55f521-5704-45c8-8061-de159faaae21"><ac:parameter ac:name="">1186350</ac:parameter></ac:structured-macro> Defaults are identified in [bracketed bold type].
<Additional Information>
Identifies any additional information specific to the option.
Configuration Options List
The following table identifies all UEM Server configuration options.
Option | Description |
---|---|
UEM Server component to which a stored event definition is assigned. | |
Code page used for text translation | |
ID of a stored event handler record that should be used whenever an event is set to an expired state. | |
Base directory in which UEM Server is installed | |
Specifies whether or not the desktop of the current interactive logon session is accessible to the handler process. | |
Frequency with which a Keep-Alive message is sent to the UEM Manager. | |
Specifies whether or not to load a user's profile and environment when a handler process is executed. | |
Specifies how a user account is logged on when the environment for execution of a handler process is established. | |
Highest return code than an event handler may exit with to still be considered as having executed successfully. | |
Level of messages written. | |
Smallest size a file may be in order for it to be considered complete. | |
List of message IDs representing Universal messages to be suppressed. | |
Directory location of message catalog and code page tables | |
Frequency with which a UEM Server will detect new occurrences of a system event. The UEM Server will also check at this time see if a monitored event should be made inactive. | |
ID of a stored event handler record that should be used whenever an event occurrence is set to a rejected state. | |
Flag that indicates whether or not a completed file should be renamed. | |
Name or pattern to use when a file is renamed. | |
Default shell interpreter for event handler processes executed as scripts. | |
Specifies the directory in which trace files are written. | |
Maximum number of lines written to a trace file before it wraps around. | |
Memory trace table specification. | |
Frequency, in seconds, with which a tracked event occurrence is tested for completeness. | |
ID of a stored event handler record that should be used whenever an event occurrence is set to a triggered state. | |
Type of script interpreter used to evaluate and execute a script on behalf of an event handler. | |
Specifies whether or not user account authorization is required to monitor an event and/or execute a handler process. |