"It's a UNIX thingy; we don't want that on our mainframe." Charles
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: Monday, March 29, 2021 12:12 PM To: [email protected] Subject: Re: IND$FILE and zFS? Not sure why not. NIH is one possible reason. "Too new-fangled for us, our programmers will never figure it out" might be another. Lack of time (under-staffing) or sheer laziness may be other possible reasons, along with "We're getting off the mainframe Real Soon Now (tm) so do nothing new there" for yet another. Along with blatant mis-trust of all things application-programmer friendly. Lawyers could be yet another reason. Fear of data breaches and the accompanying liabilities and reputation loss. Probably as many reasons as there are shops. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Monday, March 29, 2021 3:02 PM To: [email protected] Subject: Re: IND$FILE and zFS? On Mon, 29 Mar 2021 18:36:43 +0000, Farley, Peter x23353 wrote: > >There have to be less intrusive / complex-to-implement--shop-wide >alternatives, and an updated or open-sourced IND$FILE would provide one such. > As an ISV's employee, I was delighted with NFS. It made desktop filesystems visible on z/OS and Classic data sets visible on desktops. All very transparent; no need for transfer; up/download. Some filesystems were mounted at two mountpoints binary and text with CP819<->CP1047 mapping, making it possible to cross-compile on desktop and bind to load modules on z/OS; again no explicit transfers. I'm surprised that NFS isn't more widely embraced. Security concerns? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
