We have that very same issue running TSM 4.1.2.14 on AIX 4.3 with TSM 4.1.4 running on OS/390 V2R9. Traces yield different results the few times the hang occurred while trace was activated. Most times it doesn't hang at all with trace active. Archive sessions do run SLOWWWW!
We are currently working with IBM. They are now going to bring a Performance person to the conference call. Archives running in macro files worked fine in ADSM 3.1.06. After moving to TSM 4.1.2.14 the hangs occurred. IBM suggested that when we install TSM 4.2.0, then re-write the process to take advantage of a filelist feature, bundling numerous(the more, the better) file archives in one archive session. This failed in TSM 4.12.0, so IBM then suggested that we install TSM 4.2.1. The failures don't occur as often, but the hangs still do from time to time. This has been a "Moving Target", so problem determination is almost impossible. How many archives are being done per day at your site? IBM tells us that we were doing too many for TSM 4.x archive to handle. -----Original Message----- From: Gerd Bentel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 11:00 AM To: [EMAIL PROTECTED] Subject: hang archive (dsmc) on Sun Solaris Hi In the moment we have a problem, that sometimes the dsmc command hang and we dont't know why. We make an dsmc archive command (Sun Machine E10000 under Solaris 2.7 and TSM Client 4.1.2.14) and sometimes the dsmc command hang. The TSM Server is on OS/390 TSM 3.7.4. To get more information we try an Client trace but this was not very helpful. Because the last entries in the tracefile where always different. Have anybody the same problem and perhaps the solution? Thank you Gerd Bentel Sparkassen Informatik GmbH & Co. KG Standort Fellbach Datenhaltung-Middleware Wilhelm-Pfitzer-Str. 1 70736 Fellbach Telefon: (0711) 5722-2142 Telefax: (0711) 5722-1630 Mailadr.: [EMAIL PROTECTED] 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.
