Versions data exists specifies the number of versions - period - to keep.
Example:  If versions data exists = 3 that means 1 active version and up to 2
inactive versions.

Retain extra versions refers how long to keep the inactive files......so yes
if you keep inactive copies longer than 30 days they'll be deleted even if
there are less than 3 extra versions.  That's how I read it.  It's not the
easiest thing in the world to understand.  We went for a long time thinking
that like mainframe generation datasets, the extra (inactive) versions would
be kept until they were "bumped" off by another version.




ADSM-L AT VM.MARIST DOT EDU on 12/18/98 10:26:09 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Simple Question

I am a bit confused about management classes. Specifically the number of
backup versions to keep.
I understand that versions data exists specifies the number of
'inactive' copies to keep but then what does retain extra versions do.
They seem to contradict each other. Does one override the other. If I
say keep 3 extra versions and keep inactive copies 30 days, does that
mean that any inactive copies kept longer than 30 days will be deleted
even if there are less than 3 extra versions and visa-versa

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017
(212)716-2810