Re: Copy Controls
2000-03-16 09:39:39
Gary...
The retain parameters only "rule" in ADSM V3 servers.
On TSM 3.7 it works differently. The version parameter "rules"
.....and that's why I asked whether anything changed??
GOD Bless
Clarence Beukes
IT Specialist (ADSM/TSM)
IBM Intergrated Technology Services
Tel : +2711 302 5333 Fax : +2711 302 8209
Mobile : +2782 573 5665
"A computer is almost human - except that it does not blame its mistakes on
another computer. "
Gary Ison <Gary.Ison AT MAIL.STATE.KY DOT US> on 03/16/2000 03:42:57 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Clarence Beukes/South Africa/IBM)
Subject: Re: Copy Controls
Clarence,
You have the same view that I did until the light came on. Yes,
the
"retain" parameters really rule. They are the point at which "inactive"
files become "obsolete" files. Versioning parameters only determine when
an
object becomes "inactive" - not "obsolete". Only "obsolete" files are
truly
removed from *SM. If you want files to disappear from *SM when the
"version" parameters apply, change the "retain" values to zero.
This is kind of a safety valve for users who misjudge file activity
and how many versions to keep.
There is another parameter that may also have an effect on this
apparent "problem". Look at the "define domain" syntax and you'll find
that
there are parameters at the domain level (across all clients in the domain)
that also affect retention.
Just big brother looking out for us poor dumb hicks, I guess.
Gary L. Ison
Governor's Office for Technology
101 Cold Harbor Drive
Frankfort, Ky. 40601
Phone: (502) 564-8724
Fax: (502) 564-6856
E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky
DOT us>
|
|
|