Peter, PDSE's cannot be compressed by anyone but they still are compressed by the system automagically (compress here being the term IBM use for the space reclaim). PDSEs get fragmented and the fragments can become unusable. Free space (from deleted or replaced members) is not immediately added to the spare pool as there may still be pointers into the PDSE to members that have been deleted (connections). This compress is done at open for output when it is the only open for output and there are no connections. ISPF has some recovery trickery built in to invoke this rule.
I first ran into this issue with Netview. I was updating my Rexx and eventually it said there was no room left in the PDSE (D37 I believe). I read up on it then. Netview luckily provides a command to free and reallocate all its libraries so they get compressed at the next open for output I did (from ISPF). Regards, Alan Watthey -----Original Message----- From: Peter Hunkeler [mailto:[email protected]] Sent: 20 December 2017 7:09 pm Subject: AW: Re: Cobol upgrade 6.2 linklist >Since it is a PDSE dataset it will always have an active connection and so will not be able to perform >automatic compression. >Thus it will get full. Compress PDSE's? This is the (single, maybe) advantage of PDSEs: There is no need to compress. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
