Directory doesn't exclude properly
At least not when handling versions
I've discovered that the DIRECTORY command does not properly parse the /EXCLUDE qualifier when interpreting a version number of ;0, instead returning "no files found". A minor nit, but one I've submitted to HP to get resolved.
Correcting this bug would allow you to easily see what files would be deleted with a PURGE command. I'll let you know what the response from HP is.
$ dir ! Note 3 versions of the .com file
Directory SYS$:[SAKOVICH.TEST]
TEST.ZIP;1 TEST_REFLECTION.COM;3TEST_REFLECTION.COM;2 TEST_REFLECTION.COM;1
Total of 4 files.$ dir *.*;0 ! Note this properly shows only current versions
Directory SYS$:[SAKOVICH.TEST]
TEST.ZIP;1 TEST_REFLECTION.COM;3
Total of 2 files.$ dir *.*;-1 ! Note this properly shows one previous version
Directory SYS$:[SAKOVICH.TEST]
TEST_REFLECTION.COM;2
Total of 1 file.$ dir *.*;* /exclude=*.*;0 ! This does NOT list all prev files%DIRECT-W-NOFILES, no files found
I think that this last result should be a list of all files that are not the current version, not "no files found". In this case, we should see versions ;1 and ;2 of the .com file.
This is not new behavior, as I've been able to confirm it exists on OpenVMS Alpha v7.3-2 & 7.1-2.
one comment:
Got a call back from 2 chaps in India this afternoon. They went over the command with me to make sure they understood what I was saying and what the desired results were. It appears it’s not just the ;0 that the /Exclude chokes on, but any relative version number. They promised to submit a suggestion to engineering to get it implemented in a future version of DCL. Precisely what I wanted! Hope it makes it, ‘cuz this sure would be a Real Nice Feature to have!
Aaron () (URL) - 21-Sep-2007 - 15:18
No trackbacks: