[no subject]

NOTE: Management classes with the same name but which are within a
different policy domain will NOT conflict with eachother.

NOTE: Changes to a policy set will NOT have ANY effect unless that
policy set is copied into the active policy set with ACTIVATE POLICYSET.
Only the active policyset, and not it's source policyset or any other,
will have an effect.

NOTE: Active versions are converted to inactive only by the client,
through client-side expiration.  See the particular client code manual
for details. This may happen during a backup with an exclude list, or
during a backup with missing files, or through an API call to expire the
object.

NOTE: There are other parameters for all of these structures.  Please
see the ADSM/TSM Administrator's Reference Guide for details.



-------
EXAMPLE
EXAMPLE
-------
Backup copygroup is set as follows:
Backup copygroup is set as follows:
   VDE = 3
   VDD = 1
   RETEX = 100
   RETO = 1

Explaination:
 - Versions 1 through three are kept up to 100 days FROM WHEN THEY
   WERE BACKED UP.
 - Any versions past 3 will be expired immediately upon the next
   server-side EXPIRE INVENTORY process.
 - NOTE: NO MORE THAN THREE VERSIONS WILL BE KEPT AFTER EXPIRE
   INVENTORY, REGARDLESS OF THE NUMBER OF DAYS SPECIFIED IN
   RETAIN-EXTRA AND RETAIN-ONLY!
 - If the active version is made inactive (client side expiration),
   then only the most recent copy will be kept, and it will only
   be kept for one day FROM WHEN IT WAS BACKED UP.

-------
EXAMPLE
EXAMPLE
-------
Backup copygroup is set as follows:
Backup copygroup is set as follows:
   VDE = NOLIMIT
   VDD = NOLIMIT
   RETEX = 14
   RETO = 20

Explaination:
 - All versions will be kept for 14 days FROM WHEN THEY ARE BACKED UP.
 - When no active version remains (client-side expiration), the last
   inactive version will be kept for 20 days FROM WHEN BACKED UP.


-------
EXAMPLE
EXAMPLE
-------
Backup copygroup is set as follows:
Backup copygroup is set as follows:
   VDE = 5
   VDD = 0
   RETEX = NOLIMIT
   RETO = NOLIMIT

Explaination:
 - 5 versions will be kept while an active copy exists.
 - Files will not expire by age.
 - When the active version is made inactive, the next EXPIRE INVENTORY
   will remove ALL versions of the file.

------------------
DISCLAIMER/CONTACT
DISCLAIMER/CONTACT
------------------
Please test or verify any new policy settings before putting into
Please test or verify any new policy settings before putting into
production.

As usual, no guarantees, and if you have problems, call IBM support.