Richard Troth wrote:
If, for example, I have a Linux box which serves out "/export/home",
then the mount command on a Linux client would be ...
mount -t nfs linuxbox:/export/home /import/home
but the OpenVM equiv would be ...
openvm mount /../NFS:linuxbox/export/home /import/home
Right, that I get.....
Note the colons moving around like musical chairs. In both cases
/import/home must already exist. (I call it a "mount point
directory". If it is not empty then its contents are obsured by what
gets mounted there.) To be completely clear, on VM I would do
something like ...
openvm mount /../NFS:linuxbox/export/home /import/home (
nonetrc nolist
Right, I get this, too. And you're right about the colons too....:-)
But since you are mounting from an MVS system, you might could
dispense with translation on both ends and (NOTRANS. Mo betta!
But for an MVS sequential dataset, on VM the MOUNT should like like this:
OPENVM MOUNT /../NFS:mvIPaddr/ZZZZZZZZZ /root/mvsfiles
What goes where the ZZZZZZZ are above? Do I need to move the MVS dataset into
USS first?
-- Rick; <><
On Thu, Feb 26, 2009 at 9:52 AM, Dave Jones <d...@vsoft-software.com> wrote:
Thanks for the help, Rick. I don't really understand what you mean by
"shared" is the exported file system; do you mean that something must be
done on the MVS side to make the sequential dataset accessible by the CMS
NFS client? I understand about the BFS requirements over on the CMS side.
Richard Troth wrote:
The syntax I use is
openvm mount /../NFS:server/shared /local/point
where "server" is either the server's hostname or its address and
"shared" is the exported filesystem (or a usable subdirectory of it)
and "/local/point" is a pre-existing (usu empty) directory in your BFS
space. You will need to have a root BFS mounted first and the root
cannot be NFS.
I also always use (NONETRC and (NOLIST because #1 the NETRC files
complicate authentication (in my context) and #2 as a rule I do not
mix translated and non-translated files in NFS space. (Either
translate or don't, but mixing is messy.)
I cannot say enough about the excellent work of those IBMers who made
the CMS NFS client work. What a joy to be able to use GETBFS and
PUTBFS to move files to/from Linux. How much more effective to use
XEDIT on those files than to have only the Unix editors.
-- Rick; <><
Q: Isn't filtering stupidity elitist?
A: Yes. Yes, it is. That's sort of the whole point. -- Ortiz and Starr
On Thu, Feb 26, 2009 at 8:43 AM, Dave Jones <d...@vsoft-software.com>
wrote:
Hello, everyone.
I need to access an MVS sequential dataset from CMS, via NFS. What's the
correct syntax for specifying the MVS dataset on the OPENVM MOUNT
command?
I've tried several (obvious?) permutations, but none work.
Thanks and have a good one.
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
