Hi

>From previous experience, when I was using  TSM 4.2 I had set the
commitimeout and the idletimeout to a big value...ie 500000

At that time the restore completed successfully, now we upgraded aix 5.2 64
bit from aix 4.3.3 32 bit and db2 to 64 bit from 32 bit.

The idletimeout is set at 500000 and it loses the session when it is at
sendw (30 seconds).

Please help....

Thanks

Lindy

-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU]
Sent: 18 September 2003 05:42
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM AIX client


>Has anyone had any problems with TSM AIX client 5.2 64bit ? I am using
>aix5.2 64bit and  tsm client 64 bit....with db2 backing up to tsm, but my
>session is lost during a restore. it continues to create the containers and
>once it come to the step of restoring data ...the db2 restore fails as the
>session was dropped when creating the first container.
>
>Any ideas ????

The first step, always, is to look for reasons in your client and server
logs.
Thereafter you can address the issue.  As indicated in another response,
default server timeout values are almost always too low, and generally need
generous boosts.  Smallish timeouts kick out useless client sessions, but
can
also terminate long-dwell, viable sessions.

   Richard Sims, BU


This email and any accompanying attachments may contain confidential and
proprietary information.  This information is private and protected by law
and accordingly if you are not the intended recipient you are requested to
delete this entire communication immediately and are notified that any
disclosure copying or distribution of or taking any action based on this
information is prohibited.

Emails cannot be guaranteed to be secure or free of errors or viruses. The
sender does not accept any liability or responsibility for any interception
corruption destruction loss late arrival or incompleteness of or tampering
or interference with any of the information contained in this email or for
its incorrect delivery or non-delivery for whatsoever reason or for its
effect on any electronic device of the recipient.

If verification of this email or any attachment is required please request a
hard-copy version