Alternate backup file rename test for VMS.

The existing test that made a directory called foo.bak and then
made sure the rename of a backup file from in-place edit failed
to overwrite the directory doesn't work on VMS because there is
no conflict between a file named foo.bak and directory named
[foo^.bak] in directory syntax or foo^.bak.DIR in filename syntax.
The .DIR extension is always there, and other dots in the name
are escaped with caret because dot is the directory delimiter.

So just make version 32767 of foo.bak and when the rename tries
to make the next higher version it will fail.  We're testing what
happens when the rename fails not why it fails, so we accomplish
the same goal via a different mechanism.

0 files changed, 0 insertions, 0 deletions