Define a workload to monitor the application
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 (MainView for CICS)
- DWKLDDEF (MainView for DB2)
- IWKLDDEF (MainView for IMS Online)
- WKLIST (MainView 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 (MainView for CICS)
- DOBJ (MainView for DB2)
- IOBJ (MainView for IMS Online)
- WOBJ (MainView for z/OS)
For more detailed instructions, see Using-MainView-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 workloads 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.
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*