Class transitions for DB2 objects example scenario

As DB2 objects age, it is desirable to keep the objects online in order to maintain immediate access, but it is also desirable to minimize the cost of maintaining them online. To achieve this, a class transition environment is configured such that the DB2 objects are allocated and maintained on standard DASD for 90 days. After this time, they are transitioned to less expensive SATA DASD. Transitioning the objects to SATA DASD enables the objects to be kept online at a lower cost.

If any object in general remains unreferenced for 95 days, it will become eligible for migration to ML2 tape. Because the DB2 objects are expected to always be allocated and open after 90 days, the SERIALIZATION EXIT will therefore indicate that DB2 should be invoked to close and reopen the objects around the time of this transition. To minimize the period in which these objects are closed to DB2, fast replication will be the preferred data movement technique. The storage group containing the SATA DASD will be given a higher processing priority to help ensure that any objects eligible for migration are migrated off of the SATA DASD to maximize the available space for the objects that will transition to the SATA DASD from the standard DASD.

The storage groups are defined:

         NAME ===> STANDARD
         MIGRATE SYSTEM/SYSPLEX NAME ===>
         AUTO MIGRATE ===> P
         MIGRATION AND ALLOCATION THRESHOLDS: HIGH ===> 85  LOW ===> 20

         PROCESSING PRIORITY ===> 50
  ⋮
         NAME ===> SATA
         MIGRATE SYSTEM/SYSPLEX NAME ===>
         AUTO MIGRATE ===> P
         MIGRATION AND ALLOCATION THRESHOLDS: HIGH ===> 95  LOW ===> 1

         PROCESSING PRIORITY ===> 75

The management class is defined:

 NAME ===> DB2TRANS
               TIME SINCE CREATION         ===> 90
	             SERIALIZATION ERROR EXIT    ===> DB2
	             TRANSITION COPY TECHNIQUE   ===> FRP
	             PRIMARY DAYS NON-USAGE      ===> 95
	             LEVEL 1 DAYS NON-USAGE      ===> 0
	             COMMAND OR AUTO MIGRATE     ===> AUTO
	             EXPIRE AFTER DATE/DAYS      ===> NOLIMIT

During primary space management, the volumes within storage group SATA will be processed first. Any objects that have been unreferenced for more than 95 days will be migrated to tape. After all of the volumes within storage group SATA have been processed, the volumes assigned to storage group STANDARD will be processed. Any object that is 90 days or older will be transitioned to a volume assigned to the SATA storage group. Fast replication will be the preferred data movement technique.