Size estimate guidelines

As stated before, the actual storage usage by z/OS® Explorer is heavily influenced by user activity. Some actions use a fixed amount of storage (for example, logon), while others are variable (for example, listing data sets with a specified high-level qualifier).

• Use a 2 GB address space for RSE to allow room for the Java™ heap and all the system control blocks.
• When running in 64-bit mode, ensure that the storage above the 2 GB bar is actually available to RSE.
• See Address Space size to learn more about where address space size limits can be set.
• The default rse.env setup aims for 10 users per thread pool.
  • maximum.clients=10
  • maximum.threads=250 (14+19*10 = 205), so 250 allows for 10 clients
• The default rse.env setup lets the Java heap grow up to 512 MB. This allows for 10 clients using an average of 51 MB per client (10*51 = 510).

Use either of the following scenarios if monitoring shows that the current Java heap size is insufficient for the actual workload:

• Increase the maximum Java heap size with the Xmx directive in rse.env. Before doing so, ensure that there is room in the address space for the size increase.
• Decrease the maximum number of clients per thread pool with the maximum.clients directive in rse.env. RSE will still support the same number of clients, but the clients will be distributed among more thread pools.