<font size=2 face="sans-serif">I added support to mmapplypolicy &
co for HPSS (and TSM/HSM) years ago.<br></font><br><font size=2 face="sans-serif">AFAIK, it works pretty well, and pretty
much works in a not-too-surprising way.<br>I believe that besides the Spectrum Scale Admin and Command docs there
are some "red book"s to help,</font><br><font size=2 face="sans-serif">and some IBM support people know how
to use these features. </font><br><br><font size=2 face="sans-serif">When using mmapplypolicy:</font><br><br><font size=2 face="sans-serif">a) Migration and pre-migration to an
external pool requires at least two rules:</font><br><font size=2 face="sans-serif"> An EXTERNAL POOL
rule to define the external pool, say 'xpool' and a MIGRATE ... TO
POOL 'xpool' rule.</font><br><br><font size=2 face="sans-serif">b) Migration between GPFS native pools
requires at least one MIGRATE ... FROM POOL 'apool' TO POOL 'bpool'
rule.</font><br><br><font size=2 face="sans-serif">c) During any one execution of mmapplypolicy
any one particular file will be subject of at most one MIGRATE rule. In
other words</font><br><font size=2 face="sans-serif">file x will be either (pre)MIGRATEd
to an external pool. OR MIGRATED between gpfs pools. BUT not
both.</font><br><br><font size=2 face="sans-serif">(Hmm... well you could write a custom
migration script and name that script in your EXTERNAL POOL rule and do
anything you like</font><br><font size=2 face="sans-serif">to each file x that is chosen for "external"
MIGRATion... But still just one MIGRATE rule governs file x.)</font><br><br><br><BR>