Setting goals
z/OS® Explorer, z/OS Debugger, and IBM® Developer for z/OS create 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, these 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 IBM Developer for z/OS or z/OS Debugger, not the whole system.
All z/OS Debugger started tasks are servicing real-time client requests.
| Description | Task name | Workload |
|---|---|---|
| Debug Manager | DBGMGR | STC |
- Debug Manager
Debug Manager provides services to connect programs being debugged to clients debugging them. You should specify a high-performance, one-period velocity goal, because the task does not report individual transactions to WLM. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be minimal.