I'm a mainframe person that is new to server backups, ADSM and this list.
When I try the SELECT * FROM BACKUPS for a specific node, the command goes
on and on and on, but I do notice that the DIR all say STANDARD and the
files all say DEFAULT. I guess I still don't know why the files say
"DEFAULT", unless it's just saying that it uses the DEFAULT, which in my
case is STANDARD. I would have expected that they both say STANDARD. Or is
the word "DEFAULT" meaning the files are using the GLOBAL System default.
-- Thanks Karen
-----Original Message-----
From: Richard Sims [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 02, 2000 11:48 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM Management Classes
>I don't understand why e$ and g$ is expiring and bound to
both management
>class STANDARD AND DEFAULT?
>
>Support has made these two comments:
>
>1) This would be normal if a file space were being bound to
2 management
> classes.
>2) This could be a situation that a client or group of
clients is set with
> the word DEFAULT as the management class. It's actually
not going to a
> management class of that name but to their default one.
It's only being
> listed due to that's how the client reported it to the
server.
Karen - In doing a SELECT * FROM BACKUPS on my AIX system
(on a node with
minimal data so as to make the output reasonable), I
see that the
management class name for directories is a specific name,
and for files it is
"DEFAULT". This makes sense in my case at least because of
the TSM rule that
directories are bound to the management class with the
longest retention so as
to assure living at least as long as the mix of managment
classes that the
files may be under, so as to assure that the directory
structure can always be
rebuilt. This may be the case on your system as well.
Remember that initial
binding to management class occurs when files are backed up,
and doesn't
change until another backup of those object names occurs
again after policy
rules have changed; so I suspect that the rules in effect
when your backups
were done causes the binding that you are now seeing. Re
1), remember that
binding is not by filespaces, but by individual file system
objects. You
might want to look into this more deeply via Select's.
Richard Sims, BU
