Panvalet Library . Not enough Data Blocks

Products

• Database Analyzer (IMS Tools)
• Mainframe Configuration Manager for IMS for z/OS
• IMS TOOLS - MISC
• Compress Data Compression (IMS Tools)
• Database Analyzer for IMS for z/OS
• Database Copier for IMS for z/OS
• Database Organizer for IMS for z/OS
• Mainframe Extended Terminal Manager (IMS Tools)
• High Performance Recovery for IMS for z/OS
• Database Organizer (IMS Tools)
• Mainframe Program Restart Manager for IMS for z/OS
• Secondary Index Builder for IMS for z/OS
• Secondary Index for IMS for z/OS
• JARS
• JARS Resource Accounting
• JARS SMF Director
• JMR
• MIM Resource Sharing (MIM)
• MIM Data Sharing (MII)
• MIM Tape Sharing (MIA)
• MIM Message Sharing (MIC)
• Nastel AutoPilot for WebSphere MQ
• Panvalet
• QuickFetch
• Raps VSE
• Scheduler VSE
• SMR
• SOLVE:Operations Automation
• SOLVE:Access Session Management
• SOLVE:FTS
• SYSVIEW Performance Management
• NXBRIDGE - SYSVIEW/ENDEVOR
• SOLVE

Issue/Introduction

We just received an issue reported by application team about a Panvalet library. They are receiving NOT ENOUGH DATA BLOCKS.
This Panvalet library already at 130,841 blocks.
According to the doc the max TOTAL BLOCKS can be 131,071 .. which means we would not be able to expand this library anymore. 
Is there a palliative solution, like a clean up/compress on the library ?

Environment

Release:
Component: PANVLT

Resolution

Two options are available -
1)  Change the STATUS of members in the Panvalet library to DISABLED or INACTIVE and then DELETE the members.

See Error Recovery Procedure One Option One for more information on how to change the STATUS of Panvalet library members and DELETE them. 

 
2) Increase the blocksize used by the Panvalet library.

• Run PAN#2 ++ATTRIBUTE  job to determine the current block size of the Panvalet library.
• Use the Table of Block Sizes chart to determine the next larger block size

Review these considerations from Initializing the Library on block sizes:

Generally, if storage is not a problem, specify a large block size. The large block size maximizes the storage capacity of the DASD device, whereas a smaller block size means some loss in storage due to inter-record gaps (true of all DASD files). CA Panvalet stores only one member in a block. Therefore, the chosen block size should not greatly exceed the average compressed space anticipated for most members. Too large a block size wastes considerable disk space.

Additional Information

See KB000027431 for instructions on how to expand a Panvalet library