Debug Manager resource usage
Use the information in this section to estimate the normal and maximum resource usage by Debug
Manager, so you can plan your system configuration accordingly.
For more information about resource usage, see the topic about resource usage in IBM® Explorer for z/OS Host Configuration Reference Guide (SC27-8438).
Overview
Table 1 gives an overview of the number of address spaces, processes, and threads used by DBGMGR.
| Started task | Address spaces | Processes | Threads |
|---|---|---|---|
| DBGMGR | 1 | 1 | 4 |
Address space count
Table 2 lists the address spaces that are used by Debug Manager.
| Count | Description | Task name | Shared | Ends after |
|---|---|---|---|---|
| 1 | Debug Manager | DBGMGR | Yes | Never |
Process count
Table 3 lists the number of processes per address space that is used by Debug Manager.
| Processes | Address spaces | Description | User ID |
|---|---|---|---|
| 1 | 1 | Debug Manager | STCDBM |
Thread count
Table 4 lists the number
of threads used by Debug Manager. The thread count is listed per process,
as limits are set at this level.
- RSEDx: These threads are created in the RSE thread pool, which is shared by multiple clients. All threads ending up in the same thread pool must be added together to get the total count.
- Active: These threads are part of the process that actually does the requested function. Each process is a stand-alone unit, so there is no need to sum the thread counts, even if they are assigned to same user ID, unless noted otherwise.
- Bootstrap: Bootstrap processes are needed to start the actual process. Each has 1 thread, and there can be multiple consecutive bootstraps. There is no need to sum the thread counts.
| Threads
|
User ID | Description | ||
|---|---|---|---|---|
| RSEDx | Active | Bootstrap | ||
| - | 4 | - | STCDBM | Debug Manager |