>From the tsmjbbd.ini file where the client is installed: ; NotifyFilter ; ; Specifies what types of filesystem activity to monitor for ; a journaled filesystem. ; ; Multiple activities may be monitored by combining (logical OR) ; values. ; ; The default value is 0x117 (File and Dir name changes, ; last write changes, attribute changes, size changes, and ; security changes). ; ; ; Notification Type Filter Value ; ; File name changes, including create, 0x00000001 ; delete and rename ; ; Dir name changes, including create, 0x00000002 ; delete, and rename ; ; Attribute changes 0x00000004 ; ; Size changes, notification is deferred 0x00000008 ; until cache is flushed ; ; Last written time changes, notification 0x00000010 ; is defered until cache is flushed ; ; Last access time changes 0x00000020 ; ; Creation time changes 0x00000040 ; ; Security changes 0x00000100
Curt Magura Lockheed Martin EIS Orlando Fla. 321-235-1203 -----Original Message----- From: Richard Foster [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 10:03 AM To: [EMAIL PROTECTED] Subject: Re: File scan takes ages during backup Al You asked Geoff, but I'll reply :) > Did IBM say why the notifyfilter parameter was significant? I'm > curious what that controls. If I remember correctly, IBM said that it controls exactly which events get notified to the journal service. If your journal buffer is filling up, you want to cut out unnecessary events. But I can't remember where they define which bit corresponds to which event. Richard Foster Norsk Hydro asa