Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Thomas Koenig Newsgroups: comp.arch Subject: Re: The Design of Design Date: Wed, 1 May 2024 19:28:55 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: <868r0xum1h.fsf@linuxsc.com> Injection-Date: Wed, 01 May 2024 21:28:55 +0200 (CEST) Injection-Info: dont-email.me; posting-host="efd99de0385348acff2dc04631268ba2"; logging-data="3516147"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18WxJcWIRRXZQyMyjYl8BNMs/JrGRZx2Tk=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:J8UmegZVmdIrvUr/I5AHIfCzR7Q= Bytes: 2080 Scott Lurndal schrieb: > The worst parts of JCL were "DD" cards, manual track allocation, and the lack > of any form of real filesystem. PDS do not count. The lack of a hierarchical file system was due to the OS, not really JCL itself. But the difference is mostly academic to the user, who has to deal with the idiosyncracies of the OS through JCL. But PDS (which you needed to use, in reality) were also a trap if you wrote to one member and read another one... or you locked it with DISP=OLD and could not access it for reading. Rather like Microsoft Windows these days, by the way... Personally, I found the limited number of extents for a file (sorry, dataset) to be most bothersome. If you exceeded this (and space for new members of PDS was not reclaimed), you got an ABEND E37 (or something similar). Bah. Although it wasn't all bad... as a student, I did a side job of keeping track of file allocations etc on a mainframe for one of the institutes, plus some scientific work, on an hourly basis. This took quite some hours. I also accidentally broke through RACF once; that was fun.