z/OS

DFSMSdss Storage AdministrationVersion 2 Release 3

SC23-6868-30

IBM

NoteBefore using this information and the product it supports, read the information in Notices on page 671.

This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modificationsuntil otherwise indicated in new editions.

Last updated: December 7, 2017

Copyright IBM Corporation 1984, 2017.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . xiii

About this document . . . . . . . . xvRequired product knowledge . . . . . . . . xv

z/OS information . . . . . . . . . . xvii

How to send your comments to IBM xixIf you have a technical problem . . . . . . . xix

Summary of changes . . . . . . . . xxiSummary of changes for z/OS Version 2 Release 3(V2R3) . . . . . . . . . . . . . . . . xxiSummary of changes for z/OS Version 2 Release 2(V2R2) as updated December 2015 . . . . . . xxiSummary of changes for z/OS Version 2 Release 2(V2R2) . . . . . . . . . . . . . . . xxiiSummary of changes for z/OS Version 2 Release 1(V2R1) as updated February 2015 . . . . . . xxiiSummary of changes for z/OS Version 2 Release 1(V2R1) as updated September, 2014 . . . . . . xxiiz/OS Version 2 Release 1 summary of changes xxiii

Part 1. DFSMSdss StorageAdministration Guide . . . . . . . . 1

Chapter 1. Introduction to theDFSMSdss component of DFSMS. . . . 3Understanding the role of DFSMSdss . . . . . . 3

Managing user data with SMS . . . . . . . 3Sequential data striping. . . . . . . . . . 4Record counting . . . . . . . . . . . . 4Installation exit routines . . . . . . . . . 5Authorization checking . . . . . . . . . . 5

Managing availability with DFSMSdss . . . . . . 5Backing up and restoring volumes and data sets . 6Using DFSMShsm for backup. . . . . . . . 7Using concurrent copy . . . . . . . . . . 7Using the stand-alone restore program ofDFSMSdss . . . . . . . . . . . . . . 8

Managing data movement with DFSMSdss . . . . 9Moving data . . . . . . . . . . . . . 9Moving data in an SMS-managed environment . . 9Moving data with concurrent copy . . . . . 10Moving data with FlashCopy . . . . . . . 10Moving data with SnapShot . . . . . . . . 10

Converting data to and from SMS management . . 10Converting data sets with data movement . . . 10Converting volumes without data movement . . 11

Managing space with DFSMSdss . . . . . . . 11

Chapter 2. Requirements for runningDFSMSdss . . . . . . . . . . . . . 13Understanding the operating environment . . . . 13Storage requirements . . . . . . . . . . . 13Hardware requirements . . . . . . . . . . 15Volume formats . . . . . . . . . . . . . 15Indexed VTOC . . . . . . . . . . . . . 16Data set organizations . . . . . . . . . . . 16Temporary data set names . . . . . . . . . 17

Chapter 3. Logical and physicalprocessing and data set filtering . . . 21Defining logical and physical processing. . . . . 21

Logical processing . . . . . . . . . . . 21Physical processing . . . . . . . . . . . 22Data integrity considerations . . . . . . . 23

Choosing data sets for processingfiltering . . . 24Filtering by data set names . . . . . . . . 24Filtering by data set characteristics . . . . . 25The FILTERDD keyword . . . . . . . . . 27Uses of filtering . . . . . . . . . . . . 27

Chapter 4. Invoking DFSMSdss . . . . 29Invoking DFSMSdss with ISMF. . . . . . . . 29

How to invoke ISMF . . . . . . . . . . 29Invoking DFSMSdss with JCL . . . . . . . . 29Invoking DFSMSdss with the application interface 29

User interaction module exit functions . . . . 30

Chapter 5. Protecting DFSMSdssfunctions. . . . . . . . . . . . . . 31Protecting DFSMSdss and ISMF functions withRACF . . . . . . . . . . . . . . . . 31

ISMF functions you might want to protect . . . 31Setting up the authorization structure . . . . 31

Protecting DFSMSdss functions with RACFFACILITY class profiles . . . . . . . . . . 33Name-hiding . . . . . . . . . . . . . . 35

Chapter 6. Managing availability withDFSMSdss . . . . . . . . . . . . . 37Planning an availability strategy . . . . . . . 37

Backup and recovery . . . . . . . . . . 37Disaster recovery . . . . . . . . . . . 38Maintaining vital records . . . . . . . . . 40Archiving data sets . . . . . . . . . . . 41

Backing up data sets . . . . . . . . . . . 41Logical data set dump . . . . . . . . . . 42Physical data set dump . . . . . . . . . 43Renaming data sets during dump processing . . 44Backup with concurrent copy . . . . . . . 45Backing up data sets to an object storage cloud 47Using DFSMSdss as a backup utility for CICSVR 49A backup scenario . . . . . . . . . . . 49

Copyright IBM Corp. 1984, 2017 iii

||

Backing up data sets with special requirements . . 50Dumping HFS data sets . . . . . . . . . 50Dumping zFS data sets . . . . . . . . . 51Dumping multivolume data sets . . . . . . 51Dumping integrated catalog facility user catalogs 53Dumping non-VSAM data sets that have aliases 53Dumping VSAM spheres . . . . . . . . . 54Dumping indexed VSAM data sets . . . . . 54Dumping SYS1 system data sets . . . . . . 54Dumping data sets containing records past thelast-used-block pointer . . . . . . . . . 55Backing up SMS-managed data sets . . . . . 55Backing up data sets being accessed with recordlevel sharing . . . . . . . . . . . . . 56Backing up data sets with extended attributes . . 56

Backing up volumes . . . . . . . . . . . 56Logical volume DUMP . . . . . . . . . 56Physical volume dump . . . . . . . . . 57Backing up system volumes . . . . . . . . 57Backing up VM-format volumes . . . . . . 57

Dumping data efficiently . . . . . . . . . . 58Combining volume copy and volume dump toreduce your backup window . . . . . . . 58Space considerations . . . . . . . . . . 61Performance considerations . . . . . . . . 61Shared DASD considerations . . . . . . . 67Backing up and restoring volumes withincremental FlashCopy . . . . . . . . . 67

Securing your tape backups . . . . . . . . . 70Using host-based encryption to secure backups 71DFSMSdss processing of dump encryptionrequests . . . . . . . . . . . . . . 75

Restoring data sets . . . . . . . . . . . . 77Logical data set restore . . . . . . . . . 78DFSMSdss handling of the expiration dateduring logical restore . . . . . . . . . . 82DFSMSdss handling of the data-set-changedindicator during restore . . . . . . . . . 82Physical data set restore . . . . . . . . . 83Coexistence considerations . . . . . . . . 84

Restoring data sets with special requirements . . . 84Restoring multivolume data sets and restoringdata sets using multiple target volumes (spillvolumes) . . . . . . . . . . . . . . 84Restoring integrated catalog facility catalogs . . 85Restoring non-VSAM data sets that have aliases 88Restoring indexed sequential, unmovable, direct,and absolute track data sets . . . . . . . . 88Restoring an undefined DSORG data set . . . 90Restoring an extended-format VSAM data setwith stripe count of one . . . . . . . . . 90Restoring a VSAM sphere . . . . . . . . 90Restoring a preallocated VSAM cluster . . . . 91Restoring the VVDS and the VTOCIX . . . . 91Restoring a PDSE . . . . . . . . . . . 91Restoring a damaged PDS . . . . . . . . 91Restoring data sets in an SMS-managedenvironment . . . . . . . . . . . . . 92Converting non-VSAM data sets to multivolume 92Restoring SMS-managed data sets . . . . . . 93Restoring GDG data sets . . . . . . . . . 96

Restoring non-SMS-managed data sets . . . . 97Logical restore of data sets with phantom catalogentries . . . . . . . . . . . . . . . 97Logical restore of preformatted empty VSAMdata sets . . . . . . . . . . . . . . 98

Restoring volumes . . . . . . . . . . . . 98Specifying output volumes . . . . . . . . 99Recovering VM-format volumes . . . . . . 101Coexistence considerations . . . . . . . . 101

Chapter 7. Managing data movementwith DFSMSdss . . . . . . . . . . 103Preparing for data movement . . . . . . . . 103

Evaluating the use of logical and physical copy 103Controlling what DFSMSdss copies . . . . . 104Moving data sets . . . . . . . . . . . 104Moving volumes . . . . . . . . . . . 105

Logical data set copy . . . . . . . . . . . 105Physical data set copy . . . . . . . . . . 106Specifying input volumes . . . . . . . . . 106Selecting output volumes . . . . . . . . . 107Renaming data sets . . . . . . . . . . . 108Expiration date handling . . . . . . . . . 110

SMS to SMS . . . . . . . . . . . . . 110SMS to non-SMS . . . . . . . . . . . 110Non-SMS to SMS . . . . . . . . . . . 111Non-SMS to non-SMS . . . . . . . . . 111

Defining RACF profiles . . . . . . . . . . 111Moving data sets with utilities . . . . . . . . 111Moving data sets with concurrent copy. . . . . 113

Specifying concurrent copy for COPY requests 113Moving data sets with FlashCopy . . . . . . 115

Designating FlashCopy usage . . . . . . . 116Moving data sets with SnapShot . . . . . . 118

Moving data sets with special requirements . . . 120Moving undefined DSORG and emptynon-VSAM data sets . . . . . . . . . . 120Moving system data sets . . . . . . . . 121Moving catalogs . . . . . . . . . . . 121Moving non-VSAM data sets that have aliases 122Moving multivolume data sets . . . . . . 122Converting VSAM and non-VSAM data sets tomultivolume . . . . . . . . . . . . 123Moving VSAM data sets. . . . . . . . . 124Moving a PDSE . . . . . . . . . . . 125Moving a damaged PDS. . . . . . . . . 125Moving unmovable data sets . . . . . . . 126Moving data sets to unlike devices . . . . . 126Moving indexed sequential data sets . . . . 127Moving direct access data sets . . . . . . . 127Moving GDG data sets . . . . . . . . . 127Movi