How to mount NFS UNIX volume using VMS client

[Carlos Moreira]

I am a beginner when when it comes to VMS. I would like to know what the commands are to mount an NFS volume (UNIX server), proceeded by how I can change into the directory and write information to that directory (from any account on the system).

I am more familiar with UNIX than VMS, so an equivalent UNIX explanation would be helpful.

Thanks in advance!

P.S. I would send along the pertinent version numbers, etc., but I don't know the commands.

[Steven Schweda · Accepted solution]

Start with "TCPIP SHOW VERSION". When that
fails, try "SHOW LOGICAL *TCP*" and
'WRITE SYS$OUTPUT F$GETSYI( "VERSION")'.

VAX, Alpha, or Itanium hardware?

There is more than one TCP/IP kit for VMS,
and the details for NFS and everything else
differ among them.

[Carlos Moreira]

Here is the post and version of TCPIP (UCX):

Welcome to OpenVMS (TM) Alpha Operating System, Version V7.3-2

$ tcpip show version

HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 1
on a AlphaStation DS15 running OpenVMS V7.3-2

[Steven Schweda]

TCPIP HELP MOUNT

As a crude example:

$ tcpip
mount dnfs16: /host = urt /path = "/" /auto
mount dnfs17: /host = urt /path = "/usr" /auto
mount dnfs18: /host = urt /path = "/var" /auto

Defining some logical names can make some
things more convenient.

$ define /system urt_root dnfs16:[000000]
$ define /system /trans = conc urt_root_ dnfs16:[000000.]
$ define /system urt_usr dnfs17:[000000]
$ define /system /trans = conc urt_usr_ dnfs17:[000000.]
$ define /system urt_var dnfs18:[000000]
$ define /system /trans = conc urt_var_ dnfs18:[000000.]

To see "/net/urt/usr/local/src/vim":

ALP $ dire /date /size /prot urt_usr_:[local.src.vim]

Directory URT_USR_:[LOCAL.SRC.VIM]

PATCH.DIR;1 2 25-JAN-2004 01:15:50.95 (RWED,RWED,RED,RED)
VIM-5$5N7.DIR;1 1 25-JAN-2004 01:16:13.51 (RWED,RWED,RED,RED)
VIM-5.7-RT$5NTAR$5NGZ;1
2147 27-FEB-2001 21:45:08.00 (RWD,RWD,RD,RD)
VIM-5.7-SRC$5NTAR$5NGZ;1
2405 27-FEB-2001 21:45:20.00 (RWD,RWD,RD,RD)

Total of 4 files, 4555 blocks.

The ODS2-compatible names may be annoying.

Note that VMS lacks the concept of a root
file system, so looking for files in "/usr"
in the root fails:

ALP $ dire /date /size /prot urt_root_:[usr]
%DIRECT-W-NOFILES, no files found

even though the directory appears there:

ALP $ dire /date /size /prot urt_root_:[000000]usr

Directory URT_ROOT_:[000000]

USR.DIR;1 1 24-JAN-2004 23:26:44.73 (RWED,RWED,RED,RED)

Total of 1 file, 1 block.

But "urt_usr:" or "urt_usr_:[000000]" works.

Is that sufficiently confusing?

[Jan van den Ende]

Steven,

I really do NOT like any syntax that contains [000000.
Of course it is OK to specify the [000000] pseudo-directory itself, but if you specify a subdirectory by using a full stop after the 6 zeroes, you are inplying a REAL, existant 000000.DIR.
And if you do that in any command that implicitly creates directories (like BACKUP) you end up with a real 000000.DIR.
Still no harm done, but if you some time later repeat those actions, you create [000000]000000.DIR, and NOW the real fun can start!

Secondly, if these concealed devices are going to be needed by innermode code, they need to be /EXECUTIVE
An illustrative example is to use it as the device spec in AUTHORIZE.

In short, do not:
$ define /system /trans = conc urt_usr_ dnfs17:[000000.]
but use:
$ define /system/exec /trans = conc urt_usr_ dnfs17:

hth,

Proost.

Have one on me.

jpe

[Carlos Moreira]

I must be doing something wrong:

TCPIP> mount dnfs16: /host=engna2.bu.edu /path="/vol/research/eng_research_mctda
ta" /auto
%TCPIP$DNFSMOUNT-S-MOUNTED, /vol/research/eng_research_mctdata mounted on _DNFS1
6:[000000]
TCPIP> define /system mctdata dnfs16:[000000]
%CLI-W-NOQUAL, qualifiers not allowed - supply only verb and parameters
\SYSTEM\
TCPIP> exit
$ define /system mctdata dnfs16:[000000]
$ dire /date /size /prot mctdata_:[000000]
%DIRECT-E-OPENIN, error opening MCTDATA_:[000000]*.*;* as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
$ define /system mctdata dnfs1:[000000]
%DCL-I-SUPERSEDE, previous value of MCTDATA has been superseded
$ dire /date /size /prot mctdata_:[000000]
%DIRECT-E-OPENIN, error opening MCTDATA_:[000000]*.*;* as input
-RMS-F-DEV, error in device name or inappropriate device type for operation

Any assistance would be great, thanks!

[Jan van den Ende]

Carlos,

if you posted EXACTLY what you did, then it is clear.

$ define /system mctdata dnfs16:[000000]
$ dire /date /size /prot mctdata_:[000000]


Look very good:

you DEFINE mctdata

and then USE mctdata_

Whatch carefully and notice the extra underscore.

But there is something more.

Either you define a construct containing a directory spec to SUBSTITUTE that dierectory spec, OR, you specify a CONCEALED DEVICE as a substitute for a device spec.
Concealed device definitions contain the mandatory /TRANS=CONCEAL qualifier ( "switch" in U*x speak )
A concealed device defines a name for a device spec (ending with : (colon) OR a name for a concealed device root, consisting of a real device spec, a colon, a directory spec WITH A FULL STOP ( . ) DIRECTLY IN FRONT OF THE CLOSING SQUARE BRACKET { ] }
in your example:
DEFI/SYS/EXE mctdata_ dnfs16: /trans = conc
or
DEFI/SYS/EXE mctdata_ dnfs16:[data.] trans is conc

Now, use it as

DEFIN /SYSTEM MCTDAT_XYZ /ctdata_:[XYX]

In the first case, use U*X system would have
/vol/research/eng_research_mctdata/xyz
in the second case that would be
/vol/research/eng_research_mctdata/data/xyz

A little extra advise: please choose your naming a little less confusing!
Two totally different definitions with only an underscore as (hardly visible) differentiator CAN BE a little confusing, as you yourself have made very obvius!

PS. If you want to have a clearer view of the exact spellings, then copy the text out ot the forums display, and paste it into a plain ASCI format, like any VMS or U*x editor, or even M$ Notepad.

hth,

Proost.

Have one on me.

jpe

[Jan van den Ende]

Carlos,

me again.

Sorry, I was a little late in noting your request for explanatios from a U*x perspective.

Unix does not display the notion of devices.
Perhaps the best way I can describe it: consider VMS to have not just ONE filesystem, but a separate one PER DEVICE.
And you can use them all mixed together, if only you specify them each time, like you would use a mix of files in /dev /var /etc /bin ...
(and lets forget about relative adressing, although the concepts are similar)

The concept of Logical Names has no real U*x equivalent.
Loosely speaking, they may be considered as environment variables. But /SYSTEM logicals are usable by all processes on the system, and can be changed with immedeate effect on all processes by suitably privileged users. Same applies for /GROUP logicals for all processes in that UIC group (cf the same gid )

Proost.

Have one on me.

jpe

[Carlos Moreira]

Thank you for your notes. They appear to be helpful, but I am still a bit confused.

How do I verify that I have successfully mounted the UNIX volume?

Also, what is the command to "change into that directory"? After that, I will try writing a file to see if that works. That is basically all I want to do.

Thanks,
Carlos

[Steven Schweda]

> How do I verify that I have successfully
> mounted the UNIX volume?

The DIRECTORY command offers a clue.

> Also, what is the command to "change into
> that directory"?

SET DEFAULT

You appear to need a general VMS primer.
Google can probably find several.

> After that, I will try writing a file to
> see if that works.

Writing how?