Basically DFSMShsm is an EDM (External Data Manager) and manages its own tapes and needs to communicate with the TMS (Tape Management Subsystem), in this case DFSMSrmm that the tape has changed status, in this case from private to scratch. There's a nice summary @ https://www.ibm.com/support/pages/tapes-released-scratch-without-hsm. Put simply, safeguard in an DFSMSrmm environment, the EDGTVEXT exit is used, the sample provided in the DFSMSrmm product resources works well. If you're using another TMS (E.g. CA-1, TLMS, et al), even in a DFSMSrmm migration scenario, use the ARCTVEXT exit. In a DFSMSrmm migration scenario, ARCTVEXT would take preference and would need to call EDGTVEXT once its processing was complete, to update DFSMSrmm, while running both TMS in parallel during the migration process.
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
