This topic contains detailed explanations of the operator, storage administrator, and system programmer commands, which are listed in alphabetical order. Long-running commands are limited to having only one of each such command being performed by DFSMShsm at any time. Other commands can also run for a long time. If a command is running for a long time and is returning data to your terminal, you can be prevented from performing other operations at your terminal.
|Published (Last):||25 March 2019|
|PDF File Size:||1.40 Mb|
|ePub File Size:||5.75 Mb|
|Price:||Free* [*Free Regsitration Required]|
It contains examples of the commands needed to perform the tasks, descriptions of the processing that DFSMShsm performs, and examples of the results of that processing.
Backup is the process of copying a data set from a level 0 or an ML1 volume to daily backup volume. This copy is called a backup version. The purpose of backup is to have copies of data sets in case something happens to the original data sets.
The difference between dump and backup is that the dump function backs up the entire allocated space on a volume, whereas the DFSMShsm backup function backs up individual data sets.
DFSMShsm can create backup versions of data sets either automatically or by command. DFSMShsm automatically creates backup versions of data sets on specified days beginning at a specified time of day. The data sets must meet eligibility criteria and must be on DFSMShsm-managed volumes that have been designated for automatic backup. Fast replication uses volume-level fast replication to create backup versions for sets of storage groups. You can define a set of storage groups through the SMS copy pool construct.
The fast replication backup versions can be dumped to tape. You can use FRBACKUP to dump an existing fast replication backup version, or when no backup version exists, create a fast replication backup version and dump it to tape. In all cases, the dump copies are associated with the original source DASD volumes in the copy pool, but not with the target DASD volumes that are actually dumped.
The dump time stamps reflect when the fast replication backup version is made, not the actual time of the dumps. Recovery from a fast replication backup version can be performed at the copy pool level from a disk copy, at the individual volume level from a disk or tape copy, or at the data set level from a disk or tape copy.
This Fast Replication function enables the backup and recovery of a large set of volumes to occur within a small time frame. Dump is the process of copying all data from a DASD volume to dump tape volumes. The purpose of the full-volume dump is to expedite the recovery process when an entire volume is lost or damaged and to supplement the incremental recovery process.
The full-volume-dump process can be one volume in and one dump copy out. It can also be one volume in and multiple dump copies out. Each dump copy is a complete image of the dumped volume, not just an incremental backup of selected data sets. Each successive full-volume dump of a volume, regardless of the number of dump copies, is a generation. Each dump copy in a generation is associated with a different dump class, which specifies how the dump copy is to be managed. DFSMShsm allows from one to five dump copies to be made concurrently for any one full-volume dump.
DFSMSdss discontinues writing to dump copies on which errors occur. DFSMSdss creates the multiple copies and continues its full-volume-dump process as long as one output copy is good.
DFSMShsm discards the contents of only the bad copies and issues an appropriate message. If all copies fail, the full-volume dump is failed.
DFSMShsm keeps generations of dump copies for any given volume unless all the copies in a generation expire. When all dump copies in any generation for a volume reach their expiration dates, DFSMShsm deletes that generation from its records. When the generations for a particular volume have been reached and the next full-volume dump for that volume is performed, the control records for the oldest generation are discarded, regardless of the retention periods of the individual copies.
When DFSMShsm needs another daily backup volume, it chooses an unassigned daily backup volume before it chooses an unassigned backup volume. DFSMShsm volume recovery can use incremental backups or full-volume dumps or both. DFSMShsm automatically chooses the more recent copy of the data set if you allow users to perform data set restores see Controlling restoring of individual data sets from dump tapes.
Data recovery scenarios , describes real-life examples of data loss and recovery situations. It describes a variety of situations where data is lost, and what steps to take to recover that data. It also includes situations where the lost data is a control data set or journal. How to use this document. You are introduced to the example system, which is referred to throughout the rest of this document.
The following topics introduce the tasks necessary to control space management functions. Space management is the DFSMShsm program function that you use to ensure that your customers have space available on DASD volumes to allocate new data sets or to extend old ones.
You can make the space available by deleting data sets that have outlived their usefulness, removing unused allocated space from data sets, moving low-activity data sets from level 0 volumes to other DASD or tape volumes, and returning the moved data sets to the level 0 devices when the data sets are needed. Space management of SMS-managed storage , describes the tasks to be performed and the results of processing for space management of data sets managed by the storage management subsystem SMS.
Space management of non-SMS-managed storage , describes the tasks to be performed and the results of processing for space management of data sets not managed by SMS. Other space management considerations , describes aspects of space management that deserve consideration but are peripheral to the discussions in the two preceding topics.
Space management procedures , describes procedures for starting and stopping space management under varying conditions. Functions of space management: Automatically delete, remove unused space from, and move data sets on DFSMShsm-managed volumes to provide a specified amount of free space on each volume. The space management functions begin at a specified time of day and only on a specific day of a cycle.
This operation is called automatic primary space management. The process of removing unused space from the data sets is called space reduction. Moving the data sets as opposed to deleting or removing unused space from them is called migration. Reconnect unchanged data sets that are recalled from ML2 tapes to their original ML2 tapes with the fast subsequent migration function.
If DFSMShsm finds any volume without the specified amount of space, it performs migration from all such volumes known as event-driven migration following a space check. Automatically clean up migration volumes and the migration control data set MCDS. This function and the following one are known as automatic secondary space management. Automatically, or by command, migrate data sets from level 1 migration volumes to level 2 migration volumes.
Automatically recall needed migrated data sets to level 0 volumes. Recall migrated data sets to level 0 volumes by command. Delete eligible data sets on a non-SMS-managed volume by command. Delete eligible non-SMS migrated data sets on a migration volume by command. Migrate individual data sets or eligible data sets on a volume by command. The following topics introduce the tasks necessary to control availability management functions.
Availability management is the function of the DFSMShsm program that you use to ensure that your customers can retrieve usable copies of their data sets should their online copies become lost or damaged. You can make the copies available by making daily incremental backup copies of changed data sets, making periodic dump copies of the DFSMShsm-managed and ML1 volumes, making aggregate backup copies of data sets that your operation will need if your installation is damaged, and making fast replication backup versions for sets of storage groups.
Availability management of SMS-managed storage , which describes the tasks to be performed and the results of processing for availability management of data sets managed by SMS. Availability management of non-SMS-managed storage , which describes the tasks to be performed and the results of processing for availability management of data sets not managed by SMS. Aggregate backup and recovery support ABARS , which describes the command-driven functions that back up and recover a user-defined group aggregate group of data sets.
Making disaster backup copies of DFSMShsm-owned tape volumes , which describes how to make backup copies of DFSMShsm-owned, cartridge-type, single-file-format tape volumes and how to recover those volumes. Other availability management considerations , which describes aspects of availability management that deserve consideration but are peripheral to the discussions in the preceding topics. Availability management procedures , which describes procedures for starting and stopping availability management under varying conditions.
Functions of availability management: Automatically make backup copies of individual changed data sets on DFSMShsm-managed volumes. This is known as incremental backup. You can specify how frequently to back up data sets on a data set basis for SMS-managed data sets and on a system-wide basis for non-SMS-managed volumes.
You can specify on a system-wide basis how often backup runs. You can dump different groups of volumes on different days with different periods for the number of days between dumps. Allow your customers to issue commands to recover their own data sets.
See Inline backup. By command, back up user data sets. By command, back up data sets of an application to tape so they can be taken to another computer site for recovery. By command, recover user data sets or data sets of an application to their original system environment at another computer site. By command, restore a volume from a dump copy and update the restored volume from later incremental backup versions.
By command, recover a specific data set from either a dump copy or an incremental backup version. By command, create a fast replication backup of a copy pool. Automatically or by command, create a dump copy of a fast replication DASD backup version By command, recover volumes that have a fast replication backup version.
By command, recover data sets from fast replication backup versions. You can define the following types of tape or DASD backup volumes to DFSMShsm: Daily backup volumes: Daily backup volumes are assigned to a specific day in the backup cycle and contain the backup versions created on that day.
DFSMShsm creates these backup versions during the backup of a level 0 volume or during the backup of migrated data sets. However, the daily backup volume used to contain these manually backed up versions does not necessarily correspond to the day in the backup cycle when DFSMShsm created the backup version.
Instead, the daily backup volume corresponds to the day in the backup cycle that DFSMShsm moved the backup version from its temporary location on an ML1 volume to a daily backup volume.
Fast replication target volumes: Fast replication target volumes contain the fast replication backup copies of DFSMShsm-managed volumes. Fast replication target volumes are defined with the SMS copy pool backup storage group type. Spill backup volumes: Spill backup volumes contain older backup versions of data sets. Tape spill volumes also receive all valid backup versions of data sets when a tape backup volume is recycled.
Unassigned backup volumes: DFSMShsm uses unassigned volumes whenever it needs more daily or spill backup volumes. There are two types of unassigned volumes: unassigned daily backup volumes and unassigned backup volumes. Unassigned daily backup volumes are those volumes defined to DFSMShsm as daily backup volumes but not associated with any day in the backup cycle.
DFSMShsm can use these volumes only as daily backup volumes, but DFSMShsm determines which day in the backup cycle the volume should be assigned to when it first uses the volume. Unassigned backup volumes are those volumes defined to DFSMShsm as backup volumes but not specified as daily or spill backup volumes.
When it first uses unassigned backup volumes, DFSMShsm assigns the volumes as daily or spill backup volumes.
DFSMShsm Storage Administration Guide
DFSMShsm Storage Administration Reference