Span of MVS workload manager operation

MVS™ workload manager operates across a sysplex. You can run each MVS image in the sysplex in either goal mode or compatibility mode. However, there can be only one active service policy for all MVS images running in goal mode in a sysplex.

All CICS® regions (and other MVS subsystems) running on an MVS image with MVS workload manager are subject to the effects of workload management.

If the CICS workload involves non-CICS resource managers, such as DB2® and DBCTL, CICS can pass information through the resource manager interface (RMI1) to enable MVS workload manager to relate the part of the workload within the non-CICS resource managers to the part of the workload within CICS.

Unlike MRO links, CICS does not pass information across ISC links to relate the parts of the task execution thread on either side of the ISC link. If you use tasks that communicate across ISC links, you must define separate performance goals, and service classes, for the parts of the task execution thread on each side of the ISC link. These rules apply to ISC links that are:

If you use tasks that communicate across ISC links between two sysplexes, the separate performance goals are defined in the active service policy for each sysplex.

Related tasks
Defining performance goals for MVS Workload Manager
Setting up service definitions for MVS Workload Manager
Using MVS workload manager

Related concepts
MVS workload manager
Terms used in MVS workload management
CICSPlex SM workload management

1.
The CICS interface modules that handle the communication between a task-related user exit and the resource manager are usually referred to as the resource manager interface (RMI) or the task-related user exit (TRUE) interface.

[[ Contents Previous Page | Next Page Index ]]