Life-Cycle of a SMS data set under CA Disk

Document ID : KB000106869
Last Modified Date : 17/07/2018
Show Technical Document Details
Question:
How does the supposed Life-Cycle of a SMS data set under CA Disk look like?
Answer:
Life-Cycle of a SMS data set under CA Disk
 
The best way to follow the life-cycle of a SMS managed dataset is to list all the SMS parameters involved like in the following sample:             
 
Expire after days non-usage:                       365          
Primary days non-usage:                             33           
Level-1 days non-usage:                             60           
Backup frequency:                                    0            
Max. Number of backup versions data set exists:      5                    
Max. Number of backup versions data set deleted:     2                    
Retain days only backup:                           100          
Retain days extra backup:                           30 
 
         

                                                                            
and then to go through the supposed life-cycle of a corresponding data set as follows.                                                   
 
Running a daily BACKUP for changed data sets then gives: 

Dataset status          Day     Backup versions available            
--------------          ---     ---------------------------          
Changed                   1     1                            
Changed                   2     2, 1                         
Changed                   3     3, 2, 1                      
Changed                   4     4, 3, 2, 1                   
Changed                   5     5, 4, 3, 2, 1                
Changed                   6     6, 5, 4, 3, 2                

Changed                   8     8, 7, 6, 5, 4 

There are max. 5 backup versions available if the data set changes daily, because of Max. Number of backup versions data set exists = 5

Note:
Backup frequency specifies the number of days that must pass before CA Disk will back up the data sets that have changed since the last backup!               

                                                                            
Last change on day       10      10, 9, 8, 7, 6               
Not used                 12      10, 9, 8, 7, 6               
Not used                 30      10, 9, 8, 7, 6               
Not used                 36      10, 9, 8, 7, 6               
Not used                 37      10, 9, 8, 7                  
Not used                 38      10, 9, 8                     
Not used                 40      10

After 30 days without new backup, there is only 1 backup version left because of Retain Days Extra Backup = 30.   
IXMAINT has deleted the older Backup entries.           
                                                                            
Archive to disk          44      10                            
The dataset gets archived to disk on day 44 (after 10 + 33 days) because of Primary days non-usage = 33.                       
                                                                            
Archive to Tape          71      10                           
The data set gets archived to tape (by MERGE Disk to Tape) on day 71 (after 10 + 60 days) because of Level-1 days non-usage = 60.
This is equivalent to a HSM Migrate from level 1 to level 2 storage 60 days after last use.
                                                                             
Expired                 376      10                           
The Archive entry is deleted (by an IXMAINT) after 10 + 365 days because of Expire after days non-usage = 365
                                                                             
Last Backup deleted     476      --
The Last Backup is deleted (by an IXMAINT) after 10 + 365 + 100 days because of Retain days only backup = 100