Adding a new workload definition
You can add a new workload definition using the Add DB2 Workload Definition dialog box.
To add a new workload definition
- Use one of the following methods:
- In Edit mode, type ADD on the DWKLDDEF COMMAND line to open the dialog box with the default workload definition settings.
- In Edit mode, type ADD beside an existing workload to open the dialog box using the selected workload’s settings and then specify a new workload name.
Enter values for the following parameters:
Parameter
Description
Workload identification
Workload name
workloadName (maximum eight alphanumeric characters)
Name of the workload
A workload name should clearly represent the work performed by the target subsystem or region. Consistent workload names make it easier to sort and filter views to find
the information that you want to display.Description
description (maximum 40 alphanumeric characters)
Description of the workload.
Composite wkld
compositeName (maximum eight alphanumeric characters)
Name used to group workloads together.
All workloads that share the same composite name are grouped together for a given target and are reported to MainView VistaPoint as a single entity. Consider the following points when specifying a composite name
- The first character in the name must be an alpha character.
- The composite name can be the same as the workload name if only one workload is associated with the composite name.
- If multiple workloads are to be combined, each workload name must be different and the composite name must be the same for each.
- If a composite name is not specified for a workload, the workload name is automatically assigned as the composite name.
Composite workloads have no meaning for CPU workload monitors.
Target DB2
subsystemName
Name of a target Db2 subsystem from which the workload data should be collected.
You can use asterisk, plus sign, and question mark wildcards to create a selection mask to represent multiple Db2 targets.
This is a required field. If a target is not specified in the field, the field must contain an asterisk.SMF System
systemID
ID of a z/OS system if the workload is to be restricted to a single operating system image.
You can use asterisk, plus sign, and question mark wildcards to create a selection mask to represent multiple z/OS systems.
This is a required field. If a system is not specified in the field, the field must contain an asterisk.Workload Time and Performance Goals
Start Time
hh:mm
When the workload monitor is to begin collecting thread response time data from targets specified in the workload definition.
You can specify a start time and an end time to establish a regularly scheduled period of data collection.Start and end times can span midnight, creating a data collection period of two consecutive days. For example, you can set your start and end times to 08:00 hours. The previous monitoring period ends at 08:00 hours and the next monitoring period begins immediately at 08:00.
End Time
hh:mm
When the workload monitor is to stop collecting thread response time data from targets specified in the workload definition.
You can specify a start time and an end time to establish a regularly scheduled period of data collection.
Start and end times can span midnight, creating a data collection period of two consecutive days. For example, you can set your start and end times to 08:00 hours. The previous monitoring period ends at 08:00 hours and the next monitoring period begins immediately at 08:00.
Goal
ss
Response time or CPU time goal for threads that occur within a target workload, in seconds. Service level objectives are based on whether a defined minimum percentage of a workload's threads can complete within the specified goal.
The minimum percentage of successful workload threads is specified in the Percent Goal field .Goal Type
R | C
Whether the goal is a response type goal, or a CPU goal.
Percent Goal
nn
Minimum percentage of workload threads that must complete within the response time or CPU time target to meet service level agreements (SLAs). If the percentage of a target's threads is less than the minimum specified in this field, the workload is failing to meet its SLAs.
In DB2 Time
Y | N
Whether to monitor total time for a thread, or only CPU time used while in Db2.
Specifying Y starts the @CPTD monitor, which monitors CPU time in Db2. Specifying N starts the @CPTM monitor, which monitors all CPU time used in a thread.
Thread Selection
CONNTYPE
TSO | IMS | CICS | BATCH | CAF |IMSMPP | IMSBMP |IMSTBMP | IMSCTL | DLI | DDF | DRDA | RRSAF | UTIL | blank
Qualifies a workload monitor by connection type. Blank collects data for all connection types.
DB2PLAN
planName
Qualifies a workload monitor by a one- to eight-character Db2 plan name.
DB2AUTH
authorizationID
Qualifies a workload monitor by Db2 authorization ID.
DB2CONN
connectionName
Qualifies a workload monitor request by a one- to eight-character connection name. 1
DB2CORR
DB2LOC
locationName
Qualifies a workload monitor by a 1- to 16-character remote location name. Only distributed DBAT threads with this requester location are selected. Optionally, you can specify the full local location name or a single + to monitor all distributed threads.
Specify an IP address in quotation marks.
DB2PKG
packageName
Qualifies a workload monitor request by a 1- to 128-character Db2 package name (only when accounting class 7 or 8 is active). 1
DB2RTN
routineName
Specify the 1- to 64-character Db2 activity name of a stored procedure, trigger, or user-defined function (available only when accounting class 7/8/10 is active).
A record is selected if the specified qualifier matches any routine name found in the accounting package sections. With RRSAF/ DDF rollup data, only rollup package data is available and the name might not be available for matching. 1
1 The maximum number of operands is the total field length (128 characters). You can use the + character as a name qualifier for a summary monitor.
- To save the workload definition, type END on the COMMAND line.
The DWKLDDEF view is displayed.
Where to go from here
Related topic