[Info-vax] VMS Enhancement request: setfilenomove.com

[Robert A. Brooks]

On 7/10/2019 7:58 PM, John E. Malmberg wrote:

> It should only complain about the open files if the nomove attribute is not set.

Yeah, I agree

>> It's not like it takes a long time, and the only way to
>> ensure that it's been run would be to check each file of interest for
>> the nomove attribute, and declaring the device safe for a defragmenter
>> if and only if each file of interest has been set /NOMOVE.
> 
> It does not do that.  It only tries to set the /nomove attribute and complains 
> about the files that it can not set.
> 
> Which means that you have do a dir/full on each file that it complains about.

You can do this

$ write sys$output f$file( "sys$loadable_images:sys$base_image.exe", "move" )
FALSE

But yeah, I'll look into doing something.

Andy Goldstein and I had a short discussion today about the list of files that
setfilenomove.com attempts to work on.  It's an incomplete list of execlets
and device drivers, and we're not sure why all those files are in there to
begin with.

Certainly files like the IA64 GPT, but in general, I'm not sure that
a j-random execlet needs to be there.  The MULITPATH execlets, for example,
are not there.

-- 
                  -- Rob