Re: ANR4391I during expiration

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:fmu AT OERAG DOT DE]
Verzonden: woensdag 5 november 2003 15:12
Aan: ADSM-L AT VM.MARIST DOT EDU
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