We migrated our TSM server off of OS390 about 6 months ago. But when we were on OS390 we had that problem and had to go to maintenance level 4.2.1.9 to fix it. A work around seem to be to cycle the TSM server every day.
David >>> [EMAIL PROTECTED] 12/04/02 09:41PM >>> Hello All Our TSM server is experiencing intermittant problems (on average every second day) with these characteristics.... 1. TSM is consuming a lot of CPU resources. 2. There is no TAPE I/O activity occuring when I know there are migrations/reclamations running. 3. I'm unable to logon to TSM using dsmadmc. The login attempt hangs and eventually times out. 4. There is no activity being recorded in the TSM activity log (ie syslog). 5. There is nothing unusual prior to the last entry in the activity log...no errors. Sometimes after and hour or so of TSM doing nothing productive, things come right and everything continues on as normal. Leaving an hour or two's gap in the activity log. On other occasions the TSM server grinds to a halt..Zero CPU activity and Zero tape I/O activity, resulting in us having tp recycle the TSM server. We are running TSM with a region size of 1280MB. I know we are back level in TSM server maintenance and are in the process of migrating to TSM 5.1, but in the meantime has anyone on the list seen something like this or can suggest what I can do to resolve this problem. Thanks Gavin Ring 36-46 George Street Burwood, NSW, 2134 Ph: +61 2 9378-0985 Fax: +61 2 9378-0731
