On Thu, 7 Mar 2019 14:25:07 -0600, Bruce Schaefer wrote: >Paul, I have not found any IBM doc to indicate that PDSE solves the problem. >The JES2 Init&Tuning Guide simply says: >To ensure performance and integrity, do not: >v Allocate additional extents or release extents >v Compress a PROCLIB data set >v Defragment (move) a volume containing a PROCLIB > >My understanding of PDSE is that all enqueue's must be released before SMSPDSE >will reclaim space. Do JES2 (with NODSI in PPT) and SMSPDSE play well? This >proclib (and our VTAMLST) is always in use. > Since the Tuna is directed to PDS, I suspect the JES2 developers haven't yet heard of PDSE.
>I don't have a response to your questions on STOW. > My understanding is that that after any individual member is replaced or deleted STOW DISC makes the space available for reclaim even while the data set is open and enqueued. I suspect (see above) that JES does not issue STOW DISC. If JES is processing the same member in multiple threads, would a STOW DISC by one of them pose an integrity threat to the others? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
