VSE does not support the Format-? (3? 5?) VTOC record that inventories free space. "Traditional" DASD space management in VSE involves a chart on the sysprog's wall showing which tracks of each volume are free. All "traditional" DASD space allocation in VSE is what z/OS JCL calls ABSTR (is that the right spelling?). A backstop against "oops" is that VSE datasets are usually defined with an expiration date (unlike z/OS) which causes VSE to complain if one attempts to overwrite them.
The more modern approach in VSE uses large VSAM extents as "sub-regions" of a disk. VSAM then allocates space for sequential datasets within this area. I think there are also some third-party solutions. I know I set out to write one once (but did not complete the project). Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Saturday, February 27, 2010 8:07 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Item on TPF On Fri, 26 Feb 2010 20:58:32 -0500, George Henke wrote: >IBM was about to sunset VSE a few years ago until it found out that in >mainland China, VSE was the operating system of choice. >... >Unfortunately, it has always lacked at least one major control block, the >DEB and so tech support has always been shackled with the burden of manually >keeping track of every cylinder and track. > ??? I was aware of the deficiency some decades ago. I'm not sure what it has do do with DEB; it seems to be more related to the DSCB in the VTOC. And I thought it was merely that VSE development abdicated the responsibility of automating DADSM. >Though now it has been mitigated. > At last? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
