CA Tape Encryption

Expand all | Collapse all

TMSXEXP Exit for TMSEXPDT

  • 1.  TMSXEXP Exit for TMSEXPDT

    Posted 08-23-2012 02:35 PM
    I am wondering if anyone is using the TMSXEXP exit to set/enforce retention periods. And if so would anyone be willing to share their coding in this area.
    We are in the processing of looking into the various options that are available to better manage tape retentions and to enforce company standards with
    regards to how long files can and should be saved.


  • 2.  RE: TMSXEXP Exit for TMSEXPDT

    Posted 11-16-2012 11:45 AM
    I am wondering why you want to use an exit to enforce retention standards.

    We have the TMC update functons under RACF control with only a few people allowed to update it. We have the option set to have the RDS override the JCL. Only a limiited number of people have update access to the RDS. The RDS is processed daily to enforce the rules for all newly created tape datasets. (Created since the last CA1 maintanance cycle.)

    An exit would need to be tested with each upgrade. With other exits that were needed to support hardware, we have had things fiail after a system or subsystem upgrade occured. With the RDS controling expiration, it is less likely that an upgrade will cause an issue.

    Have a Terrific day!