Deutsch English Français Italiano |
<v5b9qt$raj8$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!feed.opticnetworks.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Thomas Koenig <tkoenig@netcologne.de> Newsgroups: comp.arch Subject: Re: ancient OS history, ARM is sort of channeling the IBM 360 Date: Mon, 24 Jun 2024 08:13:17 -0000 (UTC) Organization: A noiseless patient Spider Lines: 17 Message-ID: <v5b9qt$raj8$1@dont-email.me> References: <s7r87j1c3u6mim0db3ccbdvknvtjr4anu3@4ax.com> <v51tcr$26io$1@gal.iecc.com> <87plsb87hn.fsf@localhost> <v5aggt$j1nj$7@dont-email.me> <v5an0l$10bj$1@gal.iecc.com> Injection-Date: Mon, 24 Jun 2024 10:13:18 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0d1b638f181d02a601469e29140c68e9"; logging-data="895592"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19AiTdZEgA15DbFCpanMAFDVFYUlbfMlTc=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:bKIrIAUuU2nFnAjh8wr4qXNxl8E= Bytes: 1958 John Levine <johnl@taugh.com> schrieb: > According to Lawrence D'Oliveiro <ldo@nz.invalid>: >>The difference was, with MFT, a program had to declare its memory >>requirement before it could be started, and the only way to change that >>was to stop the program and start it again. Whereas MVT allowed a program >>to change its memory requirements while it was executing. (Whoah! Program >>relocation requirement styleee!) > > Nope. MFT partitioned memory into fixed sized areas when the system > started, MVT assigned each program as much memory as it said it > needed, and the areas could be reallocated between job steps. In every > case the JCL had to say how big a partition each job step needed. When I first looked at the syntax for slurm, a workload manager for HPC clusters (did somebody say "Job Entry Subsystem"?), I found it striking how similar its syntax and semantics are to JCL's job cards. But then, they have a similar task.