Peter, Start using PDS-E 😊
I used to like to have maxextents set to 8. That worked for all but the most pathological of PDSs with many members updated per day. PDS-E ended up resolving that (but Lizette has some horror stories about large PDS-E). Extent reduction as I recall it does not need adjacent extents. It's was a migrate/recall cycle to ML1 that reallocates the Primary as the size of the current data set. Are you thinking of DEFRAG? Ron -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: Tuesday, January 30, 2018 10:56 AM To: [email protected] Subject: [IBM-MAIN] AW: Re: AW: Re: Dataclass question >What is your concern with secondary extents on a PDS? I don't have a problem with secondary extents as such. It is only that I fear the 16 extent limit may me reached sooner with space release. Extent reduction may help, but only if the device has low "extent" allocation activity. Otherwise, chances are lower to get an adjacent extent. >I don't think my "more appropriate" is an absolute in the same way as >"not appropriate for PDSs in any form." Yeah, my statement was probably too absolute :-) I just don't see a problem with highly overallocated space of PDSs. YMMV, though. -- 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
