Skip to Content

Workloads you can define

By using BMC AMI Ops Monitor for z/OS, you can define these types of workloads:

Related topic

Deciding-which-workloads-to-define

  • ASCH—composed of address spaces scheduling work for z/OS APPC (Advanced Program-to-Program Communications)
  • Batch—composed of address spaces running batch jobs
  • OMVS—composed of address spaces running OpenEdition z/OS applications
  • Started task—composed of address spaces running Started Tasks
  • TSO—composed of address spaces running TSO sessions

  • Composite—collections of other previously defined workloads
    With composite workloads, you can monitor diverse collections of address spaces as a single entity.

    For example, you might create a workload called DB2WORK to track all address spaces that are related to IBM Db2: TSO address spaces that are used for QMF sessions, batch jobs that update Db2 tables, and Db2’s own Started Tasks. This concept is illustrated in the following figure.

GUID-9DA9D478-4E55-4482-BCEB-B45838965995-low.png

Up to 128 workloads can be defined.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for z/OS 6.3