Hi, This was some of the things that changes in one of the upgrades, and one of the reasons we turned detailed off...
Regard, Karel ps Reclamation once every hour??? Nice that you can, but why? -----Oorspronkelijk bericht----- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 16:08 Aan: [EMAIL PROTECTED] Onderwerp: Antwort: Re: ANR4391I during expiration Hi Karel, thanks for your answer. The problem is not the detailed output, but the number of entries in the log. The option was on both server on detaillet. But I did not see ever so many same entries before. The expiration runs on this server 1 x hour and I get 1 message per expiration in the log. But after the update I get > 30 messages per second. Here for and after the update: tsm: ADSM_OERAG02>q act begind=-2 search=ANR4391I Date/Time Message -------------------- ---------------------------------------------------------- 11/03/03 15:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 16:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 17:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . after update: 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . Best regards, Frank Mueller Karel Bos <[EMAIL PROTECTED] An: [EMAIL PROTECTED] OM> Kopie: Gesendet von: Thema: Re: ANR4391I during expiration "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 05.11.2003 15:36 Bitte antworten an "ADSM: Dist Stor Manager" Expiration is running without the quiet option. When scheduled update the command by adding quiet=yes, else modify the dsmserv.opt. Regard, Karel -----Oorspronkelijk bericht----- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 15:12 Aan: [EMAIL PROTECTED] Onderwerp: ANR4391I during expiration Hi *, we have 2 TSM-Server runs on 2 x AIX-nodes (AIX 4.3.3). Both server runs with 4.2.2.6 (I know, no support, but I want now migrate to TSM 5.1). So I update the first server to Version TSM 4.2.4.0 Now (after the update) I observe many many entries during a expiration on this server with the same contents: 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. What is the reason for this? What can I do now? Best regards, Frank Mueller
