Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Redefining volumes among storage groups z/OS DFSMSdfp Storage Administration SC23-6860-01 |
|
Perform the following steps if you defined DASD volumes to belong to one storage group but you now want them to belong to a different storage group.
Result: The changes take effect when
you activate this updated configuration.
You are responsible for maintaining consistent physical connections. You must also be aware of multivolume data sets. In general, all of a multivolume data set must be in a single storage group (it is possible, when the primary storage group is stressed, for a multivolume data set to extend to more than one storage group). You must also maintain storage group, management class, and storage class consistency. If a data set has a management class with certain migration and backup attributes, and you redefine the volume containing that data set from one storage group to another, the new storage group might not be eligible for the same migration and backup processing. You can also use the MVS SETSMS command to change the SMS status of volumes. Any SMS status that is changed by a SETSMS command is effective only until a new configuration is activated. The MVS status is not affected by either the SETSMS command or the activation of a new configuration. Only the SMS status is affected. |
Copyright IBM Corporation 1990, 2014
|