thank you very much for your answer !

i might know the "consequences of vital archive files which are
supposed to be retained
for five years, which suddenly get cut back to 90 days because of a
management class slip-up in TSM server administration"

does that (all) mean if i create mc in new pd which has the exactly
same name and copy group values the data will preserve their original
retention ?

as for second ... yea. i have these administration files ... around
150 *.txt files with all kind of mumbo jumbo "define ... yada yada"
and other stuff :-)  , yes i agree that this kind of administration is
very useful but i tought i would make a step further with my "select
..." idea

thanks a lot again.

<me going to write select "define schedule" again>

peace,
//
g



On Wed, Sep 17, 2008 at 3:25 PM, Richard Sims <rbs AT bu DOT edu> wrote:
> On Sep 16, 2008, at 5:30 AM, goc wrote:
>
>> ...basically my question is what will happen to data archived with
>> old mc ?
>
> The Admin Guide manual basically sums it up:
>
> "If the management class to which an archive copy is bound no longer
> exists or no longer contains an archive copy group, the server uses
> the default management class.  If you later change or replace the
> default management class, the server uses the updated default
> management class to manage the archive copy.
>
> "If the default management class does not contain an archive copy
> group, the server uses the archive retention grace period specified
> for the policy domain."
>
> Be very careful to assure always having a management class copy group
> which guarantees keeping files around as long as you assured client
> sites that they would be retained in the TSM server.  Consider the
> consequences of vital archive files which are supposed to be retained
> for five years, which suddenly get cut back to 90 days because of a
> management class slip-up in TSM server administration.
>
>> the second thing is ... is there a way to copy schedule definition to
>> new domain ? this is really pain in the ass ... i even tried to make
>> select statement from client_schedules to create "define schedule ..."
>> yada yada but i gave up after few days :-)
>
> I always recommend keeping "administration files" containing the
> "source commands" for all the current settings in the server.  When
> changing things, update the commands in the file, and then paste them
> into a dsmadmc session to effect the changes.  Such file-based
> management makes it easier to see your server values at a glance, and
> you can place lots of comments in the file to explain the rationale
> for choices, etc.  And, such a file is very helpful for server
> replication and disaster recovery.
>
>    Richard Sims
>



--

Erma Bombeck