On 2/14/2012 9:42 AM, Thomas Berg wrote:
AFAICS, what needs to be changed is just the interpretation of the SPACE parm and the actual allocation on disk at the time of execution. -> There have been changes in the JCL "language" the latest Years: LIKE, DCB subparms outside of the DCB parm, etc. This could obviously be done. -> There can't be that many places that does the allocation of the space on disk. Note that there is no change of cataloging as such, just the process of adding/extending the extents as the dataset is expanding. There is no need to change the old code more than allowing a "branch" to the new code to handle the case of the new variant of the SPACE parm.
You may think of your request as being reasonable, but a new SPACE parameter could be added in less time than this thread has been going. There is no one place where old code can be branched away from, rather space/extent processing is endemic in all DASD related code. More critically, most I/O related control blocks have physical limits, and would require major redesign to handle even static expansion, not to mention dynamic. By comparison, supporting FBA devices in zOS would have been trivial, but IBM could not justify that, either.
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
