On 2017-01-10, at 17:46, David W Noon wrote: > >> And how would you preserve one of the aboriginal design objectives of OS/360: >> the ability to ENQ all needed resources before job initiation to avoid >> deadlocks. > > That went out the window with the arrival of MVS/370, which introduced > SVC 99. > I believe ENQs with job scope remain in "the bread and butter of commercial data processing."
> Well, MVT was a single address space system. All regions were in > separate extents of the same physical address space. > I see some suggestion in this thread that the same DDNAME can not refer to different data sets within a single address space. But didn't MVT work that way? Each job (up to 15, limited by storage keys?) could use common DDNAMEs, such as SYSIN, SYSPRINT, SYSUT1, ... referring to different data sets. How have we lost that facility? > Single address space jobs are still the bread and butter of commercial > data processing. You might not like them, but non-shell jobs still run > that way. You see things; and you say “Why?” But I dream things that never were; and I say “Why not?”. -- GBS -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
