• Abstract for DFSMShsm Storage Administration
    • Summary of changes
      • Summary of changes
      • Summary of changes
      • z/OS Version 2 Release 1 summary of changes
  • DFSMShsm Storage Administration Guide
    • Welcome to DFSMShsm
      • Purpose of space management
      • Purpose of availability management
      • What you are expected to do
        • Tasks for managing storage with DFSMShsm
      • Overview of DFSMShsm functions
        • DFSMShsm functions for SMS-managed volumes
          • Use of storage groups and management classes
          • Dump and restore functions
          • Backup and recovery functions
          • Aggregate backup and recovery functions
          • Extended address volume (EAV) considerations
          • Fast replication function
          • Space management function
          • DFSMS sysplex name support for DFSMShsm automatic functions
        • DFSMShsm functions for non-SMS-managed volumes
          • Dump and restore functions
          • Backup and recovery functions
          • How the system selects non-SMS extended address volume (EAV)
          • EAV considerations for recovery functions
          • Space management function
      • Devices supported by DFSMShsm
      • How to use the example system
        • Multiple z/OS images in the example system
        • DASD storage in the example system
        • Tape devices in the example system
        • Other assumptions in the example system
    • Space management of SMS-managed storage
      • Space management functions
        • Automatic primary space management
        • Automatic secondary space management
        • Event-driven migration
          • Using interval migration
          • Using on-demand migration
          • Comparison of interval migration and tape mount management
        • Automatic recall
        • Automatic dynamic volume expansion space management
        • Command space management
      • Tasks for automatic space management
        • Specifying the storage to be managed and the space requirements
          • Specifying the DFSMShsm hosts that process each storage group
        • Specifying how groups of data sets are managed
          • Specifying expiration attributes
          • Specifying partial release
          • Specifying migration attributes
          • Specifying class transition attributes
          • Specifying GDG management attributes
          • Using the default management class
          • Management class examples
            • Standard management class attributes
            • GDS management class attributes
            • Large management class attributes
            • No-migration management class attributes
            • Transition data management class attributes
            • Transition DB2 data management class attributes
        • Specifying when automatic primary space management can process
          • Specifying when automatic primary space management starts
        • Specifying when automatic secondary space management can process
          • Specifying when automatic secondary space management starts
        • Specifying migration of data sets to overflow volumes
        • Specifying how to migrate data sets to migration level 2
          • Using the SETSYS TAPEMIGRATION parameter
          • Specifying when to migrate from ML1 to ML2
        • Specifying how to do extent reduction
        • Specifying how to scratch expired data sets
        • Specifying the maximum automatic volume space management tasks and subtasks
        • Specifying the maximum automatic secondary space management tasks
        • Specifying the maximum interval migration or on-demand migration tasks
        • Specifying an on-demand migration number of concurrently queued volumes notification limit
        • Specifying recall tasks
        • Specifying small data set packing
        • Specifying the first qualifier for names of migrated data sets
        • Specifying if class transitions should be performed during event-driven migration
        • Configuring migration cleanup
        • Identifying migration level 2 volumes to DFSMShsm
        • Specifying duplexing for migration level 2 tapes
      • Integrity age for space management
      • Automatic space management operation examples
        • Automatic space management
        • Starting automatic secondary space management
          • Migration cleanup
          • Level 1 to level 2 migration
          • Migration from SDSP data sets
          • Migration to a tape migration level 2 volume
          • Migration to a DASD level 2 volume
          • Output media error handling
          • Installation exits called during level 1 to level 2 migration
          • Example of level 1 to level 2 migration
        • Starting automatic primary space management
        • Automatic primary space management
          • Specifying a storage group priority for space management functions
          • Overview of two-pass automatic primary space management
          • Pass 1 of automatic primary space management
          • Unmatched data sets
          • Deleting temporary data sets
          • Deleting expired data sets
          • Determining eligible data sets for class transitions and migration
          • Determining eligible data sets for backup
          • Determining eligible data sets for extent reduction
          • Releasing unused space
          • Performing fast subsequent migration
          • Performing class transition with management class changes only
          • Pass 1 processing example
          • Pass 2 of automatic primary space management
          • Transition data sets that are candidates for a class transition
          • Migrate candidates for both migration and extent reduction
          • Migrate candidates for extent reduction
          • Place candidate data sets in priority order for migration
          • Migrate data sets
          • Output media error handling
          • Names of migrated data sets
          • Compaction or zEDC compression during migration
          • Space management of VSAM data sets
          • Size eligibility for data sets to migrate to an SDSP
          • SDSP selection
          • Out-of-space condition during migration
          • Catalog considerations for migration
          • Maintenance and use of the data set date-last-referenced field for space management
          • Writing to a cartridge-type, single-file-format tape during migration
          • End of level 0 volume processing
          • Pass 2 processing example
        • Event-driven migration example scenario
        • Class transitions for DB2 objects example scenario
        • Automatic recall
          • Automatic recall with DFSMSdss
          • Recalling extent-reduced data sets
          • Automatic recall during data set allocation
          • Automatic recall for command deletion of VSAM AIX clusters
          • Automatic recall for data set renaming
          • Automatic recall during catalog updates
          • Additional recall considerations
          • Reblocking during recall
          • Marking data sets eligible for fast subsequent migration during recall
        • Additional space management during migration and recall when DFSMShsm is the data mover
      • Command space management tasks
        • Deleting migrated data sets
          • Using the DELETE command
          • Deleting data sets that have not expired
        • Migrating an individual data set
        • Migrating an SMS-managed volume
        • Recalling SMS-managed data sets
        • Recalling direct access data sets
        • Reconnecting data sets using fast subsequent migration
    • Space management of non-SMS-managed storage
      • Differences in what the example system shows
      • Tasks for space management of non-SMS-managed storage
        • Specifying the age for deleting list and utility data sets
        • Specifying the minimum age for migrating data sets
        • Specifying when data sets become eligible for level 1 to level 2 migration
        • Specifying recall characteristics for the type of volume
          • JES3 considerations
        • Defining primary volumes to DFSMShsm
        • Attributes of primary volumes
          • Recall attributes
        • Defining pools of volumes
        • Pools in systems running under JES2
        • Pools in systems running under JES3
          • Specifying pools in systems running under JES3
          • Example of JES3 pooling
      • Automatic space management processing for non-SMS-managed storage
        • Automatic secondary space management
        • Automatic primary space management
          • Pass 1
            • Deleting list and utility data sets
            • Deleting expired data sets
            • Determining eligible data sets for migration
            • Determining eligible data sets for backup
            • Determining eligible data sets for extent reduction
            • Pass 1 processing example
          • Pass 2
            • Sorting the candidate data sets into priority order
            • Performing space management on the volume
              • Data set deletion
              • Data set retirement
              • Migration
              • With thresholds of occupancy
              • Without thresholds of occupancy
          • Space management of VSAM data sets
          • JES3 considerations
          • Performing extent reduction on the volume
          • Installation exits during automatic primary space management
        • Automatic interval migration
        • Recall
          • Recall volume selection
          • Calling the recall exit
          • Allocating recalled data sets to volumes
          • Automatic recall during non-VSAM data set opening
          • Automatic recall during VSAM data set opening
          • Automatic recall for data set command scratching
          • JES3 considerations
          • Recall example
      • Command space management
        • Command volume space management
        • Command volume space management (primary)
        • Controlling migration of data sets and volumes
        • Recalling a data set to a specific volume
        • Recalling an SMS-managed data set to a non-SMS-managed volume
        • Recalling an SMS-managed BDAM data set to a non-SMS-managed volume
        • Recalling an SMS-managed sequential extended-format data set to a non-SMS-managed volume
    • Other space management considerations
      • Space management of extended address volumes (EAVs)
        • Track management for SMS-managed volumes
        • Track management for non-SMS-managed volumes
        • Controlling allocations to extended address volumes (EAVs)
        • Recommendations for using extended address volumes (EAVs)
      • Common recall queue
        • Connecting to a common recall queue list structure
        • Populating the common recall queue
        • Selecting requests from the common recall queue
        • Processing recall requests on the common recall queue
        • Disconnecting from the common recall queue
        • Processing of common recall queue requests during shutdown
        • Deleting the common recall queue structure
        • Processing failures in a common recall queue environment
          • Coupling facility or coupling facility structure failure
          • Coupling facility link failure
          • z/OS image failure
          • DFSMShsm primary address space failure
          • Full list structure failure
      • Processing priority of recalls and deletions
      • Specifying the order in which data sets from a single tape are processed
      • Migration volume contention priorities
        • Tape migration level 2 volume contention
          • Single DFSMShsm-host environment
            • Migration or recycle output needs volume
            • Recall needs volume
            • ABACKUP needs input volume
            • Recycle input volume in use
          • Multiple DFSMShsm-host environment
            • Recall needs tape in use by recall on a different host
            • Recycle needs tape in use by recycle on a different host
          • Common recall queue environment
        • Specifying the desired number of ML2 partial tapes
        • SDSP data set contention
        • Multitasking considerations for SDSP data sets
      • Preventing the processing of data sets during space management
      • Deferred generation data sets
      • Security considerations for automatic space management
        • Space management of data sets with discrete data set profiles
          • Migrating RACF-protected data sets
          • Deleting RACF-indicated migrated data sets
          • Recalling RACF-indicated data sets
        • Password protection of data sets on DASD
      • Access method services considerations
      • GUARANTEED SPACE attribute considerations
        • Results of recalling GUARANTEED SPACE VSAM data sets
        • Possible problems
          • Changes in the storage group
          • Changes in the storage-class-to-data set mapping
          • Conversions of data sets to GUARANTEED SPACE
      • DFSMShsm retrieval of management classes and storage groups
      • Deletion of dynamic I/O device considerations
      • Space management considerations for sequential extended-format data sets
        • Volume space management processing
        • Automatic primary space management processing
        • Recall processing
    • Space management procedures
      • Interrupting and restarting primary space management, secondary space management, or event-driven migration
        • When primary space management, secondary space management, or event-driven migration needs to be restarted
        • Automatic restart of primary space management or secondary space management
        • Automatic restart of event-driven migration
        • Manual restart of primary space management or secondary space management
      • Defining a new primary space management or secondary space management processing window
      • Allowing another host to take over secondary space management functions
    • Availability management of SMS-managed storage
      • What the example system shows
        • Automatic incremental backup
        • Automatic full-volume dump
        • Command availability management
      • Tasks for automatic availability management
      • Dump tasks
        • Specifying which volumes to dump and the dump classes to use
        • Specifying when automatic dump processing starts
        • Specifying the DFSMSdss DASD I/O buffering technique to use for dump
        • Specifying concurrent copy for volume dumps
        • Specifying the maximum number of dump tasks
        • Specifying the day on which a dump occurs
        • Specifying the characteristics of dump classes
          • Controlling automatic reuse of dump tapes
          • Controlling restoring of individual data sets from dump tapes
          • Specifying the day to dump data to this dump class
          • Specifying how often to dump data to the dump classes
          • Specifying what to do with the dump volumes
          • Specifying whether to reset the data-set-changed indicator
          • Specifying when the data on dump volumes becomes invalid
          • Specifying a tape expiration date
          • Specifying the kind of tape units to use for dump volumes
          • Specifying the maximum number of dump copies to stack on a dump volume
          • Specifying the number of VTOC copies to keep
          • Specifying whether to compress and encrypt the dump data
          • Specifying whether the dump class is required or optional
        • Defining dump volumes to DFSMShsm
      • Backup tasks
        • Specifying which storage group has automatic backup performed
        • Specifying how to manage groups of data sets
        • Specifying a storage group priority for autobackup processing
        • Specifying whether to use concurrent copy
        • Specifying frequency of backup
        • Guaranteeing frequency of backup
        • Specifying the maximum number of backup versions to keep
          • Relationship of frequency and maximum number of backup versions
        • Specifying how long to keep backup versions
          • Relationship of the NUMBER OF BACKUP VERSIONS and RETAIN DAYS attributes
          • Specifying the number of days to retain a backup copy of a data set
          • Creating retained backup copies
        • Specifying who can back up data sets by command
        • Specifying whether to perform automatic backup
        • Example management classes
          • Standard management class
          • GDS management class
          • Large management class
          • No migration management class
        • Specifying the start time for automatic backup
        • Specifying whether to perform volume backup and the kind of device to use
        • Specifying the first qualifier for names of backup versions
        • Specifying the maximum number of volume backup tasks in each host
        • Specifying the data set backup by command environment
        • Specifying whether to back up RACF discrete data set profiles
        • Specifying whether DFSMShsm performs spill processing
        • Specifying whether to back up only changed data sets
        • Specifying how DFSMShsm should respond to a data set in use
        • Specifying the days on which automatic backup occurs
        • Defining backup volumes to DFSMShsm
        • Specifying duplexing for backup tapes
      • Automatic availability management operation
      • Dump processing
        • Deleting expired dump copies
        • Defining what to do with tapes marked unavailable during DUMP processing
        • Dumping DFSMShsm-managed volumes
          • Volume serialization
          • Names of dump copy data sets
          • Write dump VTOC copy data set
          • Selecting tape dump volumes
        • Deleting and uncataloging excess dump VTOC copy data sets
      • Automatic backup processing
        • Phase 1: Backing up the control data sets
        • Phase 2: Moving backup versions
        • Phase 3: Backing up migrated data sets
        • Phase 4: Backing up SMS-managed volumes from storage groups with the automatic backup attribute
          • Processing unmatched data sets
          • Deleting temporary data sets
          • Create a VTOC copy data set entry for the volume
          • Backing up eligible data sets
          • Resetting the data-set-changed indicator and last backup date
          • Backing up VSAM data sets
          • Generating names of backup versions of data sets
          • Backing up RACF discrete profiles for cataloged data sets
          • Profile backup for migrated data sets
          • Deleting backup profiles
          • Parameters used in creating backup profiles
        • Selecting daily backup volumes
          • Selecting DASD daily backup volumes
          • Selecting initial DASD daily backup volumes
            • Daily limit not reached
            • Daily limit reached or exceeded
          • Selecting subsequent DASD daily backup volumes
          • Selecting tape daily backup volumes
          • Selecting initial tape daily backup volumes
          • Selecting subsequent tape daily backup volumes
          • Selecting DASD and tape daily backup volumes
          • Selecting initial daily backup volumes (DASD or tape)
            • Daily limit reached or exceeded
            • Daily limit not reached
          • Selecting subsequent daily backup volumes (DASD or tape)
      • Backup volume spill process
      • Selecting spill backup volumes
        • Initial spill backup volume selection (DASD and tape)
        • Subsequent spill backup volume selection (DASD and tape)
      • Cleanup processing
        • Backup volume cleanup process
      • Releasing a backup volume
      • Automatic backup example
      • Command availability management
        • Dumping a volume
        • Dumping the volumes in one or more storage groups
        • Backing up an individual data set
        • Using the data set backup by command capabilities
          • Specifying data set backup tasks
          • Controlling target devices that are used by data set backup
          • Assigning DASDSELECTIONSIZE values
          • Switching data set backup tapes
          • Taking a backup tape away from a data set backup task
          • Targeting data set backups to required device types
          • Using concurrent copy for data set backup
            • Authorizing the use of concurrent copy
          • Inline backup of an individual data set
        • Backing up all data sets on one or more volumes
        • Backing up all data sets in one or more storage groups
        • Backing up all eligible changed data sets on one or more volumes
        • Backing up all eligible changed data sets in one or more storage groups
        • Deleting expired backup versions from the backup volumes
          • EXPIREBV processing
          • Issue a starting message
          • Set up the output destination
          • Retrieve a list of management class definitions
          • Determine the starting point for the BCDS scan
          • Determine the ending point for the BCDS scan
          • Process each data set record in the BCDS
          • End the scan of the BCDS
          • Issue an ending message
        • Deleting backup versions of specific data sets
          • Transferring the backup profile from one backup version to another
            • Profile creation
          • Authorization checking during HBDELETE processing
        • Command recovery and restore
        • Data set recovery and restore
          • Determining whether the data set exists
          • Selecting the target volume for incremental backup version recovery
          • Selecting the target volume for physical dump copy restore
          • Determining the storage class, management class, and data class
          • Determine whether to use backup or dump versions for data set recovery
          • Searching for eligible dump copies
          • Recovering the data sets to SMS-managed volumes
            • Recovering a non-VSAM data set from a DFSMShsm backup version
            • Recovering a VSAM data set from a DFSMShsm backup version
            • Restoring a non-VSAM data set from a dump copy
            • Restoring a VSAM data set from a dump copy
          • Recovery of direct access data sets
          • Recovery of extended format data sets
          • Last-backup date after recovery
          • Reblocking during recovery
          • Resetting the date-of-scratch field
          • Tape mount optimization during recovery
          • Processing priority of data set recoveries
        • Restoring a data set from a DFSMShsm dump copy
        • Restoring VSAM data sets
      • Managing volume backups with fast replication
        • Combining fast replication options in DFSMShsm
        • Combining copy services operations in DFSMS
        • Using the copy pool construct for fast replication setup
        • Using the copy pool backup storage group type for fast replication setup
        • Using the extend and overflow storage group types with fast replication
        • Preparing for the fast replication backup
        • Creating a fast replication backup
          • Considerations for the FRBACKUP COPYPOOL command
          • Serialization for the fast replication function
          • Saving catalog information at the time of backup
          • Dumping a fast replication backup to tape
          • Creating a copy pool incremental version
          • Using Metro Mirror primary volume during fast replication backup
          • Creating consistent copies using FlashCopy consistency groups
          • Parallelism for fast replication backup copies to DASD
          • Parallelism for fast replication backup copies to dump tape
        • Recovering a fast replication backup
          • Recovering a data set from a fast replication backup
          • Considerations for the FRRECOV command
          • Selecting a data set level recovery method
          • Making dump classes available for data set level recovery and volume recovery
          • Recovering a copy pool using fast reverse restore
          • Recovering from a copy pool incremental version
          • Using Metro Mirror primary volume during fast replication recovery
          • Parallelism for fast replication
            • Parallelism for fast replication data set recovery
            • Parallelism for fast replication volume recovery from tape
        • Withdrawing DFSMShsm background copies
        • Holding and releasing the fast replication functions
        • Deleting unneeded DFSMShsm fast replication backup versions
        • Obtaining DFSMShsm fast replication backup information
          • Using the QUERY command to obtain fast replication information
          • Using the LIST command to obtain fast replication information
          • Using the REPORT command to obtain fast replication information
          • Using the ARCXTRCT macro to obtain fast replication information
        • Preventing DFSMShsm functions from processing target volumes
        • Other copy pool considerations
          • Migration of data sets within a copy pool
          • Data set recovery errors
          • Maintaining catalogs with fast replication backup
          • Increasing the number of volumes in a copy pool
          • Decreasing the number of volumes in a copy pool
          • Decreasing the number of volumes in a copy pool backup storage group
          • Defining a storage group to multiple copy pools
          • Using multivolume data sets in a fast replication environment
          • Using the APPLYINCREMENTAL keyword
          • Using an alternate copy pool backup storage group
            • Defining an override copy pool backup storage group
      • Volume recovery and restore
        • Specifying the maximum number of data set recovery tasks in each host
        • Specifying the maximum number of volume recovery from dump tasks
        • Full-volume restore with update
        • Full-volume restore from a dump copy
        • Volume recovery from incremental backup versions
        • Processing priority of volume recoveries
    • Availability management of non-SMS-managed storage
      • Tasks for availability management of non-SMS-managed storage
        • Specifying how frequently data sets are backed up
        • Specifying how many versions to keep for each backed up data set
        • Specifying which volumes are backed up automatically
        • Specifying which volumes are dumped automatically
      • Automatic availability management of non-SMS-managed volumes
        • Backing up cataloged and uncataloged data sets with the same name
      • Command availability management for non-SMS-managed storage
        • Dumping a volume
        • Changing the backup conditions for a data set
          • Security checking with discrete profiles
        • Backing up an individual data set
        • Inline backup of an individual data set
        • Backing up all primary volumes
        • Backing up all changed data sets on volumes
        • Deleting expired backup versions of non-SMS-managed data sets
          • Processing for expired backup versions of non-SMS-managed data sets
        • Deleting backup versions of specific data sets
        • Recovering specific data sets
        • Recovery of VSAM data sets
        • Data set restore from a DFSMShsm dump copy
        • Data set recovery of retired data sets
        • Combining full-volume restore with volume recovery
        • Volume recovery from incremental backup versions
    • Aggregate backup and recovery support (ABARS)
      • How aggregate backup works
        • Specifying data sets to be backed up
          • Aggregate group
          • Management class
          • Selection data set
          • Skipped data sets
          • Instruction data set
      • Backing up applications
        • ABACKUP command
        • Example of data sets associated with an aggregate group
      • Filtering for generation data sets
      • Preparing for aggregate backup
        • SMS requirements during aggregate backup
        • Creating selection data sets
          • Selection data set syntax
          • Processing user tape data sets in the include list
          • Selection data set keywords
            • INCLUDE
            • EXCLUDE
            • ACCOMPANY
            • ACCOMPANYEXCLUDE
            • ALLOCATE
            • ALLOCATEEXCLUDE
          • Examples of selection data sets
        • Creating an instruction data set
          • Example instruction data set
        • Defining an aggregate group
          • Example aggregate group
        • Management class considerations
        • DFSMShsm coexistence considerations for aggregate groups and management classes
        • Protecting aggregate backup tape volumes
        • Checking authorization during aggregate backup
        • Authorizing comprehensive ABACKUP command authority
        • Authorizing restricted ABACKUP command authority
        • Using the aggregate backup installation exits
        • Ensuring that the necessary volumes are online
        • Defining SETSYS parameters for aggregate backup
          • Example SETSYS commands for aggregate backup
        • Determining the unit type for the control and data files
        • Minimizing data set contention
        • Data sets that DFSMShsm dynamically allocates during aggregate backup processing
      • Performing aggregate backup
        • ABACKUP command
          • Examples of ABACKUP commands
        • Issuing the ABACKUP command with the VERIFY parameter
        • Issuing the ABACKUP command with the EXECUTE parameter
      • Aggregate backup output
        • Data files
        • Control file
        • Instruction and activity log file
        • Activity log
        • ABACKUP CPU time and accounting codes
        • DFSMShsm coexistence considerations for new ABACKUP output data sets
        • Expiring ABR records in the BCDS
        • ABACKUP considerations
        • ABARS user catalog and catalog alias ABACKUP support
      • Aggregate backup assist
        • How aggregate backup assist works
        • What aggregate backup assist produces
        • Special considerations for ABARS
        • Authorization and security requirements
        • Input requirements
        • SMF data
        • Aggregate job names
        • Storage requirements
        • DD statements used by ABA
        • Sample JCL
        • Sample output
      • Aggregate stacking procedure
        • Backing up data with ABARS aggregate backup function
        • Stacking multiple aggregates on one tape
        • Aggregate recovery from the stacked tape
        • Preventing aggregate roll off and tape expiration
        • Deleting specific versions of aggregates from a stacked tape
        • RACF protection of tapes used for stacking
        • RACF protection of tapes after EXPIREBV processing of versions
        • End of volume during the stacking process
        • Cleanup after stacking errors
        • Copying ABARs aggregates to another device type
      • How aggregate recovery works
        • Recovered aggregate data sets
        • Example aggregate recovery site
      • Preparing for aggregate recovery
        • Authorization checking during aggregate recovery
        • Authorizing comprehensive ARECOVER command authority
        • Authorizing restricted ARECOVER command authority
        • Considering storage management subsystem requirements
        • Determining aggregate recovery site constraints
        • Retrieving the instruction data set
          • Example instruction data set
        • Creating an ABR record in the BCDS
          • Defining ABARS tapes to RACF
        • Issuing the DEFINE ARPOOL command
          • Example DEFINE ARPOOL command for aggregate eecovery
        • Defining SETSYS parameters for aggregate recovery
          • Example SETSYS commands for aggregate recovery
        • Defining the model entity
        • Using the aggregate recovery installation exits
      • Processing generation data sets
        • GDSs from level 0 DASD in the include list
        • Migrated GDSs in the include list
        • GDSs in the ALLOCATE list
        • GDS processing order
      • Processing migrated data sets in the INCLUDE list
      • Processing VSAM data sets in the ALLOCATE list
      • Catalog considerations during ARECOVER processing
      • Performing aggregate recovery
        • ARECOVER command
          • Examples of ARECOVER Commands
        • Issuing the ARECOVER command with the PREPARE parameter
        • Issuing the ARECOVER command with the VERIFY parameter
        • Issuing the ARECOVER command with the EXECUTE parameter
          • Restart data set
        • Issuing the ARECOVER command with the ONLYDATASET parameter
          • Recovering an individual data set from an aggregate backup
          • Recovering a group of data sets from an aggregate backup
        • Recovering the ABARS instruction data set
          • ABACKUP considerations
          • ARECOVER considerations
        • Backing up and recovering the ABARS activity log
          • The SETSYS ABARSACTLOGTYPE parameter
        • Conflict avoidance and conflict resolution processing options
        • ARECOVER data set name conflict resolution
          • DATASETCONFLICT parameter
          • Conflict resolution data set
          • ARCCREXT installation exit
          • Order of processing for conflict resolution
          • RACF facility class authorization checking
        • Holding and releasing ABARS functions
          • Holding ABARS functions
          • Releasing held ABARS functions
          • Querying held ABARS functions
        • Displaying SMS class definitions during ABACKUP and ARECOVER
        • ABARS user catalog and catalog alias ARECOVER support
        • Data sets that are dynamically allocated during aggregate recovery processing
      • Aggregate recovery output
        • Activity log
          • Recovered data sets at the example aggregate recovery site
        • ARECOVER CPU time and accounting codes
        • Using ISMF panels to perform aggregate backup
          • Using the ISMF LIST option to perform aggregate backup
          • Using the ISMF ABACKUP option to perform aggregate backup
        • Using ISMF panels to perform aggregate recovery
          • Panel DFQDCAG5
          • Panel DFQDCAG6
          • Panel DFQDCAG7
          • Panel DFQDCAG8
          • Panel DFQDCAG9
          • Panel DFQDCAGA
          • Panel DFQDCAGC
          • Panel DFQDCAGB
          • Using ISMF to recover individual data sets from an aggregate backup
      • Using the NetView file transfer program to transmit aggregate Backup files
        • Using NetView file transfer program panels
          • Invoking NetView FTP panels
          • Creating a request
          • Using a batch job to transmit aggregate backup files
        • Issuing the ARECOVER command when using NetView FTP
      • ABARS considerations for sequential data striping
        • Aggregate backup processing
        • Aggregate recovery processing
      • Aggregate roll-off processing
      • Defining GDGs at the recovery site
      • Ensuring backup copies of ARECOVERed SMS-managed data sets exist at the recovery site
      • Directing ABARS files to DASD
    • Making disaster backup copies of DFSMShsm-owned tape volumes
      • Planning disaster recovery
      • Disaster backup facilities
        • Making copies of DFSMShsm-owned tape volumes
          • Duplex tape option
          • TAPECOPY command
          • Copying individual volumes
        • Converting tape volumes marked partially full to marked full
        • Replacing an original with an alternate tape volume
        • Creating duplex tapes off site
        • Sending alternate tapes off site
        • Managing alternate volumes
      • Disaster alternate volumes
        • Considerations when using disaster alternate volumes
    • Other availability management considerations
      • Additional considerations for backup
        • Backup volume contention resolution
        • Implications of redefining the backup cycle
        • Inline backup
          • Invoking inline backup
        • Preventing backup processing when using the HOLD BACKUP command
        • GUARANTEED SPACE attribute
          • Results of recovering GUARANTEED SPACE data sets
          • Problems that can occur
            • Changes in the storage group
            • Changes in the storage-class-to-data-set mapping
            • Conversions of data sets to GUARANTEED SPACE
        • Data set backup with concurrent copy
          • Authorizing concurrent copy with RACF
        • Data set backup using NEWNAME
      • Additional considerations for dump
        • Dumping DFSMShsm-owned volumes
        • Dumping control data sets
        • Dumping the journal data set
        • Preventing dump processing
        • Dumping all allocated space
        • Invoking full-volume dump compression
        • Bypassing enqueue processing between full-volume dump and DFP functions
      • Volume recovery and restore considerations
        • Restoring data sets or volumes directly with DFSMSdss
        • Requesting a list of dump volumes for a dump copy
        • Determining the dump copy data set name
        • Invoking the DFSMSdss RESTORE function
        • Preventing recovery and restore processing when using the HOLD RECOVER command
        • Using the date-last-referenced field for recovery
      • Deferred generation data sets
      • Security considerations for availability management
        • Authorization checking during recovery
        • Recovering or restoring RACF-indicated data sets
          • Recovering RACF discrete profiles
          • Authorization checking during profile recovery
          • Characteristics of the recovered profile
          • Effects of profile modeling on profile recovery
          • Accessing a data set when the profile cannot be recovered
        • Maintaining password protection for recovered data sets
      • DFSMShsm retrieval of management classes
      • Availability management considerations for extended SAM and extended and compressed VSAM data sets
      • Availability management considerations for sequential data striping
        • Backup processing
        • Recover and restore processing
    • Availability management procedures
      • Backup and recovery procedures
        • Interrupting and restarting backup processing
        • Defining a new automatic backup start window
          • Defining a new start window when automatic backup is running
          • Defining a new start window when automatic backup is not running
        • Backing up and recovering a catalog
          • Backing up and recovering RLS user catalogs
          • Restoring a catalog from a dump copy
      • Full-volume dump procedures
        • Interrupting and restarting automatic dump processing
        • Defining a new automatic dump start window
          • Defining a new start window when automatic dump is running
          • Defining a new start window when automatic dump is not running
    • Maintaining DFSMShsm control data sets
      • Tasks for maintaining the control data sets
      • Specifying how DFSMShsm backs up the control data sets
        • Allocating backup data sets
        • Choosing the data mover to be used
          • DFSMSdss as data mover
            • Concurrent copy management class support
          • DFSMShsm as data mover
        • Using non-intrusive journal backup
        • Specifying how many backup versions to keep
        • Specifying the names of the backup data sets
        • Specifying the device type for backup of the control data sets
          • Specifying DASD for backup
          • Specifying tape for backup
          • Protecting CDS backup tapes
      • Invoking the CDS backup exit (ARCCBEXT)
      • Backing up to multiple DASD data sets
      • Backing up to multiple tape data sets
      • Considerations in a multiple DFSMShsm host environment
      • Considerations when using multicluster control data sets
      • Nulling the journal
      • Changing the names of the backup data sets
      • Changing backup device from tape to DASD
      • Changing backup device from DASD to tape
      • Using the QUERY command to get CDS information
      • Backing up the control data sets manually
      • Possible failures during CDS and journal backup
      • Reasons for recovering the control data sets
        • I/O errors
      • Recovering control data sets using the enhanced CDS recovery function
        • Requirements for using the enhanced CDS recovery function
        • Implementing enhanced CDS recovery using JCL
          • ARCBJRNL and ARCIMPRT return codes
      • Recovering multicluster non-key range control data sets
      • Control data set recovery procedure using CDSVERSIONBACKUP with UPDATEC
        • Updating recovered control data sets using UPDATEC
      • VSAM considerations for the control data sets
      • Determining if control data sets are accurate
      • Repairing errors in the control data sets
      • Procedures for handling a journal EOV error
      • Recovering from a journal I/O error
      • Moving the journal
      • Steps to ensure that the control data sets are accurate
      • Control data set backup and recovery examples
        • Recovery examples using the enhanced CDS recovery function
          • Example 1: Recovering the MCDS from DASD
          • Example 2: Replacing a damaged journal
          • Example 3: Recovering the MCDS from tape when the latest MCDS backup version is unusable
      • Performance considerations in a multiple DFSMShsm host environment
        • MASH configuration considerations
    • Managing DFSMShsm media
      • Moving all data sets from one level 0 volume to other level 0 volumes
        • Processing SMS-managed data sets
        • Processing non-SMS-managed data sets
        • Examples of moving data sets between level 0 volumes
          • SMS-managed volume
          • Non-SMS-managed volume
      • Moving some data sets from migration level 1 volumes
        • Using the FREEVOL command for migration level 1 volumes
          • Processing for SMS-managed data sets
          • Processing for non-SMS-managed data sets
        • Using the MIGRATE command for migration level 1 volumes
          • Migrating data sets
            • Processing for SMS-managed data sets
            • Processing for non-SMS-managed data sets
        • Deleting non-SMS-managed data sets from migration volumes
      • Moving all the data sets from a migration level 1 volume
        • Processing for SMS-managed data sets
        • Processing for non-SMS-managed data sets
      • Moving data sets from a DASD migration level 2 volume to other migration level 2 volumes
      • Removing residual dump and backup VTOC copy data sets from migration level 1 volumes
      • Preventing further migration to a DASD migration volume
      • Moving data sets from DASD backup volumes
      • Removing volumes from DFSMShsm management or control
        • Removing dump copies and dump VTOC copy data sets from DFSMShsm
      • JES3 considerations
      • Consolidating valid data on tape volumes
        • Defining the parameters of the recycle process
        • Initiating recycle processing
        • PERCENTVALID calculation
        • Selecting tape volumes during recycling
        • Making cartridge-type, single-file-format tapes from reel-type or multiple-file-format tapes
      • Limiting data that is written to a cartridge-type device
      • Specifying capacity utilization
      • Considerations for using the 3592 Model J tape drive
      • Considerations for using the 3592 Model E05 tape drive
      • Considerations for using the 3592 Model E06 tape drive
      • Considerations for using the 3592 Model E07 tape drive
      • Limiting the number of ML2 and backup data sets that span tape volumes
      • How to handle inconsistencies between tape media contents and OCDS TTOC records
      • Recovering a damaged DFSMShsm single-file migration level 2 volume
      • Making migration level 2 key range volumes available
      • Recovering a migrated data set
      • Recovering a migration volume
        • Procedure 1
        • Procedure 2
      • Recovering backup versions from a damaged migration level 1 volume
      • Returning dump tapes to use
      • Managing SDSP data sets
        • Reorganizing SDSPs
        • SDSP backup and recovery
        • Removing SDSPs
          • Removing a migration level 1 volume that contains an SDSP
          • Removing an SDSP from a migration level 1 volume
      • Protecting DFSMShsm-owned tape volumes
      • Converting to a new tape technology
      • Requesting DFSMShsm service from your applications
    • Obtaining information
      • Obtaining information from the control data sets
        • Obtaining backup volume information
        • Obtaining data set information
        • Obtaining copy pool information
        • Obtaining dump class information
        • Obtaining dump volume information
        • Obtaining DFSMShsm host serialization information
        • Obtaining lists of backup and dump parameters and backup volume serial numbers
        • Obtaining information about migration and DFSMShsm-managed volumes
        • Obtaining DFSMShsm-managed volume information
        • Obtaining tape volume information
        • Obtaining user authorization information
        • Determining which tape dump volumes are available for output during dump processing
      • Obtaining information about the DFSMShsm address space
      • Determining which tape volumes are available for output
        • Determining which tape backup volumes are available for output
        • Determining which tape migration level 2 volumes are available for output
      • Obtaining statistical information about DFSMShsm operations
      • Running new reports with report generator
      • Using the problem determination aid to trace DFSMShsm processing
        • Specifying to DFSMShsm to use the PDA
      • Using the TRAP command to obtain information about conditions in the system when an error occurs
      • Using DEBUG to determine the results of DFSMShsm processing without moving data sets
    • DFSMShsm tape libraries
      • Automated tape library
      • Manual tape library
    • Using DFSMShsm with DFSMSrmm
      • Retaining DFSMShsm tape volumes by expiration date
      • Retaining DFSMShsm tape volumes by DFSMSrmm vital record processing
      • Tape security when using DFSMShsm and DFSMSrmm
      • Recommendations for using DFSMShsm with DFSMSrmm
    • Operating procedures for DFSMShsm
      • Partitioning DFSMShsm functions
      • Starting DFSMShsm
      • Stopping DFSMShsm
        • Shutdown processing on the common recall queue
      • Preventing DFSMShsm functions from running
      • Allowing previously prevented DFSMShsm functions to run
      • Canceling DFSMShsm requests
      • Altering the priority of DFSMShsm queued requests
      • Printing DFSMShsm log information
      • Restarting DFSMShsm after an abnormal end
      • Running automatic functions concurrently
    • RACF considerations
      • RACF basics
        • RACF data set profiles
          • Generic profile
          • Discrete data set profiles
        • RACF indication
        • Always-call support
          • RACF indicator with always-call
        • RACF protect-all environment
      • RACF environment for DFSMShsm
        • DFSMShsm and RACF concepts
          • RACF authority needed to perform DFSMShsm functions
          • RACF security bypassing for DFSMShsm commands
      • The RACF user ID for DFSMShsm
      • RACF started task table
      • Always-call support for migrated data sets and backup copies
      • Migration and recall from DASD
      • Backup and recovery from DASD
      • Aggregate backup and recovery data set security
      • Backing up RACF-indicated data sets
      • Authorizing the use of concurrent copy for data set backup commands
      • Small data set packing data set security
      • Uncataloging migrated data sets
      • Controlling command access with RACF FACILITY class
    • Health Checker for DFSMShsm
      • Check registration
    • Data recovery scenarios
      • Case 1: Damaged CDS, full journal
      • Case 2: Damaged journal, undamaged CDS
      • Case 3: Full journal, undamaged CDS
      • Case 4: Structurally damaged CDS, missing journal records
      • Case 5: Time sequence gaps in CDS records, journal records also missing
      • Case 6: Overwritten migration tape
      • Case 7: Overwritten backup tape
      • Case 8: Damaged ML1 volumes
      • Case 9: Reestablish access to previously deleted migrated data sets (no backup exists, ML2 only)
      • Case 10: Correcting errors within the common recall queue
      • Case 11: Recovering a deleted ML1 data set without a backup
    • Consolidated commands, storage group definitions, and management classes for the example system
      • ADDVOL command
      • DEFINE command
      • SETSYS command
      • Storage groups
      • Management classes
    • Preventive methods for avoiding data loss
      • Steps for preventing a full journal (damaged CDS)
      • Preventing a full journal (undamaged CDS)
      • Preventing structural damage to CDS and missing journal records
      • Preventing time sequence gaps in CDS records (journal records also missing)
      • Preventing overwritten migration tape or overwritten backup tape
      • Prepare for recovery of a head crash on an ML1 volume
      • Reestablishing access to previously deleted, migrated data sets (no backup exists, ML2 only)
    • Linux-z/OS DFSMShsm dump or restore how-to
      • How DFSMShsm supports linux
      • Using DFSMShsm with Linux requirements
        • Hardware environment
        • DASD background
        • Linux requirements
        • Linux disk utilities
          • dasdfmt
          • fdasd
          • z/OS requirements
        • Authorization requirements
      • Setting up your dump environment for Linux volumes
        • Performing only dumps
        • When do you want your dumps performed?
        • How long do you want to keep your dumps?
        • How many dumps are stacked on each dump tape?
        • How many tape drives do you have?
      • Recovering your data
        • Recovering a volume with DFSMShsm
        • Recovering a volume with DFSMSdss
        • Recovering a partition with DFSMShsm
        • Recovering a partition with DFSMSdss
      • Example dump environment
        • How to define your dump cycle
        • How to define your dump classes
        • How to ADDVOL your volumes
        • How to start automatic dumping
        • Recovering from a dump
          • Recovering with DFSMShsm
          • Recovering data from DFSMShsm dump with DFSMSdss
      • Submitting DFSMShsm commands using JCL and FTP
      • The DFSMShsm LIST command
      • Naming conventions
        • Data set and partition naming conventions
        • Volume serial number naming conventions
  • DFSMShsm Storage Administration Reference
    • DFSMShsm commands
      • User commands
      • Operator commands
      • Storage administrator commands
      • System programmer commands
      • Using RACF FACILITY class to control authorization of commands
      • Using DFSMShsm commands
        • Positional parameters
        • Keyword parameters
        • Abbreviating commands and parameters
        • Delimiters
        • Line continuations
        • Data set naming conventions
        • Comments
        • TSO attention key
        • How to read syntax diagrams
      • Considering the command sequence
      • Submitting DFSMShsm commands
      • Commands in a system without RACF: Method 1
      • Commands in a system without RACF: Method 2
    • ABACKUP command: Backing up aggregated data sets
      • Syntax of the ABACKUP command
      • Required parameters of the ABACKUP command
        • agname: Specifying the aggregate group name
        • EXECUTE and VERIFY: Specifying whether data movement processing or data verification occurs
      • Optional parameters of the ABACKUP command
        • FILTEROUTPUTDATASET: Specifying the output data set
        • LIST: Listing data sets not backed up due to the SKIP parameter
        • MOVE: Removing the data sets
        • OPTIMIZE: Overriding the SETSYS ABARSOPTIMIZE command
        • PROCESSONLY: Designating the categories to process
        • SKIP: Skipping data sets on volumes protected by PPRC or XRC
        • STACK and NOSTACK: Overriding the SETSYS ABARSTAPES setting
        • UNIT: Designating the output device
      • Examples of how to code the ABACKUP command
    • ADDVOL command: Adding or changing DFSMShsm volumes
      • Syntax of the ADDVOL command
      • Required parameters of the ADDVOL command
        • volser: Specifying the volume to be added or changed
        • BACKUP, DUMP, MIGRATION, and PRIMARY: Identifying the type of volume
        • UNIT: Specifying the type of device
      • Optional parameters of the ADDVOL command
        • AUTOBACKUP and NOAUTOBACKUP: Specifying whether the primary volume is eligible for automatic backup
        • AUTODUMP and NOAUTODUMP: Specifying whether a volume is eligible for automatic dumping to tape
        • AUTOMIGRATION and NOAUTOMIGRATION: Specifying whether the primary volume is eligible for automatic volume space management
        • AUTORECALL and NOAUTORECALL: Specifying whether the primary volume is eligible for automatic recall
        • BACKUPDEVICECATEGORY: Specifying where backup versions reside
        • DAILY and SPILL: Identifying the type of backup volume
        • DELETEBYAGE, DELETEIFBACKEDUP, and MIGRATE: Specifying the type of space management on a primary volume
        • DENSITY: Specifying the tape density
        • DRAIN and NODRAIN: Specifying whether a volume should be selected for migration output
        • DUMPCLASS: Restricting the specified volume to use a specific dump class
        • MIGRATIONLEVEL1 and MIGRATIONLEVEL2: Specifying the migration level
        • OVERFLOW and NOOVERFLOW: Specifying the usage of a level 1 volume for data set migration and backup versions
        • SMALLDATASETPACKING and NOSMALLDATASETPACKING: Specifying small data set packing on the level 1 volume
        • THRESHOLD: Specifying thresholds of occupancy
        • TRACKMANAGEDTHRESHOLD: Specifying the high and low threshold for the track-managed space of a non-SMS level 0 extended address volume
        • Selecting thresholds for volumes
      • Examples of how to code the ADDVOL command
    • ALTERDS command: Changing the back-ups for a non-SMS-managed data set
      • Syntax of the ALTERDS command
      • Required parameters of the ALTERDS command
        • dsname: Specifying the name of the data set being altered
      • Optional parameters of the ALTERDS command
        • FREQUENCY and SYSFREQUENCY: Specifying the frequency of backup versions
        • VERSIONS and SYSVERSIONS: Specifying the number of backup versions to maintain
      • Examples of how to code the ALTERDS command
    • ALTERPRI command: Altering the priority of queued requests
      • Syntax of the ALTERPRI command
      • Required parameters of the ALTERPRI command
        • REQUEST, USERID, and DATASETNAME: Specifying the requests to be reprioritized
      • Optional parameters of the ALTERPRI command
        • HIGH and LOW: Specifying the new priority of a request
      • Examples of how to code the ALTERPRI command
    • ARECOVER command: Recovering a specified aggregate group
      • Syntax of the ARECOVER command
      • Required parameters of the ARECOVER command
        • AGGREGATE: Specifying the aggregate group to be recovered
        • DATASETNAME: Specifying the control file
        • VOLUMES and XMIT: Specifying the volume type
        • EXECUTE, VERIFY, and PREPARE: Specifying whether data movement or verification should occur or whether an ABR record should be created
      • Optional parameters of the ARECOVER command
        • ACTIVITY: Recovering the activity log
        • DATASETCONFLICT: Resolving data set naming conflicts
        • DATE and VERSION: Specifying the specific aggregate group to be recovered
        • INSTRUCTION: Recovering the instruction data set
        • MENTITY: Specifying a model entity
        • MIGRATEDDATA: Specifying the migration level for recovering migrated data sets
        • NOBACKUPMIGRATED: Specifying that automatic backup does not occur for recovered migrated data sets
        • ONLYDATASET: Recover a single data set or a group of data sets from an aggregate group backup
          • LISTOFNAMES: Recover multiple data sets from an aggregate group backup
        • PERCENTUTILIZED: Specifying the percentage of DASD space used during ARECOVER of data sets to non-SMS volumes
        • RECOVERNEWNAMEALL and RECOVERNEWNAMELEVEL: Specifying a high-level qualifier for recovered data sets
        • STACK and NOSTACK: Specifying whether or not the ABACKUP output is STACKED
        • TARGETUNIT: Specifying unit types to be used for ARECOVER
        • TGTGDS: Overriding the SETSYS ARECOVERTGTGDS command
        • UNIT: Specifying unit types used for ARECOVER
        • VOLCOUNT: Allowing data sets to expand to multivolume as necessary during ARECOVER
      • How to create the ABR record
      • Examples of how to code the ARECOVER command
    • AUDIT Command: Auditing DFSMShsm
      • Auditing control data sets
      • Auditing common queues
      • Using the AUDIT command
      • Syntax of the enhanced AUDIT commands
      • Syntax of the original AUDIT commands
      • Required and optional parameters of the AUDIT command
        • ABARSCONTROLS: Requesting an audit of ABR records in the BCDS
        • ALL, BACKUPCONTROLDATASET, MIGRATIONCONTROLDATASET, and OFFLINECONTROLDATASET: Requesting an audit of data sets
        • BACKUPTYPE, BACKUPVOLUMES, and VOLUMES: Requesting an audit of primary, migration, or backup volumes
        • COMMONQUEUE: Requesting an audit of common queues
        • COPYPOOLCONTROLS: Requesting an audit of fast replication CDS record relationships
        • DATASETCONTROLS: Requesting an audit of data set control records
        • DATASETNAMES, LEVELS, and RESUME: Requesting an audit of data sets
        • DIRECTORYCONTROLS VOLUMES: Comparing a VTOC or a TTOC to CDS records
        • MASTERCATALOG and USERCATALOG: Requesting an audit of a catalog
        • MEDIACONTROLS VOLUMES and MEDIACONTROLS(SDSP) VOLUMES: Requesting an audit of control information
        • VOLUMECONTROLS (BACKUP, MIGRATION, and RECOVERABLE): Requesting an audit of control information
      • Optional parameters of the AUDIT command
        • FIX and NOFIX: Specifying whether auditing repairs errors
        • OUTDATASET, SYSOUT, and TERMINAL: Specifying the output location for the report
        • REPORT: Specifying how much audit information to print
        • SERIALIZATION: Stabilizing control information
      • Using the AUDIT command
    • AUTH Command: Identifying authorized users
      • Syntax of the AUTH command
      • Required parameters of the AUTH command
        • userid: Specifying the user whose authorization is to be changed
        • DATABASEAUTHORITY and REVOKE: Giving authority to or revoking authority of a user
      • Examples of how to code the AUTH command
    • BACKDS command: Backing up a specific data set
      • Syntax of the BACKDS command
      • Required parameters of the BACKDS command
        • dsname: Specifying the name of the data set to be backed up
      • Optional parameters of the BACKDS command
        • CC: Specifying concurrent copy for data set backup
        • NEWNAME: Specifying a name to assign to the backup version
        • RETAINDAYS: Specifying the number of days to retain a backup copy
        • TARGET: Specifying a required target output device
        • UNIT: Specifying the type of device
        • VOLUME: Specifying the volume where the data set resides
      • Examples of how to code the BACKDS command
    • BACKVOL command: Backing up data sets from volumes or dumping volumes
      • Backing up data sets from one or more SMS-managed volumes or dumping SMS-managed volumes
      • Syntax of the BACKVOL command with SMS-managed volumes
      • Required parameters for SMS-managed volumes
        • CONTROLDATASETS: Specifying the control data sets to be backed up
        • STORAGEGROUP: Specifying the storage group to back up or dump
        • VOLUMES: Specifying the volumes to be backed up or dumped
      • Optional parameters for SMS-managed control data sets
        • BACKUPDEVICECATEGORY: Specifying the backup device for the control data sets and journal
        • DATAMOVER: Specifying the type of data movement used when backing up the control data sets
        • NULLJOURNALONLY: Specifying that DFSMShsm null the journal
      • Optional parameters for SMS-managed volumes
        • BACKUPDEVICECATEGORY: Specifying where the backup versions are to reside
        • DUMP, INCREMENTAL, and TOTAL: Specifying which data sets are backed up
        • DUMPCLASS: Specifying that each dump copy be targeted to a particular dump class
        • RETENTIONPERIOD: Requesting a specific retention period for the dump copy
        • STACK: Specifying the maximum number of dump copies to be stacked for the specified dump classes
        • TERMINAL: Requesting that backup or dump messages appear at the terminal
      • Examples of how to code the BACKVOL command for SMS-managed volumes
      • Backing up data sets from one or more non-SMS-managed volumes or from all primary volumes or dumping non-SMS-managed volumes
      • Syntax of the BACKVOL command with non-SMS-managed volumes
        • Summary of parameters
      • Required parameters for non-SMS-managed volumes or all primary volumes
        • CONTROLDATASETS: Specifying the control data sets to be backed up
        • PRIMARY and VOLUMES: Specifying the volumes to be backed up or dumped
      • Optional parameters for non-SMS-managed control data sets
        • BACKUPDEVICECATEGORY: Specifying the backup device for the control data sets and journal
        • DATAMOVER: Specifying the type of data movement used when backing up the control data sets
        • NULLJOURNALONLY: Specifying that DFSMShsm null the journal
      • Optional parameters for non-SMS-managed volumes or all primary volumes
        • BACKUPDEVICECATEGORY: Specifying where the backup versions reside
        • DUMP, INCREMENTAL, and TOTAL: Specifying which data sets are backed up
        • DUMPCLASS: Specifying that each dump copy be targeted to a particular dump class
        • FREQUENCY: Specifying the frequency of backup for data sets
        • RETENTIONPERIOD: Requesting a specific retention period for the dump copy
        • STACK: Specifying the maximum number of dump copies to be stacked for the specified dump classes
        • TERMINAL: Requesting that backup or dump messages appear at the terminal
        • UNIT: Specifying the type of device
      • Examples of how to code the BACKVOL command for non-SMS-managed volumes
    • BDELETE command: Deleting backup versions of a data set
      • Syntax of the BDELETE command
      • Required parameters of the BDELETE command
        • dsname: Specifying the name of the data set whose backup versions are to be deleted
        • ALL, DATE and TIME, and VERSIONS: Specifying which backup versions to delete
        • ALL: Deleting all backup versions
        • DATE and TIME: Specifying the date and time of the backup version to delete
        • VERSIONS: Specifying the backup versions to delete
      • Optional parameters of the BDELETE command
        • FROMVOLUME: Specifying the volume where the data set resided when the backup versions were created
      • Examples of how to code the BDELETE command
    • CANCEL command: Canceling a queued or active DFSMShsm request
      • Syntax of the CANCEL command
      • Optional parameters of the CANCEL command
        • DATASETNAME: Canceling a queued request by data set name
        • REQUEST: Canceling a queued request by request number
        • USERID: Canceling a queued request by user ID
        • SASINDEX: Canceling an active request by ABARS secondary address space
        • TCBADDRESS: Canceling an active request by TCB address
      • Examples of how to code the CANCEL command
    • DEFINE command: Defining control structures for use by DFSMShsm
      • Syntax of the DEFINE command
      • Optional parameters of the DEFINE command
        • ARPOOL: Identifying the volumes for aggregate recovery
        • BACKUP: Specifying the backup cycle
        • CYCLESTARTDATE: Specifying the start date of a cycle
        • DUMPCLASS: Adding or changing a volume dump class
        • DUMPCLASS(AUTOREUSE and NOAUTOREUSE): Specifies whether DUMP volumes are automatically available for reuse when invalidated
        • DUMPCLASS(DATASETRESTORE and NODATASETRESTORE): Data set restore is allowed from a full-volume dump copy in this dump class
        • DUMPCLASS(DAY): Specifying the target day of the dump cycle for this class
        • DUMPCLASS(DISABLE): Specifying the volume dump class and making it unavailable as a target of any full-volume dump
        • DUMPCLASS(DISPOSITION): Specifying the disposition of dump volumes
        • DUMPCLASS(ENCRYPT): Specifying whether to encrypt the dump data with host based encryption
        • DUMPCLASS(FASTREPLICATIONDUMP): Specifying whether a dump class is required or optional
        • DUMPCLASS(FASTREPLICATIONRECOVER): Specifying whether a dump class copy is immediately available to be mounted for recovery
        • DUMPCLASS(FREQUENCY): Specifying the minimum number of days that must elapse between volume dumps of a volume to this class
        • DUMPCLASS(HWCOMPRESS): Specifying whether to compress the data to be encrypted
        • DUMPCLASS(RECOVERRESET): Specifying whether to reset the data-set-changed indicator in the VTOC entry
        • DUMPCLASS(RESET and NORESET): Specifying whether DFSMSdss resets the change bit for each data set following a full-volume dump
        • DUMPCLASS(RETENTIONPERIOD): Specifying the enforcement of retention periods for the dump copies in this class
        • DUMPCLASS(STACK): Specifying the maximum number of dump copies that are stacked for this dump class
        • DUMPCLASS(TAPEEXPIRATIONDATE): Specifying a unique expiration date for all dump copies created in a dump
        • DUMPCLASS(UNIT): Specifying a default tape unit name
        • DUMPCLASS(VTOCCOPIES): Specifying the number of dump VTOC copy data sets to keep for dump copies created in this class
        • DUMPCLASS(ZCOMPRESS): Specifying whether to use zEDC Services on the dump data
        • DUMPCYCLE: Specifying the automatic dump cycle
        • MIGRATIONCLEANUPCYCLE and SECONDARYSPMGMTCYCLE: Specifying the cycle for automatic secondary space management functions
        • MIGRATIONLEVEL2: Specifying DASD level 2 volumes and their associated key range structure
        • POOL: Identifying the non-SMS-managed volumes where the data sets with the same first qualifier are recalled
        • PRIMARYSPMGMTCYCLE: Specifying the cycle for automatic primary space management
        • SWITCHTAPES: Releasing mounted tapes for command data set backup
        • VOLUMEPOOL: Identifying groups of volumes where data sets are recalled
      • Examples of how to code the DEFINE command
    • DELETE Command: Deleting a migrated data set from a migration volume
      • Syntax of the DELETE command
      • Required parameters of the DELETE command
        • dsname: Specifying the data set to be deleted
      • Optional parameters of the DELETE command
        • PURGE: Specifying deletion of a data set
      • Examples of how to code the DELETE command
    • DELVOL command: Removing a volume from DFSMShsm management
      • Syntax of the DELVOL command
      • Required parameters of the DELVOL command
        • volser: Specifying the volume you are deleting
        • BACKUP, DUMP, MIGRATION, and PRIMARY: Specifying the type of volume
      • Optional parameters of the DELVOL command
        • COPYPOOLCOPY: Deleting a copy pool dump volume
        • LASTCOPY: Invalidating the only valid dump copy of a source volume
        • MARKFULL, PURGE, REASSIGN, and UNASSIGN: Specifying the options for deleting a backup, dump, or ML2 volume
          • MARKFULL with BACKUP or MIGRATION
          • PURGE with BACKUP
          • PURGE with DUMP
          • PURGE with MIGRATION
          • REASSIGN with DUMP
          • UNASSIGN with BACKUP
          • UNASSIGN with DUMP
          • UNASSIGN with MIGRATION
      • Examples of how to code the DELVOL command
    • DISPLAY command: Displaying DFSMShsm storage locations
    • EXPIREBV command: Deleting unwanted backup versions of data sets
      • Syntax of the EXPIREBV command
      • Required parameters of the EXPIREBV command
        • DISPLAY and EXECUTE: Specifying whether to delete the backup versions
      • Optional parameters of the EXPIREBV command
        • ABARSVERSIONS: Specifying that only aggregate group versions are to be processed
        • NONSMSVERSIONS: Specifying expiration criteria for backup versions of data sets not managed by SMS
        • STARTKEY and RESUME: Determining the starting point for BCDS processing during command execution
        • ENDKEY: Determining the ending point for BCDS processing during command execution
        • OUTDATASET and SYSOUT: Specifying the output location for EXPIREBV DISPLAY listing
      • Examples of how to code the EXPIREBV command
    • FIXCDS command: Displaying or modifying MCDS, BCDS, and OCDS records
    • FRBACKUP command: Requesting a fast replication backup or dump version
      • Syntax of the FRBACKUP command
      • Required parameter of the FRBACKUP command
        • COPYPOOL: Specifying the name of the copy pool for backup
      • Optional parameters of the FRBACKUP command
        • BACKUPSTORAGEGROUP: Overriding the copy pool backup storage group with an alternate storage group
        • DUMP: Creating a fast replication DASD version followed by a dump
        • DUMPCLASS: Specifying unique dump classes for fast replication dump processing
        • EXECUTE, PREPARE, WITHDRAW, and DUMPONLY: Specifying the backup or dump action
        • FCINCREMENTAL: Requesting DFSMShsm to create a copy pool version using incremental FlashCopy
        • FCINCREMENTALLAST: Requesting a FlashCopy incremental copy with a subsequent withdraw
        • FORCE: Replacing a DASD backup copy that has an incomplete dump copy
        • NOVTOCENQ: Requesting DFSMShsm to not serialize the VTOC of processed volumes
        • TOKEN: Specifying an identifier for each copy pool backup version
      • Examples of how to code the FRBACKUP command
    • FRDELETE command: Deleting fast replication backup or dump versions
      • Syntax of the FRDELETE command
      • Required parameters of the FRDELETE command
        • COPYPOOL: Specifying the name of the copy pool for deletion
        • ALL, TOKEN, and VERSIONS: Specifying the delete action
      • Optional parameters of the FRDELETE command
        • DASDONLY, DUMPONLY, and BOTH: Specifying which copies to delete
      • Examples of how to code the FRDELETE command
    • FREEVOL command: Freeing DFSMShsm-owned volumes
      • Syntax of the FREEVOL command
      • Required parameters of the FREEVOL command
        • MIGRATIONVOLUME and BACKUPVOLUME: Specifying a volume to free
        • ML1BACKUPVERSIONS: Moving backup versions off migration volumes
      • Optional parameters of the FREEVOL command
        • AGE: Specifying data set use
        • TARGETLEVEL: Specifying the target to which data sets are moved
        • RETAINNEWESTVERSION: Preventing movement of backup versions
      • Examples of how to code the FREEVOL command
    • FRRECOV command: Requesting a fast replication recovery
      • Syntax of the FRRECOV command
      • Required parameters of the FRRECOV command
        • COPYPOOL: Specifying the copy pool for which to recover all backup volumes
        • DSNAME: Specifying the data sets to recover from a copy pool backup version
        • TOVOLUME: Specifying a single volume within a copy pool to recover
      • Optional parameters of the FRRECOV command
        • ALLOWPPRCP: Specifying Metro Mirror primary volume and preserve mirror options for a FlashCopy operation
        • DATE, GENERATION, TOKEN, VERSION: Specifying a specific backup version to recover
        • FASTREPLICATION: Indicating a recovery preference
        • FORCE: Allowing recovery from a DASD backup copy that has an incomplete dump copy
        • FROMCOPYPOOL: Recovering a volume or data set that belongs to multiple copy pools
        • FROMDASD: Recovering a volume from DASD
        • FROMDUMP: Recovering a volume from a dump tape
        • NEWNAME: Specifying a New Data Set Name for the Recovered Data Set
        • NOCOPYPOOLBACKUP: Setting an alternate return code
        • REPLACE: Recovering a cataloged data set
        • RSA: Overriding the RSA key label
        • VERIFY: Verifying that no unexpected FlashCopy relationship exists for a volume in a copy pool
      • Examples of how to code the FRRECOV command
    • HOLD command: Preventing DFSMShsm functions from running
      • Syntax of the HOLD command
      • Optional parameters of the HOLD command
        • ABACKUP: Preventing aggregate backup
        • ALL: Preventing all DFSMShsm functions
        • ARECOVER: Preventing aggregate recovery
        • AUDIT: Ending the audit function
        • AUTOMIGRATION: Preventing automatic volume and automatic secondary space management
        • BACKUP: Preventing backups
        • COMMONQUEUE: Preventing common queue functions
        • DUMP: Preventing dumps
        • ENDOFDATASET: Specifying when aggregate group processing should stop
        • ENDOFDATASET and ENDOFVOLUME: Specifying when volume processing should stop
        • EXPIREBV: Ending the expire backup function
        • FRBACKUP: Preventing fast replication backup or dump processing
        • FRRECOV: Preventing fast replication recovery processing
        • LIST: Ending the list function
        • LOG: Preventing logging
        • MIGRATION: Preventing space management
        • RECALL: Preventing recall and deletion
        • RECOVER: Preventing recovery and restore
        • RECYCLE: Ending the recycle function
        • REPORT: Ending the report function
        • TAPECOPY: Preventing DFSMShsm from copying a tape
        • TAPEREPL: Preventing DFSMShsm from replacing an original tape volume with an alternate
      • Examples of how to code the HOLD command
    • HSENDCMD command: Issuing DFSMShsm authorized-user commands from a TSO terminal
      • Syntax of the HSENDCMD command
      • Required parameters of the HSENDCMD command
        • command: Specifying DFSMShsm authorized command
      • Optional parameters of the HSENDCMD command
        • WAIT and NOWAIT: Specifying whether to wait for command completion
      • Examples of how to code the HSENDCMD command
    • LIST command: Listing information from the MCDS, BCDS, and OCDS
      • Syntax of the LIST command
      • Required parameters of the LIST command
        • AGGREGATE: Listing the aggregate backup and recovery activity information
        • BACKUPVOLUME: Listing backup volume entries
        • COPYPOOL: Listing information for each version of a copy pool
        • COPYPOOLBACKUPSTORAGEGROUP: Listing copy pool information for each volume in the specified copy pool backup storage group
        • DATASETNAME and LEVEL: Listing data set entries
        • DUMPCLASS: Listing dump class profiles
        • DUMPVOLUME: Listing information about a single dump volume or a set of dump volumes
        • HOST: Listing all control data sets serialized by the DFSMShsm host
        • MIGRATIONVOLUME, MIGRATIONLEVEL1, MIGRATIONLEVEL2, and VOLUME: Listing migration volumes
        • PRIMARYVOLUME: Listing primary volumes
        • TAPETABLEOFCONTENTS: Listing tape volume information from the OCDS
        • TAPETABLEOFCONTENTS(volser): Listing tape volume information and data set names from the TTOC
        • USER: Listing user entries
      • Optional parameters of the LIST command
        • ALLDUMPS and BACKUPCONTENTS: Determining existence of dumps or listing incremental backup contents
        • ALLVOLS, DATASETS, DUMPVOLS, FASTREPLICATIONVOLS, and NOVOLS: Listing a specific type of copy pool information
        • BACKUPCONTROLDATASET, MIGRATIONCONTROLDATASET, and BOTH: Controlling the source of information
        • DATASETINFORMATION and NODATASETINFORMATION: Including or not including data set information
        • DATE and VERSION: Specifying the date or version of the aggregate group
        • DUMPCONTENTS: Listing contents of a set of dump volumes
        • INCLUDEPRIMARY: Listing entries for any data set that has migrated
        • OUTDATASET, SYSOUT, and TERMINAL: Specifying the location of output for the list
        • RESET: Requesting that the host ID field indicate no serialization
        • SELECT: Listing only those data set or volume entries that meet selection criteria
        • SELECT (ACTIVE and RETAINDAYS): Displaying information about active and retained backup copies
        • SELECT (AGE): Specifying data set use by age
        • SELECT (ALTERNATEVOLUME and NOALTERNATEVOLUME): Listing tape volumes that have alternate tape volumes
        • SELECT (AVAILABLE): Listing available dump volumes for dump output
        • SELECT (CAPACITYMODE): Identifying tape volumes by their ability to use available tape capacity
        • SELECT (CONNECTED and NOTCONNECTED): List volumes that contain spanning data sets
        • SELECT (DISASTERALTERNATEVOLUMES): Listing tape volumes that have disaster alternate volumes
        • SELECT (DUMPCLASS)
        • SELECT (DUMPSTATE, FASTREPLICATIONSTATE, INCOMPLETERECOVERY, and NONPREFERREDFRVOLS): Listing specific information about copy pools
        • SELECT (EFMT1, EFMT2, EEFMT2, EFMT3, EEFMT3, EFMT4, EEFMT4, ENCRYPTED, and NOTENCRYPTED): Recording format
        • SELECT (EMPTY, FULL, NOTFULL, ASSOCIATED, NOTASSOCIATED, ERRORALTERNATE, and RECYCLETAKEAWAY): Identifying tape volume capacity
        • SELECT (EXCESSIVEVOLUMES): Listing volumes with data sets spanning four or more volumes
        • SELECT (EXPIRED): Listing expired dump volumes
        • SELECT (FAILEDCREATE): Listing all tape volumes that have incomplete data set information saved in the OCDS TTOC record
        • SELECT (FAILEDRECYCLE): Listing only those volumes that have failed recycle
        • SELECT (LIBRARY and NOLIBRARY): Listing tape volume library status
        • SELECT (MIGRATIONLEVEL1, MIGRATIONLEVEL2, VOLUME(volser), BACKUP, and BOTH): Requesting specific information for volumes
        • SELECT (MULTIPLEVOLUME): Listing multiple-volume non-VSAM data sets from backup or dump VTOC copy data sets
        • SELECT (NORETENTIONLIMIT): List dump volumes with no retention period
        • SELECT (OVERFLOW and NOOVERFLOW): List overflow or non-overflow ML1 volumes
        • SELECT (RECALLTAKEAWAY): Listing ML2 volumes taken away by recall or ABACKUP functions
        • SELECT (RESUMEAUDIT): Listing tape volumes that are capable of being resumed after AUDIT MEDIACONTROLS was interruped
        • SELECT (SMALLDATASETPACKING and NOSMALLDATASETPACKING): Specifying whether data sets have migrated to SDSP
        • SELECT (UNAVAILABLE): Listing dump volumes with invalid contents
        • SELECT (UNEXPIRED): Listing dump volumes that have not reached their expiration date
        • SELECT (VSAM): Specifying the data set organization
        • SUMMARY: Requesting a summary
      • Examples of how to code commonly used list requests
    • LOG command: Entering data into the DFSMShsm log
      • Syntax of the LOG command
      • Required parameters of the LOG command
        • data: Specifying the data for the log
      • Example of how to code the LOG command
    • MIGRATE command: Requesting a space management function
      • Requesting a space management function for SMS-managed data sets
      • Syntax of the MIGRATE command for SMS-managed data sets
        • Summary of parameters
      • Required parameters of the MIGRATE command for SMS-managed data sets
        • DATASETNAME: Specifying migration of a specific data set
        • MIGRATIONLEVEL1: Specifying migration of data sets from level 1 to level 2 volumes
        • VOLUME: Specifying the space management attribute for the eligible data sets on a volume
      • Optional parameters of the MIGRATE command for SMS-managed data sets
        • CONVERT: Specifying movement of data sets from one volume to another
        • DAYS: Specifying migration eligibility of data sets
        • MIGRATIONLEVEL1: Specifying migration of a data set
        • MIGRATIONLEVEL2: Specifying migration of a data set directly to a level 2 volume
        • TERMINAL: Requesting that volume space management messages appear at the terminal
      • Examples of how to code the MIGRATE command for SMS-managed data sets
      • Requesting a space management function for non-SMS-managed data sets
      • Syntax of the MIGRATE command for non-SMS-managed data sets
        • Summary of parameters
      • Required parameters of the MIGRATE command for non-SMS-managed data sets
        • DATASETNAME: Specifying migration of a specific data set
        • MIGRATIONLEVEL1: Specifying migration of data sets from level 1 to level 2 volumes
        • PRIMARY: Specifying space management of eligible data sets on all primary volumes
        • VOLUME: Specifying the space management attribute for the eligible data sets on a volume
      • Optional parameters of the MIGRATE command for non-SMS-managed data sets
        • CONVERT: Specifying movement of data sets from one volume to another
        • DAYS: Specifying migration eligibility of data sets
        • MIGRATIONLEVEL1: Specifying migration of a data set directly to appropriate level of hierarchy
        • MIGRATIONLEVEL2: Specifying migration of a data set directly to a level 2 volume
        • TERMINAL: Requesting that volume space management messages appear at the terminal
        • UNIT: Specifying the type of device
      • Examples of how to code the MIGRATE command for non-SMS-managed data sets
    • ONLYIF command: Running commands in ARCCMDxx conditionally
      • Syntax of the ONLYIF command
      • Required parameters of the ONLYIF command
        • HSMHOST: Specifying the host ID of a specific host or hosts
      • Optional parameters of the ONLYIF command
        • BEGIN: Begin a group of commands
        • END: End a group of commands
      • Examples of how to code the ONLYIF command
    • PATCH command: Modifying storage within DFSMShsm
    • QUERY command: Displaying the status of parameters, statistics, and requests
      • Syntax of the QUERY command
      • Optional parameters of the QUERY command
        • ABARS: Displaying aggregate backup and recovery control parameters
        • ACTIVE: Displaying all active requests
        • ARPOOL: Displaying aggregate recovery pools
        • AUTOPROGRESS: Displaying an indication of volumes to be processed
        • BACKUP: Displaying backup parameters and backup volumes
        • CDSVERSIONBACKUP: Displaying the control data set multiple backup support parameters
        • COMMONQUEUE: Displaying common queue information
        • CONTROLDATASETS: Displaying control data set space-use information
        • COPYPOOL: Displaying copy pool information
        • CSALIMITS: Displaying the common service area storage limits
        • DATASETNAME, REQUEST, and USER: Displaying selected requests
        • IMAGE: Displaying information for the DFSMShsm address spaces active within a single z/OS image
        • MIGRATIONLEVEL2: Displaying key ranges and migration level 2 volumes
        • POOL: Displaying recall pools
        • RETAIN: Displaying data set levels prevented from space management
        • SECURITY: Displaying the type of command authorization in effect
        • SETSYS: Displaying control parameters
        • SPACE: Displaying volume space-use information
        • STARTUP: Displaying the startup information
        • STATISTICS: Displaying daily statistics
        • TRAPS: Displaying trap requests
        • VOLUMEPOOL: Displaying current volume pools
        • WAITING: Displaying the number of requests waiting to be processed
      • Examples of how to code the QUERY command
    • RECALL command: Recalling a specific migrated data set
      • Syntax of the RECALL command
      • Required parameters of the RECALL command
        • dsname: Specifying the name of the data set to be recalled
      • Optional parameters of the RECALL command
        • DAOPTION: Selecting target volume track length
        • DFDSSOPTION: Pass optional parameters to DFSMSdss
        • FORCENONSMS: Recalling an SMS-managed data set to a non-SMS-managed volume
        • UNIT: Specifying the type of device
        • VOLUME: Specifying the volume to receive the recalled data set
      • Examples of how to code the RECALL command
    • RECOVER command: Recovering a backup version or dump copy of a data set or a volume
      • Syntax of the RECOVER command
      • Required parameters of the RECOVER command
        • dsname and *: Specifying the name of the data set to be recovered
      • Optional parameters of the RECOVER command
        • DAOPTION: Selecting target volume track length
        • DATE, GENERATION, and VERSION: Specifying the particular backup version or dump copy to recover
        • DFDSSOPTION: Pass optional parameters to DFSMSdss
        • FORCENONSMS: Recovering an SMS-managed data set to a non-SMS-managed volume
        • FROMDUMP: Specifying which dump copy is used for restoring data sets
        • FROMVOLUME: Specifying the volume from which the backup version of a data set has been created
        • NEWNAME: Specifying a new data set name for the recovered data set
        • REPLACE: Specifying that the recovered backup version or dump copy is to replace any existing data set of the same name
        • RSA: Specifying that the RSA parameter is to override the RSA key label
        • TARGETVOLUME: Specifying the volume to receive the restored data sets
        • TERMINAL: Requesting that volume recovery messages appear at the terminal
        • TOVOLUME: Specifying the volume to receive the recovered data set
        • UNIT: Specifying the type of device
      • Examples of how to code the RECOVER command
    • RECYCLE command: Consolidating valid data to one tape from other tapes
      • Syntax of the generic RECYCLE command
      • Syntax of the specific RECYCLE command
      • Required parameters of the RECYCLE command
        • ALL, BACKUP, DAILY, ML2, SPILL, and VOLUME: Specifying the tape volumes to be recycled
        • EXECUTE, VERIFY, and DISPLAY: Specifying whether to list or to recycle tape volumes
      • Optional parameters of the RECYCLE command
        • CHECKFIRST: Allowing connected set to be recycled sooner
        • FORCE: Forcing DFSMShsm to permit a tape recycle
        • LIMIT: Quiescing recycle processing when the desired number of tapes have been returned to scratch
        • OUTDATASET: Directing recycle messages
        • PERCENTVALID: Specifying the percent valid criteria for recycle eligibility
        • SELECT: Specifying tape eligibility for generic recycle
        • TAPELIST: Listing volumes for pulling and mounting tapes
      • Examples of how to code the RECYCLE command
    • RELEASE command: Releasing all or some DFSMShsm functions for processing
      • Syntax of the RELEASE command
      • Optional parameters of the RELEASE command
        • ABACKUP: Releasing aggregate backup
        • ALL: Releasing all DFSMShsm functions
        • ARECOVER: Releasing aggregate recovery
        • AUDIT: Releasing the audit function
        • AUTOMIGRATION: Releasing only automatic volume and automatic secondary space management
        • BACKUP: Releasing backup
        • COMMONQUEUE: Releasing holds on the common queue
        • DUMP: Releasing dump
        • EXPIREBV: Releasing the expire backup versions function
        • FRBACKUP: Releasing the fast replication backup or dump function
        • FRRECOV: Releasing the fast replication recover function
        • HARDCOPY: Releasing the activity logs
        • LIST: Releasing the list function
        • LOG: Releasing logging
        • MIGRATION: Releasing space management
        • RECALL: Releasing recall and deletion
        • RECOVER: Releasing recovery and restore
        • RECYCLE: Releasing the recycle function
        • REPORT: Releasing the report function
        • RMM: Releasing the DFSMSrmm function
        • TAPECOPY: Releasing the tape copy function
        • TAPEREPL: Releasing the tape replace function
      • Examples of how to code the RELEASE command
    • REPORT Command: Requesting reports based on DFSMShsm statistics records
      • Syntax of the REPORT command
        • Summary of parameters
      • Optional parameters of the REPORT command
        • DAILY: Requesting daily statistics
        • DELETE: Deleting statistics records used as input to the report
        • FROMDATE: Requesting statistics of activity on or after the specified date
        • FUNCTION and NOFUNCTION: Requesting statistics by function
        • FUNCTION(BACKUP): Requesting statistics of the backup function
        • FUNCTION(DELETE): Requesting statistics of the delete function
        • FUNCTION(MIGRATION): Requesting statistics of the migration function
        • FUNCTION(RECALL): Requesting statistics of the recall function
        • FUNCTION(RECYCLE): Requesting statistics of the recycle function
        • FUNCTION(RECOVER): Requesting statistics of the recovery function
        • FUNCTION(SPILL): Requesting statistics of the spill function
        • FUNCTION(TRANSITION): Requesting statistics of the transition function
        • OUTDATASET and SYSOUT: Specifying the output location
        • SUMMARY: Requesting only the totals of the statistics
        • TODATE: Requesting statistics of activity on or before the specified date
        • VOLUMES: Requesting volume statistics
      • Examples of how to code the REPORT command
    • SETMIG command: Changing the space management status of non-SMS-managed data sets or volumes
      • Syntax of the SETMIG command
      • Required parameters of the SETMIG command
        • DATASETNAME, LEVEL, and VOLUME: Changing the space management status
      • Optional parameters of the SETMIG command
        • COMMANDMIGRATION, MIGRATION, and NOMIGRATION: Specifying the way space management is controlled
      • Examples of how to code the SETMIG command
    • SETSYS command: Establishing or changing the values of DFSMShsm control parameters
      • Syntax of the SETSYS command
      • SETSYS fast-path for DFSMShsm functions
      • Relationship of SMS to SETSYS parameters
      • Summary of DFSMShsm default values
      • Optional parameters of the SETSYS command
        • ABARSACTLOGMSGLVL: Specifying which DFSMSdss messages are written to the log
        • ABARSACTLOGTYPE: Specifying the ABARS activity log output data set type
        • ABARSBUFFERS: Specifying the number of I/O buffers for ABARS
        • ABARSDELETEACTIVITY: Allowing DFSMShsm to automatically delete the ABARS activity log
        • ABARSKIP: Specifying which types of data sets ABACKUP should skip
        • ABARSOPTIMIZE: Adjusting performance when backing up level 0 DASD specified in INCLUDE list
        • ABARSPROCNAME: Specifying the base procedure name to start the ABARS secondary address space
        • ABARSTAPES: Allowing DFSMShsm to stack the ABACKUP output files
        • ABARSUNITNAME: Specifying a unit name for ABARS
        • ABARSVOLCOUNT: Specifying the method for determining volume count for SMS target data set allocations done by DFSMSdss
        • ACCEPTPSCBUSERID and NOACCEPTPSCBUSERID: Allowing non-RACF installations to issue authorized commands in a TMP environment
        • ACTLOGMSGLVL: Specifying message level for recording data sets
        • ACTLOGTYPE: Specifying the type of output data set to receive messages
        • ARECOVERML2UNIT: Specifying the unit when recovering migrated data sets to nonspecific volumes
        • ARECOVERPERCENTUTILIZED: Specifying the percentage of DASD space for non-SMS-managed volumes
        • ARECOVERTGTGDS: Passing the TGTGDS parameter to DFSMSdss during restore processing
        • ARECOVERUNITNAME: Specifying tape unit type for aggregate recovery
        • AUTOBACKUPSTART: Specifying when automatic backup is to start
        • AUTODUMPSTART: Specifying when automatic dump is to start
        • AUTOMIGRATIONSTART: Specifying the start time for automatic primary space management
        • BACKUP and NOBACKUP: Specifying whether you intend to use DFSMShsm backup, recovery, and dump
        • BACKUPPREFIX: Specifying the prefix for the backup version name or the dump copy data set name
        • CDSVERSIONBACKUP: Specifying whether the control data sets should be backed up to multiple data sets
        • CDSVERSIONBACKUP (BACKUPCOPIES): Specifying the number of backup copies to keep for each control data set and journal data set
        • CDSVERSIONBACKUP (BACKUPDEVICECATEGORY): Specifying the backup device to which the control data sets and journal will be backed up
        • CDSVERSIONBACKUP (DATAMOVER): Specifying the type of data movement used when performing CDSVERSIONBACKUP
        • CDSVERSIONBACKUP (BCDSBACKUPDSN): Specifying the initial characters of the backup data set name for the backup control data set
        • CDSVERSIONBACKUP (MCDSBACKUPDSN): Specifying the initial characters of the backup data set name for the migration control data set
        • CDSVERSIONBACKUP (OCDSBACKUPDSN): Specifying the initial characters of the backup data set name for the offline control data set
        • CDSVERSIONBACKUP (JRNLBACKUPDSN): Specifying the initial characters of the backup data set name for the journal data set
        • CLASSTRANSITIONS: Specifying if class transitions will be performed during event-driven migration
        • COMMONQUEUE: Specifying settings for the common queues
        • COMMONQUEUE (RECALL(CONNECT(basename))): Specifying the base name of the list structure for CRQ host connection
        • COMMONQUEUE (RECALL(DISCONNECT)): Specifying disconnection from the CRQ
        • COMPACT: Specifying when compaction should be done
        • COMPACT ALL and NONE: Specifying whether to compact data sets
        • COMPACT DASDBACKUP and NODASDBACKUP: Specifying whether to compact data sets during backup to DASD
        • COMPACT DASDMIGRATE and NODASDMIGRATE: Specifying whether to compact data sets during migration to DASD
        • COMPACT TAPEBACKUP and NOTAPEBACKUP: Specifying whether to compact data sets during backup to tape
        • COMPACT TAPEMIGRATE and NOTAPEMIGRATE: Specifying whether to compact data sets during migration to tape
        • COMPACTPERCENT: Specifying the percentage of space saved for compaction
        • CONVERSION and NOCONVERSION: Specifying whether reblocking is to occur
        • CSALIMITS and NOCSALIMITS: Specifying whether to use CSA limiting for MWE allocation
        • CSALIMITS (ACTIVE): Specifying the percentage of the maximum limit to be allocated to any type of MWE
        • CSALIMITS (INACTIVE): Specifying the percentage of the maximum limit to be allocated to NOWAIT MWEs
        • CSALIMITS (MAXIMUM): Specifying the maximum number of CSA bytes allocated to all types of MWEs
        • CSALIMITS (MWE): Specifying maximum number of NOWAIT MWEs per address space
        • DAYS: Specifying the minimum migration age of a data set
        • DEBUG and NODEBUG: Specifying debug mode
        • DEFERMOUNT: Specifying defer mounting of tapes
        • DENSITY: Specifying the tape density
        • DFHSMDATASETSERIALIZATION and USERDATASETSERIALIZATION: Specifying data set serialization
        • DISASTERMODE: Specifying the tape operation mode for DFSMShsm in disaster mode
        • DSBACKUP: Controlling the command data set backup environment
        • DSSXMMODE: Specifying whether DFSMSdss will be loaded in its own address space using the cross memory interface, or in the DFSMShsm address space, for backup, CDS backup, dump, migration, and full-volume and data set recovery
        • DUMPIO: Specifying the DFSMSdss DASD I/O buffering technique
        • DUPLEX: Allowing DFSMShsm to create two tapes concurrently
        • EMERGENCY and NOEMERGENCY: Specifying no data set movement
        • ERASEONSCRATCH and NOERASEONSCRATCH: Specifying to check for erasure of DFSMShsm-owned data sets
        • EXITOFF: Specifying inactive installation exits
        • EXITON: Specifying active installation exits
        • EXITS: Specifying the installation exits to be taken
        • EXPIREDDATASETS: Specifying whether to scratch data sets with expired expiration dates
        • EXTENDEDTTOC: Specifying whether to use extended tape table of contents (TTOC)
        • FASTREPLICATION: Specifying fast replication methods
        • FREQUENCY: Specifying the number of days between backup versions of a data set
        • INCREMENTALBACKUP: Specifying whether to back up only changed data sets during incremental volume backup
        • INPUTTAPEALLOCATION: Specifying whether to wait for the input tape to be allocated
        • INTERVALMIGRATION and NOINTERVALMIGRATION: Specifying whether interval migration is performed
        • JES2 and JES3: Specifying the job entry subsystem
        • JOURNAL and NOJOURNAL: Specifying whether to write updated control data set records in the journal data set
        • MAXABARSADDRESSSPACE: Specifying the maximum number of concurrent secondary address spaces supported
        • MAXBACKUPTASKS: Specifying the maximum number of concurrent volume backup tasks
        • MAXCOPYPOOLTASKS: Specifying the maximum number of concurrent DFSMSdss invocations for each fast replication command
        • MAXDSRECOVERTASKS: Specifying the maximum number of data set recovery tasks from DASD and tape
        • MAXDSTAPERECOVERTASKS: Specifying the maximum number of data set recovery tasks from tape
        • MAXDUMPRECOVERTASKS: Specifying the maximum number of concurrent volume recovery from dump tasks
        • MAXDUMPTASKS: Specifying the maximum number of concurrent volume dump tasks
        • MAXEXTENTS: Specifying the number of extents to cause extent reduction
        • MAXINTERVALTASKS: Specifying the maximum number of automatic interval migration or on-demand migration tasks that can run concurrently
        • MAXMIGRATIONTASKS: Specifying the maximum number of automatic volume space management tasks that can run concurrently
        • MAXRECALLTASKS: Specifying the maximum number of active recall tasks
        • MAXRECYCLETASKS: Specifying the maximum number of active recycle tasks
        • MAXSSMTASKS: Specifying the maximum number of concurrent automatic secondary space management tasks
        • MIGDENSITY: Specifying the tape density when allocating scratch tapes for migration
        • MIGRATEPREFIX: Specifying the prefix for the migration copy name
        • MIGRATIONCLEANUPDAYS: Specifying the number of days to keep MCDS data set records and statistics records
        • MIGRATIONLEVEL1DAYS: Specifying the inactive age for data sets migrating from level 1 volumes
        • MIGRATIONSUBTASKS: Enabling multiple migration subtasks
        • MIGUNITNAME: Specifying the type of unit for allocating a scratch tape during migration
        • ML1OVERFLOW: Manage ML1 OVERFLOW volumes
        • ML2PARTIALSNOTASSOCIATEDGOAL: Specifying the maximum number of allowed partial ML2 tapes
        • ML2RECYCLEPERCENT: Specifying the maximum percentage of valid data on a migration tape
        • MONITOR: Specifying which informational messages to print at the system console
        • MONITOR (BACKUPCONTROLDATASET): Monitoring the space used in the BCDS
        • MONITOR (JOURNAL): Monitoring the space used in the journal data set
        • MONITOR (MIGRATIONCONTROLDATASET): Monitoring the space used in the MCDS
        • MONITOR (OFFLINECONTROLDATASET): Monitoring the space used in the OCDS
        • MONITOR (SPACE and NOSPACE): Printing volume space-use messages
        • MONITOR (STARTUP and NOSTARTUP): Printing DFSMShsm startup informational messages
        • MONITOR (VOLUME and NOVOLUME): Printing data set messages during volume processing
        • MOUNTWAITTIME: Specifying the time DFSMShsm waits for a tape mount and open
        • OBJECTNAMES: Specifying the compaction-control qualifier of the object data set
        • ONDEMANDMIGRATION: Specifying whether on-demand migration should be performed
        • ODMNOTIFICATIONLIMIT: Specifying an on-demand migration number of concurrently queued volumes notification limit
        • OPTIMUMDASDBLOCKING and NOOPTIMUMDASDBLOCKING: Specifying whether DFSMShsm should use its defined optimum block size
        • OUTPUTTAPEALLOCATION: Specifying whether to wait for the output tape to be allocated
        • PARTIALTAPE: Specifying whether to reuse partially full tapes
        • PDA: Specifying whether the problem determination aid is initiated
        • PLEXNAME: Specifying a name for an HSMplex
        • PRIMARYSPMGMTSTART: Specifying the start and stop times for automatic primary space management
        • PROFILEBACKUP and NOPROFILEBACKUP: Specifying whether to create backup RACF discrete profiles for cataloged data sets
        • PROMOTE: Specifying whether a host is eligible for promotion
        • RACFIND and NORACFIND: Specifying whether to put RACF-indication on migration copies and backup versions
        • RECALL: Specifying the target volume to receive recalled data sets
        • RECYCLEINPUTDEALLOCFREQUENCY: Allowing periodic deallocation of input unit during recycle processing
        • RECYCLEOUTPUT: Limiting the selection and allocation of an output volume during recycle processing
        • RECYCLEPERCENT: Specifying the maximum percentage of valid data on a backup tape
        • RECYCLETAKEAWAYRETRY: Specifying whether to automatically generate a new RECYCLE command for a tape
        • RECYCLETAPEALLOCATION: Specifying whether to wait for the recycle tape to be allocated
        • REMOVECOMPACTNAMES: Removing the compaction-control qualifier for source or object data sets
        • REQUEST and NOREQUEST: Specifying whether the operator's permission is required
        • SCRATCHFREQUENCY: Specifying how long to retain list data sets
        • SECONDARYSPMGMTSTART: Specifying the start and stop time for automatic secondary space management
        • SELECTVOLUME: Specifying whether DFSMShsm should select a scratch tape volume or a DFSMShsm tape volume
        • SKIPABPRIMARY and NOSKIPABPRIMARY: Specifying whether to skip automatic backup of primary volumes
        • SMALLDATASETPACKING and NOSMALLDATASETPACKING: Specifying whether DFSMShsm should use small data set packing
        • SMF and NOSMF: Specifying whether DFSMShsm writes SMF records
        • SOURCENAMES: Specifying the compaction-control qualifier of the source data set
        • SPILL and NOSPILL: Specifying whether DFSMShsm does spill or cleanup processing on full DASD daily backup volumes
        • SWAP and NOSWAP: Specifying whether the DFSMShsm address space can be swapped
        • SYSOUT: Directing DFSMShsm output
        • SYS1DUMP and NOSYS1DUMP: Specifying where DFSMShsm dumps should be written
        • TAPEDATASETORDER: Specifying order for processing tape
        • TAPEDELETION: Specifying what to do with tapes that no longer contain valid data
        • TAPEHARDWARECOMPACT and NOTAPEHARDWARECOMPACT: Specifying the data format used when writing to a 3480X tape device
        • TAPEINPUTPROMPT: Specifying whether to suppress input tape messages
        • TAPEMAXRECALLTASKS: Specifying the maximum number of concurrent tape recall tasks
        • TAPEMIGRATION: Specifying the type of migration to tape
        • TAPEOUTPUTPROMPT: Specifying whether to suppress output tape messages
        • TAPERECALLLIMITS: Specifying limits to continuously mounted ML2 tapes during multiple recalls
        • TAPESECURITY: Specifying the type of security for tape volumes
        • TAPESPANSIZE: Reducing tape volume spanning
        • TAPEUTILIZATION: Specifying the desired tape utilization
        • UNITNAME: Specifying the type of unit for mounting a scratch tape during backup or dump
        • UNLOAD and NOUNLOAD: Specifying whether to unload MSS virtual DASD volumes
        • USECYLINDERMANAGEDSPACE: Specifying whether to allow use of cylinder managed space for migration copies and backup versions
        • USERUNITTABLE and NOUSERUNITTABLE: Specifying esoteric tape unit names to DFSMShsm
          • General example
          • Specific example
        • VERSIONS: Specifying the maximum number of backup versions to keep for any data set
        • VOLCOUNT: Specifying the method for determining volume count for SMS target data set allocations when performed by DFSMSdss
        • VOLUMEDUMP: Specifying concurrent copy options for dump volumes
        • ZCOMPRESS: Specifying when compression with zEDC should be done
        • ZCOMPRESS (NONE | ALL): Specifying whether to use zEDC Services for data sets
        • ZCOMPRESS (DASDBACKUP (NO | YES)) : Specifying whether to use zEDC Services for data sets during backup to DASD
        • ZCOMPRESS (DASDMIGRATE (NO | YES)) : Specifying whether to use zEDC Services for data sets during migration to DASD
        • ZCOMPRESS (TAPEBACKUP (NO | YES)) : Specifying whether to use zEDC Services for data sets during backup to tape
        • ZCOMPRESS (TAPEMIGRATE (NO | YES)) : Specifying whether to use zEDC Services for data sets during migration to tape
      • Examples of how to code the SETSYS command
    • STOP command: Shutting down DFSMShsm
      • Syntax of the STOP command
      • Optional parameters of the STOP command
        • DUMP: Requesting a dump of the DFSMShsm address space
        • PROMOTE: Specifying that a specific host in a sysplex is eligible to be promoted for another host
      • Example of how to code the STOP command
    • SWAPLOG command: Switching between the DFSMShsm log or PDA data sets
      • Syntax of the SWAPLOG command
      • Optional parameters of the SWAPLOG command
        • LOG: Specifying to swap the log data sets
        • PDA: Specifying to swap the PDA data sets
      • Examples of how to code the SWAPLOG command
    • TAPECOPY command: Making copies of selected cartridge-type tape volumes
      • Syntax of the TAPECOPY command
      • Required parameters of the TAPECOPY command
        • ALL: Specifying to copy all eligible cartridge-type single-file tape volumes
        • MIGRATIONLEVEL2: Specifying to create copies of all eligible migration level 2 volumes
        • BACKUP: Specifying to create copies of all eligible backup tape volumes
        • ORIGINALVOLUMES: Copying specified volumes
        • INDATASET: Specifying to use a data set containing a volume list
      • Optional parameters of the TAPECOPY command
        • ALTERNATEUNITNAME: Specifying alternate unit names for a tape copy
        • ALTERNATE3590UNITNAME: Specifying 3590 alternate unit name for a tape copy
        • ALTERNATEVOLUMES: Specifying which volumes to copy
        • EXPDT and RETPD: Specifying a tape expiration date or a retention period
      • Examples of how to code the TAPECOPY command
    • TAPEREPL command: Replacing cartridge-type tape volumes with their alternate volumes
      • Syntax of the TAPEREPL command
      • Required parameters of the TAPEREPL command
        • ALL: Specifying replacement of all cartridge-type single-file tape volumes
        • BACKUP: Specifying replacement of all cartridge-type single-file backup tape volumes
        • INDATASET: Specifying the use of a data set containing a volume list
        • MIGRATION: Specifying replacement of all cartridge-type single-file migration tape volumes
        • ONLYDISASTERALTERNATES: Converting disaster alternate volumes to original volumes
        • ORIGINALVOLUMES: Specifying volumes to be replaced
      • Optional parameters of the TAPEREPL command
        • ALTERNATEUNITNAME: Specifying an alternate unit name for a tape replacement
        • ALTERNATEVOLUMES: Specifying the replacement volumes to use
        • DISASTERALTERNATEVOLUMES: Identifying the alternate volume as the disaster alternate volume
      • Examples of how to code the TAPEREPL command
    • TRAP command: Requesting a dump when a specified error occurs
    • UPDATEC command: Recovering the control data sets
      • Syntax of the UPDATEC command
      • Required parameters of the UPDATEC command
        • ALL, BACKUPCONTROLDATASET, MIGRATIONCONTROLDATASET, and OFFLINECONTROLDATASET: Specifying which control data set to update
      • Optional parameters of the UPDATEC command
        • JOURNAL: Specifying the journal data set to use
      • Examples of how to code the UPDATEC command
    • Using the AUDIT command
      • Using the enhanced audit command to audit DFSMShsm control information
        • Using the AUDIT ABARSCONTROLS command
          • Diagnosis and repair action for AUDIT ABARSCONTROLS
        • Using the AUDIT COMMONQUEUE command
          • Diagnosis and repair action for AUDIT COMMONQUEUE(RECALL)
        • Using the AUDIT COPYPOOLCONTROLS command
          • Diagnosis and repair action for AUDIT COPYPOOLCONTROLS
        • Using the AUDIT DATASETCONTROLS (BACKUP) command
          • Diagnosis and repair action for AUDIT DATASETCONTROLS (BACKUP)
        • Using the AUDIT DATASETCONTROLS (MIGRATION) command
          • Diagnosis and repair action for AUDIT DATASETCONTROLS (MIGRATION)
        • Using the AUDIT DIRECTORYCONTROLS command
          • Errors detected when using AUDIT DIRECTORYCONTROLS for a DASD migration volume
          • Diagnosis and repair action for AUDIT DIRECTORYCONTROLS for DASD
          • Errors detected when using AUDIT DIRECTORYCONTROLS for a tape volume
          • Diagnosis and repair action for AUDIT DIRECTORYCONTROLS for tape
        • Using the AUDIT MEDIACONTROLS (SDSP) VOLUMES command
          • Diagnosis and repair action for AUDIT MEDIACONTROLS (SDSP) VOLUMES
        • Using the AUDIT MEDIACONTROLS VOLUMES command
          • Errors detected when using AUDIT MEDIACONTROLS for a DASD migration volume
          • Diagnosis and repair action for AUDIT MEDIACONTROLS for DASD
          • Errors detected when using AUDIT MEDIACONTROLS for a tape volume
            • No TTOC record exists for a migration volume
            • Checking TTOC entries for a migration volume
            • No TTOC record exists for a backup volume
            • Checking TTOC entries for a backup volume
          • Diagnosis and repair action for AUDIT MEDIACONTROLS for tape
        • Using the AUDIT VOLUMECONTROLS (BACKUP) command
          • Checking backup volume cycle records
          • Checking TTOC records for backup volumes
          • Diagnosis and repair action for AUDIT VOLUMECONTROLS (BACKUP)
        • Using the AUDIT VOLUMECONTROLS (MIGRATION) command
          • Checking the level 2 control record
          • Checking migration level 1 free space records
          • Diagnosis and repair action for AUDIT VOLUMECONTROLS (MIGRATION)
        • Using the AUDIT VOLUMECONTROLS (RECOVERABLE) command
          • Checking backup related controls
          • Checking dump related controls
          • Diagnosis and repair action for AUDIT VOLUMECONTROLS (RECOVERABLE)
        • Summary of errors detected by the enhanced AUDIT commands
      • Using the original AUDIT command to audit DFSMShsm data set information
        • Using the AUDIT DATASETNAMES and AUDIT LEVELS commands
          • Information reported when using AUDIT DATASETNAMES and AUDIT LEVELS
          • Diagnosis and repair action for AUDIT DATASETNAMES and AUDIT LEVELS
        • Using the AUDIT VOLUMES command
          • Errors detected when using AUDIT VOLUMES for a primary or migration DASD
          • Errors detected when using AUDIT VOLUMES for a tape migration volume
          • Information reported when using AUDIT VOLUMES
          • Diagnosis and repair action for AUDIT VOLUMES
        • Using the AUDIT BACKUPVOLUMES and AUDIT BACKUPTYPE commands
          • Error detected when using AUDIT BACKUPVOLUMES or AUDIT BACKUPTYPE for a backup DASD
          • Error detected when using AUDIT BACKUPVOLUMES or AUDIT BACKUPTYPE for a tape backup volume
          • Information reported when using AUDIT BACKUPVOLUMES and AUDIT BACKUPTYPE
          • Diagnosis and repair action for AUDIT BACKUPVOLUMES and AUDIT BACKUPTYPE
        • Using the AUDIT MASTERCATALOG and AUDIT USERCATALOG commands
          • Information reported when using AUDIT MASTERCATALOG and AUDIT USERCATALOG
          • Diagnosis and repair action for AUDIT MASTERCATALOG and AUDIT USERCATALOG
        • Using the AUDIT MIGRATIONCONTROLDATASET command
          • Information reported when using AUDIT MIGRATIONCONTROLDATASET
          • Diagnosis and repair action for AUDIT MIGRATIONCONTROLDATASET
        • Using the AUDIT BACKUPCONTROLDATASET command
          • Information reported when using AUDIT BACKUPCONTROLDATASET
          • Diagnosis and repair action for AUDIT BACKUPCONTROLDATASET
        • Using the AUDIT OFFLINECONTROLDATASET command
          • Errors detected when using AUDIT OFFLINECONTROLDATASET for backup
          • Errors detected when using AUDIT OFFLINECONTROLDATASET for migration
          • Information reported when using AUDIT OFFLINECONTROLDATASET
          • Diagnosis and repair action for AUDIT OFFLINECONTROLDATASET
        • Summary of errors detected by the original AUDIT commands
      • Error codes (*ERR) and diagnosis
      • Unexpected errors during an audit
        • Unexpected error messages
          • MSG 900
        • Errors encountered during AUDIT VOLUMES, AUDIT BACKUPVOLUMES, or AUDIT BACKUPTYPE
          • ARC0500I
      • Other considerations when using the AUDIT command
        • Multiple DFSMShsm host considerations when using the AUDIT command
        • Printing information from the AUDIT command
    • Using the LIST command
      • Requesting information for aggregate backup and recovery activity information
      • Requesting information for backup volumes
      • Requesting information for copy pools
      • Requesting information for copy pool backup storage groups
      • Requesting information for data sets
        • Requesting data set information from the MCDS
        • Requesting data set information from the BCDS
        • Requesting data set information from the MCDS and BCDS
        • Requesting data set information for the latest backup version
      • Requesting information for dump classes
      • Requesting information for dump volumes
        • Requesting dump content information for dump volumes
      • Requesting information for primary and migration volumes
        • Requesting primary and migration volume information from the MCDS
        • Requesting primary and migration volume information from the BCDS
        • Requesting primary volume dump information from the BCDS
        • Requesting contents of backup VTOC for a primary volume from the BCDS
      • Requesting a list of records serialized by DFSMShsm host ID
      • Requesting information from the tape table of contents (TTOC)
      • Requesting information for all user entries or a specific user entry
    • Using the QUERY command
    • Using the REPORT command
      • Requesting a report of the daily statistics for all functions
      • Requesting a report of the volume statistics for all functions
      • Requesting a summary of the daily or volume statistics