How to mount NFS UNIX volume using VMS client

[Carlos Moreira]

My apologies, I meant to say that I just want to test the creation of a file so that the users of the system can begin storing data on this mount point.

I've been searching for a primer but haven't found anything specific enough.

How do I translate the following UNIX commands to VMS:

1) mount engna2.bu.edu:/vol/research/eng_research_mctdata /mnt/mctdata
(is this VMS directory dnfs#:[000000]?)
2) df
(i presume show dev /mou will work similarly)
3) cd /mnt/mctdata
(set def dnfs#:[000000]?)
4) touch test.file
(create /dir test.file?)

Thanks in advance,
Carlos

[Steven Schweda]

1) With the "/auto" in the TCPIP MOUNT
command, any reference to the remote file
system should get the thing mounted. (Just
as a reference to "/net/node/dir/file" would
on a UNIX system.)

TCPIP SHOW MOUNT can show what's mounted (or
subject to automounting).

2) "SHOW DEVICE DNFSxx" should show free
(512-byte) blocks. On my systems:

ALP $ sho dev DNFS16

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DNFS16: Mounted 0 URT$/ 729470 1 1

ALP $ sho dev DNFS17

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DNFS17: Mounted 0 URT$/usr 4270322 1 1


urt# df / /usr
Filesystem 512-blocks Used Available Capacity Mounted on
root_device 1048576 319106 708624 32% /
usr_domain_x#usr 14628416 10358094 3730320 74% /usr


Of course, this forum de-formats all that
output into practical illegibility,

3) "set def dnfs#:[000000]" looks reasonable.
(Filling in "#" with a real value, of
course.)

4) There is no exact match for "touch" in
DCL. People have written "touch.com"
procedures to get pretty close. "CRE /DIR"
creates a directory. To create a simple
empty file, you could try something like:
COPY NL: dnfs#:[000000]test.file
or
SET DEFAULT dnfs#:[000000]
COPY NL: test.file

NL: = NLA0: = the null device (like
"/dev/null")

More device info is available using a
lexical function, F$GETDVI(). For example:

ALP $ write sys$output f$getdvi( "dnfs17", "freeblocks")
4270322

ALP $ write sys$output f$getdvi( "dnfs17", "maxblock")
14628416

HELP LEXICAL F$GETDVI

Isn't this all interesting and educational?

[Carlos Moreira]

Here is where I am at:

TCPIP> mount dnfs: /host=engna2.bu.edu /path="/vol/eng_research_mctdata"
%TCPIP$DNFSMOUNT-S-MOUNTED, /vol/eng_research_mctdata mounted on _DNFS27:[000000]

TCPIP> show mount
_DNFS27:[000000] mounted
ENGNA2.BU.EDU:/vol/eng_research_mctdata

TCPIP> exit
$ set def dnfs27:[000000]

$ show def
DNFS27:[000000]
%DCL-I-INVDEF, DNFS27:[000000] does not exist

What did I type incorrectly or should this work?

Thanks!

[Steven Schweda]

That all looks reasonable (except for the
result). The local analogue works on my
system, of course.

I assume that:

1) The UNIX file system is suitably exported.
2) It can be NFS mounted on a non-VMS system.

What sort of UNIX system is this?

Are you working as SYSTEM on the VMS system,
or could there be a permissions problem?

[Carlos Moreira]

I feel better. I thought I was going crazy.

I am logged on as SYSTEM. I can mount the volume on other UNIX systems.

The UNIX server is actually a NetApp filer (3020c). Here is the output from sho dev /mou dnfs:

Device Device Error Volume Free Trans Mnt
Name Status Count Label Space Count Cnt
DNFS27: Mounted 0 ENGNA$/vol/e 319.99GB 1 1
DNFS28: Mounted 0 MCTDATA$DISK 319.99GB 1 1

[Steven Schweda]

> I thought I was going crazy.

Could still be true.

> [...] NetApp filer (3020c) [...]

That's beyond my (limited) range of
experience.

If you get desperate, the current ECO for
TCPIP V5.4 is 5, which is higher than your 1.
No bets, but it might be worth reading the
release notes and/or installing the thing.

ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/

Look for "DEC-AXPVMS-TCPIP_ECO-V0504-155-4.*".

[Jan van den Ende]

Carlos,

looks like Steven took over nicely while I was asleep.

Checking your profile, I am a little ashamed by my omisson yesterday, but here is a belated, although sincerely meant:

WELCOME to the VMS Forums!!!

I think there is one more general note I should add:

HELP

in VMS really DOES help! It is very good (although not completely perfect), and in pretty reasonable human-readable English.
Lots of utilities (amongst them TCPIP) even have their own HELP, so
TCPIP HELP
or for example
MC SYSGEN HELP
provide even more.

and as you found out you can ask here.

Proost.

Have one on me.

jpe

[Stanley F Quayle]

By the way -- if you add /ADF=CREATE to your TCPIP MOUNT command, each file's VMS characteristics will be stored on the NFS server in a "hidden" file (".$ADR$"). This is very useful for keeping the files useful on the VMS system.

[Carlos Moreira]

Is the mapping that I've seen in other posts required? In other words, is it merely a permissions problem that is causing me not to have the ability to read and/or write. At this point, I don't care which account can write to the NFS mounted volume. For my purposes any account on the system should have full access.

Thanks in advance,
Carlos

[Steven Schweda]

"mapping"?

"permissions problem"?

What did you do, and what happened when you
did it? Or has nothing changed since Jan 7,
2006 03:49:36 GMT?

Have you installed the latest TCPIP ECO?