Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Defining accessibility z/OS DFSMSdfp Storage Administration SC23-6860-01 |
||||||||||||||||||||||||||||||||||||||||
The storage class accessibility attribute defines the function of the hardware supporting the point-in-time copy, using either concurrent copy, virtual concurrent copy, or FlashCopy®. The point-in-time copy allows database management systems (DBMSs) to take what appears to be an instantaneous copy of data or a "fast" point-in-time copy. The copy can be for backup purposes (generally to tape) or for copying a database from one set of DASD volumes to another. The accessibility attribute allows you to direct allocation of new data sets to DASDs connected to an IBM® 3990 Storage Control unit with cache that supports the concurrent copy function, IBM RAMAC Virtual Array (RVA) devices with the SnapShot copy support, DFSMSdss with the virtual concurrent copy, and the IBM ESS with the FlashCopy service. The IBM Enterprise Storage Server® (ESS) FlashCopy service provides the appearance of instantaneous replication of a range of track images. You can invoke this service with DFSMSdss and use it to create copies for disaster recoveries, business intelligence applications, data in a test environment, and instantaneous checkpoints. See z/OS DFSMS Advanced Copy Services for further information on the ESS FlashCopy service. When you specify accessibility attributes, you identify whether you want SMS to use versioning or backup devices for either concurrent copy or virtual concurrent copy.
You can use a combination of values for the accessibility attribute and its subparameters, Versioning and Backup, to request the point-in-time copy. In the Accessibility field, you specify whether allocation to a point-in-time copy-capable volume is required (CONTINUOUS), preferred (CONTINUOUS PREFERRED), or discouraged (STANDARD). You then specify values for the Versioning and Backup subparameters to select which devices you want used for the copy. The following defines your
allocation request to a point-in-time
copy-capable volume:
Table 1 identifies the values you specify based on your specific accessibility requirements:
You can also use the data set alter application to alter a storage class so that data sets can be allocated on point-in-time copy-capable volumes. |
Copyright IBM Corporation 1990, 2014
|