Even in the case of CONTIG, allocation would create the primary space as requested, but subsequent merged contiguous extents and/or the RLSE option, could also leave behind a different primary extent after CLOSE.
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Terry Sambrooks Sent: 06 May, 2015 16:21 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Primary allocation of a dataset Hi As several people have already alluded IT IS NOT POSSIBLE to retrieve the Primary Request for SPACE as it IS NOT recorded in the DSCB. There is no need to store this information as it is either available and used or it is not in which case the data set is not created. The Secondary Request has to be stored in the DSCB for subsequent use if the need arises. The FIRST EXTENT will only equate to the Primary Request if CONTIG were specified at allocation time. If CONTIG is not specified then the system will attempt to allocate the Primary in up to 5 extents. When LISTDSI and ISPF 3.2 are used they only report the first extent, which may only be a subset of the Primary Request. Kind Regards - Terry Director KMS-IT Limited 228 Abbeydale Road South Dore Sheffield S17 3LA UK Reg : 3767263 Outgoing e-mails have been scanned, but it is the recipients responsibility to ensure their anti-virus software is up to date. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
