topic Re: "TCPIP DIR" of ODS5 shares brings "TCPIP-E-INVPATH" msg in Operating System - OpenVMS

"TCPIP DIR" of ODS5 shares brings "TCPIP-E-INVPATH" msg

Andreas Kaempfe — Mon, 18 Sep 2006 05:10:48 GMT

Under OpenVMS TCPIP the "DIRECTORY" command brings an error message for ODS5 exports. ODS2 exports are OK. I checked it from OpenVMS 7.3-2 up to V8.3. Same attitude on these versions. Do I missed any important information to export these directories or is it a general problem?
Any hints and tips are welcome.
See the attachment for further information.

Re: "TCPIP DIR" of ODS5 shares brings "TCPIP-E-INVPATH" msg

John Gillings — Mon, 18 Sep 2006 16:59:53 GMT

Andreas,

What are your process settings for parse style and case? (HELP SET PROC/PARSE & /CASE). Although both your the mount point and the command are in upper case, there may be some case conversions going on.

Perhaps try defining everything in lower case and see if that makes a difference?

Re: "TCPIP DIR" of ODS5 shares brings "TCPIP-E-INVPATH" msg

Andreas Kaempfe — Tue, 19 Sep 2006 02:42:33 GMT

Hi John! First of all I forgot that this problem belongs to TCPIP NFS.
I switched between parse style "EXTENDED" and "TRADITIONAL" but the messages are the same. To "rename" the exports in lowercase had no success, too. I tried also to add the export with "/options=case_sensitive". No way to get the directory of that NFS ODS5 share! Any ideas??

Re: "TCPIP DIR" of ODS5 shares brings "TCPIP-E-INVPATH" msg

H_Bachner — Tue, 02 Jan 2007 19:51:35 GMT

I know this reply comes late, but maybe it's still useful.

In my experience (with OpenVMS V7.3-2 and TCP/IP Services V5.4 ECO 5), if you export a directory other than the root directory on a mapped device with ODS-5, you must use /OPTION=TYPELESS to make it work.

Hans.