View previous topic :: View next topic
|
Author |
Message |
MadHadder
New User
Joined: 09 Apr 2008 Posts: 9 Location: Virginia
|
|
|
|
I'm having an issue where my DSNB's are growing at a very high rate and its getting to the point that it might start causing problems. Has anyone ran into a case like this where the problem is not the expired DSNB’s but rather the few cataloged data sets on a set of tapes which in turn keeps the expired DSNB’s. If so does anyone know a way to correct something like this. |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 580 Location: London
|
|
|
|
I don't think DSNB's on multi-volume multi-file tapes expire or release until everything in the set finally expires.
Is this a virtual or native tape environment? Maybe your virtual tape sizes are to small? Maybe there's bad JCL around that doesn't cater for a virtual tape environment. Have a look at the jobs creating the tape files. It should become clear if you run a few TMSGRW jobs collecting CJOB, CDATE, DSN etc. Maybe someone is 'reusing' one or more of the datasets in the set thus never allowing the rest to expire? |
|
Back to top |
|
|
|