The Eunix way alweays struck me as the "Turing Tar Pit": when the only tool you have is a pipe, everything looks like a filter. It's not a paradigm that lends itself well to feedback.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Monday, May 10, 2021 3:24 PM To: [email protected] Subject: Re: IEBCOPY New Function - Support for PDSE Member Generations On Mon, 10 May 2021 21:02:23 +0200, Radoslaw Skorupka wrote: >While I'm not convinced there is real need for member >generations/versions, I have to admit there is lack of support for this >feature. Even with this enhancement. > It's a lack of modularity/reusability. The UNIX Way, as preached by such as Rob Pike and Eric Raymond but much ignored would be notionally something like: IEBCOPY [-o options1] | TRANSMIT [-o options2] giving the programmer control and access to any new features of either utility. This could be done, painstakingly, with two job steps and a temp DSN. >It's like long names in PDSE. I heard about it ~20 years ago. And I have >never seen it. And never seen any IBM tool (ISPF/PDF?) supporting such >names. > Aliases only, not names. Perhaps intended to support Hungarian Notation used by OO languages (such as C++?) -- 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
