> You will never be able to determine the original primary allocation amount, > because it is not recorded. When the primary allocation is done, it can be > done in one or more extents and adjacent secondary extents can be merged > together into 1 extent. Furthermore after close of the dataset, idle space can > be released. From that moment on, all what is left is the status of the > dataset > at that moment, which is the result of any or all of the above actions, but > you > cannot determine the requested primary allocation from it.
The strange part is that TSO 3.2 option seems to be able to recreate this info. If I allocate a dataset with a recordlength and blocksize of 100 bytes, a primary allocation of 14 KB and a secondary allocation of 2KB it is reported as: 1st extent kilobytes: 14 Secondary kilobytes : 2 Current Allocation Allocated kilobytes : 14 Allocated extents . : 1 The DSCBs in the VTOC contains a secondary allocation of 2K and an allocation in one extent of 2 tracks. Where did 3.2 find my primary allocation of 14K? Fred! ----------------------------------------------------------------- ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. ----------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
