Table 1 lists
the address spaces that are used by z/OS
Explorer,
where “u” in the “Count” column indicates
that the amount must be multiplied by the number of concurrently active
users using the function. z/OS® UNIX will substitute “x”
in the “Task Name” column by a random 1-digit number.
| Count | Description | Task name | Shared | Ends after |
|---|---|---|---|---|
| 1 | JES Job Monitor | JMON | Yes | Never |
| 1 | RSE daemon | RSED | Yes | Never |
| 2 | RSE daemon APF authorized | RSEDx | Yes | Never |
| (a) | RSE thread pool | RSEDx | Yes | Never |
| (a) | RSE thread pool APF authorized | RSEDx | Yes | Never |
| 1u | Interactive ISPF Gateway | <userid> | No | 15 minutes or user logoff |
| lu | Legacy ISPF Gateway(TSO Commands service) | <userid>x | No | 15 minutes or user logoff |
| lu | TSO Commands service (APPC) | FEKFRSRV | No | 60 minutes or user logoff |
| (b) | Simultaneous Legacy ISPF Gateway usage by 1 user | <userid>x | No | Task completion |
| 1u | z/OS UNIX shell | <userid> | No | User logoff |
Note:
- (a) There is at least one RSE thread pool address space active.
The actual number depends on:
- The minimum.threadpool.process directive in rse.env. The default value is 1.
- The number of users that can be serviced by one thread pool. The default settings aim for 30 users per thread pool.
Note: If the single.logon directive is active, then there will be at least 2 thread pools started, even if minimum.threadpool.process is set to 1. The default setting for single.logon in rse.env is active. - (b) z/OS Explorer has multiple threads active per user. In the event that the Legacy ISPF Gateway address space has not finished serving the request of one thread when another thread sends a request, ISPF will start up a new Gateway to process the new request. This address space ends after task completion.
- Most MVS™ data set related actions use the TSO Commands service, which can be active in the ISPF Gateway or an APPC transaction, respectively.
Use the formula in Figure 1 to
estimate the maximum number of address spaces used by z/OS
Explorer.
Figure 1. Maximum number
of address spaces
Where - “4” equals the number of permanent active server address spaces.
- “A” represents the number of RSE thread pool address spaces.
- “N” represents the maximum number of concurrent users.
- “x” is one of the following values, depending on the
selected configuration options.
X TSO (Interactive ISPF Gateway) TSO (Legacy ISPF Gateway) TSO (APPC) 1 Yes No No 1 No Yes No 1 No No Yes - “2 + N*0.01” adds a buffer for temporary address spaces. The required buffer size might differ at your site.
Use the formula in Figure 2 to estimate
the maximum number of address spaces used by a z/OS
Explorer client
(not counting the undocumented temporary address spaces).
Figure 2. Number of address
spaces per client
Where - "x" depends on the selected configuration options and is documented for the formula to calculate the maximum number of address spaces (Figure 1).
The definitions in Table 2 can limit
the actual number of address spaces.
| Location | Limit | Affected resources |
|---|---|---|
| rse.env | maximum.threadpool.process | Limits the number of RSE thread pools |
| IEASYMxx | MAXUSER | Limits the number of address spaces |
| ASCHPMxx | MAX | Limits the number of APPC initiators for TSO Commands service (APPC) |