View previous topic :: View next topic |
Author |
Message |
BobGilbert Beginner
Joined: 12 Sep 2006 Posts: 24 Topics: 10
|
Posted: Fri Jul 31, 2015 10:35 pm Post subject: VRS Rules and expired datasets |
|
|
Yes our shop uses retention periods, it is what it is....
I can see 275,000 expired files out there and we continually have attempted to get them cleaned up and deleted. I am being told this is a manual process. Our support indicates it is due to VRS rules, when I look at the rule and other documentation it appears a small change would allow the expired tapes to expire, looking for someone to indicate this:
If they change until expired=yes will this allow the expired datasets to expire? I read in a SHARE presentation this is a "or" statement meaning until not cataloged or expired? Currently I believe the expire but not being un-cataloged.
Thanks!
Code: |
Command ===>
Data set mask . : '**' GDG . : NO
Job name mask . :
Count . . . : 99999 Retention type . . . . . : CYCLES
While cataloged . . . . . : YES
Delay . . . : 0 Days Until expired . . . . . . : NO
Location . . . . . : HOME
Number in location : 99999
Priority . . . . . : 0
Release options:
Next VRS in chain . : Expiry date ignore . . . : NO
Chain using . . : Scratch immediate . . . . : NO
Owner . . . . . : DFRMM
Description . . : WHILECAT
Last reference : 2015/205 07:14:21 ( YYYY/DDD HH:MM:SS )
Delete date . . : 1999/365 ( YYYY/DDD )
Last Change information:
Date . . . . . . : 2015/205 Time . : 07:20:12 System : ESYS
User change date : 2013/332 Time . : 06:37:43 User ID : XXXXXX |
|
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Mon Aug 03, 2015 10:21 am Post subject: |
|
|
BobGilbert,
I am not an RMM expert but I think the issue is with Retention Type. Shouldn't it be DAYS instead of CYCLES?
Single-dataset cycles are always problematic
• Usually only current cycle cataloged to MVS
• Older cycles must be referenced by volser
• GDG's were designed to replace CYCLES
Can you run the VRSEL REPORT and see the DROP reason? _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
|
|