Erwann, Thanks for pointing it out. I use it for other receivers and remembered the "actlog" option was available, totally missing that tidbit.
-Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann Simon Sent: Wednesday, October 07, 2015 2:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Reg: can we diable events for ANR0422W Hi Rick, Sorry, but this won't work for actlog. The help for disable events command considering actlog receiver says : You can disable only client events, not server events for the activity log. Le 7 octobre 2015 19:33:12 CEST, Rick Adamson <rickadam...@segrocers.com> a écrit : >Try using "disable events"..... for example: "disable events actlog >abcd,abcd,abcd" >Where "abcd" is replaced with the 4-digit number preceeded by ANR. > >See help section 3.15.1 > >-Rick Adamson > > >On Wed, Oct 7, 2015 at 9:42 AM, Srikanth Kola23 <srkol...@in.ibm.com> >wrote: > >> Hi Team, >> >> recently we have moved servers to tsm/ve backups , but most of the >> clients we do not alter sys/opt files & do not kill scheduler service > >> hence we are getting below alerts as a bunch ( we do not have client >> access) >> >> can we disable events for the particular msg number (ANR0422W) for >act >> log tracking for some nodes ( more than 1000) >> >> Oct 7, 2015, 12:08:40 AM ANR0422W Session 15971 for node POKCPSAPAP12 > >> (Linux x86-64) refused - node name not registered. (SESSION: 15971) >> >> Thanks & Regards, >> >> Srikanth kola >> Backup & Recovery >> IBM India Pvt Ltd, Chennai >> Mobile: +91 9885473450 >> -- Erwann SIMON Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
