| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 344.1 | SETFILENOMOVE might be the cause | BACHUS::VERCAMMEN | You never walk alone... | Thu May 29 1997 05:00 | 12 | 
|  |      John,
    
    
    I think this is due to the execution of the SETFILENOMOVE.COM
    	procedure, which is asked for during the installation.
    	If you answer 'YES', it will change the file characteristics
    	of (most) files on the system disk (NOMOVE attribute).
    
    Regards,
    
    
    	\Jan 
 | 
| 344.2 | hmmm could be.. | COMEUP::SIMMONDS | loose canon | Thu May 29 1997 17:58 | 5 | 
|  |     Jan, yes, that could well be it.. I will ask the person who installed
    HSM V2.1 whether that question arose and how they answered it..
    
    Thanks,
    John.
 | 
| 344.3 | nothing in Rel. Notes, but... | COMEUP::SIMMONDS | loose canon | Thu May 29 1997 18:41 | 10 | 
|  |     Just spoke to the installer and she says there was no question about
    SETFILENOMOVE , just one question about using (or not) the existing HSM
    Catalogue file..
    
    I just noticed that all files on the system disk have been set 
    "Not Shelvable" ..
    Does the HSM installation do this?
    
    Thanks,
    John.
 | 
| 344.4 | HSM inst. performs SET FILE/NOSHELVABLE | ATZIS3::KARTNER_M | HOUSTON, we have a problem | Fri May 30 1997 00:27 | 8 | 
|  |        Yes indeed !
    
        The HSM installation process will perform a SET FILE/NOSHELVABLE
    	on OpenVMS system files but not on layered product files. Please
        check the modification dates of your layered products
    
                                                    hope this helps
                                                            Michael
 | 
| 344.5 | undocumented side-effect | COMEUP::SIMMONDS | loose canon | Fri May 30 1997 01:01 | 5 | 
|  |     Re: .4
    
    Thanks.. So _why_ isn't this Documented in the V2.1 Release Notes??
    
    John.
 | 
| 344.6 | See HSM for OpenVMS Guide to Operations | ATZIS3::KARTNER_M | HOUSTON, we have a problem | Mon Jun 02 1997 01:56 | 13 | 
|  |     Hi!
    
    This behaviour is stated in the 
    
    	HSM for OpenVMS Guide to Operations
    	6.5.2 OpenVMS System Files and System Disks Page 6-5
    
    								bye
    								Michael
    
    PS.: By  the way after a product update a full backup of the
    	 system disk has to be done anyway ;-) so whats the problem
    	 with the changed modification dates? 
 | 
| 344.7 | topic shelved.. | COMEUP::SIMMONDS | loose canon | Thu Jun 05 1997 01:15 | 5 | 
|  |     Re: .6
    
    Michael, Thanks for your help in clearing this query up!
    
    John.
 |