The answer we've received is move to TSM 4.2 using the filelist option.
Filelist will combine numerous archives in one archive session so that the
cleanup process is not invoked as much.
We can't say we're happy about having to re-write something that use to work
GREAT in release 3.1.06 and the ONLY thing changing is a release of the same
product.
Isn't software that degrades performance usually referred to as a virus?
:-)
-----Original Message-----
From: Price, Bob R. [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 1:32 PM
To: [EMAIL PROTECTED]
Subject: Re: Archive hangs and Poor Archive Performance at TSM 4.1.2 &
4.2
I too, have noticed the occasional hang during an archive after updating the
AIX client from 3.1 to 4.1.20. Please post any progress on this problem.
Thanks.
-----Original Message-----
From: Petr Prerost [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 2:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Archive hangs and Poor Archive Performance at TSM 4.1.2 &
4.2
Upgrade to 4.1.3 and use commnad convert node xxxx reorg=yes for node
with archive problems. Check listeserv discussions about this problem
month or two ago.
Regards
Petr
----- Puvodnm zprava -----
Od: "b290" <[EMAIL PROTECTED]>
Komu: <[EMAIL PROTECTED]>
Odeslano: 21. zarm 2001 4:14
Predmet: Archive hangs and Poor Archive Performance at TSM 4.1.2 & 4.2
> I'm trying to find out if anyone out there in TSM land has problems with
> Archiving file after upgrading from ADSM 3.1.06 to TSM 4.1.2 & TSM 4.2.
>
> There is an process using macros to build DSMC archive statements to
archive
> files. At ADSM 3.1.06 it ran fine with sub-second response time. Now
that
> TSM 4.anything is installed the best response time we've seen is 3
seconds,
> the worst is 41 seconds. To make matters worse, Archives hang in idle
wait
> for no apparent reason. We've tried to trace this, but when trace is on,
> archive stop hanging in idle wait. It's a problem determination
nightmare.
>
> The response from IBM is to use the TSM 4.2 with the filelist option and
we
> are working hard to implement this.
>
> Does anyone have ANY ideas on what we might do to improve performance
while
> our EDI techie re-write the process to implement the filelist option?
>
> Any help would be greatly appreciated. This issue has been outstanding
for
> a month now.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this e-mail
message. Any personal comments made in this e-mail do not reflect the views of Blue
Cross Blue Shield of Florida, Inc.
