 |
DFSMShsm Commands >> | |
The following information applies to both SMS and non-SMS-managed data sets.
Task: List selected information from the MCDS and BCDS.
You can issue the HLIST command without specifying any parameters to list all of your migrated data sets. Or, you can list information from the following categories, using the HLIST command:
Backup volume information from the BCDS
The HLIST command can process only one of the four categories at a time. If you specify more than one category, the HLIST command processes the category of the highest order of preference. The following is the order of preference:
PRIMARYVOLUME, MIGRATIONVOLUME, or VOLUME BACKUPVOLUME USER DATASETNAME or LEVEL
Ex. HLIST DATASET('SEG1T.BMS.CNTL') BCDS TERMINAL HLIST DATASET ('SEG1T.BMS.CNTL') MCDS TERMINAL HLIST DATASET('SEG1T.BMS.CNTL') BOTH TERMINAL Output : DSN=SEG1T.BMS.CNTL MIGVOL=HSMD01 DSO=PO SDSP=NO LAST REF=99/02/16 MIG=99/02/16 TRKS=000001 2K BLKS=0000002 TIMES MIG=001 16K BLKS=****** LAST MIGVOL=****** *** Recovering a Backup Version or a Dump Copy of a Data Set
Task: Recover a backup version or a dump copy of one or more data sets.
When recovering SMS-managed or non-SMS-managed data sets, you can do any of the following tasks: DFSMShsm- managed volumes.
You cannot recover the backup version of a cataloged VSAM data set that is currently migrated, as specified in the computing system catalog or the MCDS, until DFSMShsm recalls or deletes the migrated VSAM data set. Ex. HRECOVER 'SEG1T.BMS.CNTL' VERSION(1) REPLACE TOVOLUME(DEVD04) UNIT(3390)
Recalling a Data Set In this example, you are issuing the HRECALL command from a TSO session to recall the data set SEG1T.BMS.CNTL to a DFSMShsm-managed volume. Ex. HRECALL 'SEG1T.BMS.CNTL' VOLUME(DEVD04) UNIT(3390) HRECALL 'SEG1T.BMS.CNTL' REPLACE TOVOLUME(DEVD04) UNIT(3390) Recalling Two SMS-Managed Data Sets and Not Waiting for Completion In this example, you are issuing the HRECALL command to recall two SMS-managed data sets, ELMST.TEXTVER3.TEXT and ELMST.VER1TEXT.LIST. Because the data are SMS-managed, SMS directs the return of the data sets. You do not want to wait for DFSMShsm to complete the recall of the data sets.
Example : HRECALL ('ELMST.TEXTVER3.TEXT','ELMST.VER1TEXT.LIST') NOWAIT HMIGRATE -Migrating Data Sets This topic describes how to migrate data sets using ISMF or TSO. This command applies to both SMS-managed and non-SMS-managed data sets and is intended to supplement the automatic functions of DFSMShsm. Using TSO Commands The following information applies to both SMS-managed and non-SMS-managed data sets.
Task: Migrate one or more data sets to migration volumes.
The data set migrates to a level 1 migration volume unless you specify the MIGRATIONLEVEL2 parameter in the command or you are in an environment that migrates directly to migration level 2 volumes. An SMS-managed data set, for example, can migrate directly to a level 2 volume if defined to do so by a management class parameter. You can cause a data set on a level 1 migration volume to migrate to a level 2 migration volume if you specify a data set that is already on a level 1 migration volume and you specify the MIGRATIONLEVEL2 parameter.
Command migration of SMS-managed data sets is available for eligible data sets only. Data set eligibility is determined by an SMS management class attribute. Example : HMIG (‘SEG1T.BMS.CNTL’) ML1 HMIG (‘SEG1T.BMS.CNTL’) ML2 Notes:
1. Parentheses are required only when multiple dsnames are specified.
2. Password does not apply to SMS-managed data sets. Backing Up a Data Set Task: Create a backup version for a specific data set, a list of data sets, or a filter specification.
Only eligible data sets are backed up. Whether an SMS-managed data set is eligible to be backed up by command is determined by SMS management class attributes. For a non-SMS-managed data set, eligibility for back up is determined by the VERSIONS parameter of the HALTERDS command.
If the data set to be backed up is currently allocated, DFSMShsm attempts to Allocate it. DFSMShsm does not try to reallocate the data set at the end of BACKDS processing.
Note: When you backup a data set, it must fit on a migration level 1 volume. If it does not, the command fails Example : The following is the Syntax of the HBACKDS command for SMS-managed data sets: HBACKDS ('SEG1T.ARCH.CNTL') NOWAIT you can use following options WAIT EXTENDRC NOWAIT CHANGEDONLY Note: The HBACKDS command will not back up a migrated data set if CHANGEDONLY is specified. The following diagram presents the syntax of the HBACKDS command for non-SMS-managed data sets: HBACKDS ('SEG1T.ARCH.CNTL') UNIT(3390) VOLUME(volser) NOWAIT You can use use following options WAIT EXTENDRC NOWAIT CHANGEDONLY HDELETE - Deleting Migrated Data Sets This topic describes how to delete migrated data sets using ISMF, TSO, or a user macro. This command is intended to supplement the automatic functions of DFSMShsm. Using ISMF,TSO, User Macro using TSO The following discussion applies to both SMS-managed and non-SMS-managed data sets.
Task : Delete one or more migrated data sets from a migration volume.
Usage Notes: DFSMShsm deletes the data set without recalling it to a DFSMShsm-managed volume. When DFSMShsm deletes the data set, it maintains any backup versions of the data set and the information in the BCDS. You cannot delete data sets from DFSMShsm-managed volumes or backup volumes with this command. This command deletes both the migrated data set and the data set's catalog entry.
RACF Authority: If you want to delete a RACF-protected data set, you must have RACF ALTER authority to the data set.
Abbreviation: The minimum abbreviation for the HDELETE command is HDEL.
You can use following options PURGE WAIT NOWAIT EXTENDRC Example : HDELETE 'seg1t.bms.jcls' WAIT HDELETE 'seg1t.bms.jcls' NOWAIT HDELETE 'seg1t.bms.jcls' PURGE HDELETE 'seg1t.bms.jcls' WAIT EXTENDRC
Changing the Backup Conditions for a Data Set SMS-managed storage controls the frequency of backup and the number of versions retained for each data set through the management class attributes. For non-SMS-managed storage, frequency and versions are a processor-wide specification. However, you can control the frequency and versions for individual data sets with the (H)ALTERDS command. You can control the frequency and the versions independently of each other. The forms for the command are:
ALTERDS dsname . . . FREQUENCY(days) ALTERDS dsname . . . VERSIONS(limit) ALTERDS dsname . . . FREQUENCY(days) VERSIONS(limit) HALTERDS dsname . . . FREQUENCY(days) HALTERDS dsname . . . VERSIONS(limit) HALTERDS dsname . . . FREQUENCY(days) VERSIONS(limit)
Non-DFSMShsm-authorized and DFSMShsm-authorized users can use the HALTERDS form of the command. Only DFSMShsm-authorized users can use the ALTERDS form of the command. ADDVOL Command : The ADDVOL command is used to define DFSMShsm-owned volumes and non-SMS-managed volumes to DFSMShsm. It is not used for SMS-managed volumes. Note: A maximum of eight processing units can ADDVOL a primary or migration volume at the same time. Defining ML1 Volumes to DFSMShsm in all processing Unit ADDVOL ML1001 UNIT(3390) - MIGRATION(MIGRATIONLEVEL1 - SMALLDATASETPACKING) THRESHOLD(85) ADDVOL ML1002 UNIT(3390) - MIGRATION(MIGRATIONLEVEL1 - SMALLDATASETPACKING) THRESHOLD(90) ADDVOL ML1003 UNIT(3390) - MIGRATION(MIGRATIONLEVEL1 - NOSMALLDATASETPACKING) THRESHOLD(90) Defining Automatic Dump of ML1 volume in Processing ADDVOL ML1001 UNIT(3390) MIGRATION(AUTODUMP - (ONEWEEK,TWOWEEK)) ADDVOL ML1002 UNIT(3390) MIGRATION(AUTODUMP - (ONEWEEK,TWOWEEK)) ADDVOL ML1003 UNIT(3390) MIGRATION(AUTODUMP - (ONEWEEK,TWOWEEK)) Defining Primary Volumes for Migrating And Backup in processing Unit 2 ADDVOL GP0001 UNIT(3390) PRIMARY(AUTOMIGRATION AUTOBACKUP - AUTORECALL MIGRATE(12)) THRESHOLD(95 80) ADDVOL UG1001 UNIT(3390) PRIMARY(AUTOMIGRATION AUTOBACKUP - NOAUTORECALL MIGRATE(12)) THRESHOLD(95 80) DELVOL Command Deleting a Primary Volume : In this example, a primary volume (added using the ADDVOL command or SMS-managed) is deleted from DFSMShsm control. Example : DELVOL VOL005 PRIMARY Deleting a Migration Level 1 Volume : In this example, a migration level 1 volume is deleted from DFSMShsm control. Example : DELVOL MIG003 MIGRATION Deleting a Tape Migration Level 2 Volume : In this example, a tape migration level 2 volume is purged from DFSMShsm if it does not contain any valid data. Example : DELVOL TML203 MIGRATION(PURGE) Deleting a DASD Migration Level 2 Volume : In this example, a DASD migration level 2 volume is purged from DFSMShsm. Example : DELVOL DML201 MIGRATION(PURGE) Deleting a Tape Backup Volume Example : DELVOL TAPE01 BACKUP(PURGE)  |