  NFS and case preservation/change support? 
 The Question is:
 
I'm positive this has been asked by I can't find a satisfactory answer,
so I apologize up front:   Is there an NFS-client for VMS w/ configurable (or disable-able) case-mangling of filenames?
 
MultiNet, currently an orphaned stepchild of Process Software is often
reported to resolve this problem but does not seem to.
 
Ideally, we'd like an NFS client that ignores case on the (Solaris) server
the same as a VMS NFS server would, and lets us take the risk for collision.
(Actually, VMS might easily deal w/ collisions using it's version #, e.g:
if a server FS contains "Makefile" and "makefile", I'd get a MAKEFILE;1
and a MAKEFILE;2 on the client).
 
The problem: We're compiling select parts of a mature, large and complex (1M lines C++) codebase for VMS, and must deal w/ the conflict presented
by something like: "#include "FooBar.h".  On the VMS side, the NFS client
we use (UCX) calls the included file something like: $Foo$Bar.h, and the
CXX compiler seems to look for "FOOBAR.H", so the compile fails.  NT
NFS clients seem to allow some flexibility here, and there must be one
for VMS which does too, I simply can't find it.  I even tried using the
POSIX "LOCALE" functionality to deal w/ this, to no avail.
 
Any help much appreciated.   Thanks,        Keith Wingate
 
 
 
 The Answer is:
 
  Please contact Process for information on Multinet products.
 
  Please contact the vendor of the NFS client for assistance with
  the (non-OpenVMS) client environment.
 
  The OpenVMS TCP/IP Services NFS server provides two interfaces,
  the traditional OpenVMS container file and the UNIX container
  file.  The former serves uppercase only, the latter preserves
  case.  (The use of container file is somewhat of a misnomer, as
  TCP/IP Services actually serves and uses a directory of individual
  files.)  The OpenVMS NFS client preserves case.
 
  While work is underway to better support the ODS-5 file system under
  TCP/IP Services, this support is not presently available.
 
  Probably the easiest approach would be a PERL script, and simply
  fix the problem in the source code and source pool.
 
