On Wed, 7 Oct 2015 08:57:49 +0200, Stevet wrote: >While we are whining... Does a iPhone have any way to do cntl+z like Linux or >Winderz? > I don't do Windows. On Linux, as on z/OS UNIX, I use cntl+z to interrupt a foreground process so I can "bg" it. And the lack of such multiprocessing is lamented alike in iOS and TSO. It's a relic of resource limitation the early days of both systems.
>And Gil, how would you get QSAM to correctly do a STOW at CLOSE if you do not >set DSORG to PO? > Hadn't thought of that. Is the information nowhere else avaiable? >Now the change you propose, how do we make it transparent to existing code >running in a bank, mfg co., etc. ? > Which change that I "propose"? How would allowing V(iew) to select a directory in UDLIST impact "existing code running in a bank, mfg co., etc. ?" >POSIX came LONG after MVS. > The interval OS/360 to UNIX is surprisingly short, yet the latter was able to learn from and avoid many of the design shortcomings of the former that persist in z/OS. >> On Oct 7, 2015, at 12:28 AM, Paul Gilmartin wrote: >> >>> Lots of variations. What about dataset accessed as a QSAM file but actually >>> PDS/PDSE member? FWIW the distinction goes away for USS -- every file is a >>> "member" of a directory. >> Sometimes that directory and membership are fictitious, as for /dev/fd/0. >> >> And ISPF is woefully ignorant of the similarity. For example, if in DDLIST I >> select a PDS with V(iew), DSLIST opens a member list with View as the >> point-and-shoot selection default. >> >> If in UDLIST I select a UNIX directory with V(iew), I get a failure, "Invalid >> file type". Why doesn't UDLIST do as DSLIST does and show a list of >> members in that directory? >> >> As for the sequential allocation of a PDS member you mention, I was dismayed >> to learn that OPEN sets DCBDSORG to PO, not PS. >> >> -- gil >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
