  TCP/IP NFS not honoring ADF files? 
 The Question is:
 
Dear Mr. Wizard;
 
We configured a NFS client on an OpenVMS/Alpha 7.1 system (UCX 4.2) and
after tests, a user copied 6000+ files to the NFS mounted device. Our tests
did not include dismounting and remounting the device.
 
Since the device has now been dismounted and remounted access to the 6000
files is broken. They all show up as Stream_LF and errors occur upon access
attempts. In the future, we probably will mount with /noconvert (defaults to
/convert) but this option do
es not help now. A "ucx show mount/full" command shows that the "ADF mode"
is "update,use,create"; yet it is NOT using the ADF data upon re-mounting.
 
Wondering if the difference between tcp/ip 4.2 and 5.0 comes into play. The
matching paragraphs in the old and new docs (15.1.2 "storing file
attributes" and 17.1.2 in "TCP/IP - Management" AA-LU50J) seem to indicate
that the 5.0 version might NOT have to
 guess to "reconstruct" the file characteristics after a remount. Is this
true? We don't see any mention of such an improvement in the TCP/IP 5.0
release notes.
 
The users ran for weeks before the first dismount was done and the 6000
files (and .$ADF$ files) are only backed up on the UNIX NFS server side, so
we must be able to restore the link between the .$ADF$* files and their
coresponding files.
 
Thanks in advance for any insights.
 
Paul Martin, Frank Troth
 
 
 The Answer is:
 
  On OpenVMS V7.1, the OpenVMS Wizard would move to TCP/IP Services V4.2
  with the current ECO, or to V5.0A or later.
 
  The fix for the problem that appears to be the central issue here is
  included in V4.2 ECO 3 and later, and is also present in V5.0A and later.
