Table of Contents

z/OS DFSMShsm Managing Your Own Data

Previous topic | Next topic | Contents | Contact z/OS | Library | PDF

Contents (exploded view)

z/OS DFSMShsm Managing Your Own Data
SC23-6870-00

Introduction to DFSMShsm

How are DFSMShsm commands protected?

Methods of performing tasks

Using ISMF to perform tasks

Using DFSMShsm user macros

Space management

How does DFSMShsm manage space?

Availability management

How does DFSMShsm ensure data availability?

Space management and availability management capabilities

Space-saving functions

Associated data sets

How does DFSMShsm know where my data sets are located?

How do I know where my data sets are located?

Understanding syntax diagrams and using DFSMShsm commands

How to read syntax diagrams

Using DFSMShsm commands

Interacting with DFSMShsm

Incompatibilities caused by DFSMShsm

Submitting commands in batch mode

Example JCL for submitting an DFSMShsm command

Introduction to DFSMShsm user tasks

DFSMShsm user tasks

HALTERDS: Changing data set parameters

dsname: Specifying the name of the data set being altered

Optional parameters

FREQUENCY and SYSFREQUENCY: Specifying the frequency for creation of backup versions for changed data sets

VERSIONS and SYSVERSIONS: Specifying the number of backup versions to maintain

Examples of different ways to code the HALTERDS command

HBACKDS: Backing up data sets

dsname: Specifying the name of one or more data sets to be copied for backup

Optional parameters

CHANGEDONLY: Specifying whether to back up only changed data sets

DATE: Specifying the address of a field containing the date

EXTENDRC: Requesting an extended set of return and reason codes

GENVSAMCOMPNAMES: Overriding SETSYS DSBACKUP(GENVSAMCOMPNAMES)

NEWNAME: Specifying a backup version of a specified data set

RETAINDAYS: Specifying a number of days to retain a backup copy

Explanation

SPHERE: Specifying whether components of a VSAM data set will be backed up with the base cluster

TIME: Specifying the address of a field containing the time

UNIT: Specifying the type of device

VOLUME: Specifying the volume where the data set resides

WAIT and NOWAIT: Specifying whether to wait for the HBACKDS command to be completed

TARGET: Specifying the media target of the backup data set

CC: Tailoring concurrent copy backups for SMS and non-SMS data sets

Examples of different ways to code the HBACKDS command

HBDELETE: Deleting backup versions

Optional parameters

FROMVOLUME: Specifying the volume on which the data set resided when the backup versions were created

Examples of different ways to code the HBDELETE command

HCANCEL: Canceling a queued request

Cancel queued requests

REQUEST: Specifying the DFSMShsm request number to be canceled

USERID: Specifying that all requests submitted by a particular user be canceled

DATASETNAME: Specifying that all requests submitted to process a particular data set be canceled

Examples of different ways to code the HCANCEL command

HDELETE: Deleting migrated data sets

dsname: Specifying the data set to delete

Optional parameters

PURGE: Specifies deletion of migrated data sets within their retention periods

WAIT and NOWAIT: Specifying whether to wait for the data set to be deleted

EXTENDRC: Requesting an extended set of return and reason codes

Examples of different ways to code the HDELETE command

HLIST: Listing information from the BCDS and MCDS

Listing information from the BCDS and MCDS in TSO

Syntax

Required parameters

BACKUPVOLUME: Requesting a list of backup volume entries

DATASETNAME and LEVEL: Requesting a list of data set entries

MIGRATIONVOLUME, MIGRATIONLEVEL1, MIGRATIONLEVEL2, PRIMARYVOLUME, and VOLUME: Requesting a list of primary and migration volume entries

USER: Requesting a list of user entries

Optional parameters

BACKUPCONTROLDATASET, MIGRATIONCONTROLDATASET, and BOTH: Controlling the source of information listed

INCLUDEPRIMARY: Requesting a list of entries for a data set that has migrated even though the data set might have been recalled

OUTDATASET, SYSOUT, and TERMINAL: Specifying the location of output for the list

SELECT: Requesting a list of only those data set entries that meet selection criteria

SELECT(MIGRATIONLEVEL1 | MIGRATIONLEVEL2 | VOLUME(volser)): Selecting entries based on the volume where the data set resides

SELECT(SMALLDATASETPACKING | NOSMALLDATASETPACKING): Selecting entries based on whether the data sets migrated to an SDSP data set

SELECT(VSAM): Specifying the data set organization

SUMMARY: Requesting a summary only

Examples of different ways to code the HLIST command

Sample lists from the HLIST command

HMIGRATE: Migrating data sets

dsname: Specifying the name of the data set that is to migrate

Optional parameters

MIGRATIONLEVEL2: Specifying migration of a data set directly to a level 2 volume

WAIT and NOWAIT: Specifying whether to wait for data set migration

EXTENDRC: Requesting an extended set of return and reason codes

Examples of different ways to code the HMIGRATE command

HQUERY: Listing pending requests

Using TSO commands

DATASETNAME: Specifying a list of requests by data set name

REQUEST: Specifying a list of requests by request number

Examples of different ways to code the HQUERY command

Messages from the HQUERY command

HRECALL: Recalling data sets

dsname: Specifying the name of the data set to be recalled

Optional parameters

DAOPTION: Selecting target volume track length

EXTENDRC: Requesting an extended set of return and reason codes

UNIT: Specifying the type of unit for the receiving volume

VOLUME: Specifying the volume to receive the recalled data set

WAIT and NOWAIT: Specifying whether to wait for the data set to be recalled

Examples of different ways to code the HRECALL command

HRECOVER: Recovering data sets

dsname: Specifying the name of the data set to be recovered

Optional parameters

DAOPTION: Selecting target volume track length

EXTENDRC: Requesting an extended set of return and reason codes

FROMVOLUME: Specifying the volume from which the backup version or dump copy of a data set was created

GENERATION, DATE, and VERSION: Specifying the particular data set backup version to recover

NEWNAME: Specifying a new data set name for the recovered data set

REPLACE: Specifying that the recovered data set version is to replace any existing data set of the same name

TOVOLUME: Specifying the volume to receive the recovered data set

UNIT: Specifying the type of unit for the receiving volume

WAIT and NOWAIT: Specifying whether to wait for the data set to be recovered

Examples of different ways to code the HRECOVER command

DFSMShsm application programming interface

Using DFSMShsm user macros

ARCHBACK: Backing up a specific data set

ARCHBDEL: Deleting a backed up version of data sets

ARCHDEL: Deleting migrated data sets

ARCHMIG: Migrating data sets

ARCHRCAL: Recalling a data set

ARCHRCOV: Recovering a data set

ARCHSEND: Sending a command to DFSMShsm

ARCXTRCT: Extracting data from DFSMShsm

Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites

Copyright IBM Corporation 1990, 2014