Creating VistaPoint workloads

This section describes how to create workload definitions and incorporate them into VistaPoint applications.

The following figure shows a transaction environment composed of z/OS, CICS, Db2, and IMS regions and subsystems running on two z/OS images. CICS and Db2 have production and development work running on MVSA. Query work is done on MVSB for CICS, Db2, and IMS. z/OS production batch and TSO are split between the two images:

CICS, Db2, and IMS Running on Two MVS Images 

In this example, you have a heterogeneous integrated transaction environment. Transactions no longer occur within the domain of a single product. Typically, Db2 is a server to CICS and IMS client transactions. An accurate performance assessment in this environment requires the ability to combine performance from separate products performing shared tasks. Also, you need the ability to combine related performance occurring simultaneously in separate MVS images.

BMC AMI Ops products that work with VistaPoint provide the capability to monitor transaction performance for the IBM products. BMC AMI Ops Monitor for CICS, BMC AMI Ops Monitor for Db2, BMC AMI Ops Monitor for IMS, and BMC AMI Ops Monitor for z/OS individually monitor their target's transaction response times.

You build workload definitions that describe how you want these products to monitor their respective targets. In an ISPF dialog, you fill in fields with the values that you want for your workload definition.

As part of the definition, you assign a composite name to which a workload belongs. VistaPoint combines performance from similarly named composite workloads into a common application. VistaPoint presents application views that allow you to see the combined performance of workloads sharing common tasks.