Event Monitors (DB2)
Event monitors show activity from start to finish, and often consist of both a start and end event record. The most common uses for event monitors are for connections, locks, and statements. PowerDesigner models event monitors as extended objects with a stereotype of <<EventMonitor>>.
You can create an event monitor in any of the following ways:
-
Select
Model 
Event Monitors 
to access the List of Event Monitors, and click the
Add a Row tool. -
Right-click the model or package in the Browser, and select
New Event Monitor .
You can modify an object's properties from its property sheet. To open an event monitor property sheet, double-click its diagram symbol or its Browser entry in the Event Monitors folder.
The following extended attributes are available on the General tab:
|
Name |
Description |
|---|---|
|
Workload management event monitor |
Specifies that the event monitor is used for workload management. Selecting this option affects the types that are available in the Type field. Scripting name: WlmEventMonitor |
|
Type |
Specifies the type of event to record. Click the button to the right of the field to select multiple types. Scripting name: Type |
Event condition |
[connections, transactions, or statements type] Defines a filter that determines which connections cause a CONNECTION, STATEMENT or TRANSACTION event to occur. Scripting name: EventCondition |
Details |
[deadlock type] Specifies that the event monitor is to generate a more detailed deadlock connection event for each application that is involved in a deadlock. Scripting name: DeadlocksDetails |
The following extended attributes are available on the DB2 tab:
|
Name |
Description |
|---|---|
|
Write to |
Specifies the location where the event monitor will record its information. If you are writing to a table, you can additionally associate the event monitor with one or more event monitor groups on the EVMGroup tab. Event monitor groups identify the logical data group for which a target table is being defined, and PowerDesigner models them as extended sub-objects with a stereotype of <<EventMonitor>>. Scripting name: WriteToObject |
Blocked |
[table, file] Specifies that each agent that generates an event should wait for an event buffer to be written out to disk if the agent determines that both event buffers are full. This option should be selected to guarantee no event data loss. Scripting name: Blocked |
Buffer size |
[table, file] Specifies the size of the event monitor buffers (in units of 4K pages). All event monitor file I/O is buffered to improve the performance of the event monitors. Scripting name: BufferSize |
Path |
[file] The name of the directory in which the event monitor should write the event files data. The path must be known at the server. Scripting name: Path |
Max files |
[file] Specifies that there is a limit on the number of event monitor files that will exist for a particular event monitor at any time. Scripting name: MaxFiles |
Maximum file size |
[file] Specifies that there is a limit to the size of each event monitor file. Scripting name: MaxFileSize |
Append |
[file] Specifies that if event data files already exist when the event monitor is turned on, then the event monitor will append the new event data to the existing stream of data files. Scripting name: Append |
Pipe name |
[pipe] The name of the pipe to which the event monitor will write the data. The naming rules for pipes are platform specific. Scripting name: PipeName |
Start |
Specifies that the event monitor must be activated manually or is to be automatically activated whenever the database partition on which the event monitor runs is activated. Scripting name: Start |
Scope |
Either the event monitor reports on all database partitions (global) or only on the database partition that is running (local). Scripting name: Scope |
Database partition |
[pipe, file] Specifies the database partition on which the event monitor is to run. Scripting name: DBPartitionNum |
You can create and manage event monitor groups from the EVMGroup tab of an event monitor. PowerDesigner models event monitor groups as extended sub-objects with a stereotype of <<EVMGroup>>.
The following extended attributes are available on the General tab:
|
Name |
Description |
|---|---|
|
Group |
Identifies the logical data group for which a target table is being defined. Scripting name: Group |
|
Table |
Specifies the name of the target table. Scripting name: Table |
PCTDeactivate |
If a table is being created in a DMS table space, the PCTDEACTIVATE parameter specifies how full the table space must be before the event monitor automatically deactivates. Scripting name: PCTDeactivate |
Tablespace |
Defines the table space in which the table is to be created Scripting name: Tablespace |
Trunc |
Specifies that the STMT_TEXT and STMT_VALUE_DATA columns are defined as VARCHAR(n), where n is the largest size that can fit into the table row. Scripting name: Trunc |
Inclusion criteria |
Specifies which elements will be included in the table. Scripting name: Elements |
Elements |
Identifies a monitor element that will be included in or excluded from monitoring Scripting name: ElementList |