Sharing OpenVMS directory to PC / NFS

[Mahmoud_1]

Hello all,
In fact I tried to configur the NFS server on an OpenVMS system then when I start performing the command referred to Export,MAP,.... I get stucked.
If any one can help in steps it will be appreciated.
I have :
Alpha server IP 100.110.10.1
User name test_user UIC [111,1]
PC ip 100.110.10.2
Directory dka0:[test] owned by test_user
.
If I want to see this directory from my PC what I have to do ( In Steps )
Best Regards

[Kris Clippeleyr]

Hi Mahmoud,

Might I redirect you to
http://h71000.www7.hp.com/doc/732final/6526/6526pro_044.html#nfs_server_chap
for configuration guidelines?

Regards,
Kris (aka Qkcl)

[Joseph Huber_1 · Accepted solution]

First, follow Kris's advice, read the NFS documentation.
In Your partical case, You want to export a VMS disk/directory, not a container file-system.

In TCPIP:
Map the disk:
MAP "/vmsdisk" dka0:
(use SET CONFIGURATION MAP for permanent settings).

Export the mount point:
ADD EXPORT "/vmsdisk/test" /HOST=100.110.10.2

(better of course have DNS name of PC rather than IP address).


In addition You need to add NFS PROXIES for the PC user specified by GID,UID pointing to test_user: see HELP ADD PROXY.

[Mahmoud_1]

Hello all,
Thanks for fast response.
I did:
TCPIP> sh proxy
VMS User_name Type User_ID Group_ID Host_name

TEST_USER OND 1 111 mahmoudd

TCPIP> sh map
Dynamic Filesystem Map
Pathname Logical File System

/vmsdisk DKA0:
TCPIP> sh expo

File System Host name

/vmsdisk/test 100.110.10.2

After that will you please tell me how can see this device on the PC.

Best Regards

[Joseph Huber_1]

I know only VMS and a bit U*x.
If Your "PC" is Windoze, ask somewhere else.

In U*x (Linux) systems, You have to mount the VMS export at the given mountpoint, i.e. /vmsdisk/test .
An entry in /etc/fstab would look like:
vmsnodename:/vmsdisk/test:/mnt/test:rw:0:0
where /mnt/test is any directory You choose.

[Mahmoud_1]

Hi to All,
Thanks for all.
Regards
Mahmoud

[Mahmoud_1]

hi ,

Last thing Will you confirm the seting that I did .
Is all the setings right or not.
Regards
Mahmoud

[Joseph Huber_1]

Yes, the export and map look o.k.
You know Yourself if the proxy values (1,111) are o.k., check at the PC side if this is correct (gid,uic).

[Mahmoud_1]

dear sir,
will you please tell me if I want to share this disk & directory to another openvms system.
and what do mean by share file system and container .
best regards

[Joseph Huber_1]

On VMS, You use TCPIP MOUNT to mount the NFS shared disk:
TCPIP MOUNT DNFS0: label logical_name /HOST=nfsserver /path="/vmsdisk/test"

See HELP MOUNT in TCPIP to see more options like /SYSTEM /UIC /SHARE /STRUCT /AUTOMOUNT.
To mount NFS file systems automatically at startup:
put the TCPIP MOUNT command(s) into sys$manager:TCPIP$NFS_CLIENT_SYSTARTUP.COM .

And You really should take the time to read the TCPIP documentation mentioned above.
There You will see two different ways of serving disks/directories from VMS:

File-system: this is the usual mode as used between Unix-like systems, the same view of files is visible on both sides, server and client. This mode is for sharing of files between VMS and remote systems.

Container: a Unix file system is created inside a dedicated directory of a VMS volume.
The files and directory-structures within this container are not directly accessed by the VMS file-system (only via special EXPORT/IMPORT commands of TCPIP). This mode is for providing (secure as VMS is) diskspace for other systems, not for frequent sharing of files.


And by the way, if only (not clustered) VMS systems are involved, then DECNET is a much simpler way to share files. This does not need exporting and mounting file-systems, but simply accessing files like this:
$ directory node"user passw"::dka0:[test]
and with recommended DECnet proxy access as simple as
$ directory node::
for user test.

[Willem Grooters]

There are several approaches. Some are excellent (since VMS based) and some are (very) ugly.

1. Cluster the systems. In that case, the disks would be shared by default, you won't need ANYTHING else but VMS.
2. Use DECNet in stead of TCPIP to access these disks. If setup properly, that's all it takes. DECnEt-Plus offers you to connect over IP, if the network in between doesn't support it.
3. If the disks are on a SAN, it might be possible to mount them from all VMS machins (I have no SAN experience, so that's a wild guess. Others could tell if this is possible)
4. Could AdvancedServer (FKA Pathworks) be a solution? It wouldn't matter (AFAIK) what system connects. Could be Windows, could be VMS.
If that could work, Samba could be an alternative.
5. You can use NFS, the one serving the disks as a server, the other as a client. Consult the manual, and follow the instructions.

[Joseph Huber_1]

Mahmoud,
I have overlooked one point in Your setup, the GID/UIC in the PROXY definition.
You told user TEST has VMS UIC [111,1].
Your NFS proxy of /GID=111/UID=1 is only correct if the remote user (on whatever system) has the same group/user ID's. In other words, the proxy gid,uid is NOT the local VMS UIC, but maps a remote gid/uid to a VMS userid.

[Kris Clippeleyr]

Att. Willem

4. Could AdvancedServer (FKA Pathworks) be a solution? It wouldn't matter (AFAIK) what system connects. Could be Windows, could be VMS.
If that could work, Samba could be an alternative.


I should watch out with SAMBA. I recently ported Samba 2.2.8 (maintained by Jean-Yves Collot) to VMS on Itanium. It seems to work, but after a few days it freezes solid. I haven't got a clue what causes the problem (and at the moment not the time to investigate).
Regards,
Kris (aka Qkcl)