Retention of 65 days means "after" 65 days -- so that would be tomorrow; but, 
even then, only AFTER you run EXPIRATION will they be deleted from the db.  To 
prevent/defer that action, just avoid running EXPIRATION.  

Unfortunately, there is not a supported (ie, externalized) mechanism to 
re-establish the expiration of these archived objects... you must either re-run 
the archive job (ugh!), or maybe use EXPORT Node to re-save the data.  See the 
Richard Sims *AND* Josh Bassi responses to this thread, as well -- they are 
BOTH correct.

There is a pending SHARE requirement to change this, so we can "update" the 
retention for an existing archive package... don't know the prospects for 
delivery.



Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT ayett DOT net (change aye to a for replies)

Professional Association of Contract Employees 
(P.A.C.E. -- www.pacepros.com)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Joni Moyer
Sent: Thursday, March 06, 2003 4:27 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: archive retention - quick question!!


Hi everyone!

I just wanted to make sure I understood the archive retention period
correctly so that some of the users at my company don't lose data they
wanted to restore from 12/31/2002.  Apparently they archived the data on
12/31/2002 and it has a retention period of 65 days.  Today is the 65th
day.  Will the files expire today or will they expire tomorrow?  Also, is
there anyway to prevent them from expiring (give them a longer retention
period)  before restoring the file?  Thanks for your help!

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338