HSMS makes use of common memory pools. The HSMS administrator can define the size of these common memory pools via the COMMON-MEMORY-SIZE operand of the HSMS statement MODIFY-HSMS-PARAMETERS, while the system administrator can use the same operand of the START-HSMS statement for this purpose.
If HSMS performs an internal calculation during loading and discovers that the size defined in MODIFY-HSMS-PARAMETERS is not large enough, it automatically creates the memory pool with the calculated size. Note that, in contrast to this, HSMS does not correct the value defined for the current HSMS session by means of START-HSMS.
SHOW-HSMS-PARAMETERS VALID-PERIOD=*SESSION causes HSMS to output the currently valid value, i.e. the corrected value, if applicable.
The value calculated by HSMS will usually be sufficiently large. Note, however, that bottlenecks may occur in cases where the computer center-specific application requires values that are markedly different from the parameters on which HSMS calculations are based. Such bottlenecks may, for instance, render the creation of archives impossible.
Situations of this sort will be reported by HSMS. When they arise, the HSMS administrator should increase the value for the common memory pool. The new value does not take effect, however, until the next HSMS session.
When selecting the value it should be remembered that the size of the common memory pool limits the user address space.