[Info-vax] Suggested SEARCH utility enhancement - /update_expiration=[never|match|always]

[Jon Pinkley]

We use file expiration dates as file access dates.  You can enabled updating of expiration dates on a disk by disk basis with the following command.
$ set volume/retention=(0,0:0:0.01) <disk volume>
You can control the frequency of update by adjusting the delta between the min and max values.  See help set volume /retention for more info.
The expiration date is useful to determine what files are being accessed, and what can safely be archived or zipped.
The problem is that if someone is searching for something, it will reset the expiration (faux access) date, on every file searched regardless of whether the file had a match or not.  So the result is you will see many files with the last access date being very close.
RMS has the ability to prevent the expiration date from being updated, via the XAB$_NORECORD XABITM (see http://h30266.www3.hpe.com/odl/axpos/opsys/vmsos84/4523/4523pro_017.html#index_x_731 )

I suggest /UPDATE_EXPIRATION[=(never|match|always)] and 
/noupdate same as /update=never

Originally I was going to suggest /RECORD but that is an ambiguous homograph (can be record as in a row of a file, or record as in update information).  And record would be confusing as it could also be used for another enhancement that could limit the records in the file to select, as is used in the dump/record=(option,...) 

I would prefer the default to be /noupdate_expiration date, and it probably wouldn't affect many users, because I doubt many people even know about file retention.  As long as the default could be controlled with a CLD file, then sites could override the default while still using the same image.