Using DFSMShsm with DFSMSrmm

The z/OS® component, DFSMSrmm provides enhanced management for tape volumes that DFSMShsm uses for each of its tape functions. Precisely how the two products work together depends on how you use each of them in your installation.

DFSMShsm can tell DFSMSrmm when it no longer requires a tape volume or when a tape volume changes status. When DFSMShsm is using DFSMSrmm, it cannot mistakenly overwrite one of its own tape volumes if an operator mounts a tape volume in response to a request for a non-specific tape volume.

DFSMSrmm supports any of the naming conventions DFSMShsm uses for its tape data sets, and all DFSMShsm options—with the exception of password security on tape volumes—are supported.

DFSMSrmm lets you use a system scratch tape pool or a DFSMShsm-managed tape pool. DFSMSrmm manages the movement of disaster recovery and vital record data for both pool types. It also provides a way to retain DFSMShsm tapes until the contents are invalid.

You must let DFSMShsm decide whether a tape volume contains valid data and whether it should return to the scratch pool or DFSMShsm-managed tape pool.

You should use vital record specifications because you can avoid expiration dates, operator message handling, and the need to reinitialize tape volumes before you can reuse them. However, if you are using a DFSMShsm-managed tape pool, you can use expiration date protection without this overhead; DFSMShsm can override expiration protection for its own tape volumes.

DFSMShsm uses the DFSMSrmm EDGTVEXT interface to maintain the correct volume status. DFSMSrmm provides a programming interface so you can use the DFSMShsm exit.