ADSM-L

Re: Useless (to me) error needs explanation......

2004-06-10 12:27:53
Subject: Re: Useless (to me) error needs explanation......
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 10 Jun 2004 12:27:36 -0400
Thanks for the response.

Here are the server messages I found, around that time:

06/09/04 20:34:28     ANR9999D imutil.c(4127): ThreadId<42> Primary row
for Backup.Objects object 0.233632121 not found(rc = 2).
06/09/04 20:34:28     ANR9999D imgroup.c(1121): ThreadId<42> Error 19
retrieving Backup Objects row for object 0.233632121
06/09/04 20:34:28     ANR9999D smnode.c(6745): ThreadId<42> Session 1131:
Invalid Group Id 0,233632121 for ADD function
06/09/04 20:34:29     ANR0403I Session 1131 ended for node
XYTHOSDB.VCU.EDU (WinNT).

<session stats snipped>

06/09/04 20:34:38     ANR2579E Schedule ADMINSYS in domain ADMINSYS for
node XYTHOSDB.VCU.EDU failed (return code 12).
06/09/04 20:34:38     ANR0403I Session 1130 ended for node
XYTHOSDB.VCU.EDU (WinNT).

FYI, in case this is server related, it is AIX 5.2.1.3 !




Andrew Raibeck <storman AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/10/2004 11:51 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Useless (to me) error needs explanation......






What messages do you see in the server actlog when this occurs? The only
APAR that I know of that comes close to matching this is IC38377, but that
is supposed to be fixed at the level you are running (I'm not convinced
that's it, either, but it's worth a shot...). Make sure your API is at the
current level as well. Otherwise I suggest contacting IBM technical
support for further assistance.

As to the message.... yes, not very helpful. API messages are sometimes
intended more for application developers; so for TSM application
developers (be it our own Data Protection products or other vendor
products that use the TSM API), the message may make more sense. With that
said:

- If the message is geared for other than end user, we should indicate as
much.

- Message explanation should NOT restate the message text. It should be
"None" if there is no additional explanation, or else try to offer
additional insight into the error.

- User response needs to be.... er.... usable.   :-)    Caveat: it won't
always be able to give you a *solution*, but it should always at least
point in you a direction where you can move the problem forward.

We are aware of these issues and efforts to address them are underway,
even as I type this response

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/10/2004
06:29:08:

> Can someone expand on this pretty useless message and its useless
> explaination:
>
> 06/09/2004 13:46:53 ConsoleEventHandler(): Caught Logoff console event .
> 06/09/2004 13:46:53 ConsoleEventHandler(): Process Detached.
> 06/09/2004 13:46:54 ConsoleEventHandler(): Caught Logoff console event .
> 06/09/2004 13:46:54 ConsoleEventHandler(): Process Detached.
> 06/09/2004 20:34:36 findAbortState: Unknown abort #237 from the server
> 06/09/2004 20:34:46 ANS0343E An invalid operation was attempted on a
group
> leader or group member.
> 06/09/2004 20:34:46 ANS1512E Scheduled event 'ADMINSYS' failed.  Return
> code = 12.
>
> And the ever wonderfully helpful book says:
>
> ANS0343E An invalid operation was attempted on a group leader or group
> member.
> Explanation: An invalid operation was attempted on a logical group.
> System Action: The current operation stops.
> User Response: Retry a valid operation.
>
> What the heck is it talking about ?  What group ? What logical group ?
> What group leader ?  What group member ?  What invalid operation ?  What
> is an "Unknown abort #237"
>
> TSM Client is the latest Windows 5.2.2.10 with the latest SQL TDP !