You are abit confused.  The *ONLY* way to have TWO policies applicable to a
given file is to use TWO node-names for your backups;  swapping policy sets
*may* work for your situation, if what you want (and set) is 30 versions of
a given file... that piece will work.

Files can be bound only to one management class at a time; if you try
changing MC for the file, it will change ALL versions to that MC, not just
the next backup.  The policyset-swap trick is useful when changing from
modified to absolute and back;  that's about the only use I've ever seen for
multiple policy sets.  Hope this helps.

Regards,
Don

Don France
Technical Architect - Tivoli Certified Consultant
Professional Association of Contract Employees (P.A.C.E.)
San Jose, CA
(408) 257-3037
don_france AT att DOT net