Accommodate increase in nucleus size
Description
With the introduction of the z/OS® V1R13 RSM Enablement Offering web deliverable, the nucleus will increase in size by approximately 380K above the 16MB line. Because of this increase, the available private storage might affect the way your applications run on your system.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | BCP |
|---|---|
| When change was introduced: | z/OS V1R13 RSM Enablement Offering Web deliverable. |
| Applies to migration from: | z/OS V1R13 without the z/OS V1R13 RSM Enablement Offering web deliverable. |
| Timing: | Before the first IPL of z/OS V2R2. |
| Is the migration action required? | Yes, if the increase in nucleus size will affect the private storage available to applications on your system above the 16MB line. |
| Target system hardware requirements: | None. The migration action is relevant on all servers. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | Failure to have sufficient private storage available might result in errors that affect the running of your applications. |
| Related IBM® Health Checker for z/OS check: | VSM_CSA_CHANGE. You can use this health check to identify changes in the size of CSA or private (including the extended areas) since the last IPL. |
Steps to take
Review your current available private storage usage above the 16MB line using reports from RMF™ or an equivalent product. Ensure that an increase of 380K for the nucleus above the 16 MB line will not adversely affect your system. Adjust values accordingly.
Reference information
For more information,
see the following references:
- Verify that virtual storage limits are set properly
- z/OS MVS Initialization and Tuning Guide
- z/OS MVS Initialization and Tuning Reference.