Is there a way that we can avoid creating such HUGE test libraries?
Some of the PDS hold 15,000 tracks and have only 2 pieices of JCL in them.How can I stop people from allocating libraries a huge size?
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Unless there is info you haven't posted, the reason the test libraries are so large is because you/someone made them that way. . .
What reason is there that they cannot be re-allocated at some small fracton of the problem size?
How can I stop people from allocating libraries a huge size?
What i have done in similar situations (with management approval when i was not the manager) is to first ask them not to. If this does not work, send them an e-mail explaining that when these are found, the will be deleted and copy their boss and your boss. Include some wording about the massive waste of dasd space. Be aware that some whiny people will convince their boss that to properly allocate these datasets will slow them down (a lie, but often gotten away with) and their boss will say they cannot afford the delay.
You might consider running a job to identify these (easier if there are naming standards that makes identification easy(ier) and automatically re-size them over the weekend as part of the system backup/reorg time.
DFDSS (ADRDSSU) RELEASE or COMPAKTOR RELEASE jobs may sort these out by releasing overallocated space.
Other options are to get the Storage people to put a size check in the ACS routines and prevent allocations over a certain size, or assign a Dataclas that has the OVERRIDE SPACE attribute that forces Dataclas space values to override JCL