3 ms·
Sounds like a good idea, but it had little value in practice (for me). Since disk space came at a premium back then, it led to constant manual/auto purging.
by tgv 3y ago
Sounds like a good idea, but it had little value in practice (for me). Since disk space came at a premium back then, it led to constant manual/auto purging.
- Tor3 3y agoIt's so long since I was using VMS, but one thing I do remember is the constant purging. It was necessary.
- hulitu 3y agoThere are areas (CAD) where it made a lot of sense.
- mikewarot 3y agoYou could set the number of versions to keep on a per directory level.
- ngcc_hk 3y agoNo one told me then and keep on purging it. Any command to do that just for old time sake?
- mikewarot 3y agofor a single file (or directory, the syntax is the same). I've forgotten how much I love the HELP command on DEC systems. Having the old versions there saved my bacon more than once back in my student days. SET FILE /VERSION_LIMIT /VERSION_LIMIT[=n] Specifies the maximum number of versions for the specified file. If you do not specify a version limit, a value of 0 is used, indicating that the number of versions of a file is limited only to the Files-11 architectural limit of 32,767. When you exceed that limit, the earliest version of the file is deleted from the directory without notification to the user. For example, if you set the version limit to three when there are already five versions of that file in your directory, there will continue to be five versions of the file unless you specifically delete some or purge the directory. Once the number of versions is equal to or less than the current version limit, the version limit is maintained.