If using UNIX on z/OS, then your hitting the network. Instead you are staying within the same TCP stack. Even if it's on another system in the SYSPLEX, then it would go thru the coupling facility. If you are going off platform, then you would need samba or NFS anyways. If no one is accessing it, then there should be much overhead other than memory that is probably paged out anyways.
I suspect that IBM felt that this implementation was the best bang for their buck. z/OS specific would be too limiting when most user's of this facility would be off platform anyways. If it's useful and saves time/money, then why not just use it. I would think you might as well use it. It's far less overhead than running an X-client on z/OS. Jon Perryman. >________________________________ > From: Paul Gilmartin <paulgboul...@aim.com> > > > >On Wed, 6 Nov 2013 12:15:34 -0800, Jon Perryman wrote: > >>It's been a long time but I though DFS had a server (SMB or NFS) that did >>exactly what you want. �I think this was one of the configuration I setup. I >>won't swear to it though. >> >True. I was hoping to bypass TCP/IP and network overhead. > >>________________________________ >> From: Paul Gilmartin <paulgboul...@aim.com> >>�I would make an addition of a virtual filesystem, >> >>perhaps such as: >> >>� � /dev/Legacy/SYS1.MACLIB(SPLEVEL) > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
