Defining a workload to monitor the application
Related topics
After you have collected information about the application, define a workload to monitor the application.
- Establish some basic service level objectives for the application, for example
- 90% of all transactions should be finished within one second
- Transactions MTGF and MDB2 represent the majority of the Finance workload and 95% of these transactions should be finished within 0.5 seconds
- Create and install a workload definition for the application by using the appropriate view for your product, for example
- CWKLDDEF (BMC AMI Ops Monitor for CICS)
- DWKLDDEF (BMC AMI Ops Monitor for Db2)
- IWKLDDEF (BMC AMI Ops Monitor for IMS Online)
- WKLIST (BMC AMI Ops Monitor for z/OS)
- Verify that the newly installed workload definition is collecting data by displaying the workload objective view for your product, for example
- COBJ (BMC AMI Ops Monitor for CICS)
- DOBJ (BMC AMI Ops Monitor for Db2)
- IOBJ (BMC AMI Ops Monitor for IMS Online)
- WOBJ (BMC AMI Ops Monitor for z/OS)
For more detailed instructions, see Using BMC AMI Ops products or online Help.
Best Practices for workload definitions
Use the following Best Practices when creating workload definitions:
- Create workload definitions in one BBPARM data set and share that data set with all of the PASs to reduce the number of workload definitions.
Use a consistent naming convention for workload definitions to allow easy identification and to facilitate sorting and filtering in views. Use names that reflect the work performed by the target of the workload.
- Specify a composite name for workload definitions. All workload definitions that share the same composite name are grouped together for a given target and are reported to MainView VistaPoint as a single entity.
- Identify critical workload monitoring periods and create workload definitions for those time periods.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*