Description: If you are migrating to a new level of coupling facility control code (CFCC), you have to make appropriate coupling facility structure size updates in the z/OS® coupling facility resource management (CFRM) policy.
Element or feature: | Multiple. |
When change was introduced: | General migration action not tied to a specific release. |
Applies to migration from: | z/OS V1R13 and z/OS V1R12. |
Timing: | Anytime. |
Is the migration action required? | Yes, if you are migrating to a new CFCC level. |
Target system hardware requirements: | See http://www.ibm.com/systems/z/advantages/pso/cftable.html . |
Target system software requirements: | None. |
Other system (coexistence or fallback) requirements: | None. |
Restrictions: | None. |
System impacts: | None. |
Related IBM® Health Checker for z/OS check: | None. |
Steps to take: If you are migrating to a new CFCC level, do the following:
Alternatively, you can run an as-is batch utility program called SIZER after you have brought a new CFLEVEL coupling facility into use in your configuration. SIZER examines your currently allocated coupling facility structures and recalculates the size that should be used for them with the new later-CFLEVEL coupling facility. The as-is SIZER utility is available as a zipped package that you can download from http://www.ibm.com/systems/support/z/cfsizer/altsize.html .
Reference information: For a detailed description of coupling facility code levels and the processors that support those levels, see http://www.ibm.com/systems/z/advantages/pso/cftable.html .