<font size=2 face="sans-serif">Not withstanding JAB's remark that this
may not necessary:</font><br><br><font size=2 face="sans-serif">Some customers/admins will want to "stage"
a fileset in anticipation of using the data therein.</font><br><font size=2 face="sans-serif">Conversely you can "destage"
- just set the TO POOL accordingly.</font><br><br><font size=2 face="sans-serif">This can be accomplished with a policy
rule like:</font><br><br><font size=2 face="sans-serif">RULE 'stage' MIGRATE FOR FILESET('myfileset')
TO POOL 'mypool'</font><br><font size=2 face="sans-serif"> /* no FROM POOL clause is required,
files will come from any pool - for files already in mypool, no work is
done */</font><br><br><font size=2 face="sans-serif">And running a command like:</font><br><br><font size=2 face="sans-serif">mmapplypolicy /path-to/myfileset -P
file-with-the-above-policy-rule -g /path-to/shared-temp -N nodelist-to-do-the-work
...<br></font><br><font size=2 face="sans-serif">(Specifying the path-to/myfileset on
the command line will restrict the directory scan, making it go faster.)</font><br><br><br><font size=2 face="sans-serif">As JAB remarked, for GPFS POOL to GPFS
POOL this may be overkill, but if the files have been "HSMed"
migrated or archived to some really slow storage like TAPE ... they
an analyst who want to explore the data interactively, might request a
migration back to "real" disks (or SSDs) then go to lunch or
go to bed ...</font><br><br><font size=2 face="sans-serif">--marc of GPFS</font><BR>