• • Abstract for DFSMSdss Storage Administration
  • Where to find more information
  • Summary of changes
    • Summary of changes
    • z/OS Version 2 Release 1 summary of changes
• DFSMSdss Storage Administration Guide
  • Introduction to the DFSMSdss component of DFSMS
    • Understanding the role of DFSMSdss
      • Managing user data with SMS
      • Sequential data striping
      • Record counting
      • Installation exit routines
      • Authorization checking
    • Managing availability with DFSMSdss
      • Backing up and restoring volumes and data sets
      • Using DFSMShsm for backup
      • Using concurrent copy
        • Virtual concurrent copy
      • Using the stand-alone restore program of DFSMSdss
    • Managing data movement with DFSMSdss
      • Moving data
      • Moving data in an SMS-managed environment
      • Moving data with concurrent copy
      • Moving data with FlashCopy
      • Moving data with SnapShot
    • Converting data to and from SMS management
      • Converting data sets with data movement
      • Converting volumes without data movement
    • Managing space with DFSMSdss
  • Requirements for running DFSMSdss
    • Understanding the operating environment
    • Storage requirements
    • Hardware requirements
    • Volume formats
    • Indexed VTOC
    • Data set organizations
    • Temporary data set names
  • Logical and physical processing and data set filtering
    • Defining logical and physical processing
      • Logical processing
        • When to use logical processing
      • Physical processing
        • When to use physical processing
      • Data integrity considerations
        • Broken data set considerations
    • Choosing data sets for processing—filtering
      • Filtering by data set names
      • Filtering by data set characteristics
        • Some examples of filtering by data set characteristics
      • The FILTERDD keyword
      • Uses of filtering
  • Invoking DFSMSdss
    • Invoking DFSMSdss with ISMF
      • How to invoke ISMF
    • Invoking DFSMSdss with JCL
    • Invoking DFSMSdss with the application interface
      • User interaction module exit functions
  • Protecting DFSMSdss functions
    • Protecting DFSMSdss and ISMF functions with RACF
      • ISMF functions you might want to protect
      • Setting up the authorization structure
        • Finding the DFSMSdss/ISMF module names
        • Protecting DFSMSdss/ISMF modules
    • Protecting DFSMSdss functions with RACF FACILITY class profiles
    • Name-hiding
  • Managing availability with DFSMSdss
    • Planning an availability strategy
      • Backup and recovery
        • Data set backup
        • Volume backup
        • Backup and recovery in an SMS-managed environment
          • SMS-managed data
          • Non-SMS-managed data
        • Backup and recovery in a non-SMS-managed environment
      • Disaster recovery
        • Storing at a remote site
        • Using logical data set dump
        • Back up only critical data sets
      • Maintaining vital records
      • Archiving data sets
    • Backing up data sets
      • Logical data set dump
      • Physical data set dump
      • Renaming data sets during dump processing
      • Backup with concurrent copy
        • Specifying concurrent copy for DUMP requests
        • Invocation from an application program
      • Using DFSMSdss as a backup utility for CICSVR
      • A backup scenario
    • Backing up data sets with special requirements
      • Dumping HFS data sets
        • Logical dump
        • Physical dump
      • Dumping zFS data sets
        • Logical dump
        • Physical dump
      • Dumping multivolume data sets
      • Dumping integrated catalog facility user catalogs
      • Dumping non-VSAM data sets that have aliases
      • Dumping VSAM spheres
      • Dumping indexed VSAM data sets
      • Dumping SYS1 system data sets
      • Dumping data sets containing records past the last-used-block pointer
      • Backing up SMS-managed data sets
        • Filter on class names
        • Class names saved
      • Backing up data sets being accessed with record level sharing
      • Backing up data sets with extended attributes
    • Backing up volumes
      • Logical volume DUMP
      • Physical volume dump
      • Backing up system volumes
      • Backing up VM-format volumes
    • Dumping data efficiently
      • Combining volume copy and volume dump to reduce your backup window
        • Combining the functions
        • Special considerations
          • Restrictions
          • Related information
      • Space considerations
      • Performance considerations
        • DUMP
        • Concurrent copy
        • Concurrent copy storage requirements
        • Virtual concurrent copy working space
          • Virtual concurrent copy using SnapShot
          • Virtual concurrent copy using FlashCopy
          • Common working space data sets considerations
        • Read DASD I/O pacing
          • Invocation from a customer program
      • Shared DASD considerations
      • Backing up and restoring volumes with incremental FlashCopy
        • Using the FCINCREMENTAL keyword
        • Using the FCINCREMENTALLAST keyword
        • Using the FCINCRVERIFY keyword
        • Using the FCWAIT keyword
        • Usage scenario 1: periodic dump to tape
        • Usage scenario 2: check-point batch processing with incremental FlashCopy
    • Securing your tape backups
      • Using host-based encryption to secure backups
        • Types of host-based encryption
          • What is DES and AES?
          • Cryptographic keys and DFSMSdss
        • Considerations for host-based encryption
        • Key management considerations
        • Using compression with host-based encryption
        • Examples of host-based encryption
        • Hardware requirements for encryption and decryption
        • Performance and processor types
        • Software requirements for encryption and decryption
        • ICSF callable services for DFSMSdss
      • DFSMSdss processing of dump encryption requests
        • If double encryption is required
    • Restoring data sets
      • Logical data set restore
        • Output volume selection
        • Restoring to preallocated target data sets
        • Cataloging data sets during logical restore processing
        • Renaming data sets during logical restore processing
        • Restoring data sets with the IMBED or REPLICATE attributes
        • Restoring data sets with the KEYRANGES attribute
      • DFSMSdss handling of the expiration date during logical restore
        • Allocating to SMS
        • Allocating to non-SMS
      • DFSMSdss handling of the data-set-changed indicator during restore
      • Physical data set restore
        • Output volume selection
        • Cataloging data sets during physical restore processing
      • Coexistence considerations
    • Restoring data sets with special requirements
      • Restoring multivolume data sets and restoring data sets using multiple target volumes (spill volumes)
      • Restoring integrated catalog facility catalogs
      • Restoring non-VSAM data sets that have aliases
      • Restoring indexed sequential, unmovable, direct, and absolute track data sets
        • Restoring without preallocated targets
        • Restoring to preallocated targets
        • Restoring direct access data sets
      • Restoring an undefined DSORG data set
      • Restoring an extended-format VSAM data set with stripe count of one
      • Restoring a VSAM sphere
        • Restrictions for restore processing
      • Restoring a preallocated VSAM cluster
      • Restoring the VVDS and the VTOCIX
      • Restoring a PDSE
      • Restoring a damaged PDS
      • Restoring data sets in an SMS-managed environment
      • Converting non-VSAM data sets to multivolume
      • Restoring SMS-managed data sets
        • Changing storage class with the RESTORE command
        • Changing management class with restore processing
        • Restoring SMS-managed data sets physically
      • Restoring GDG data sets
        • Restoring SMS-managed GDG data sets
      • Restoring non-SMS-managed data sets
      • Logical restore of data sets with phantom catalog entries
        • Using the DELETECATALOGENTRY keyword
        • IMPORT keyword
      • Logical restore of preformatted empty VSAM data sets
    • Restoring volumes
      • Specifying output volumes
        • Processing RACF-protected data sets
        • Recovering system volumes
      • Recovering VM-format volumes
      • Coexistence considerations
  • Managing data movement with DFSMSdss
    • Preparing for data movement
      • Evaluating the use of logical and physical copy
      • Controlling what DFSMSdss copies
      • Moving data sets
      • Moving volumes
    • Logical data set copy
    • Physical data set copy
    • Specifying input volumes
    • Selecting output volumes
    • Renaming data sets
    • Expiration date handling
      • SMS to SMS
      • SMS to non-SMS
      • Non-SMS to SMS
      • Non-SMS to non-SMS
    • Defining RACF profiles
    • Moving data sets with utilities
    • Moving data sets with concurrent copy
      • Specifying concurrent copy for COPY requests
    • Moving data sets with FlashCopy
      • Designating FlashCopy usage
        • Preserve Mirror FlashCopy
        • Determining why FlashCopy cannot be used
        • Freeing subsystem resources
      • Moving data sets with SnapShot
        • Designating SnapShot usage
        • Determining why SnapShot cannot be used
    • Moving data sets with special requirements
      • Moving undefined DSORG and empty non-VSAM data sets
      • Moving system data sets
      • Moving catalogs
      • Moving non-VSAM data sets that have aliases
      • Moving multivolume data sets
      • Converting VSAM and non-VSAM data sets to multivolume
      • Moving VSAM data sets
        • Restrictions for the COPY command
      • Moving a PDSE
      • Moving a damaged PDS
      • Moving unmovable data sets
      • Moving data sets to unlike devices
      • Moving indexed sequential data sets
      • Moving direct access data sets
      • Moving GDG data sets
        • Moving generation data sets to SMS-managed volumes
        • Moving generation data sets to non-SMS-managed volumes
      • Moving SMS-managed data sets
        • Selecting target volumes
        • Changing storage class with Copy
        • Changing management class with Copy
      • Moving non-SMS-managed data sets
      • Moving to preallocated data sets
        • Rules for moving to preallocated target data sets
          • VSAM preallocation
          • Non-VSAM preallocation
        • Specifying multiple target volumes
        • How keywords work with preallocated targets
          • ALLEXCP and ALLDATA
          • CATALOG and RECATALOG
          • NOPACKING
          • PERCENTUTILIZED
          • PROCESS(SYS1)
          • REBLOCK
          • RENAMEUNCONDITIONAL
      • Moving data sets being accessed with record level sharing
      • Moving preformatted empty VSAM data sets
    • VTOC considerations for moving volumes
    • Logical volume copy operation
    • Physical volume copy operation
    • Moving volumes with FlashCopy
      • Designating FlashCopy usage
      • Determining why FlashCopy cannot be used
      • Freeing subsystem resources
      • Choosing space efficient FlashCopy with the FCSETGTOK keyword
      • Initializing the volume with the FCWITHDRAW keyword
      • Backing up volumes with FlashCopy consistency group
        • Creating consistent copies with FlashCopy consistency group
        • Freezing the source volumes in copy operations
        • Thawing the frozen volumes in CGCREATED operation
        • Verifying the consistency group
        • Example
    • Moving volumes with SnapShot
      • Designating SnapShot usage
      • Determining why SnapShot cannot be used
    • Moving volumes to like devices of equal capacity
    • Moving volumes to like devices of greater capacity
    • Moving volumes to unlike devices
    • Moving VM-format volumes
  • Converting data to and from SMS management
    • Evaluating conversion to SMS management
      • Data sets ineligible for conversion to SMS
      • Data sets ineligible for conversion from SMS
      • Volumes eligible for conversion to SMS
    • Conversion by data movement
      • Converting to SMS management by data movement
      • Conversion from SMS management by data movement
    • Conversion without data movement
      • Simulating conversion
      • Preparing a volume for conversion
    • Converting to SMS management without data movement
      • SMS report
    • Special data set requirements for conversion to SMS
      • VSAM sphere eligibility
      • Multivolume data sets
      • GDG data sets
      • Temporary data sets
      • VTOC and VVDS
    • Converting from SMS management without data movement
    • Special data set requirements for conversion from SMS
      • Multivolume data sets
      • GDG data sets
      • Temporary data sets
      • VTOC and VVDS
    • Special considerations for using non-SMS-managed targets
  • Managing space with DFSMSdss
    • Reclaiming DASD space
      • Releasing unused space in data sets
      • Compressing a PDS
      • Deleting unwanted data sets
      • Combining data set extents
    • Consolidating free space and extents on volumes
      • When to run DEFRAG and CONSOLIDATE functions
      • Designating FlashCopy usage
      • Preserve Mirror FlashCopy
      • Determining why FlashCopy cannot be used
      • Designating SnapShot usage
      • Determining why SnapShot cannot be used
      • Data sets excluded from DEFRAG or CONSOLIDATE processing
      • DEFRAG options
        • General hints
      • Serialization
      • Security considerations
    • Maximizing track utilization by reblocking data sets
  • Diagnosing problems in DFSMSdss operations
    • Determining the source of the failure: DFSMSdfp, DFSMSdss, or DFSMShsm
    • Using keywords to identify the problem
      • Component identification keyword
      • Release-level keyword
      • Type-of-failure and function keywords
        • ABENDxxx
        • MSGADRnnnt
        • WAIT
        • LOOP
        • INCORROUT
        • DOC
        • PERFM
      • Module keyword
      • Maintenance-level keyword
    • Using the IBM Support Center
      • Using the software support facility
      • Using IBMLink/ServiceLink
      • Info/System
  • ACS routine information
    • ACS variables available during Copy function
    • ACS variables available during RESTORE and CONVERTV processing
      • Using SIZE and MAXSIZE variables
  • Dumping and restoring Linux for System z partitions and volumes
    • Preparing to work with Linux volumes
      • Understanding the hardware environment
      • Choosing VOLSERs for Linux volumes
      • Formatting and partitioning Linux volumes
        • Using dasdfmt to format a Linux volume
        • Using fdasd to partition a Linux volume
      • Obtaining authorization for Linux volumes
      • Backing up a Linux volume with partitions
    • Using DFSMSdss dump and restore commands
      • Example 1. DUMP FULL
      • Example 2. DUMP FULL with CONCURRENT COPY
      • Example 3. DUMP DATASET
      • Example 4. COPY FULL
      • Example 5. COPY FULL COPYVOLID ALLEXCP
      • Example 6. RESTORE FULL
      • Example 7. RESTORE DATASET
      • Example 8. COPYDUMP
    • Submitting JCL batch jobs to a z/OS system using FTP
    • Using DFSMSdss stand-alone services
  • Format of the DFSMSdss dump data set
    • Format of the DFSMSdss dump data set
    • ADRBMB data area
      • ADRBMB constants
      • ADRBMB cross-reference
    • ADRTAPB data area
      • ADRTAPB constants
      • ADRTAPB cross-reference
  • DFSMSdss patch area
    • Sample JCL
    • Forcing the use of preallocated VSAM data sets (PN04574)
    • Ignoring VSAM duplicate key errors (PN05529)
    • Modifying the timeout period for enqueue lockout detection (PL84514)
    • Controlling the wait/retry time for serialization of system resources (PN11523)
    • Using CONVERTV on data sets with a revoked user ID in the RESOWNER field (OY59957)
    • Restoring inconsistent PDSE data sets (OY60301)
    • Changing default protection status during RESTORE (PN37489)
    • Restoring or copying undefined, multivolume SMS-managed data sets (OY63818)
    • Bypassing backup-while-open processing (OY63531)
    • Bypassing storage and management class authorization checking during RESTORE (OY65348)
    • Issuing notification for tape and migrated data sets (OY66092)
    • Using RESET with concurrent copy (OY65555)
    • Forcing RESTORE after message ADR482E (OY67532)
    • Restoring VSAM KSDS or VRRDS after messages ADR789W, ADR364W, and ADR417W (OY67942)
    • Restoring VSAM data sets with expiration date of 1999365 (OW00780)
    • Restoring VSAM data sets with expiration dates beyond 2000 (OW00780)
    • Changing default insertion of EOF track during COPY with ALLDATA specified (OW15003)
    • Using RESET or UNCATALOG in a logical data set dump (PN60114)
    • Changing secondary allocation quantity in format 1 DSCB for PDSE data sets (OW07755)
    • Changing reference date default settings during data set COPY and RESTORE processing (OW12011)
    • Changing default protection processing during COPY (OW10314)
    • Bypassing management and storage class access checks during COPY (PN72592)
    • Changing default handling of invalid tracks created during data set COPY and RESTORE processing (OW08174)
    • Forcing RESTORE to the same volumes as the source VSAM data set (OW07077)
    • Modifying number of volumes allocated for SMS data sets during logical RESTORE and COPY (OW15880)
    • Dumping a keyed VSAM data set that has data CAs without corresponding index CIs (OW17877)
    • Changing the default DEFRAG processing of checkpointed data sets (OW20285)
    • Setting the percentage to overallocate target data set space (OW27837)
    • Bypassing RLS processing (OW32817)
    • Changing creation date default settings during data set COPY and RESTORE (OW19618)
    • Copying and dumping a PDSE data set using the VALIDATE PDSE option (OW48074)
    • Changing the default maximum number of active parallel subtasks
    • Changing the default initialization processing during DUMP with FCWITHDRAW (OA18929)
    • Changing the default DEFRAG processing of LINKLIST-indicated data sets (OW43874)
    • Changing the FASTREPLICATION default setting during Copy and Defrag (OA11637)
    • Tuning hardware assisted compression (OA13300)
    • Resetting the data-set-changed indicator during physical full or partial RESTORE operation (OA20907)
    • Requesting that DFSMSdss double-check data set high used RBA values for LDS data sets (OA23805)
    • Enabling or disabling use of the catalog search interface for data set name filtering
    • Requesting that DFSMSdss restore the VM-formatted volume that was DUMPed by z/OS V1R10 before OA27531 was applied.
    • Adding timestamps to messages
    • Enabling building appropriate channel programs
    • Requesting that DFSMSdss attempt to fix ESDSes with corrupted RDFs
    • ADRPTCHB data area
      • ADRPTCHB cross-reference
• DFSMSdss Storage Administration Reference
  • Specifying DFSMSdss commands
    • Command syntax
    • How many subkeywords are allowed?
    • Specifying subkeywords in a command data set
    • How to read syntax diagrams
    • JCL that you need
      • How to control DFSMSdss through PARM information in the EXEC statement
      • Examples of invoking DFSMSdss with JCL
        • Moving a data set
        • Dumping a data set
        • Restoring a data set
  • DFSMSdss filtering—choosing the data sets you want processed
    • How DFSMSdss filters data sets
      • Virtual storage access method (VSAM) data set considerations
    • Filtering by data set names
      • Using an asterisk in partially qualified data set names
      • Using a percent sign in partially qualified data set names
      • Examples of fully and partially qualified data set names
        • Fully qualified data set names:
        • Partially qualified data set names using **:
        • More partially qualified data set names:
      • Relative generation filtering
    • Filtering by data set characteristics
      • Some examples of the BY keywords
    • Standard catalog search order
      • Broken data set considerations
  • Syntax—DFSMSdss function commands
    • What DFSMSdss commands do
      • Building the stand-alone IPL-able core image
      • Using DUMP and RESTORE for backup and recovery
      • Moving data with COPY
      • Converting to and from Storage Management Subsystem (SMS) with CONVERTV
      • Managing space with COMPRESS, CONSOLIDATE, DEFRAG, and RELEASE
      • Using COPY for partitioned data set (PDS) and partitioned data set extended (PDSE) conversions
      • Copying DFSMSdss-produced dump data with COPYDUMP
      • Printing for diagnostic purposes with PRINT
    • BUILDSA command for DFSMSdss
      • BUILDSA syntax
      • Explanation of BUILDSA command keywords
        • ADMINISTRATOR
        • INDDNAME
        • IPL
        • OPERCNSL
        • OUTDDNAME
        • OUTDYNAM
      • BUILDSA command examples
        • Example 1: core image using the default parameters
        • Example 2: core image for IPL from tape
        • Example 3: core image for IPL from DASD
        • Example 4: core image for IPL from DASD with OPERCNSL option
    • CGCREATED command for DFSMSdss
      • CGCREATED syntax
      • Explanation of CGCREATED command keywords
        • ACCESSVOLUME
        • FCCGVERIFY
    • COMPRESS command for DFSMSdss
      • COMPRESS syntax
      • Explanation of COMPRESS command keywords
        • ADMINISTRATOR
        • BY
        • DDNAME
        • DYNALLOC
        • DYNAM
        • EXCLUDE
        • FILTERDD
        • INCLUDE
        • PASSWORD
        • WAIT
      • Example of compress operations
    • CONSOLIDATE command for DFSMSdss
      • CONSOLIDATE command syntax
      • Explanation of CONSOLIDATE command keywords
        • ADMINISTRATOR
        • BY
        • CANCELERROR
        • DATASET
        • DEBUG
        • DYNALLOC
        • EXCLUDE
        • FASTREPLICATION
        • FCTOPPRCPRIMARY
        • FILTERDD
        • FORCECP
        • INCLUDE
          • Restrictions
        • MAXTIME
        • PASSWORD
        • PHYSINDDNAME
        • PHYSINDYNAM
        • PROCESS
        • WAIT
        • WRITECHECK
      • Example of a CONSOLIDATE operation
    • CONVERTV command for DFSMSdss
      • CONVERTV command syntax
      • Explanation of CONVERTV command keywords
        • CATALOG
        • DDNAME
        • DEBUG
        • DYNAM
        • FORCECP
        • INCAT
        • NONSMS
        • PREPARE
        • REDETERMINE
        • SELECTMULTI
        • SMS
        • TEST
      • Examples of CONVERTV operations
        • Example 1: using the CONVERTV command to simulate conversion
        • Example 2: using the CONVERTV command to convert to SMS
        • Example 3: using the CONVERTV command to convert from SMS
    • COPY Command for DFSMSdss
      • Special Considerations for COPY
      • COPY DATASET Command Syntax for Logical Data Set
      • COPY DATASET Command Syntax for Physical Data Set
      • COPY FULL and COPY TRACKS Syntax
      • Explanation of COPY Command Keywords
        • ADMINISTRATOR
        • ALLDATA
        • ALLEXCP
        • AUTORELBLOCKADDRESS
        • BY
        • BYPASSACS
        • CANCELERROR
        • CATALOG
        • CHECKVTOC
        • CICSVRBACKUP
        • CONCURRENT
        • CONVERT
        • COPYVOLID
        • CPVOLUME
        • DATASET
        • DEBUG
        • DELETE
        • DUMPCONDITIONING
        • DYNALLOC
        • EXCLUDE
        • FASTREPLICATION
        • FCCGFREEZE
        • FCFASTREVERSERESTORE
        • FCFULLVOLUMERELATION
        • FCINCREMENTAL
        • FCINCREMENTALLAST
        • FCINCRVERIFY
        • FCNOCOPY
        • FCNOCOPYTOCOPY
        • FCSETGTOK
        • FCTOPPRCPrimary
        • FCWAIT
        • FILTERDD
        • FORCE
        • FORCECP
        • FREESPACE
        • FULL
        • INCAT
        • INCLUDE
        • INDDNAME
        • INDYNAM
        • LOGINDDNAME
        • LOGINDYNAM
          • Notes for LOGINDDNAME, LOGINDYNAM and STORGRP keywords
        • MAKEMULTI
        • MENTITY
        • MGMTCLAS
        • NOPACKING
        • NOTIFYCONCURRENT
        • NULLMGMTCLAS
        • NULLSTORCLAS
        • ONLYINCAT
        • OUTDDNAME
        • OUTDYNAM
          • Notes for OUTDDNAME and OUTDYNAM Keywords
        • OUTTRACKS
        • PASSWORD
        • PERCENTUTILIZED
        • PHYSINDD
        • PHYSINDYNAM
        • PROCESS
        • PURGE
        • READIOPACING
        • REBLOCK
        • RECATALOG
        • RELBLOCKADDRESS
        • RENAMEUNCONDITIONAL
        • REPLACE
        • REPLACEUNCONDITIONAL
        • SELECTMULTI
        • SHARE
        • SPHERE
          • Restrictions
        • STORCLAS
        • STORGRP
        • TGTALLOC
        • TGTGDS
        • TOLERATE
        • TRACKS
        • TTRADDRESS
        • UNCATALOG
        • VOLCOUNT
        • WAIT
        • WRITECHECK
      • Data Integrity Considerations for Full or Tracks Copy Operation
      • Examples of Full and Tracks Copy Operations
        • Example 1: Data Set Copy Operation
        • Example 1A: A Full Copy Operation
        • Example 1B: A Tracks Copy Operation
        • Example 2: A Tracks Copy with Track Relocation
      • Examples of Data Set Copy Operations
        • Example 1: A Data Set Move—Only Single Volume Data Sets
        • Example 2: A Data Set Copy to Move Data Sets to a Single Volume—Device Conversion
        • Example 3: A Data Set Copy of a Multivolume Data Set
        • Example 4: A Data Set Copy with DELETE and RENAMEU Options
        • Example 5: A Data Set Copy With REBLOCK Option
        • Example 6: A Data Set Copy to a Preallocated Target Data Set
        • Example 7: Using the COPY Command to Convert to SMS
        • Example 8: A Data Set Copy Using CONVERT PDSE
        • Example 9: A Data Set Copy with CONCURRENT
        • Example 10: Copying a HFS using logical COPY
      • ALLDATA and ALLEXCP Interactions
    • COPYDUMP command for DFSMSdss
      • COPYDUMP syntax
      • Explanation of COPYDUMP command keywords
        • INDDNAME
        • LOGICALVOLUME
        • OUTDDNAME
      • Examples of COPYDUMP operations
        • Example 1: making two copies of a dump
        • Example 2: copying a dump created by using physical data set processing
        • Example 3: copying a dump created by using logical data set processing
    • DEFRAG command for DFSMSdss
      • DEFRAG syntax
      • Explanation of DEFRAG command keywords
        • ADMINISTRATOR
        • BY
        • CONSOLIDATE
        • DDNAME
        • DEBUG
        • DYNALLOC
        • DYNAM
        • EXCLUDE
        • FASTREPLICATION
        • FCTOPPRCPrimary
        • FORCECP
        • FRAGMENTATIONINDEX
        • MAXMOVE
        • MAXTIME
        • MMOVPCT
        • PASSDELAY
        • PASSWORD
        • VERSION1
        • WAIT
        • WRITECHECK
      • Examples of DEFRAG operations
        • Example 1: a DEFRAG operation with excluded data sets
        • Example 1A: with the names of excluded data sets in the input stream
        • Example 1B: with the names of excluded data sets in a data set
        • Example 2: a DEFRAG operation using a BY criterion
      • Results of a successful DEFRAG operation
    • DUMP command for DFSMSdss
      • Special considerations for dump
      • DUMP FULL and DUMP TRACKS syntax
      • DUMP DATASET syntax for logical data set
      • DUMP DATASET syntax for physical data set
      • Explanation of DUMP command keywords
        • ADMINISTRATOR
        • ALLDATA
        • ALLEXCP
        • BY
        • CANCELERROR
        • CHECKVTOC
        • CICSVRBACKUP
        • COMPRESS
        • CONCURRENT
        • CPVOLUME
        • DATASET
        • DELETE
        • DYNALLOC
        • ENCRYPT
        • EXCLUDE
        • FCWITHDRAW
        • FILTERDD
        • FORCECP
        • FULL
        • HWCOMPRESS
        • INCAT
        • INCLUDE
        • INDDNAME
        • INDYNAM
        • KEYPASSWORD
        • LOGINDDNAME
        • LOGINDYNAM
        • NEWNAMEUNCONDITIONAL
        • NOTIFYCONCURRENT
        • NOVALIDATE
        • ONLYINCAT
        • OPTIMIZE
        • OUTDDNAME
        • PASSWORD
        • PHYSINDD
        • PHYSINDYNAM
        • PROCESS
        • PURGE
        • READIOPACING
        • RESET
        • RSA
        • SELECTMULTI
        • SHARE
        • SPHERE
        • STORGRP
        • TOLERATE
        • TRACKS
        • UNCATALOG
        • VALIDATE
        • WAIT
          • For physical data set dump processing
          • For logical data set dump processing
        • ZCOMPRESS
      • Data integrity considerations for full or tracks dump operation
      • Format of the output data set
      • Examples of full and tracks dump operations
        • Example 1: a data set dump
        • Example 1A: a full dump operation
        • Example 1B: a tracks dump operation
        • Example 1C: full volume dump operation with CONCURRENT
      • Examples of physical data set dump operations
        • Example 2: depicting DASD volume DUMP
        • Example 2A: using the INCLUDE subkeyword
        • Example 2B: using the INCLUDE and EXCLUDE subkeywords
        • Example 2C: using the INCLUDE, EXCLUDE, and BY subkeywords
        • Example 2D: with filtering data in a data set
        • Example 2E: with passwords in the input stream
        • Example 2F: with passwords in a data set
        • Example 2G: wait for data sets if they or other data sets with the same name are in use by other jobs
        • Example 2H: clearing volumes of uncataloged data sets
      • Examples of logical data set dump operations
        • Example 1: dumping data sets constantly in use
        • Example 2: dumping a user catalog and its aliases
        • Example 3: logical data set dump operation with catalog filtering
        • Example 4: logical data set dump operation with VTOC filtering
        • Example 5: logical data set dump operation for Storage Management Subsystem (SMS)
        • Example 6: logical dump operation with CONCURRENT
        • Example 7: clearing volumes of uncataloged data sets
    • PRINT command for DFSMSdss
      • PRINT syntax
      • Explanation of PRINT command keywords
        • ADMINISTRATOR
        • ALLDATA
        • CPVOLUME
        • DATALENGTH
        • DATASET
        • DYNALLOC
        • ERRORTRACKS
        • INDDNAME
        • INDYNAM
        • KEYLENGTH
        • OUTDDNAME
        • PASSWORD
        • SHARE
        • TOLERATE
        • TRACKS
        • VTOC
        • WAIT
      • Examples of print operations
        • Example 1: printing a range of tracks
        • Example 2: printing a component of a Virtual Storage Access Method (VSAM) cluster
        • Example 3: printing a data set
    • RELEASE command for DFSMSdss
      • RELEASE syntax for physical processing
      • RELEASE syntax for logical processing
      • Explanation of RELEASE command keywords
        • ADMINISTRATOR
        • BY
        • DDNAME
        • DYNALLOC
        • DYNAM
        • EXCLUDE
        • INCAT
        • INCLUDE
        • LOGDDNAME
        • LOGDYNAM
        • MINSECQTY
        • MINTRACKSUNUSED
        • ONLYINCAT
        • PASSWORD
        • PROCESS
        • SELECTMULTI
        • SPHERE
        • STORGRP
        • WAIT
      • Example of a release operation
    • RESTORE command for DFSMSdss
      • Special considerations for RESTORE
      • Data integrity considerations for full or tracks restore operations
      • RESTORE FULL and RESTORE TRACKS command syntax
      • RESTORE DATASET command syntax for logical data set
      • RESTORE DATASET command syntax for physical data set
      • Explanation of RESTORE command keywords
        • ADMINISTRATOR
        • AUTORELBLOCKADDRESS
        • BCSRECOVER
        • BY
        • BYPASSACS
        • CANCELERROR
        • CATALOG or RECATALOG
        • COPYVOLID
        • CPVOLUME
        • DATASET
        • DEBUG
        • DELETECATALOGENTRY
        • DYNALLOC
        • EXCLUDE
        • FILTERDD
        • FORCE
        • FORCECP
        • FREESPACE
        • FULL
        • IMPORT
        • INCLUDE
        • INDDNAME
        • KEYPASSWORD
        • LOGICALVOLUME
        • MAKEMULTI
        • MENTITY
        • MGMTCLAS
        • NOPACKING
        • NULLMGMTCLAS
        • NULLSTORCLAS
        • OUTDDNAME
        • OUTDYNAM
          • Notes for OUTDDNAME and OUTDYNAM Keywords
        • OUTTRACKS
        • PASSWORD
        • PERCENTUTILIZED
        • PROCESS
        • PURGE
        • REBLOCK
        • RECATALOG
        • RELBLOCKADDRESS
        • RENAME
        • RENAMEUNCONDITIONAL
        • REPLACE
        • REPLACEUNCONDITIONAL
        • RESET
        • SHARE
        • SPHERE
        • RSA
        • STORCLAS
        • TGTALLOC
        • TGTGDS
        • TOLERATE
        • TRACKS
        • TTRADDRESS
        • VOLCOUNT
        • WAIT
        • WRITECHECK
      • DFSMSdss RESTORE process
        • Assignment of class names by using the RESTORE and COPY commands
      • Examples of full and tracks restore operations
        • Example 1: DASD volume-restore operation
        • Example 1A: full restore operation
        • Example 1B: tracks restore operation
        • Example 1C: tracks RESTORE—restore to different tracks
      • Examples of physical data set restore operations
        • Example 2: label tape volume RESTORED to DASD
        • Example 2A: using the INCLUDE subkeyword to restore all data sets on a dump tape
        • Example 2B: using the INCLUDE and EXCLUDE subkeywords
        • Example 2C: using the INCLUDE, EXCLUDE, and BY subkeywords
        • Example 2D: with filtering data in a data set
        • Example 2E: using the LOGICALVOLUME and REPLACE keywords
        • Example 2F: using the REPLACE and RENAME keywords
        • Example 2G: using the REPLACE and RENAMEUNCONDITIONAL keywords
        • Example 2H: restore all data sets
        • Example 2I: restore data sets
      • Examples of logical data set restore operations
        • Example 1: logical data set RESTORE—output volumes not specified
        • Example 2: logical restore of an unmovable data set
        • Example 3: logical data set dump, followed by a restore to an unlike device
        • Example 4: dump and restore for storage management subsystem (SMS) conversion
        • Example 5: using the RENAME keyword to restore a VSAM data set
        • Example 6: using the RECATALOG keyword
  • Syntax—auxiliary commands
    • Writing to the operator for DFSMSdss
      • WTO command
      • WTOR command for DFSMSdss
    • Scheduling tasks
      • SERIAL command for DFSMSdss
      • PARALLEL command for DFSMSdss
    • Controlling task processing
      • SET command—setting condition codes and patch bytes
        • SET command for DFSMSdss
          • Examples of the SET command
      • IF-THEN-ELSE command sequence for DFSMSdss—using condition codes
        • IF-THEN-ELSE command sequence
        • Creating a null command
        • Continuation rules for IF-THEN-ELSE command sequencing
        • Nesting IF commands
        • Examples of controlling task processing for the IF-THEN-ELSE command
          • Example 1
          • Example 2
        • Common continuation errors
          • Error example 1
          • Error example 2
          • Error example 3
      • EOJ command—ending your DFSMSdss step
  • DFSMSdss stand-alone services
    • Preparing to run the stand-alone services program
      • Running stand-alone services in 370 mode
      • Running stand-alone services in XA or ESA mode
      • Running stand-alone services with a predefined console
      • Using a tape library
        • IPLing and restoring from a tape library
        • Identifying procedures to mount and demount tapes using the IBM Tape Library Stand-Alone Device setup features
      • Using an automatic cartridge loader
      • Controlling command sequence processing
    • IPLing and running the Stand-Alone Services Program
      • IPLing Stand-Alone Services
        • IPL example
        • Interpreting wait-state codes
      • RESTORE—restoring a formatted dump tape
        • RESTORE command syntax
        • Required parameters
        • Optional keywords
        • RESTORE command examples
      • TAPECNTL—rewinding and unloading a tape
        • TAPECNTL command syntax
        • Required keywords
        • TAPECNTL command examples
    • Building the IPL-able core image
      • BUILDSA function
      • Understanding BUILDSA command authorization levels
        • Using BUILDSA without special authorization
        • Using BUILDSA with DASDVOL-access authorization
        • Using BUILDSA with the ADMINISTRATOR keyword
  • Data security and authorization checking
    • Effects of SPECIAL, OPERATIONS, and DASDVOL
      • SPECIAL
      • OPERATIONS
      • DASDVOL
    • General data security information
      • Protecting resources and data sets
      • Protecting the usage of DFSMSdss
      • Password protection
      • Protected user and group data sets
        • User data set
        • Group data set
      • Generic and discrete profile considerations
        • Generic profiles
        • Discrete profiles
        • Discrete and generic profile checking
        • Global access checking table
        • Automatic data set protection (ADSP) attribute
      • Security-level, category, and label checking
      • Protect-all and always-call
      • Standard naming conventions
      • DFSMSdss temporary data set names
      • Discretely protected multivolume data set
      • Erase-on-scratch
      • SMS-managed data set protection
      • Logging
    • DFSMSdss storage administrator
      • ADMINISTRATOR keyword
      • FACILITY class profiles for the ADMINISTRATOR keyword
    • DFSMSdss volume, data set and catalog access authority
      • Volume access and DASDVOL
        • DASDVOL access authority
        • DASDVOL limitations
      • Data set access authorization levels
      • Protected catalogs
        • Catalog access authority
      • Non-SMS versus SMS authorization
      • System operator authorization, special data set types
    • Access authorization for DFSMSdss commands
      • CGCREATED
      • COMPRESS
      • CONSOLIDATE
      • CONVERTV
      • COPY
        • COPY and deleting data sets
        • Copy and data set profile considerations
          • Copy and data set profiles
          • COPY and the MENTITY keyword
          • COPY and define discrete profile summary
          • Protection states after a copy or move
        • Other COPY command considerations
      • COPYDUMP
      • DEFRAG
      • DUMP
        • Dumping and deleting data sets
      • PRINT
      • RELEASE
      • RESTORE
        • Restore and access authorization
        • Restore and data set profile considerations
          • Restore and the MENTITY keyword
          • Restore and physical data sets
          • Restore and define discrete profile summary
          • Protection states after a restore
        • RESTORE command and the IMPORT keyword
  • Data integrity—serialization
    • Volume serialization
      • Avoiding lockout
      • The WAIT option
    • Data set serialization
      • Enqueuing—ENQ
      • Dumping HFS data sets
        • Logical dump
        • Physical dump
      • zFS data sets
        • Logical dump
        • Physical dump
        • Physical data set copy
      • Dynamic allocation (DYNALLOC)
      • Enqueuing versus dynamic allocation of data sets
      • Read/Write serialization scheme
      • WAIT option
      • An example of RESERVE-ENQUEUE processing
    • Backup-while-open data sets (CICS and DFSMStvs)
      • Backup-while-open status definition
      • Backup-while-open processing
      • Backup-while-open and concurrent copy
      • TOLERATE (ENQFAILURE) and SHARE considerations
      • CICS recovery data
    • Backup-while-open data sets (IMS)
  • Application programming interface
    • Calling block structure
    • User interactions
      • Service considerations
      • Cross-memory Application Interface overview
      • Using the cross memory application interface to control DFSMSdss
    • System programming information
      • Application interface blocks
      • Exit identification block
      • Application programming interface restrictions
      • Cross-memory application interface restrictions
    • User interaction module exit option descriptions
      • Function startup (Eioption 00)
      • Reading SYSIN record (Eioption 01)
      • Printing SYSPRINT record (Eioption 02)
      • Reading physical tape record (Eioption 03)
      • Reading logical tape record (Eioption 04)
      • Writing logical tape record (Eioption 05)
      • Writing physical tape record (Eioption 06)
      • Reading disk track (Eioption 07)
      • Writing disk track (Eioption 08)
      • Reading utility SYSPRINT (Eioption 09)
      • Writing SYSPRINT record (Eioption 10)
      • Writing WTO message (Eioption 11)
      • Writing WTOR message (Eioption 12)
      • Presenting ADRUFO record (Eioption 13)
      • Function ending (Eioption 14)
      • Presenting WTOR response (Eioption 15)
      • OPEN/EOV tape volume security and verification exit (Eioption 16)
      • OPEN/EOV nonspecific tape volume mount (Eioption 17)
      • Insert logical VSAM record during restore (Eioption 18)
      • Output tape I/O error (Eioption 19)
      • Volume notification (Eioption 20)
      • Data set verification (Eioption 21)
      • Bypass verification exit (Eioption 22)
      • Data set processed notification exit (Eioption 23)
      • Concurrent copy initialization complete (Eioption 24)
      • Backspace physical tape record (Eioption 25)
      • Dump volume output notification (Eioption 26)
      • Physical data set processed notification exit (Eioption 27)
      • Target data set allocation notification exit (Eioption 28)
      • Physical data set volume allocation notification exit (Eioption 30)
    • Avoiding lockout
    • Application interface summary
    • ADREID0 data area
      • Constants for ADREID0
      • Cross reference for ADREID0
    • Example: invoking DFSMSdss by using an application program
      • How to determine DFSMSdss version, release, and modification level
  • Examples of the application program with the user interaction module (UIM)
  • Data set attributes
• Coexistence Considerations
  • Restoring backups using DFSMSdss