Use the DB2 for LUW Workload Editor to create and set properties for DB2 LUW Workloads. A workload is used to identify incoming work based on its source, so that it can later be managed. Use options on the Collection Attributes tab, Collection Data tab, Histogram Template tab, and Connection Attributes tab to set properties for a selected workload.
Note: This topic applies to DB2 for LUW versions 9.5 and 9.7 only.
To define a DB2 LUW workload
The DB2 for LUW Workload Editor opens.
Note: Click New on the toolbar to create a workload name. Use the Enter filter text text box to filter a large list of names to locate the one you want to work with.
Specifies the name of the workload.
Indicates that the selected workload is enabled.
Specifies whether or not the selected workload can access database while executing.
Specifies the service class associated with the workload.
Specifies whether or not to generate DDL for this object during Forward Engineering.
Specifies the type of connection you want to use to connect to the database. The valid values for this field are ADDRESS, APPLNAME, SYSTEM_USER, SESSION_USER, SESSION_USER GROUP, SESSION_USER ROLE, CURRENT CLIENT_USERID, CURRENT CLIENT_APPLNAME, CURRENT CLIENT_WRKSTNNAME, AND CURRENT CLIENT_ACCTNG.
Specifies the value for the type of connection you have selected. Click the New icon (icon) to create a value.
The collection parameters specify the data about each activity associated with this workload that is sent to any active activities event monitor when the activity completes. Specify values for the following fields:
Specifies how you want to collect activity data. The valid values are none, without Details, with details, with details and values, with details and sections, with details and section and values.
Specifies that activity data is collected at database partitions where the activity is processed. You can specify whether to collect data from coordinated partitions or all partitions.
Specifies that monitor metrics are collected for an activity submitted by an occurrence of the workload.
Specifies that aggregate activity data about the activities associated with this workload is sent to the statistics event monitor, if one is active.
Specifies that data about lock timeout events that occur within this workload is sent to an event monitor when the lock event occurs.
Specifies that data about deadlock events that occur within this workload is sent to any active locking event monitor when the lock event occurs.
Specifies that data about each transaction associated with this workload is sent to the unit of work event monitor, if any are active, when the unit of work ends.
Specifies that data about lock wait events that occur within this workload is sent to any active locking event monitor when the lock has not been acquired within wait-time.
Specifies the maximum time within which the lock has to be acquired for the data about lock wait events to be sent to a locking event monitor.
Specifies the template that describes the histogram used to collect statistical data about the duration, in microseconds, of DB2 activities running in the workload during a specific interval. This time includes both time queued and time executing.
Specifies the template that describes the histogram used to collect the length of time, in microseconds, of DB2 activities running in the workload are queued during a specific interval.
Specifies the template that describes the histogram used to collect statistical data about the length of time, in microseconds, that DB2 activities running in the workload are executing during a specific interval. This time does not include the time spent queued.
Specifies the template that describes the histogram used to collect statistical data about the estimated cost, in timerons, of DML activities running in the workload.
Specifies the template that describes the histogram used to collect statistical data about the length of time, in microseconds, between the arrival of any two consecutive DML activities into this workload.
The DB2 for LUW Workload Editor closes.
Copyright © 2013 CA.
All rights reserved.
|
|