Setting goals
As documented in Workload classification, Developer for z/OS® creates different types of workloads on your system. These different tasks communicate with each other, which implies that the actual elapse time becomes important to avoid time-out issues for the connections between the tasks. As a result, Developer for z/OS tasks should be placed in high-performance service classes, or in moderate-performance service classes with a high priority.
A revision, and possibly an update, of your current WLM goals is therefore advised. This is especially true for traditional MVS shops new to time-critical OMVS workloads.
- The goal information in this section is deliberately kept at a descriptive level, because actual performance goals are very site-specific.
- To help understand the impact of a specific task on your system, terms like minimal, moderate and substantial resource usage are used. These are all relative to the total resource usage of Developer for z/OS itself, not the whole system.
Table 1 lists the address spaces that are used by z/OS Explorer and Developer for z/OS. z/OS UNIX will substitute "x" in the "Task Name" column by a random 1-digit number.
| Description | Task name | Workload |
|---|---|---|
| (z/OS Debugger) Debug Manager | DBGMGR | STC |
| (z/OS Explorer) JES Job Monitor | JMON | STC |
| (z/OS Explorer) RSE daemon | RSED | STC |
| (z/OS Explorer) RSE thread pool | RSEDx | OMVS |
| (ISPF) Interactive ISPF Gateway (TSO Commands serverice) | <userid> | JES |
| (ISPF) Legacy ISPF Gateway (TSO Commands service) | <userid>x | OMVS |
| CARMA (batch) | CRA<port> | JES |
| CARMA (crastart) | <userid>x | OMVS |
| MVS build (batch job) | * | JES |
| z/OS UNIX build (shell commands) | <userid>x | OMVS |
| z/OS UNIX shell | <userid> | OMVS |