There is not enough information here to make a thorough diagnosis, but it
is likely that the ANR8216W messages are a result of the ANS1074I
messages, not the cause.

One problem I am aware of at this level of the client (5.1.1.0, if I
understand correctly) is IC34996. For AIX, this is fixed in patch level
5.1.5.11. You might try applying that patch to one or two machines that
consistently see this problem to see if that resolves it.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

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




David E Ehresman <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
03/04/2003 08:54
Please respond to "ADSM: Dist Stor Manager"


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        Re: TSM 5.1.6.2 and AIX client 5.1.1.0



The server side sees error "ANR8216W Error sending data on socket nnn.
Reason 32."  The client gets "ANS1074W ***User Abort***" in the
dsmerror.log.  TSM server is running on AIX 5.1 in 64 bit mode.  The
problems are happening every night and started with the TSM upgrade.
I've opened a PMR but am still trying to find out if anyone else has
already solved this problem.

Can I revert from TSM 5.1.6.2 back to 5.1.1.6 without doing a data base
restore?

David

>>> [EMAIL PROTECTED] 03/03/03 02:30PM >>>
Any ANR / ANS Messages?  Any more details you can provide?

-----Original Message-----
From: David E Ehresman [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 1:25 PM
To: [EMAIL PROTECTED]
Subject: TSM 5.1.6.2 and AIX client 5.1.1.0


I just got back from a week off and we are having problems with
backups
not finishing.  The backup client is on AIX backup level 5.1.1.0
backing
up to an AIX server at TSM level 5.1.6.2.  Anyone else seen problems
with this combination?

David

Reply via email to