" HSM - Hierarchical Storage Manager  	 Overview:   B HSM is an add-in to the VMS I/O system which provides VMS with theB ability to have transparent file migration between active and nearF line storage in one or more steps. When files are migrated ("shelved")F from normal disk storage to backing storage, a marking is left on themB which is automatically read so that when the file is opened, it isB automatically retrieved by HSM from nearline storage. Thus, a user? or program need not be aware at all that such shelving occurred B and no operator intervention is needed to perform the "unshelving"G operation. This is distinguished from operation where a user must first E request an archived file be reloaded, which requires detailed advance B knowledge of such needs. The files appear to have been on disk allD the time, but in fact the online disk space is conserved. It is also@ distinct from modes of operation where a file's location visibly@ changes. These, too, require that programs be told where the newA site is, which can be awkward. HSM provides total transparency of @ file migration, invisible to programs and users apart from small% delays where files must be unshelved.   @ In addition, HSM provides two unique "soft link" abilities which0 complement unshelving, and manages volume space.  ( The basic capabilities of HSM are these:  A * Files can be shelved (by space-making script or by command) and < 	unshelved automatically from nearline storage when they are2 	opened. The process opening the files then sees a; 	successful open with no side effects. Shelved files can be 9 	stored in compressed form if this is desired, and can be < 	stored in any desired location. Storage of shelved files on$ 	tapes or the like can be done also.  ? * Files can be "soft linked" to other files, even across disks. 8 	This mode of access can be used for a sort of permanent; 	shelving on another volume by truncating the original file : 	to zero blocks. The soft link operates extremely fast and4 	causes the file in question to be opened in its new; 	location, with the channel restored on close so that again 7 	a program observes no change, but the file is accessed 7 	transparently at its new site. Where the new site is a . 	read/write device this can be most effective.  B * Files can be "soft linked" in a "readonly" mode to another file.6 	In this mode, suitable for read-only backing storage,6 	whenever a file is opened for read-only access, it is7 	transparently and instantly opened on its linked site, ; 	wherever that may be on nearline storage. When such a file : 	is opened for any kind of writing, however, it is treated: 	as a shelved file and is unshelved and replaced on normal9 	disk before the open is done. Thus any read/write access : 	will find the file in a suitable location for its open to9 	succeed, transparently. (Notice that soft linked storage 9 	must be on disks and must not be in compressed form. The 9 	decompression would induce an unwanted delay in access.)   = * Disk space can be managed. Whenever an extend or create (or < 	inswap) would not have adequate space on disk, HSM starts a6 	"make-space" script which is tailored by a fullscreen; 	utility to match site policy. This policy can select files 9 	based on access time, size, name, or characteristics for  	space making.   Installation  = 	The HSM package is installed in a three step process. First, ? you install HSM with VMSINSTAL to build the images and put them D somewhere. Then you use HS_SETUP.COM to generate the startup scriptsD and select features. Finally, you use HSSPACE_TAILOR.COM to set siteJ policy for files to be selected for shelving when space must be reclaimed.     1. VMSINSTAL@ 	First, HSM is installed with VMSINSTAL. Put the medium with the# HSM kit on it and give the command    $ @SYS$UPDATE:VMSINSTAL HSM010 medium:  ' Only one non-obvious question is asked:     Enter directory for HSM programs  @ The response to this is where the HSM programs and command filesB will be installed. It should be accessible to the whole cluster ifA you have a cluster, and is where the later setup script should be  told they are.       2. HSM_SETUP   	Next, you run the command   $ @SYS$MANAGER:HS_SETUP   ? to perform your system setup. This allows you to set the system > parameters up and will generate the command files to start HSM< up at boot time and to create a few useful symbols at login.  @ The setup script initially comes up with a menu which looks like this:        HSM SETUP  19:19:35   +    -->  Set area to hold HSM database files 6         Set start intercept driver unit number (now 0)*        *Set area for HSM executable images.         Done this menu, process disk selection8         Remove a disk from an existing HSM configuration>         Set images which are exempt from HSM (e.g. defraggers)3         Set area for storing nearline files shelved          Quit, do nothing        C Notice that the "Set area for HSM executable images" is tagged with D an asterisk (*). This indicates that a logical was found giving this; value. This will usually be the case after a VMSINSTAL run.   + The menu items have the following meanings:   # Set area to hold HSM database files @ 	HSM stores data in a database of its own indicating where filesA 	were stored. Each disk has one (and for volume sets one uses set A 	file/enter to make several synonyms for a file). Whenever a file A 	is to be shelved or unshelved, this file is consulted, and locks = 	on it serve also to synchronize cluster file access at these ; 	times. The area specified will hold these files. It can be : 	anywhere in the system, though it should be a local disk.  . Set start intercept driver unit number (now 0)@ 	You can have as many HSM servers as you like, where each server@ 	controls unshelving and space monitoring for one or more disks.? 	Each disk uses one unit of the intercept driver (HSDRIVER). To @ 	set up a second (or later) server, you may start using HS units= 	higher than 0, so that if you set up a server once for three B 	disks (thus using HSA0:, HSA1:, and HSA2:), you can set the startA 	unit number to 3 here to start with HSA3: next time. Each run of B 	HS_SETUP.COM generates control files for one server (appending to@ 	the startup files if it is not the first time). Normally, it is> 	expected that inswap activity will be low enough that one HSM< 	server will do for an entire system. Thus, this is the only> 	provision for multiple servers. You must track how many disks< 	have been set up for by hand if you choose to have multiple	 	servers.   " Set area for HSM executable images@ 	This area is expected to contain the images for the HSM server,? 	control utilities, and command files used by the system. It is = 	asked for by KITINSTAL and normally would just be left as it 	 	was set.   & Done this menu, process disk selection0 	This item allows you to go on to picking disks.  0 Remove a disk from an existing HSM configuration8 	This item allows you to remove disks in an existing HSMB 	configuration (or incidentally find out what disks are configured 	currently).  6 Set images which are exempt from HSM (e.g. defraggers)B 	Some images should not be able to generate inswaps. Defragmenters@ 	and the like can be in this class. Also it is often a good idea@ 	to have a copy of the BACKUP image, pointed to by its own verb,= 	which will not cause unshelving. Shelved files are marked as = 	NOBACKUP type to prevent a system backup from unshelving all < 	files on a disk, but this can be changed if one does system: 	backup from an image in the "exempt" list. Up to 32 imageB 	pathnames can be specified. (The pathname to use can contain wild? 	cards, e.g. "*]BACKUP.EXE;*", or use the full path returned by < 	$GETJPI (as seen, for example, in a SHOW PROCESS/CONTINUOUS9 	display) as the equally.) When an image is exempted, the @ 	HSM server simply allows the image's file opens to proceed with 	no change.   + Set area for storing nearline files shelved ? 	Sets the area on nearline storage where this server will store > 	files. It should be of form device:[directory] since the file@ 	ID is all that is really available to the HSM server. This setsA 	the logical name used for this area by the .COM files. Note that ? 	you will be warned if the area cannot be written to. Also note ; 	that if it is desired to define this area differently, the > 	command files can of course do so, or an Assign/job where the> 	servers run would do this. The current setup assumes a single@ 	location for the system. Should you configure multiple servers,> 	they will inherit job logicals for the then-current save area< 	you are using, so that each server can have a separate save> 	area if desired. These can be cascaded if you prefer, so that= 	one server's save area files get shelved to another server's  	area if need be. < 	If you have multiple areas, be sure that before running the; 	MOVEFILE or MOVEHSM commands you define the logical DELSAV < 	to point to the storage area for shelving used for the disk> 	you are operating on. If you do not, any shelving you do will9 	get files to the incorrect area, though softlinks can be  	set up in such a case.   E When the initial setup menu is exited, one goes on to select disks to F be enabled. Remember that for soft links to work properly, the disk onG which the link is AND the disk on which the file linked TO is must both  be controlled by HSM.   D The disk menu looks like this (with the selected disk highlighted by reverse video:    HSM Configuration                  Disk Selection :     Use arrows to move to selection. Use RETURN to select.    End disk selection   _ARISIA$DKA700:  _ARISIA$DKB0:  _ARISIA$DKB300:  _ARISIA$DCA0:  _ARISIA$DCA2:  _ARISIA$DCA3:  _ARISIA$DCA4:  _ARISIA$DCA5:  _ARISIA$VDB0:  _ARISIA$VDB1:  _ARISIA$DKB200:  _ARISIA$DKB700:  _ARISIA$DCA1:  _ARISIA$DCA6:  _ARISIA$DCA7:  _ARISIA$FQA0:  _ARISIA$FQA1:  _ARISIA$FQA2:I                                                Currently on item 1 of 151     B In this list, which will scroll as you move the arrow keys around,A 	mounted disks on the system are shown first, then all other disk B 	class devices. When a disk has been selected, it is tagged with *@ 	on the line to flag visually that you've already set up HSM for 	that disk.   @ When you select a disk, you get a menu of options for that disk.# This menu looks like the following:m       HSM DISK SETUP  19:48:50  9   -->   Enter file of file IDs to load for kernel markinga9         Examine only kernel-marked files for access testsa:         Set to automatically kernel-mark all files on load>               (This requires generating the file list at boot)4         Generate filelist database and set to use it@         Act as if ALL files were kernel-marked (use if most are)         Quit, do nothing.o         Done this menu  ? These items have to do with HSM's recognition of which files tod- inspect. HSM can do this in three basic ways:f  D 1. HSM can look at file ACEs that are tagged on each shelved file toF determine that the file may need to be unshelved. A fast kernel thread is used to do the test.b  F 2. HSM can use an internal structure to check in memory that this fileE might need to be unshelved, and skip such checks if the file is knowngF thereby not to be shelved. This requires loading this information intoC memory at startup, but makes the overhead of file opens practicallyt& nothing where the file is not shelved.  H 3. HSM can pretend direct ALL file opens to its server to determine fromH the server's database whether an unshelve is needed. (If most files on aB volume are shelved, this can be worth while.) This has the highestF overhead, but should be needed VERY rarely, and on only a few disks on' any system that does need it somewhere.   H The file of file IDs that are marked can be generated here automaticallyB either once, or at each HSM startup. It needs only the file ID in I parentheses, such as the "DIRECTORY/FILE_ID" command produces. Additional H information outside the parentheses is ignored but is desirable to allow the file to be inspected.h  G The "Enter file of file IDs to load for kernel marking" option will askd1 for a file of file IDs in text form, records liken  ! HSM_USER_MAN.TXT;2   (8567,104,0)r  # which are to be treated as shelved.o    G The "Examine only kernel-marked files for access tests" item tells the  E system to only examine files for unshelving if they are in the kernel.C marking list. If your kernel marking list will be relatively static.1 or can be easily regenerated this is a good idea.r  G Such a list can be produced at any time by the string of DCL following:y   $ HSa_listfile="" , $ HSauthmaint disk:[0000000]corimg.sys\%LIST  B which will leave the file spec of the list file produced in symbolD HSa_listfile, and the list will contain every file marked as shelved on the entire disk.s  I If the "examine only kernel-marked files..." option is selected, overheadnI for non-shelved files is basically nonexistent. It is present, but small, A if not. Note that this option does however require the list to bee rather static.  ? The option "Set to automatically kernel-mark all files on load"sE will generate such a list at every machine boot and arrange for it ton
 be loaded.  F The option "Generate filelist database and set to use it" on the otherD hand generates a file list at the time you run this script, and sets@ the system to use it (though not exclusively unless you so say).  E These kernel lists serve to ensure unshelving occurs even if the filerD markings are damaged, so they are useful to have even where the fileE markings will be inspected directly. A privileged user who damages ortD deletes the file ACL may wipe out the "shelved" marking in this way,E but the system can still successfully unshelve files even so if therep is a kernel marking in use..  E The option "Act as if ALL files were kernel-marked (use if most are)"tG is useful in rare cases, namely if most files on a disk ARE shelved. ItmB forces the HSM server to examine all opens and can be used if mostE files on a disk are shelved but markings have been damaged or lost indJ some cases. Certain backup options, for example, can cause this to happen.    L When this menu is finished, you return to select another disk and eventuallyG to exit. If the "Quit..." option is selected, you quit out of the wholeG% disk select menu, not just this disk.s   3. HSSPACE_TAILOR   G The HSM function of monitoring space depends on a site policy to decideaC what space should be freed. This site policy is decided upon in the  HSSPACE_TAILOR.COM script.   When you run this script with    $@GCY$SYS:HSSPACE_TAILOR  6 you will create a space-making script for your system.  1 The script produces a menu which looks like this:o  "    Site Space Policy Determination  A    --> Set min size file to migrate when space is needed (now 10)e8        Set min age in days for files to be moved (now 2)6        Specify substrings of file paths to leave alone"        Clear substring list (now )1        Done this menu, build the selection scripto#        Quit the menu, doing nothingt  C The script selects files based on age and size, so that files whoseg? last access is at least N days ago and whose size is at least MaE blocks and which don't contain strings in the full file specification C that you specify may be shelved. Files marked installed, contiguouseC files, anything with DSK or SYS in the filename string, ISAM files,aC or NOBACKUP files are not considered eligible. You may impose othersD filename strings that cannot be there. For example, to omit any fileD pathname containing the string SQUASH, add "SQUASH" to the substringA path list. The minimum age and size are set with the first 2 menuf3 items. You can of course quit the menu at any time.s  B Whenever a disk under HSM control is nearly full and a file create@ or extend for less than 1/8 of the volume size is seen, then the9 file GCY$SYS:MAKSPC.COM is run. It is operated as followsr  % $ @GCY$SYS:MAKSPC devicename: nblocks   H and will attempt to free nblocks blocks on devicename: before returning.E It does this by outswapping files that match the site policy you haveo< just chosen. Note that the site policy will use the later ofG the expiration date, the creation date, or the revision date of a file.eF Thus if you have used the SET VOLUME /RETENTION=(1-,2-) command so theC system records the last day of file access, the selection will skip,D files which have been read recently, even though they might not have0 been written for some time. This is recommended.  B It is also suggested to run the make-space script at night so thatA the outswapping can be done out of prime time, rather than imposee( a delay on file opens as space is found.      @ Now the basic installation should be complete. You may of course@ rerun the HS_SETUP at any time to alter decisions encoded there.     SHELVING FILES BY COMMAND   C There are two commands to do manual shelving. One of these lets yousD use a fullscreen front end to select files in your current directoryB tree. It is the MOVEHSM command. The other lets you specify a fileC specification (possibly a wild card) on any device for shelving. Itl is the MOVEFILE command.  F There are several modes of file shelving or moving, and these commands allow them all to be selected.  D The MOVEHSM command presents a fullscreen directory of files, with aG fairly large set of possible formats. You use arrow keys to move aroundgB and select the file by the space bar (or deselect the same way) or9 use other selection criteria to pick pieces of filenames.t  + Such a screen has the following appearance:k  P Edit   eXecute   Copy   Rename   Delete    Move   pUrge   Quit   Help   List   ?P EVERHART                    USR$ROOT:[EVERHART.HSM]                 30 Sep 22:13P +----------------------------q FILE MANAGER  *.* ------------------------------+P !  !HS.MMS;2                      7/8   7-SEP-1994 12:45  (RWED,RWED,RE,RE)    !P !  !HSACLCREA.TXT;2               1/2   7-SEP-1994 12:45  (RWED,RWED,RE,RE)    !P !  !HSALL.BLD;3                   2/2   7-SEP-1994 13:05  (RWED,RWED,RE,RE)    !P !  !HSALLDBG.BLD;2                2/2   7-SEP-1994 12:45  (RWED,RWED,RE,RE)    !P !  !HSAUTH.FOR;2                  3/4   7-SEP-1994 12:45  (RWED,RWED,RE,RE)    !P !  !HSAUTHM.MAR;2               10/10   7-SEP-1994 12:45  (RWED,RWED,RE,RE)    !P !  !HSAUTHM.OBJ;1                 3/4   9-SEP-1994 13:05  (RWED,RWED,RE,RE)    !P !  !HSAUTHMAINT.DOC;8           17/18  14-SEP-1994 12:56  (RWED,RWED,RE,RE)    !P !  !HSAUTHMAINT.EXE;1           35/36   9-SEP-1994 13:09  (RWED,RWED,RE,RE)    !P !  !HSAUTHMAINT.FOR;9           56/56   8-SEP-1994 19:39  (RWED,RWED,RE,RE)    !P !  !HSAUTHMAINT.OBJ;1           35/36   9-SEP-1994 13:08  (RWED,RWED,RE,RE)    !P !->!HSDMN.CLD;2                   3/4   7-SEP-1994 12:45  (RWED,RWED,RE,RE)    !P !  !HSDMN.EXE;1                 61/62   9-SEP-1994 13:09  (RWED,RWED,RE,RE)    !P !  !HSDMN.MAR;3               100/100   7-SEP-1994 12:48  (RWED,RWED,RE,RE)    !P !  !HSDMN.OBJ;1                 19/20   9-SEP-1994 13:06  (RWED,RWED,RE,RE)    !P !  !HSDRIVER.DOC;7                4/4   7-SEP-1994 13:08  (RWED,RWED,RE,RE)    !P !  !HSDRIVER.EXE;1              21/22   9-SEP-1994 13:09  (RWED,RWED,RE,RE)    !P !  !HSDRIVER.MAR;10           276/276  30-SEP-1994 17:04  (RWED,RWED,RE,RE)    !P !  !HSDRIVER.OBJ;1              24/24   9-SEP-1994 13:05  (RWED,RWED,RE,RE)    !P !  !HSDRIVER.OPT;2                1/2   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSDRIVER_S2.MAR;19        288/288  30-SEP-1994 17:05  (RWED,RWED,RE,RE)    !P !  !HSENTER_PASSWORDS.COM;2       3/4   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSEXEDEL.CLD;2                1/2   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSEXEMPT.CLD;3                2/2   7-SEP-1994 13:02  (RWED,RWED,RE,RE)    !P !  !HSEXEMPT.EXE;1              30/30   9-SEP-1994 13:09  (RWED,RWED,RE,RE)    !P !  !HSEXEMPT.MAR;2              40/40   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSEXEMPT.OBJ;1                5/6   9-SEP-1994 13:06  (RWED,RWED,RE,RE)    !P !  !HSFILDEL.COM;2                3/4   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSFILEMARK.COM;2            14/14   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSFILRST.COM;2                5/6   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSFILSAV.COM;3                4/4  29-SEP-1994 10:27  (RWED,RWED,RE,RE)    !P !  !HSFILUNDEL.COM;2              2/2   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P !  !HSGETLPORT.MAR;2              3/4   7-SEP-1994 12:46  (RWED,RWED,RE,RE)    !P +------------------------------------------------------------------------------+P ! current file no 12    total files 71    files selected 4    display format 2 !P +------------------------------------------------------------------------------+    H When you type the character G (or g) you are given the following prompt:  ' operate on the 4 selected files Y/N [N]   6 If you reply Y, then you enter the file shelving menu.  G If you enter via the MOVEFILE command you will be asked what file(s) toc6 move. Then in either case you enter the shelving menu.  ' The file shelving menu looks like this:l  1       Hierarchical Storage Facility - File Movingd3             File USR$ROOT:[EVERHART.HSM]HSDMN.CLD;2.  ,     -->  Set normal softlink to another file<          Set R/O softlink to another file, moving this there4          Mark and move this file now to backing area+          Quit, make no changes to this filen.          Perform database maintenance commands-          Move and mark all selected files nowe  > This selects what you can do to the file. The three modalitiesC of use are represented. In addition you can do maintenance commands 0 including resetting the file of kernel markings.   		NOTE WELL:  J In this menu, the marking commands work at once, so once you select any ofA 	the first three items, it is too late to quit and leave the file  	alone.i  7 The three types of marking in the menu work as follows:t  : Recall, there are three types of linking that can be used.  F 1. You can create a normal "softlink". A softlink means that when your@ 	file has one, it also has a pointer to another file on possibly@ 	some other device. Whenever someone attempts to open your file,@ 	the other file is opened instead on the other device, invisiblyA 	and with no need for the HSM server even to be involved. As long2= 	as the device the file that really gets opened is on has HSMhC 	control, the I/O channel used is reset to the original device when  	the file is closed.  ? 	For this menu item, you will be asked for the file to link to.fA 	If it exists already, it is used intact. Otherwise, the originaliB 	file is backed up to the desired destination file. Then in eitherC 	case, if the file is exactly the same size as the original file in ; 	bytes, the original file is truncated to zero blocks and ae 	softlink mark is inserted.l  C 	The effect if the file didn't previously exist is to move the fileeA 	to a new location so it is used there for all activities, and torB 	free the space on the original disk. If a link is being set up to? 	a different file somewhere, the effect is just to set that up,tB 	leaving the original file alone unless it appears to be a copy of 	the one linked from."  @ 	Note that softlinks MUST reside on local disks (or devices like> 	jukebox magneto optical disks that act like local disks, withA 	software like Virtual Branches which makes them appear online atnA 	all times or like Squash which will allow compressed storage buti 	will act like a normal disk).  B 2. You can set up a "R/O Softlink". This is a cross between normal< 	shelving and softlinks. You are asked where the file shouldA 	be stored, and the file is moved there. However, the marking setsB 	on it causes it to act like a soft link if the file is opened forB 	read only, and like an unshelving if the file is opened for writeB 	of any kind. That is, if you open the file for read, it is opened: 	on the device where it is saved, directly and without any: 	intervention by the HSM server. If the file is opened forA 	read/write, however, it is treated as having been shelved and ist> 	brought back to normal storage. This makes the "R/O Softlink"B 	ideal for use where files are stored on write-once media or whereB 	the linked copy is desired to be archival and untouched. Once the= 	file is unshelved, it is accessed thereafter on normal disk.o  G 3. You can mark the file and move it to a backing storage area. This is ? 	normal file shelving. This is done by backing the file up to a ? 	save area and marking it as shelved, so that a subsequent opens@ 	will be able to unshelve it. Note that with this choice, if theC 	logical name GCY$ZIPHSC is defined as "YES", the storage is in ZIPy? 	compressed form. This will save considerable space, but at thec@ 	expense of significant CPU time during shelving and unshelving.A 	On slower VAXen this time may be prohibitive. On AXP machines iti; 	may however be acceptable. The logical must be set for thed# 	unshelving to work properly also. s  0 		Note: The shelving and unshelving are actually* 		done under control of the FILSAV.COM and2 		FILRST.COM command files, which can be edited if0 		you feel comfortable doing your own support of- 		those components. (We cannot support customd3 		versions of these files, so if you edit them, yous( 		must support the versions you create.)    E The last menu item, "Move and mark all selected files now", tells thetA 	system to perform the moving of all files you have selected. Thei< 	other menu selections perform their operations immediately,< 	save for the "Quit..." operation which lets you not touch a< 	file. If you select that, it will move to the next file you? 	have selected, if you selected more than one in the fullscreenU@ 	interface or if you selected a wildcard specification with moreD 	than one file matching it. Thus you can mark files one at a time or? 	can mark all at once. Note too that only normal shelving makesl< 	sense to do all at once, since softlinks need to have their 	destinations set individually.e  A The "Perform database maintenance commands" menu looks like this:M  '            Hierarchical Storage Managerm$                 MAINTENANCE COMMANDS        --> Delete this entry:          Remove all database entries for now-deleted files+          Create listing of all files markedl          Repair deleted ACEs/          Change or delete a string in all listse          Done with this menu  2 This menu allows you to work on markings of files.   Delete this entrylC 	means that you are removing markings from the file. Note that thise> 	is NOT the same as unshelving a shelved file. Rather, it justC 	removes the marking that would allow it to be unshelved. Where you C 	have made a soft link to a file, this removes the softlink markingfA 	so that if there's another file that was linked to, an open will A 	now get the original file again. (If of course the original filey< 	was truncated to zero blocks, this may not be very useful.)  1 Remove all database entries for now-deleted filesrB 	searches the database for the current device and ensures that the= 	files it points to still exist. If they do not, the databaseoA 	entries for them are removed. This cleanup is one that should bei@ 	done periodically. Under normal conditions, there will be times= 	when files are deleted and you will want to clean up the HSMf> 	server's database. Note that deleting a shelved file does NOTD 	delete the shelved copy, so the shelved copy remains as a backup of
 	the file.  " Create listing of all files markedD 	creates a file in HSD$DB with file IDs of all files in the database= 	so that it can be used for kernel-marking all files to allowaD 	unshelving operations to succeed even if markings are disturbed. If? 	you are using the option of having HSM ignore all files exceptgC 	those marked, this allows you to produce current markings as well.R= 	The filename will be the same as the HSM database with _LIST-< 	appended to it (which encodes device name in the filename).   Repair deleted ACEs B 	ensures that all file markings match those in the HSM database soA 	that any disturbed markings are restored. Any markings that were 9 	damaged are reported on your terminal at this time also.R  & Change or delete a string in all listsD 	allows global replacement of some string in all the database. It isD 	likely this will VERY rarely be useful for anything but can be usedC 	where something unusual like a device physical name change occurs.WA 	You are prompted for the original string and replacement string.1     USAGE CONDITIONS  > 	HSM should be installed and used on all cluster nodes where aA 	VMScluster is in use, and logical name pointers for HSD$DB whichEC 	point to the device database files must agree. Any node not having @ 	HSM installed will not be able to use its benefits, and shelved- 	files will just appear as zero length files.,  C 	It should be noted too that HSM resets the end of file pointers on:C 	files shelved to the original file size, though the allocated area-@ 	is correctly left as zero blocks after shelving. If you run theD 	ANALYZE/DISK utility, it will complain about this. It is actually aD 	totally harmless condition and will mess nothing up. If this lengthA 	is reset by ANALYZE/DISK/REPAIR, the unshelving process will runRB 	exactly as before, and the only effect will be that the DIRECTORY/ 	command will be unable to show the file size.    > 	Files shelved to a backup area have names changed so that the? 	original file ID is first, and then have the first part of theEB 	original file name. If the HSM system must be down, this makes itC 	fairly straightforward to locate shelved files in nearline storage9: 	by hand, or to locate such files should they be backed up< 	separately and should someone want to access them from such	 	backups.2  A 	Finally, note that finding free space can take considerable timeSA 	on a large disk, and that unshelving requires a copy of the fileEC 	back to its original location. This, too, can require considerableEB 	time. If you have files which must be opened quickly, ensure that> 	your site policy inhibits them from shelving, and if you want= 	to be sure space won't run out, run the MAKSPC script at lowL> 	load hours so that the time required to shelve inactive files> 	will occur at hours when it is unlikely to cause trouble. You? 	are of course free to tailor the commands in the MAKSPC script-@ 	(and you may want to arrange that extremely large files are not? 	autoshelved, for example). The FIND utility is capable of thisUA 	sort of thing readily; its help is supplied to make this sort of  	site configuration possible.   A 	Remember: you choose your site policy and you choose which disks-> 	it applies to. A little advance planning can be a big help in1 	getting a policy that will cause no grief later.e