Description: As your applications grow in size and use greater amounts of storage, you should evaluate whether the DASD allocated for your stand-alone dump data continues to be adequate.
In z/OS V1R6, support was introduced for extended-format sequential data sets, a form of data set that is SMS-managed and can occupy more than 64 K tracks per volume. In z/OS V1R7, this support was supplemented with support for large format sequential data sets (DSNTYPE=LARGE), a form of data set that is essentially the same as conventional sequential data sets except that more than 64 K tracks may be spanned per volume. If your stand-alone dump data sets are spread over more volumes than you want, both types of support can help you gain better control over the number of volumes used for each stand-alone dump data set.
Element or feature: | BCP. |
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: | Before installing z/OS V2R1. |
Is the migration action required? | No, but recommended because of changes that have been made to stand-alone dump processing (that reorder dump records with the intent of recording more important data early), and especially recommended if you deploy any LPARs with significantly more main storage than previously used. |
Target system hardware requirements: | None. |
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. |
BLS21110I CISIZE(cisize) is less than 24K. It may degrade IPCS performance