Remco, Sorry for the db2 answer I'm about to give, but the diaglog size can be restricted by updating the dbm configuration parameter diagsize. Run the following command as the instance owner tsm1:
"db2 update dbm cfg using diagsize 400" See http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.config.doc/doc/r0054862.html for more details. A restart of db2 and thus TSM is required afterwards. best regards, Kurt (who is both a db2 and tsm admin) ________________________________________ Van: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] namens Remco Post [r.p...@plcs.nl] Verzonden: maandag 14 maart 2011 13:59 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] undocumented ANR Hi All, the more time I spend engeneering with TSM version 6, the more unpleasant surprises I get. To prevent one TSM server from filling up the home file system and crashing all TSM servers on that box, we had decided to create a saparate home filesystem for each TSM server on a box. The installation guide told us that each DB2 instance requires about 450 MB in the home filesystem, so we allocated space for that. Turns out that IBM forgot to print a 1 because during dsmserv format I got: "ANR1547W The server failed to update the DBDIAGLOGSIZE server option due to insufficient available space. Required space: 1024 megabytes; available space: 174 megabytes. The current value:2 megabytes." I never asked for a diaglog of 1 GB! how do I tell TSM that really, 174 MB is more that enough? I really hope that nobody really needs 1 GB of diag log... The log should roll over after a few days, right? -- Met vriendelijke groeten, Remco Post, PLCS *** Disclaimer *** Vlaamse Radio- en Televisieomroeporganisatie Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/gebruiksvoorwaarden