z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Using the VRSEL retention method to manage DFSMShsm tapes

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

To use the VRSEL retention method to manage DFSMShsm tapes, you must define movement and retention policies with vital record specifications by specifying data set names or volume serial numbers. To define vital record specifications, use the RMM ADDVRS subcommand. See z/OS DFSMSrmm Managing and Using Removable Media for information about the RMM ADDVRS subcommand and the operands you can specify.

When specifying the RMM ADDVRS command operands, it might be helpful to think about the operands in three categories:
  • Operands to define retention policies, including COUNT and CYCLES, that are used in these examples
  • Operands to define movement policies, including DELAY, LOCATION, and STORENUMBER, that are used in these examples
  • Operands to manage the vital record specification itself, including DELETEDATE and OWNER, that are defaults in the RMM ADDVRS subcommand
    • DELETEDATE(1999/365) specifies the date when the vital record specification no longer applies. The default value is 1999/365 which means the vital record specification is permanent. It can only be manually deleted if it is no longer appropriate.
    • OWNER(owner) specifies the user ID that owns the vital record specification.

As shown in the examples that follow, you can specify data set name masks in vital record specifications to manage migration, backup, dumps, TAPECOPY, DUPLEX tape feature, tapes written by ABARS, ABARS accompany tapes, and control data set version backups. You can tailor the examples to define policies for your DFSMShsm tapes. As you gain more experience defining vital record specifications, you will see that there might be several ways to define the retention and movement policies you desire.

The examples use the current DFSMShsm data set naming formats. Some old name formats were in use prior to APAR OY20664. APAR OY20664 required you to use PATCH commands to use the new format. The new format is standard in DFSMShsm. If you have occurrences of the old naming formats, you might need to define vital record specifications that use both naming formats. Delete the vital record specifications with the old naming format once the old names no longer exist. See z/OS DFSMShsm Implementation and Customization Guide for current DFSMShsm data set naming formats.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014