Re: 4.2 server memory corruption
We have upgraded our OS/390 TSM server to 4.2.1.9. This appears to have resolved our performance problems. I would like to thank Bill Colwell, John Naylor, and Brian Nick for their advice and assistance. The first time we started the server it reported that it was upgrading its database, even with the relatively small change in level. We upgraded to 4.2.1.0 before going to 4.2.1.9. The 4.2.1.0 upgrade was packaged as SMPE input. SMPE is the standard OS/390 software maintenance tool, which keeps track of installed levels, verifies that prerequisite products are installed, and so on. The 4.2.1.9 upgrade was delivered as three replacement files with no provision for SMPE tracking. Tivoli has made choices that have led to essentially interchanging the roles of maintenance releases and patches. Sites that need stable code frequently end up running patches for long periods. Given this reality, I find it extremely annoying that patches are not packaged as SMPE input.
Re: 4.2 server memory corruption
Tom, you should think seriously about upgrading to 4.2.19. I have experienced problems like you describe, but not since I went to 4.2.1.6; since then I have gone up to .9 without problems. Also, I used to run with region=0m in the JCL for tsm. While working with level 2 on a problem like what you had, I was told to specify a region size because during initialization tsm takes some small percent of the region and formats it as cellpools to avoid getmains and freemains; with region=0m it using a default which was too small. The site to download 4.2.1.9 is NOT an anonymous FTP site, you need an id and password which at one time was listed in the read-me that goes into sanrsamp during the smp apply, or you can get it from Tivoli support. At 03:41 PM 2/20/2002 -0500, you wrote: >We have a 4.2.0.0 server running under OS/390. We recently started seeing >increasingly serious performance problems with no obvious cause. The server >froze up entirely this morning. I had some difficulty shutting it down. The >server accepted a 'halt' command and generated an 'ANR5963I ADSM server >termination complete' complete message fairly rapidly. However, the started >task continued to run, and continued to use large amounts of CPU time, even >after the message. I finally cancelled the started task. The server came >back up without incident and is now performing much better. One of my >co-workers noted that the server had been up for 32 days, which was by far >the longest stretch of continued uptime since we went to 4.2 (we had >previously IPLed OS/390 every week or two for reasons unrelated to TSM). >This raises the suspicion of some kind of memory corruption that causes >server performance to degrade over time. Is the 4.2.0.0 server known to >suffer from any problems of this sort? -- Bill Colwell C. S. Draper Lab Cambridge Ma.
Re: 4.2 server memory corruption
Thomas, I believe that this is a known issue with the TSM 4.2.0.0 server on all platforms. We have always cycled our ADSM and now TSM servers once a week on OS/390 as we use FDR to backup all of the TSM data base and storage pool volumes over a weekend. If you go to the Tivoli product support site you can find patch levels 4.2.1.8 and 4.2.1.9 for the OS/390 server. Hope this helps. Brian Brian L. Nick Systems Technician - Storage Solutions The Phoenix Companies Inc. 100 Bright Meadow Blvd Enfield CT. 06082-1900 E-MAIL: [EMAIL PROTECTED] PHONE: (860)403-2281 "Thomas Denier" cc: Sent by: "ADSM: Subject: 4.2 server memory corruption Dist Stor Manager" <[EMAIL PROTECTED] EDU> 02/20/02 03:41 PM Please respond to "ADSM: Dist Stor Manager" We have a 4.2.0.0 server running under OS/390. We recently started seeing increasingly serious performance problems with no obvious cause. The server froze up entirely this morning. I had some difficulty shutting it down. The server accepted a 'halt' command and generated an 'ANR5963I ADSM server termination complete' complete message fairly rapidly. However, the started task continued to run, and continued to use large amounts of CPU time, even after the message. I finally cancelled the started task. The server came back up without incident and is now performing much better. One of my co-workers noted that the server had been up for 32 days, which was by far the longest stretch of continued uptime since we went to 4.2 (we had previously IPLed OS/390 every week or two for reasons unrelated to TSM). This raises the suspicion of some kind of memory corruption that causes server performance to degrade over time. Is the 4.2.0.0 server known to suffer from any problems of this sort?
4.2 server memory corruption
We have a 4.2.0.0 server running under OS/390. We recently started seeing increasingly serious performance problems with no obvious cause. The server froze up entirely this morning. I had some difficulty shutting it down. The server accepted a 'halt' command and generated an 'ANR5963I ADSM server termination complete' complete message fairly rapidly. However, the started task continued to run, and continued to use large amounts of CPU time, even after the message. I finally cancelled the started task. The server came back up without incident and is now performing much better. One of my co-workers noted that the server had been up for 32 days, which was by far the longest stretch of continued uptime since we went to 4.2 (we had previously IPLed OS/390 every week or two for reasons unrelated to TSM). This raises the suspicion of some kind of memory corruption that causes server performance to degrade over time. Is the 4.2.0.0 server known to suffer from any problems of this sort?
