content_image/979248.jpg
<img src='content_image/979248.jpg'>

1. A volume becomes candidate for delete-expire when all the following conditions are met: 

- The amount of time since the volume entered the scratch category is equal to or greater than the Expire Time. 

- The amount of time since the data recorded in that volume was created or last modified is greater than 12 hours. 

- At least 12 hours has passed since the volume was migrated out or recalled back into disk cache. 

Up to 1,000 delete-expire candidate volumes can be deleted per hour. The volumes that were within the scratch category the longest are deleted first. If a volume is selected for a scratch mount before it delete-expired, the previous data in that volume is deleted immediately at first write. 

2. If EXPIRE HOLD is set, the virtual volume cannot be mounted during the expire time duration and is excluded from any scratch counts surfaced to the host. The volume category can be changed, but only to a private category, which allows accidental scratch occurrences to be recovered to private. If EXPIRE HOLD is not set, the virtual volume can be mounted or have its category and attributes changed within the expire time duration. The volume is also included in scratch counts surfaced to the host. With R5.0, the maximum Expire hold time allowed was increased 10 - 2000 years (730,000 days or 17,520,000 hours), to accommodate user’s requests. 

Note:  No cross-check is conducted between defined categories in the z/OS systems and the definitions in the TS7700. 

