Thank you very much. Node groups are used for backup sets. It was my mistake.
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: G.Solonovitch AT bkme
DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM User
Sent: Wednesday, August 26, 2009 1:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Collocation node group question
Grigori:
LPAR07_GROUP is not a collocggroup. It is a nodegroup.
To view the "Collocation group", run "q COLLOCGROUP "
On Wed, Aug 26, 2009 at 6:51 AM, Grigori Solonovitch <G.Solonovitch AT bkme DOT
com
> wrote:
> Dear TSMAdmins,
> I have faced next problem in TSM Server 5.5.3 under AIX 5.3:
>
> tsm: BKME>query LPAR07_GROUP f=d
>
> Node Group Name Node Group Description Last Update by Last
> Update Node Group Member(s)
>
> (administrator) Date/Time
> ------------------------ ------------------------------
> -------------------- ----------------- ------------------------------
> LPAR07_GROUP SA25577
> 08/26/09 LPAR07 LPAR07_ORA
>
> 12:30:01
>
> tsm: BKME>move nodedata collocggroup=LPAR07_GROUP from=daily_2
> ANR4877E MOVE NODEDATA: Collocation group LPAR07_GROUP is not defined.
> ANS8001I Return code 11.
> tsm: BKME>
>
> Could somebody explain this?
> Kindest regards,
>
>
> Grigori G. Solonovitch
>
> Senior Technical Architect
>
> Information Technology Bank of Kuwait and Middle East
> http://www.bkme.com
>
> Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail:
> G.Solonovitch AT bkme DOT com<mailto:G.Solonovitch AT bkme DOT com>
>
> Please consider the environment before printing this Email
>
>
> Please consider the environment before printing this Email.
>
> ________________________________
> "This email message and any attachments transmitted with it may contain
> confidential and proprietary information, intended only for the named
> recipient(s). If you have received this message in error, or if you are not
> the named recipient(s), please delete this email after notifying the sender
> immediately. BKME cannot guarantee the integrity of this communication and
> accepts no liability for any damage caused by this email or its attachments
> due to viruses, any other defects, interception or unauthorized
> modification. The information, views, opinions and comments of this message
> are those of the individual and not necessarily endorsed by BKME."
>
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are not the
named recipient(s), please delete this email after notifying the sender
immediately. BKME cannot guarantee the integrity of this communication and
accepts no liability for any damage caused by this email or its attachments due
to viruses, any other defects, interception or unauthorized modification. The
information, views, opinions and comments of this message are those of the
individual and not necessarily endorsed by BKME."
|