OMVS

All workloads use the client user ID as base for the address space name. (z/OS® UNIX will substitute "x" in the "Task Name" column by a random 1-digit number.)

The workloads will all end up in the same service class due to a common address space naming convention. You should specify a multi-period goal for this service class. The first periods should be high-performance, percentile response time goals, while the last period should have a moderate-performance velocity goal. Some workloads, such as the ISPF Client Gateway, will report individual transactions to WLM, while others do not.

• Legacy ISPF Gateway

  The Legacy ISPF Gateway is an ISPF service invoked by Developer for z/OS to execute non-interactive TSO and ISPF commands. This includes explicit commands issued by the client as well as implicit commands issued by Developer for z/OS. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be minimal.

• CARMA

  CARMA is an optional Developer for z/OS server that is used to interact with host based Software Configuration Managers (SCMs), such as CA Endevor® SCM. Developer for z/OS allows for different startup methods for a CARMA server, some of which become an OMVS workload. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be minimal.

• z/OS UNIX build

  When a client initiates a build for a z/OS UNIX project, z/OS UNIX REXEC (or SSH) will start a task that executes a number of z/OS UNIX shell commands to perform the build. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be moderate to substantial, depending on the size of the project.

• z/OS UNIX shell

  This workload processes z/OS UNIX shell commands that are issued by the client. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be minimal.