Does the DD statement that specifies MOD also specify RLSE? When the dataset runs out of space, is it because of 16 extents or no more usable room on the pack? What is the secondary extent type (blocks, tracks, cylinders, other)? Does your shop run a "space recovery utility" periodically to trim back datasets that are over-allocated and under-consumed?
Once again, RLSE is an attribute of the current allocation, not of the dataset itself. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lynd, Eugene C. Sent: Wednesday, September 01, 2010 8:03 AM To: [email protected] Subject: Re: How to determine use of RLSE in dataset allocation <snip> GENERAL DATA: CURRENT ALLOCATION: Volume serial: FSD102 Free: 38.8% Allocated tracks: 494 Device type: 3390-27 32760 cylinders Allocated extents: 3 Organization: PS SEQ Secondary extent: 750 Record format: FB Max. dir. blocks: Record length: 132 X 212 Block size: 27984 CURRENT UTILIZATION: Management class: Y3PB3QNG Used tracks: 494 Storage class: STANDARD Used dir. blocks: Data class: SETDSORG Used extents: 3 RACF protection: GENERIC Number of members: Blocks per track: 2 It is updated with MOD every night, but periodically runs out of space - despite a generous secondary allocation. When I rebuild it I Recreate it with LIKE, and didn't notice what I still only assume - that I originally allocated it with RLSE. The output above is from a local Tool of mine. I thought it would be nice to show if the dataset was Subject to RLSE. (I assume I can solve the nightly problem by Reallocating without RLSE.) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
