| It depends on what how the application program or VMS utility creates
the file. If it explicitly includes a version number, the NFS client
software simply does as requested, as it must. A little
experimentation shows that EDT seems to specify a version number, but
the DCL CREATE command and the TPU editor do not.
That's for creating a brand new file. When editing an existing file
something else comes into play. All VMS-based editors create the next
version of a file rather than overwrite the input file, and the NFS
client still has to do as the program directs.
Assume you are using an editor that always defaults the version number,
and you start with a file that has no version number. When you exit
the editor, the NFS client sees that you are trying to create a new
file, but a file by that name already exists. It does the best it can
to help you by renaming the existing file to a ;1 name. Then it writes
the new file as ;2 and also creates a link to the ;2 file with no
version number. Now the UNIX host knows the file by its versionless
name and by its ;2 name. If you edit the file again, the versionless
link is redirected to the ;3 file.
Julie
|
| There is something to watch out for in the interface (if you are watching sample
QIOs against F11X using SET WATCH FILE):
RMS has an MXV (maximize version number) which is used to assign a new
highest version number to a file, even if an explicit version number is
supplied in the name string.
This translates to FIB$V_NEWVER [FIB$M_NEWVER in FIB$W_NMCTL]. You may
see actual file version numbers appearing in the SET WATCH output, but
you must notice that the NEWVER bit is set, in effect ignoring the
version number as visible in the name string.
|