[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[prn]
	Apple LaserWriter II NTX
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	
	
	
	
	
	801519665
	51
	791504596
	5328
	30
	0
	0
	0
	0
	
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
	
	
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Ahead
	3
	[fnt]
		Arial
		220
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		240
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		2160
		3
		0
		1
		1
		1
		65
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		79
		0
		3
		100
	[brk]
		80
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead
	6
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		180
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	7
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		300
		300
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		<*:>.
		0
		3
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	Bullet
	9
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		120
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Bullet
	2
	1
	160
	1
	400
	0
[tag]
	See also hlp
	11
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		180
		0
		3
		100
	[brk]
		96
	[line]
		9
		0
		3
		0
		1
		1
		1
		70
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Crossref
	0
	120
[tag]
	See also prnt
	12
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	2nd lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		600
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	1st lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Indnt bullet
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		420
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		16
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	Book art
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Book art
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Callout text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Callout text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Figure title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		60
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Arial
		280
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		300
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Chapter title
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Right pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Right pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Left pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Left pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Table title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		60
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		4
	[line]
		10
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table Text
	0
	0
[tag]
	Crossref
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		513
		3
		0
		300
		600
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Indnt caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt tip
	0
	0
[tag]
	Indnt note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		300
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Dhead
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Dhead
	0
	0
[tag]
	Parameter
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st lev para
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Formula
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		+
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Browse
	0
	0
[tag]
	Keyword
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		K
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Keyword
	0
	0
[tag]
	Context
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		#
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Context
	0
	0
[tag]
	Title
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		$
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Title
	0
	0
[tag]
	Macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		!
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Macros
	0
	0
[tag]
	Footnote
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		244
		0
	[spc]
		40
		2400
		3
		0
		0
		1
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		256
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[frm]
	4
	1573060
	720
	10048
	8273
	11263
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	31
	0
	0
	9920 1162
	[frmlay]
		11295
		7553
		1
		0
		0
		1
		10048
		0
		0
		2
		0
		0
		0
		0
		1
		1224
		9422
		0
	[tbl]
		 5 3 200 86 3420 86 1 43 43
		[h]
			 0 400 326 2 0 1 0
			 1 600 86 2 0 1 0
			 2 1000 86 2 0 1 0
			 3 1000 86 2 0 1 0
			 4 600 86 2 0 1 0
		[e]
		[w]
			 0 2011 86 2 0
			 1 2868 86 2 0
			 2 2373 86 2 0
		[e]
		[data]
			 0 0 8 0 0 0 0 1 0 0 0 0
<+@><+!>Notification<-!><+!> Method<-!>

>
			 0 1 0 0 0 0 0 1 0 0 0 0
<+!>When used<-!>

>
			 0 2 0 0 0 0 0 1 0 0 0 0
<+!>Corresponding Notification Destination<-!>

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Mail

>
			 1 1 0 0 0 0 0 1 0 0 0 0
To mail events to a specified person.

>
			 1 2 0 0 0 0 0 1 0 0 0 0
Name of a Notes administrator or another person.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Log to database

>
			 2 1 0 0 0 0 0 1 0 0 0 0
To report events to a database on a local server. Select this method only if the specified server(s) is reporting events to its own collection database.

>
			 2 2 0 0 0 0 0 1 0 0 0 0
Path and file name of a local database, typically STATREP.NSF.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Relay to other server

>
			 3 1 0 0 0 0 0 1 0 0 0 0
To relay events to a server that is collecting events for servers in the Server name field. This method relays events via the network rather than Notes mail.

>
			 3 2 0 0 0 0 0 1 0 0 0 0
Name of a server that is collecting events.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
SNMP

>
			 4 1 0 0 0 0 0 1 0 0 0 0
<-!><-">To report events to a Notes server management tool such as NotesView</Y>.<-!><-">

>
			 4 2 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,255><+!><+">?????<-"><-!><:f>

>
		[e]
	[tble]
[frm]
	3
	1573060
	720
	6533
	7279
	8292
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	30
	1
	0
	9920 1162
	[frmlay]
		11115
		6559
		1
		0
		0
		1
		6533
		0
		0
		2
		0
		0
		0
		0
		1
		1044
		9242
		0
	[tbl]
		 6 2 200 86 3420 86 1 43 43
		[h]
			 0 200 326 2 0 2 0
			 1 200 86 2 0 2 0
			 2 200 86 2 0 2 0
			 3 200 86 2 0 2 0
			 4 200 86 2 0 2 0
			 5 200 86 2 0 2 0
		[e]
		[w]
			 0 1499 86 2 0
			 1 4845 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
<+!>Severity level<-!>

>
			 0 1 0 0 0 0 0 1 0 0 0 0
<+!>Meaning<-!>

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Fatal

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Imminent system crash

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Failure

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Severe failure that does not cause a system crash

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Warning (high)

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Loss of function requiring intervention

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Warning (low)

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Performance degradation

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Normal

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Status messages

>
		[e]
	[tble]
[frm]
	3
	1573060
	720
	960
	7296
	4577
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	29
	2
	0
	9920 1162
	[frmlay]
		10935
		6576
		1
		0
		0
		1
		960
		0
		0
		2
		0
		0
		0
		0
		1
		864
		9062
		0
	[tbl]
		 9 2 200 86 3420 86 1 43 43
		[h]
			 0 200 326 2 0 2 0
			 1 200 86 2 0 2 0
			 2 600 86 2 0 1 0
			 3 200 86 2 0 2 0
			 4 400 86 2 0 1 0
			 5 200 86 2 0 2 0
			 6 200 86 2 0 2 0
			 7 600 86 2 0 1 0
			 8 200 86 2 0 2 0
		[e]
		[w]
			 0 1186 86 2 0
			 1 5175 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
<+!>Event Type<-!>

>
			 0 1 0 0 0 0 0 1 0 0 0 0
<+!>Information Reported<-!>

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Comm/Net

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Messages<+!><+"><:f180,BArial,0,0,255> <-"><-!><:f>related to modem or network communications

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Security

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Messages related to ID files, and server and database access. Can include notifications generated by an ACL Monitor document

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Mail

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Messages related to mail routing

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Replication

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Messages related to replication. Can include notifications generated by a Replication Monitor document

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Resource

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Messages related to system resources

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Misc

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Miscellaneous messages not in another event category

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Server

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Messages related to conditions tied to a particular server, such as server tasks not executed or problems with the server entry in the Name & Address Book.

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Statistic

>
			 8 1 0 0 0 0 0 1 0 0 0 0
Messages related to alarms you set up.

>
		[e]
	[tble]
[frm]
	13
	1573060
	720
	4113
	8787
	11644
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	28
	3
	0
	8447 51217
	[frmlay]
		3138
		8067
		1
		0
		0
		1
		4113
		0
		0
		2
		0
		255
		255
		65535
		1
		1464
		5754
		0
	[tbl]
		 11 4 200 86 1440 86 1 43 43
		[h]
			 0 600 86 2 0 1 0
			 1 800 86 2 0 2 0
			 2 800 86 2 0 1 0
			 3 1000 86 2 0 2 0
			 4 600 86 2 0 1 0
			 5 1000 86 2 0 1 0
			 6 800 86 2 0 1 0
			 7 1200 86 2 0 1 0
			 8 800 86 2 0 1 0
			 9 600 86 2 0 2 0
			 10 1000 86 2 0 1 0
		[e]
		[w]
			 0 1418 86 2 0
			 1 2142 86 2 0
			 2 1648 86 2 0
			 3 2472 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 8704 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 8704 1 0 0 0 0
Meaning

>
			 0 2 0 0 0 0 8704 1 0 0 0 0
Suggested Threshold/ Severity Level

>
			 0 3 0 0 0 0 8704 1 0 0 0 0
Implication if Threshold Exceeded

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Comm.NumOld SessionsClosed

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Number of sessions closed by server to accommodate new user sessions

>
			 1 2 0 0 0 0 0 1 0 0 0 0
<:s><;>50

<:s>Warning (high)


>
			 1 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>T<:f><:f180,BArial,0,0,0>oo many people attempting to access server or temporary surge in user activity, causing decrease in response time.<:f>

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Disk<+">.n<-">.free

>
			 2 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) amount of disk space free <:f180,BArial,0,0,255><+!><+">W<-!><-"><:f><+!><+"><:f180,BArial,0,0,255>hat about other server platforms? 
<-"><-!><:f>

>
			 2 2 0 0 0 0 0 1 0 0 0 0
<:s><<10,000,000

Warning (high)

>
			 2 3 0 0 0 0 0 1 0 0 0 0
Running out of space on a disk.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Disk.Swapdisk.Free

>
			 3 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>(OS/2 only) Number of free bytes on the disk that contains the servers swap file.<:f> 
<+!><+"><:f180,BArial,0,0,255>W<-!><-"><:f><+!><+"><:f180,BArial,0,0,255>hat about other server platforms? 
<-"><-!><:f>

>
			 3 2 0 0 0 0 0 1 0 0 0 0
<:s><<10,000,000

Fatal

>
			 3 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>A<:f><:f180,BArial,0,0,0>pproaching inadequate space for virtual memory operation, s<:f><:f180,BArial,0,0,0>ince the server uses a swap file for its virtual memory.<:f><:f180,BArial,0,0,0> 
<:f><+!><+"><:f180,BArial,0,0,255>CORRECT?<-"><-!><:f>

>
			 4 0 0 0 0 0 0 1 0 0 0 0
MAIL.Dead

>
			 4 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Number of dead (undeliverable) messages in MAIL.BOX<:f>

>
			 4 2 0 0 0 0 0 1 0 0 0 0
<:s><;>3

Failure

>
			 4 3 0 0 0 0 0 1 0 0 0 0
May indicate a routing or addressing problem.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
MAIL.Transfer Failures

>
			 5 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Number of mail messages router was unable to transfer<:f>

>
			 5 2 0 0 0 0 0 1 0 0 0 0
<:s><;>10

Failure

>
			 5 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>T<:f180,BArial,0,0,0>he router has been unable to transfer some mail messages and the senders of those messages have received non-deliverable reports.  
<:f>

>
			 6 0 0 0 0 0 0 1 0 0 0 0
MAIL.Waiting

>
			 6 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Number of outgoing mail messages currently in MAIL.BOX waiting for transfer<:f>

>
			 6 2 0 0 0 0 0 1 0 0 0 0
<:s><;>20

Warning (high)

>
			 6 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>May indicate a problem with the mailer or the connections that it uses.<:f>

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Mem.Free<-!><-"><+!><+"><:f180,BArial,0,0,255> OS/2 only?<-"><-!><:f>

>
			 7 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Amount of free memory available to the server. In OS/2, this number includes free disk space because of virtual memory capability.<:f>

>
			 7 2 0 0 0 0 0 1 0 0 0 0
<:s><<1,000,000

Fatal

>
			 7 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>The amount of free memory available to the server is dangerously low.<:f>

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Mem.SwapFile.Size

>
			 8 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Size (in bytes) of system swap file<:f>

>
			 8 2 0 0 0 0 0 1 0 0 0 0
<:s><;>20,000,000

Warning (high)

>
			 8 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Can indicate a large load on the server and therefore possible performance degradation.<:f>

>
			 9 0 0 0 0 0 0 1 0 0 0 0
Replica.Failed

>
			 9 1 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Number of attempted replications that returned some kind of error.<:f>

>
			 9 2 0 0 0 0 0 1 0 0 0 0
<:s><;>3

Failure

>
			 9 3 0 0 0 0 0 1 0 0 0 0
<:f180,BArial,0,0,0>Notes is having trouble replicating <:f><:f180,BArial,0,0,0>databases on the server with other servers.  
<:f>

>
			 10 0 0 0 0 0 8192 1 0 0 0 0
Server.Sessions.Dropped

>
			 10 1 0 0 0 0 8192 1 0 0 0 0
<:f180,BArial,0,0,0>Sessions dropped in mid-transaction.<:f>

>
			 10 2 0 0 0 0 8192 1 0 0 0 0
<:s><;>5

Warning (low)

>
			 10 3 0 0 0 0 8192 1 0 0 0 0
<:f180,BArial,0,0,0>U<:f><:f180,BArial,0,0,0>sually indicates that server performance is very slow and users are aborting transactions before they complete. 
<:f>

>
		[e]
	[tble]
[frm]
	6
	1573060
	960
	960
	7537
	1489
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	21
	4
	22016
	30463 36350
	[frmlay]
		5473
		6577
		1
		0
		0
		1
		960
		0
		0
		2
		0
		11
		246
		7029
		1
		1404
		9602
		0
	[tbl]
		 23 2 200 86 4141 86 1 43 43
		[h]
			 0 200 86 2 0 2 0
			 1 600 86 2 0 1 0
			 2 600 86 2 0 1 0
			 3 400 86 2 0 1 0
			 4 600 86 2 0 1 0
			 5 600 86 2 0 1 0
			 6 400 86 2 0 1 0
			 7 600 86 2 0 1 0
			 8 400 86 2 0 1 0
			 9 400 86 2 0 1 0
			 10 600 86 2 0 1 0
			 11 800 86 2 0 1 0
			 12 600 86 2 0 1 0
			 13 400 86 2 0 1 0
			 14 400 86 2 0 2 0
			 15 400 86 2 0 1 0
			 16 400 86 2 0 1 0
			 17 400 86 2 0 1 0
			 18 400 86 2 0 1 0
			 19 400 86 2 0 1 0
			 20 400 86 2 0 1 0
			 21 200 86 2 0 2 0
			 22 400 86 2 0 1 0
		[e]
		[w]
			 0 2390 86 2 0
			 1 3972 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 0 1 0 0 0 0
Description/Comments

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Server.Administrator

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Contents of Administrators field in the Server to Monitor document in the Stats & Events Config database. 
<+!><+"><:f180,BArial,0,0,255>CORRECT?<-"><-!><:f>

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Server.Boot.ID

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Unique number identifying the time the server was booted. Check this statistic to see if a server was restarted.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Server.Coprocessor

>
			 3 1 0 0 0 0 0 1 0 0 0 0
"yes" if server is a 486 or 386 with 387; otherwise "No."

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Server.Description

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Server's description in the Server to Monitor document in the Stats & Events Config database. 
<:f180,BArial,0,0,255><+!><+">CORRECT?<-"><-!><:f>

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Server.Name

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Server name in the Server to Monitor document in the Stats & Events Config database. 
<-!><-"> <:f180,BArial,0,0,255><+!><+">CORRECT?<-"><-!><:f>

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Server.Path.Data

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Location of this server's data directory (or Notes directory on an NLM Server).

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Server.Path.Swap

>
			 7 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) The location of the server's swap path. Default to c:\OS2\SYSTEM unless you set the NOTES.INI SWAPPATH variable differently.

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Server.Ports.RS232

>
			 8 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Number of RS232 ports on this server.

>
			 9 0 0 0 0 0 0 1 0 0 0 0
Server.Sessions.Dropped *

>
			 9 1 0 0 0 0 0 1 0 0 0 0
Number of users who gave up trying to connect to server (usually by restarting or CTRL+Break).

>
			 10 0 0 0 0 0 0 1 0 0 0 0
Server.Task

>
			 10 1 0 0 0 0 0 1 0 0 0 0
The name and status of all server tasks currently running. Can also use server command SHOW TASKS for this information.

>
			 11 0 0 0 0 0 0 1 0 0 0 0
Server.Tasks

>
			 11 1 0 0 0 0 0 1 0 0 0 0
Number of tasks currently executing. This number will probably stay constant. It's more useful to see 
<+">which <-">tasks are running by issuing the server command SHOW TASKS.

>
			 12 0 0 0 0 0 0 1 0 0 0 0
Server.Trans.PerMinute

>
			 12 1 0 0 0 0 0 1 0 0 0 0
Number of transactions that took place in the last minute. Useful in monitoring how much the server is in use.

>
			 13 0 0 0 0 0 0 1 0 0 0 0
Server.Trans.PerMinute.Peak

>
			 13 1 0 0 0 0 0 1 0 0 0 0
Peak number of transactions that took place in any given minute since the server started.

>
			 14 0 0 0 0 0 0 1 0 0 0 0
Server.Trans.PerMinutePeakTime

>
			 14 1 0 0 0 0 0 1 0 0 0 0
Date and time of day that the last peak was reached. Use with Server.Users.Peak.Time.

>
			 15 0 0 0 0 0 0 1 0 0 0 0
Server.Trans.Total

>
			 15 1 0 0 0 0 0 1 0 0 0 0
Total number of transactions the server has serviced since it was started.

>
			 16 0 0 0 0 0 0 1 0 0 0 0
Server.User

>
			 16 1 0 0 0 0 0 1 0 0 0 0
User name, session ID, number of databases accessed.

>
			 17 0 0 0 0 0 0 1 0 0 0 0
Server.Users

>
			 17 1 0 0 0 0 0 1 0 0 0 0
Number of users with sessions open on the server.

>
			 18 0 0 0 0 0 0 1 0 0 0 0
Server.Users.Peak

>
			 18 1 0 0 0 0 0 1 0 0 0 0
The maximum number of concurrent users with open sessions since the server was started.

>
			 19 0 0 0 0 0 0 1 0 0 0 0
Server.Users.Peak.Time

>
			 19 1 0 0 0 0 0 1 0 0 0 0
Date and time of day that the last maximum number of users logged on.

>
			 20 0 0 0 0 0 0 1 0 0 0 0
Server.Version.NLM

>
			 20 1 0 0 0 0 0 1 0 0 0 0
(NLM only) Version of Novell NetWare running on the server.

>
			 21 0 0 0 0 0 0 1 0 0 0 0
Server.Version.Notes

>
			 21 1 0 0 0 0 0 1 0 0 0 0
Notes Release running on the server.

>
			 22 0 0 0 0 0 0 1 0 0 0 0
Server.Version.OS2

>
			 22 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Version of OS/2 running on the server.

>
		[e]
	[tble]
[frm]
	6
	1573060
	960
	5480
	7404
	9439
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	22
	5
	22016
	30463 36350
	[frmlay]
		5113
		6444
		1
		0
		0
		1
		5480
		0
		0
		2
		0
		11
		246
		7029
		1
		1044
		9242
		0
	[tbl]
		 6 2 200 86 4141 86 1 43 43
		[h]
			 0 200 86 2 0 2 0
			 1 600 86 2 0 1 0
			 2 800 86 2 0 1 0
			 3 600 86 2 0 1 0
			 4 400 86 2 0 1 0
			 5 800 86 2 0 1 0
		[e]
		[w]
			 0 2323 86 2 0
			 1 3906 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 0 1 0 0 0 0
Description/Comments

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Mem.Allocated

>
			 1 1 0 0 0 0 0 1 0 0 0 0
(OS/2 and NLM)Total memory allocated (should be sum of Mem.Allocated.Process and Mem.Allocated.Shared).

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Mem.Allocated.Process

>
			 2 1 0 0 0 0 0 1 0 0 0 0
(OS/2 and NLM) Total process-private memory allocated by <+">al<-">l currently running processes. Mem.Allocated=Mem.Allocated.Process+ Mem.Allocated.Shared.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Mem.Allocated.Shared

>
			 3 1 0 0 0 0 0 1 0 0 0 0
(OS/2 and NLM) Total shared memory allocated Mem.Allocated=MemAllocated.Process + Mem.Allocated.Shared.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Mem.Free *

>
			 4 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) as reported by operating system. Sum of disk space and RAM free.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Mem.SwapFile.Size *

>
			 5 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Size of swap file. (Statistic relies on NOTES.INI variable "SWAPPATH" if CONFIG.SYS contains a swap path different from the default.)

>
		[e]
	[tble]
[frm]
	5
	1573060
	960
	2316
	7454
	5161
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	23
	6
	22016
	30463 36350
	[frmlay]
		4933
		6494
		1
		0
		0
		1
		2316
		0
		0
		2
		0
		11
		246
		7029
		1
		864
		9062
		0
	[tbl]
		 7 2 200 86 4141 86 1 43 43
		[h]
			 0 200 86 2 0 2 0
			 1 200 86 2 0 2 0
			 2 400 86 2 0 1 0
			 3 400 86 2 0 1 0
			 4 200 86 2 0 2 0
			 5 400 86 2 0 1 0
			 6 400 86 2 0 1 0
		[e]
		[w]
			 0 2340 86 2 0
			 1 3939 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 0 1 0 0 0 0
Description/Comments

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Disk.<+">n<-">.Free  *

>
			 1 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Free disk space on drive <+">n<-">.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Disk.<+">VolumeName<-">.Free

>
			 2 1 0 0 0 0 0 1 0 0 0 0
(NLM only) Free disk space on the volume named.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Disks.Fixed

>
			 3 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Number of hard drives available (including network drives).

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Disk.<+">n<-">.Size

>
			 4 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Total size (in bytes) of drive n.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Disk.<+">VolumeName<-">.Size

>
			 5 1 0 0 0 0 0 1 0 0 0 0
(NLM only) Total size (in bytes) of the volume named).

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Disk.Swapdisk.Free  *

>
			 6 1 0 0 0 0 0 1 0 0 0 0
(OS/2 only) Number of free bytes on the disk that contains the server's swap file.

>
		[e]
	[tble]
[frm]
	8
	1573060
	960
	2426
	7537
	5757
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	25
	7
	22016
	30463 36350
	[frmlay]
		5473
		6577
		1
		0
		0
		1
		2426
		0
		0
		2
		0
		11
		246
		7029
		1
		1404
		9602
		0
	[tbl]
		 8 2 200 86 4141 86 1 43 43
		[h]
			 0 200 86 2 0 2 0
			 1 400 86 2 0 1 0
			 2 200 86 2 0 2 0
			 3 400 86 2 0 1 0
			 4 200 86 2 0 2 0
			 5 400 86 2 0 1 0
			 6 400 86 2 0 1 0
			 7 400 86 2 0 1 0
		[e]
		[w]
			 0 2390 86 2 0
			 1 3972 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 0 1 0 0 0 0
Description/Comments

>
			 1 0 0 0 0 0 0 1 0 0 0 0
MAIL.Dead *

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Number of undeliverable mail messages in MAIL.BOX

>
			 2 0 0 0 0 0 0 1 0 0 0 0
MAIL.Delivered

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Number of messages received by router.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
MAIL.TotalRouted

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Total number of mail messages routed since the server started.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
MAIL.TransferFailures *

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Number of messages router failed to transfer

>
			 5 0 0 0 0 0 0 1 0 0 0 0
MAIL.Transferred

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Number of messages router attempted to transfer.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
MAIL.Waiting *

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Number of outgoing mail messages currently in MAIL.BOX waiting for transfer.

>
			 7 0 0 0 0 0 0 1 0 0 0 0
MAIL.Waiting.Recipients

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Number of pending mail messages awaiting local delivery.

>
		[e]
	[tble]
[frm]
	8
	1573060
	960
	6115
	7537
	8674
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	24
	8
	22016
	30463 36350
	[frmlay]
		5473
		6577
		1
		0
		0
		1
		6115
		0
		0
		2
		0
		11
		246
		7029
		1
		1404
		9602
		0
	[tbl]
		 6 2 200 86 4141 86 1 43 43
		[h]
			 0 200 86 2 0 2 0
			 1 400 86 2 0 1 0
			 2 400 86 2 0 1 0
			 3 400 86 2 0 1 0
			 4 400 86 2 0 1 0
			 5 200 86 2 0 2 0
		[e]
		[w]
			 0 2390 86 2 0
			 1 3972 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 0 1 0 0 0 0
Description/Comments

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Replica.Docs.Added

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Number of documents added through replication since server started.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Replica.Docs.Deleted

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Number of documents deleted through replication since server started.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Replica.Docs.Updated

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Number of documents updated through replication since server started.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Replica.Failed *

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Number of attempted replications that generated an error.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Replica.Successful

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Number of successful replications.

>
		[e]
	[tble]
[frm]
	9
	1573060
	960
	960
	7602
	5291
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	27
	9
	22016
	30463 36350
	[frmlay]
		5833
		6642
		1
		0
		0
		1
		960
		0
		0
		2
		0
		11
		246
		7029
		1
		1764
		9962
		0
	[tbl]
		 28 2 200 86 4141 86 1 43 43
		[h]
			 0 200 86 2 0 2 0
			 1 400 86 2 0 1 0
			 2 200 86 2 0 2 0
			 3 400 86 2 0 2 0
			 4 800 86 2 0 1 0
			 5 800 86 2 0 1 0
			 6 1600 86 2 0 1 0
			 7 400 86 2 0 1 0
			 8 400 86 2 0 1 0
			 9 200 86 2 0 2 0
			 10 400 86 2 0 1 0
			 11 1000 86 2 0 1 0
			 12 200 86 2 0 2 0
			 13 800 86 2 0 1 0
			 14 200 86 2 0 2 0
			 15 200 86 2 0 2 0
			 16 400 86 2 0 1 0
			 17 200 86 2 0 2 0
			 18 200 86 2 0 2 0
			 19 400 86 2 0 1 0
			 20 1000 86 2 0 1 0
			 21 200 86 2 0 2 0
			 22 200 86 2 0 2 0
			 23 200 86 2 0 2 0
			 24 800 86 2 0 1 0
			 25 800 86 2 0 1 0
			 26 200 86 2 0 2 0
			 27 200 86 2 0 2 0
		[e]
		[w]
			 0 2390 86 2 0
			 1 4037 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
Statistic Name

>
			 0 1 0 0 0 0 0 1 0 0 0 0
Description/Comments

>
			 1 0 0 0 0 0 0 1 0 0 0 0
CommandBlocks.Available

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Number of NetBIOS control blocks currently available.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
CommandBlocks.Total

>
			 2 1 0 0 0 0 0 1 0 0 0 0
The total number of command blocks configured.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Comm.NumOldSessionsClosed *

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Number of sessions closed by server to accommate new users sessions.*

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Errors.Alignment

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Network alignment errors reported on this port. Alignment errors occur when the number of bits received is not a multiple of 16, so the boundary between characters is ambiguous.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Errors.Collisions

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Network collision errors reported on this port. Caused when packets on the network collide and are damaged, sometimes as the result of a loose cable.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Errors.CRC

>
			 6 1 0 0 0 0 0 1 0 0 0 0
The number of Cyclic Redundancy Check (CRC) errors reported on this port. Cyclic redundancy checks are used to verify that messages are transmitted and received accurately. CRC errors mean that the CRC included in the frame is not consistent with the actual
 number of bits in the frame. CRC errors cause retransmissions and network degradation.

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Errors.Port

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Port errors on this port, indicating a port driver buffer overflow or possible parity errors. 

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Errors.RetransmittedPackets

>
			 8 1 0 0 0 0 0 1 0 0 0 0
The number of retransmissions on this port. Useful in checking remote transmissions. 

>
			 9 0 0 0 0 0 0 1 0 0 0 0
Packets.Received

>
			 9 1 0 0 0 0 0 1 0 0 0 0
Number of network packets received on this port.

>
			 10 0 0 0 0 0 0 1 0 0 0 0
Packets.Transmitted

>
			 10 1 0 0 0 0 0 1 0 0 0 0
Number of network packets transmitted on this port.

>
			 11 0 0 0 0 0 0 1 0 0 0 0
Receiver.Resources.Exhausted

>
			 11 1 0 0 0 0 0 1 0 0 0 0
Number of packets dropped. NetBIOS had to drop packets because there was no buffer ready to receive them (insufficient link support buffers); could also be caused by transmissions from a fast machine to a slow machine.

>
			 12 0 0 0 0 0 0 1 0 0 0 0
ReportPeriodMinutes

>
			 12 1 0 0 0 0 0 1 0 0 0 0
The collection time for these statistics.

>
			 13 0 0 0 0 0 0 1 0 0 0 0
Sessions.DataPacketSize

>
			 13 1 0 0 0 0 0 1 0 0 0 0
The meaning of this varies depending on the network. For example, in NetWare, it is the maximum amount of data that can be sent be send in a single packet.

>
			 14 0 0 0 0 0 0 1 0 0 0 0
Sessions.Active

>
			 14 1 0 0 0 0 0 1 0 0 0 0
Active sessions on this port.

>
			 15 0 0 0 0 0 0 1 0 0 0 0
Sessions.InUse

>
			 15 1 0 0 0 0 0 1 0 0 0 0
Sessions that are currently active.

>
			 16 0 0 0 0 0 0 1 0 0 0 0
Sessions.Maximum *

>
			 16 1 0 0 0 0 0 1 0 0 0 0
The number of sessions configured for this server.

>
			 17 0 0 0 0 0 0 1 0 0 0 0
Speed.Port

>
			 17 1 0 0 0 0 0 1 0 0 0 0
Port speed

>
			 18 0 0 0 0 0 0 1 0 0 0 0
Status

>
			 18 1 0 0 0 0 0 1 0 0 0 0
Port status

>
			 19 0 0 0 0 0 0 1 0 0 0 0
Transmissions.Aborted

>
			 19 1 0 0 0 0 0 1 0 0 0 0
Network transmissions that were cancelled. May indicate problems with the network card.

>
			 20 0 0 0 0 0 0 1 0 0 0 0
Transmissions.Retried

>
			 20 1 0 0 0 0 0 1 0 0 0 0
Network transmissions that were retried. Packets are retransmitted when they don't reach their destination the first time. Causes include CRC errors, alignment errors, collisions, and aborted transmissions.

>
			 21 0 0 0 0 0 0 1 0 0 0 0
Unit.Num

>
			 21 1 0 0 0 0 0 1 0 0 0 0
Which NetBIOS is configured at this server.

>
			 22 0 0 0 0 0 0 1 0 0 0 0
User.Bytes.Received

>
			 22 1 0 0 0 0 0 1 0 0 0 0
Number of bytes received on this port.

>
			 23 0 0 0 0 0 0 1 0 0 0 0
User.Bytes.Sent

>
			 23 1 0 0 0 0 0 1 0 0 0 0
Number of bytes sent from this port.

>
			 24 0 0 0 0 0 0 1 0 0 0 0
User.Msgs.Received

>
			 24 1 0 0 0 0 0 1 0 0 0 0
Number of transmit requests issued by the sender for one or more packets. The number should keep increasing, meaning transmission is occurring normally.

>
			 25 0 0 0 0 0 0 1 0 0 0 0
User.Msgs.Sent

>
			 25 1 0 0 0 0 0 1 0 0 0 0
Number of transmit requests issued by the user for one or more packets. The number should keep increasing, meaning transmission is occurring normally.

>
			 26 0 0 0 0 0 0 1 0 0 0 0
Version.Major

>
			 26 1 0 0 0 0 0 1 0 0 0 0
The major version of NetBIOS that is running.

>
			 27 0 0 0 0 0 0 1 0 0 0 0
Version.Minor

>
			 27 1 0 0 0 0 0 1 0 0 0 0
The minor version of NetBIOS that is running.

>
		[e]
	[tble]
[frm]
	1
	1573060
	720
	979
	8731
	10596
	0
	1
	1
	1 0 0 0 0 0 0
	0
	16777215
	32
	10
	4096
	0 0
	[frmlay]
		4651
		8011
		1
		0
		0
		1
		979
		0
		0
		2
		0
		0
		0
		16
		1
		1104
		9302
		0
	[tbl]
		 11 3 200 86 2726 86 1 43 43
		[h]
			 0 200 86 2 0 3 0
			 1 1200 86 2 0 1 0
			 2 800 86 2 0 1 0
			 3 600 86 2 0 1 0
			 4 1800 86 2 0 1 0
			 5 1200 86 2 0 1 0
			 6 1600 86 2 0 1 0
			 7 600 86 2 0 1 0
			 8 800 86 2 0 1 0
			 9 3400 86 2 0 1 0
			 10 600 86 2 0 1 0
		[e]
		[w]
			 0 2258 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 8704 1 0 0 0 0
View

>
			 0 1 0 0 0 0 8704 1 0 0 0 0
Description

>
			 0 2 0 0 0 0 8704 1 0 0 0 0
Use

>
			 1 0 0 0 0 0 0 1 0 0 0 0
Database - Sizes

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Shows the size and activity of all databases on the server, sorted by size. Includes percentage of each database's disk space that is in use and the total disk space of each database.

>
			 1 2 0 0 0 0 0 1 0 0 0 0
Use to check unused views, database size, unused space in a database.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Database - Usage

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Shows sessions (inlcuding kilobytes transferred), documents read and written, and replications, sorted by database.

>
			 2 2 0 0 0 0 0 1 0 0 0 0
Use to check database use, replication problems.

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Mail Routing Events

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Shows messages relating to mail routing and Single Copy Object Store (SCOS).

>
			 3 2 0 0 0 0 0 1 0 0 0 0
Use to check for mail routing problems.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Miscellaneous Events

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Shows information that doesn't appear in other views, including modem I/O messages (if modem or script I/O is selected) and corrupted documents, sorted by date. Messages are sorted by order of occurrence. View is similar to what appears at the Notes server 
console.

>
			 4 2 0 0 0 0 0 1 0 0 0 0
Use to check for server crashes, corrupted databases, replication problems, modem problems, and results of new user registration from a text file.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
Phone Calls - By Date

Phone Calls - By User

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Shows information about calls made and received by a server, sorted by date or by user, depending on the view.

>
			 5 2 0 0 0 0 0 1 0 0 0 0
Use for information on telephone billing or for rescheduling calls made to a server. Also use to check replication problems, dial-up problems, Connection document problems.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Replication Cycle

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Shows all replication sessions between servers, sorted by date. Indicates which server initiated replication, when replication occurred, how long replication took, the port used, and the number of documents added, deleted, or modified. 

>
			 6 2 0 0 0 0 0 1 0 0 0 0
Use to check for replication problems.

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Replication Events

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Same as Replication Cycle but replication sessions are sorted by server.

>
			 7 2 0 0 0 0 0 1 0 0 0 0
Use to check for replication problems.

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Sample Billing

>
			 8 1 0 0 0 0 0 1 0 0 0 0
Same as Usage by User view,but information is uncategorized for easy export to a spreadsheet for billing.

>
			 8 2 0 0 0 0 0 1 0 0 0 0
Use to bill for phone usage, network usage, database usage, and so on.

>
			 9 0 0 0 0 0 0 1 0 0 0 0
Usage by Date

>
			 9 1 0 0 0 0 0 1 0 0 0 0
Shows sessions this server has had with users or other servers, sorted by date. Includes sessions opened, session duration, databases opened, database access duration, number of transactions (workstation-to-server database requests), and network suage (KB t
ransferred). "Transactions" includes operatoins such as opening a document, updating a document, reading a section of a view, or going to a specific section of a view. Incluees totla by date and by user/server, as well as for all usage.

>
			 9 2 0 0 0 0 0 1 0 0 0 0
Use to check database use on a specific date.

>
			 10 0 0 0 0 0 4096 1 0 0 0 0
Usage by User

>
			 10 1 0 0 0 0 4096 1 0 0 0 0
Shows the same information as Usage by Date, but sorted by user name.

>
			 10 2 0 0 0 0 4096 1 0 0 0 0
Use to check a user's sessions with the server.

>
		[e]
	[tble]
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		0
		1
		0
		1
		0
		2
		1
		960
		9446
		1
		1
		3120
	[lft]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		0
		1
		0
		1
		0
		2
		1
		720
		9206
		1
		1
		3120
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		2
		4674
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		2
		4674
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		3
		9900
	[txt]
Administrator's Guide <:P10,0,9->	                                                                                       Lotus Confidential

>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		12960
		10166
		1
		960
		480
		3
		11940
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		3
		9900
	[txt]
@See also prnt@Lotus Confidential 	                                             Setting Up and Using Server Monitoring Tools  
<:P11,0,9->

>
[elay]
[l1]
	0
[pg]
	30
	9 0 95 512 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	10 0 5 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 9 0 0
	27 0 62 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	54 94 91 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	73 0 65 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	85 0 5 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 2 0 0
	102 101 59 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	128 0 46 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	159 0 90 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	190 97 64 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	220 123 151 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	249 107 9 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	275 0 23 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	305 0 77 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	330 0 39 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	354 205 126 0 3 0 0 200 274 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	378 207 74 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	404 0 77 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	413 0 5 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 3 0 0
	413 0 5 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 3 19 0 0
	424 0 5 0 1 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 3 0 0
	424 0 5 0 1 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 3 17 0 0
	442 0 29 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	472 108 11 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	497 0 76 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	505 0 5 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 8 0 0
	527 100 97 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	557 0 29 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	584 103 29 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	588 0 0 1025 1 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
[edoc]
@Chapter title@Chapter 9  Setting Up and Using Server Monitoring Tools

<:s><:#200,8486>This chapter describes the tools provided with Notes that you can use to monitor servers.

@Ahead@<:s><:#240,8486>About the Notes Log

<:#600,8486>The Notes Log (LOG.NSF) collects errors generated by the server and provides detailed information about databases and users on the server. The Notes Log is created automatically when you first start the server. Open the Log on your workspace to view it.

<:s><:#400,8486>You should check the Log each day for problems relating to replication, mail routing, and modem communications.

@See also prnt@<:s><:#400,8486>To report specific types of events in the Notes Log to an individual or database, you can use event reporting.

@See also prnt@<:s><:#200,8486>For more information, see "About event reporting" later in this chapter.

@Ahead@<:s><:#240,8486>About views in the Notes Log

The following table describes the views in the Notes Log (LOG.NSF) and the uses for each. 
<:p<* >>

<:s><:t10>

@Ahead@<:s><:#240,8486>About event reporting

<:#800,8486>The server Event task collects events from the Notes Log (LOG.NSF) and reports them to a person, database, or non-Notes program, according to your configuration choices. You use event reporting to report events of most interest so that you or others are not
 required to look through the Notes Log for the information. You can report the following types of Log events:

@Bullet@<:s><:#200,8486>Communications events

@Bullet@<:s><:#200,8486>Mail events

@Bullet@<:s><:#200,8486>Miscellaneous events

@Bullet@<:s><:#200,8486>Replication events

@Bullet@<:s><:#200,8486>Resource events (events relating to system resources)

@Bullet@<:s><:#400,8486>Server events (events relating to server conditions such as tasks not executed or problems with the server record in the Name & Address Book

@Bullet@<:s><:#200,8486>Statistics (statistic alarms set by you and generated by the server Report task)

<:#400,8486>To configure which events to report and where to report them, you create Event Monitor documents in the Stats & Events Config database (EVTCONFI.NSF). 

<:#600,8486>You can also use Event reporting to monitor ACL changes and replication for specific databases on a server. To do this, you create ACL Monitor documents and Replication Monitor documents in Stats & Events Config.

<:s><:#400,8486>Event reporting consumes few server resources and therefore has negligible impact on server performance.

<:s><:#200,8486>All Notes servers except the Notes Server for Windows support event reporting.

@Ahead@<:s><:#240,8486>About databases used in event reporting

<:s><:#200,8486>Event reporting uses the following databases:

<:#200,8486><+!>Stats & Events <-!><+!>Config (EVTCONFI.NSF)<-!>

<:#200,8486>You use Stats & Events Config to complete the following tasks:

@Bullet@<:s><:#200,8486>Create Event Monitor documents to specify types of events to report.

@Bullet@<:s><:#200,8486>Create ACL Monitor documents to report ACL changes made to specific databases.

@Bullet@<:s><:#400,8486>Create Replication Monitor documents to report when replication of specific databases doesn't occur as frequently as expected.

<:s><:#400,8486>The Event task automatically creates this database in a server's data directory, if the database doesn't exist already.

@Note@<:#200,8486><-!><-">You also use Stats & Events Config to configure statistics reporting. 

@See also prnt@<:s><:#200,8486>For more information on statistics reporting see "About reporting server statistics" later in this chapter.

<:#200,8486><+!>Stats & Events Report (STATREP.NSF)<-!>

<:#600,8486>Stats & Events Report is a mail-in database that can collect events reported by the Event task. Use of this database for Event monitoring is optional since you can report events to people, other databases, or server management tools instead.

<:#400,8486>Events reported to Stats & Events Report, are displayed in the Events view. From the Stats & Events Report database you can create trouble tickets to notify people of reported events.

@Note@<:s><:#200,8486>This database can also contain statistics reported by the Report task.

@See also prnt@<:s><:#200,8486>For more information on statistics reporting see "About reporting server statistics" later in this chapter.

@Ahead@<:s><:#240,8486>About running the Event task

<:#400,8486>The server Event task does not run by default; you must load it manually at the server console or run it automatically at server startup by adding Event to the NOTES.INI variable ServerTasks=.

@Note@<:#400,8486>If you use both the Event and Report tasks, run Event first since it is the Event task that creates the Stats & Events Config database used by both tasks.

@Bhead@<:s><:#220,8486>How the Event task prepares for event reporting

<:s><:#200,8486>The Event task does the following to prepare for event reporting:

@Numbered list@<:#400,8486>If Stats & Events Config (EVTCONFI.NSF) does not yet exist, the Event task creates it from a template on the server. 

@Numbered list@<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">Does Event create server to monitor documents or does Report only do that?? 
<-"><-!><:f>

@Numbered list@<:#600,8486>If Event finds any Notes Release 3 ACL Monitor, Replication Monitor, Event, or Statistic Monitor documents in the Name & Address Book associated with the server on which it is run, it moves them to Stats & Events Config.

@See also prnt@<:s><:#200,8486>See "About reporting statistic alarms" later in this chapter for information on Statistic Monitor documents.

@Numbered list@<:#800,8486>If you configure any events to be logged to Stats & Events Report (STATREP.NSF) on the local server, the Event task creates this database if it doesn't exist. 
<:f180,BArial,0,0,255><+!><+">CORRECT? Or does Event create STATREP automatically, regardless of Monitor documents? Can both Event and Report create STATREP?<-"><-!><:f>

@Bhead title@<:#220,8486>Opening Stats & Events Config

<:#200,8486>To open Stats & Events Config (EVTCONFI.NSF) on the workspace:

@Numbered list@<:s><:#200,8486>Choose File - Tools - Notes Administration.

@Numbered list@<:s><:#200,8486>Click the Databases icon and choose Configure Statistics Reporting.

@Ahead@<:s><:#240,8486>About Event Monitor documents

<:#400,8486>You create an Event Monitor document in Stats & Events Config (EVTCONFI.NSF) for each type of event from the Notes Log that you want to report. In an Event Monitor document you indicate

@Bullet@<:s><:#400,8486>Which type of event to report (communications, mail, miscellaneous, replication, resource, server, statistics).

@Bullet@<:#400,8486>Which events within this selected type to report based on severity level (Fatal, Failure, Warning (high), Warning (low), Normal, All Severities).

@Bullet@<:s><:#200,8486>Which servers should report the selected events.

@Bullet@<:s><:#200,8486>Where to report the selected events (person, database, non-Notes program).

@Bhead title@<:s><:#220,8486>Creating an Event Monitor document

<:#400,8486>For each type of event you want to report, you must create an Event Monitor document in Stats & Event Config (EVTCONFI.NSF).

@Numbered list@<:#200,8486>Open Stats & Events Config on the workspace and choose Create - Monitors - Event Monitor.

@Numbered list@<:s><:#200,8486>Leave Event Notification enabled.

@Numbered list@<:#800,8486>Next to Server name, keep the default asterisk (*) if you want all servers in the domain to report the specified events. Or select specific servers to report this event. 
<:f180,BArial,0,0,255><+!><+">Will test build 1include a keyword list? 
<:f180,BArial,0,0,255> If you want to specify a couple of servers (rather than all in domain), do you have to create separate monitor docs for each server?<-!><-"><:f>

@1st lev para@<:s><:#200,8486><+!><+"><:f180,BArial,0,0,255>Does * mean all servers in the domain?<:f><-"><-!>

@Numbered list@<:s><:#200,8486>Next to Event type, press ENTER and select a type of event to report.

@Numbered list@<:s><:#400,8486>Next to Event severity, press ENTER and select one or more severity levels to control which events of the specified type are reported:

@Indnt note@<:s><:#400,8486>In general, select only higher severity levels, so that you aren't inundated with unimportant event messages.

@Numbered list@<:s><:#200,8486>Next to Notification method, press ENTER and select a method for reporting the events.

@Numbered list@<:s><:#400,8486>Next to Notification destination, type the name of a user, database, or server that corresponds to the selected Notification method. Make sure to spell the name correctly.

@Numbered list@<:s><:#200,8486>Press F9 to automatically fill in a brief description of the event.

@Chead title@<:s><:#200,8486>Details: Creating an Event Monitor document

@Dhead@<:s><:#200,8486><+!>Event type<-!>

<:s><:#200,8486>The following table describes the types of events you can report.

@Chead title@<:s><:t2>

@See also prnt@<:s><:#400,8486>To see a list of event messages, listed by event type and severity level or listed alphabetically, see "Ways to display a list of existing message" later in the chapter. 

@Note@<:s><:#400,8486>If you purchased an add-on product designed to work with Notes server management tools, 
<-!><-">you may see additional types of events listed.

@Dhead@<:s><:#200,8486><+!>Event severity<-!>

<:s><:#400,8486>Each event message has a severity level assigned to it. The severity selection determines which events, based on severity level, are reported. 

<:s><:#200,8486>You can select one or more of the following severity levels:

<:s><:t1>

@See also prnt@<:s><:#400,8486>To see event messages listed by event type and severity level, see "Displaying messages by event type" later in this chapter.

@Dhead@<:s><:#200,8486><+!>Notification method<-!> and Notification Destination

<:s><:#400,8486>These fields determine how and where events are reported. The following table describes the notification methods you can use and the notification destination that corresponds to each method.  

@Note@<:#400,8486>If you purchased an add-on product designed to work with the Notes server management tools, for example NotesView, 
<-!><-">you may see additional notification methods <:f180,BArial,0,0,255><+!><+">and also Notification destinations?<-"><-!><:f>

<:s><:t0>

<:#1000,8486>You can also write an API program to send Event notifications outside of the Notes environment, for example, to a mail gateway or a pager gateway.<:f180,BArial,0,0,255><+!><+"> 
<-!><-"><:f>This requires writing a server add-in task that sends or receives events using the $EVENTL libraries supplied with the API. The add-in task can indicate which events to send or receive using an Event record in the Stats & Events Config database 
<:f180,BArial,0,0,255><+!><+">(CORRECT?)<-"><-!><:f> or by registering them using API calls. For more information, see the 
<+">API User Guide<-"> and <+">API Reference<-">. 

@See also prnt@<:s><:#400,8486>See "Creating a notification method" for instructions on creating a new method of distributing event notifications.

@Chead title@<:s><:#200,8486>Details: Creating an Event Monitor document

<:#400,8486>The following Event monitor document reports all Mail events with the severity level Failure on server SALES/ACME to the Stats & Events Report database on the server.

<:s><:#200,8486>Server name: SALES/ACME

<:s><:#200,8486>Event type: Mail

<:s><:#200,8486>Event severity: Failure

<:s><:#200,8486>Notification method: Log to a database

<:#200,8486>Notification destination: STATREP.NSF

@Ahead@<:s><:#240,8486>About reporting events on multiple servers

<:#400,8486>If you run the Event task on more than one server and choose to report events to Stats & Events Report (STATREP.NSF), you can configure event reporting in one of two ways:

@Bullet@<:#200,8486>Report events to each server's Stats & Events Report database.

@Bullet@<:#200,8486>Report events on each server to one Stats & Events Report database on a collecting server.

@Ahead@<:s><:#240,8486>About decentralized event reporting

<:#600,8486>If you run the Event task on more than one server and choose to report events to Stats & Events Report (STATREP.NSF), you can configure Event Monitor documents so that each server reports events to its own Stats & Events Report database rather than to a cen
tral database.

<:#800,8486>To set up this individual server event reporting, you create a separate Event Monitor document in Stats & Events Config for each server, and select "Log to a database" as the notification method. 
<:f180,BArial,0,0,255><+!><+">Is it necessary to create separate Event Monitor doc like this or can you keep the * (all servers in domain option) selected and still choose "Log to database" so that each logs to its own database?<-"><-!><:f>

<:#400,8486>Although all Stats & Events Report databases in a domain share a replica ID, the default replication settings prevent locally-reported events from replicating. 

@Ahead@<:s><:#240,8486>About centralized event reporting

<:#1000,8486>If you run the Event task on more than one server and choose to report events to Stats & Events Report (STATREP.NSF), you can configure Event Monitor documents so that each server reports to Stats & Events Report on a single collecting server. This centrali
zed approach to event reporting allows you to view in one location events generated by all servers. Although each server stores a copy of Stats & Events Report, only the database on the collecting server contains reported events. 

<:#200,8486><+!><+"><:f180,BArial,0,0,255>If you only run the Event task (not Report) is STATREP automatically recreated if you delete it? 

<:#400,8486><+!><+"><:f180,BArial,0,0,255>Would Stats & Events Report on non-collecting servers still end up containing their own stats because of selective replication settings? 
<-"><-!><:f>

<:#400,8486><:f180,BArial,0,0,255><+!><+">If people don't want copies of STATREP on non-collecting servers, should we suggest they delete the STATREP template so that STATREP isn't rebuilt? 
<-"><-!><:f>

<:s><:#400,8486>You set up centralized event reporting in one of two ways, depending on whether the collecting and non-collecting servers are in the same domain and have network protocols in common.

@Bhead@<:s><:#220,8486>Centralized event reporting within one domain and with common protocols

<:#600,8486>If the collecting and non-collecting servers are in the same domain and have network protocols in common, events on the non-collecting servers are relayed over the network (rather than through Notes mail) to Stats & Events Report on the collecting server. C
reate Event Monitor documents as follows:

@Chead@<:s><:#200,8486><+!>Event Monitor document for the collecting server<-!> 

<:s><:#200,8486>In the Event Monitor document for the collecting server specify the following:

@Bullet@<:s><:#200,8486>Server name: The name of the collecting server

@Bullet@<:s><:#200,8486>Notification method: "Log to a database."

@Bullet@<:#200,8486>Notification destination:<+!> <-!>"STATREP.NSF"

@Chead@<:s><:#200,8486>Event Monitor document for non-collecting servers

<:s><:#200,8486>In the Event Monitor document for non-collecting servers specify the following:

@Bullet@<:s><:#200,8486>Server name: All servers in the domain (*)

@Bullet@<:s><:#200,8486>Notification method: "Relay to other server."

@Bullet@<:s><:#200,8486>Notification destination: Name of the collecting server

@Note@<:#1000,8486>This configuration causes event messages generated by the collecting server to appear in Stats & Events Report twice because the collecting server is specified twice--individually in one Event Monitor document and as a member of domain in the other. You can
 avoid this by creating a separate Event Monitor document for each non-collecting server rather than selecting all servers in the domain. 
<:f180,BArial,0,0,255><+!><+">CORRECT??<-"><-!><:f>

@Bhead@<:s><:#220,8486>Centralized event reporting across domains or across protocols

<:#600,8486>If the collecting and non-collecting servers are in different domains or do not have network protocols in common, you must use Notes mail to report events on the non-collecting servers to Stats & Events Report on the collecting server, rather than relaying 
events over the network.

@Note@<:#400,8486>Collecting events across domains that include many servers is not recommended since it can cause Stats & Events Report to become very large.

<:s><:#200,8486>Create Event Monitor documents as follows: 

@Chead@<:s><:#200,8486><+!>Event Monitor document for the collecting server<-!>

<:s><:#200,8486>In the Event Monitor document for the collecting server specify the following:

@Bullet@<:s><:#200,8486>Server name: The name of the collecting server

@Bullet@<:s><:#200,8486>Notification method: "Log to a database."<-!><-">

@Bullet@<:#200,8486>Notification destination:<+!> <-!>"STATREP.NSF"

@Chead@<:s><:#200,8486><+!>Event Monitor document for non-collecting servers<-!> 

<:s><:#400,8486>For each non-collecting server outside the domain of the collecting server or without a network protocol in common with the collecting server, create an Event Monitor document as follows:

@Bullet@<:s><:#200,8486>Server name: Name of the non-collecting server

@Bullet@<:s><:#200,8486>Notification method: "Mail"

@Bullet@<:#400,8486>Notification destination: Name of the collecting servers<:f180,BArial,0,0,255><+!><+">. Should this be a mail-in database address? If you do specify a server name here, how do the events make it to STATREP? 
<-"><-!><:f>

@Bhead title@<:#220,8486>Listing events reported in Stats & Events Report 

<:#400,8486>If you report events to Stats & Events Report (STATREP.NSF), follow these steps to see a list of events reported by the Event task: 

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the server.

@Numbered list@<:s><:#200,8486>Choose View - Events.<-!><-">

<:s><:#600,8486>The Events view lists by server all events that have occurred since a server started. Each event document in the view shows the time an event occurred, the event severity level, the type of event, and a brief description of the event.

@Bhead title@<:#220,8486>Viewing details about events reported in Stats & Events Report

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the server.

@Numbered list@<:s><:#200,8486>Choose View - Events.<-!><-">

@Numbered list@<:s><:#200,8486>Double-click an Event document.

@Chead title@<:s><:#200,8486>Details: Viewing details about an event

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">To come<-!><-"><:f>

@Ahead@<:s><:#240,8486>About event Trouble Tickets

You can create a Trouble Ticket for any event reported in the Stats & Events Report database to notify one or more people of the event. Although you can also notify people by creating an Event Monitor document that mails a notification to someone, Trouble T
ickets provide administrative features to help you resolve a problem.

@Bhead title@<:s><:#220,8486>Creating a Trouble Ticket to Notify someone of a reported event<-!><-">

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF).

@Numbered list@<:s><:#200,8486>Choose View - Events.

@Numbered list@<:s><:#200,8486>Select the Event document for which you want to create a Trouble Ticket. 

@Numbered list@<:s><:#200,8486>Choose Create - Event Trouble Ticket.

@Numbered list@<:s><:#200,8486>Next to Ticket ID, type<:f180,BArial,0,0,255><+!><+"> ??<-"><-!><+!><+"><:f180,BArial,0,0,255> What's this? Is it already filled<-!><-"><:f><+!><+"><:f180,BArial,0,0,255> in? 
<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Next to Originating Server, type the name of the server that generated the event. 
<+!><+"><:f180,BArial,0,0,255>A<-!><-"><:f><+!><+"><:f180,BArial,0,0,255>lready filled<-!><-"><:f><+!><+"><:f180,BArial,0,0,255> in? 
<-"><-!><:f>

@Numbered list@<:#400,8486>Next to Logging Server, type the name of the server that collected the event (the one that holds the Stats & Events Report database). 
<+!><+"><:f180,BArial,0,0,255>already filled<-!><-"><:f><+!><+"><:f180,BArial,0,0,255> in? 
<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Next to Event Severity, type the severity level assigned to the event. 
<+!><+"><:f180,BArial,0,0,255>already filled<-!><-"><:f><+!><+"><:f180,BArial,0,0,255> in? 
<-"><-!><:f>

@Numbered list@<:s><:#400,8486>Next to "Mail trouble ticket to" type the name of a person to receive the trouble ticket. By default, this is the system administrator for the server that generated the event. 
<:f180,BArial,0,0,255><+!><+">CORRECT?

@Numbered list@<:s><:#200,8486><-">12. Click "Dispatch Trouble Ticket" to send the trouble ticket to the designated person.

<:#400,8486>Notes mails the trouble ticket to the designated recipient and puts a copy in the Trouble Tickets - Events view of the Stats & Events Report database.

@Chead title@<:s><:#200,8486>Details: Creating a trouble ticket to notify someone of a posted event<-!><-">

@Chead title@<:s><:#200,8486>Example: Creating a trouble ticket to notify someone of a posted event<-!><-">

@Bhead title@<:#220,8486>Viewing an event trouble ticket in the Stats & Events Report database

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF).

@Numbered list@<:s><:#400,8486>Choose View - Trouble Tickets - Event. The view displays the existing trouble tickets.  
<:f180,BArial,0,0,255><+!><+">How far back do they go? Do you have to occasionally delete them? 
<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Double-click a trouble ticket to open it.<-!><-">

@Bhead title@<:s><:#220,8486>Disabling an Event Monitor document

<:s><:#400,8486>If you are reporting certain events temporarily, follow these steps to disable an Event Monitor document when you are finished.

@Numbered list@Open Stats & Events Config (EVTCONFI.NSF).

@Numbered list@<:s><:#200,8486>Choose View - Event Monitors.

@Numbered list@<:#200,8486>Select an Event Monitor document and press CTRL+E (or COMMAND-E on the Macintosh).<-!><-">

@Numbered list@<:s><:#200,8486>Next to Event Notification, press ENTER, select "Event Notification Disabled", and click OK.

@Numbered list@<:s><:#200,8486>Click Save Event Monitor.

@Bhead title@<:s><:#220,8486>Ways to display a list of messages the Event task can report

<:#400,8486>Stats & Events Config (EVTCONFI.NSF) stores all the messages that the Event task can report. There are two ways to view a list of these messages:

@Bullet@<:s><:#200,8486>View messages by their event type

@Bullet@<:s><:#200,8486>View an alphabetical list of messages<-!><-">

@Bhead title@<:s><:#220,8486>Viewing messages by event type

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#200,8486>Choose Views - Names & Messages - Messages.<:f180,BArial,0,0,255><+!><+"> (Call this view "Messages by Event Type"?)<-"><-!><:f>

<:s><:#200,8486>The view sorts all messages by event type and within event type, by severity level.

@Bhead title@<:s><:#220,8486>Viewing an alphabetical list of messages

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#200,8486>Choose Views - Names & Messages - Messages by Text.<-!><-">

@Ahead@<:s><:#240,8486>About customizing event message documents

<:#600,8486>The Messages and Messages by Text views of Stats & Events Config (EVTCONFI.NSF) contain message documents for each message the Event task can report. A message document controls how the Event task reports a message. A message document determines:

@Bullet@<:s><:#400,8486>The information that appears when the message is reported including the message text, probable causes for the message and possible solutions

@Bullet@<:s><:#200,8486>Event type and severity level associated with a message

@Bullet@<:s><:#200,8486>Any limit to the number of times the Event task can report a message

<:#400,8486>You can modify message documents to suit your needs. You must have Designer or Manager access to the Stats & Events Config database to customize a message in it.

<:s><:#400,8486>You can also create new message documents to incorporate messages of a server add-in task. 
<:f180,BArial,0,0,255><+!><+">CORRECT??<-"><-!><:f> <:f180,BArial,0,0,255><+!><+">What access required for this?<-"><-!><:f> 

@Ahead@<:s><:#240,8486>Ways to customize an existing message

<:s><:#200,8486>You can customize a message in the following ways:

@Bullet@<:s><:#200,8486>Change the information that is reported

@Bullet@<:s><:#200,8486>Limit how frequently a message can be reported

@Bullet@<:s><:#200,8486>Change the severity level assigned to a message

@Bhead title@<:s><:#220,8486>Changing the information reported by a message

<:s><:#400,8486>You can change the wording of a message or expand on or modify the problem-solving information that accompanies a message.

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#200,8486>Choose Views - Names & Messages and choose Messages or Messages by Text.

@Numbered list@<:#200,8486>Select a message document and press CTRL+E (or COMMAND-E) on the Macintosh.

@Numbered list@<:s><:#200,8486>Next to Message Text, modify the message that the Event task reports. 

@Numbered list@<:s><:#400,8486><-!><-">Next to "Probable Cause," edit the description to suit your needs. The Event task reports this text along with the message.

@Numbered list@<:s><:#400,8486>Next to "Possible Solution," edit the description of suggested solutions to suit your needs. The Event task reports this text along with the message.

@Numbered list@<:s><:#400,8486>Next to "User Addendum," type any additional information for the Event task to report along with this message.

@Numbered list@<:s><:#200,8486>Click Save Message.

@Bhead title@<:s><:#220,8486>Limiting how frequently a message can be reported

<:s><:#600,8486>Sometimes the Event task may <-!><-">report a particular message too often. 
<:f180,BArial,0,0,255><+!><+">For Example? Which messages are most likely to be hyper-reported?<-"><-!><:f><-">  
<:f180,BArial,0,0,255><+!><+">List of messages that are most likely to be hyper-reported?  
<-"><-!><:f>Follow these steps to report a message less frequently.

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#200,8486>Choose Views - Names & Messages and choose Messages or Messages by Text.

@Numbered list@<:#200,8486>Select a message document and press CTRL+E (or COMMAND-E) on the Macintosh.

@Numbered list@<:s><:#200,8486>Next to "Only report this event at most every <[> ] minutes," enter a value in minutes.

@Numbered list@<:s><:#200,8486>Click Save Message.

<:s><:#400,8486>For example, if you specify a limit of 15 minutes, Notes reports the message a maximum of once every 15 minutes, even if the message occurs ten times within a 15-minute period.

@Bhead title@<:s><:#220,8486>Adding a new message

<:s><:#400,8486>You can create a new message, for example, to report additional messages associated with a Notes add-in task.<-!><-">

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#200,8486>Choose Create - Message.

@Numbered list@<:s><:#200,8486>Below Message Text, type the text for the new message.

@Numbered list@<:#400,8486>Next to Add ln Name, type the name of the non-Notes program that reports this error message.<:f180,BArial,0,0,255><+!><+"> What are some examples of the programs you'd specify here?<-"><-!><:f> 
<:f180,BArial,0,0,255><+!><+">What <-!><-"><:f><+!><+"><:f180,BArial,0,0,255> syntax is required? 
<-"><-!><:f>

@Numbered list@<:s><:#600,8486>Next to Message Value, type the internal number associated with this error message. 
<:f180,BArial,0,0,255><+!><+">Do you have to specify a number? What is an internal number exactly? Any restrictions as to the value you can enter here? 
<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Below Probable Cause, type a likely cause for the error message.<-!><-">

@Numbered list@<:s><:#200,8486>Below Possible Solution, describe possible solutions to the problem. 
<-!><-">

@Numbered list@<:s><:#200,8486>Below User Addendum, describe additional information that may be helpful in solving the problem.<-!><-">

@Numbered list@<:s><:#200,8486>Click Save Message.

@Chead title@<:s><:#200,8486>Details: Creating a new message

@Chead title@<:s><:#200,8486>Examples: Creating a new message

@Bhead title@<:s><:#220,8486>Displaying the existing event notification methods

<:s><:#200,8486>To see the existing methods for distributing event notifications:

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#400,8486>Choose View - Names & Messages - Notification Methods. The view displays a description of each existing notification method.

@Numbered list@<:s><:#200,8486>Double-click a notification method to display information about it.

@See also prnt@<:s><:#200,8486>See "Details: Setting up event reporting" for details about the default notification methods.<-!><-">

@Bhead title@<:s><:#220,8486>Creating a notification method<-!><-">

@Numbered list@<:#200,8486>Open the Stats & Events Config database.

@Numbered list@<:s><:#200,8486>Choose Create - Notification Method.

@Numbered list@<:s><:#200,8486>Type a description of the notification method.

@Numbered list@<:s><:#200,8486>Type the internal method identifier for the notification method. 

@Ahead@<:s><:#240,8486><:f180,BArial,0,0,255><+!><+">Need more information here.<-"><-!><:f>

@Chead title@<:s><:#200,8486>Examples: Creating a notification method

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">To come<-!><-"><:f><-">

@Ahead@<:s><:#240,8486>About monitoring databases

<:s><:#400,8486>In addition to reporting server events, the Event task can report ACL changes to specific databases or report infrequent replication of specific databases.  

@Bhead@<:s><:#220,8486>ACL Monitoring

<:s><:#400,8486>To report ACL changes, you create an ACL Monitor document. ACL monitoring reports manual changes to a database ACL as well as ACL changes made through replication or an API program.

<:#600,8486>After you set up ACL monitoring of a database, Notes can also report any ACL changes to the Events view of the Stats & Events Report database if you create an Event Monitor document type Security with severity level selected in the ACL monitor document.

@Note@<:s><:#400,8486>An ACL change on a server database made using the server workstation program doesn't generate a notification.<:f180,BArial,0,0,255><+!><+"> TRUE??<-"><-!><:f>

@Bhead@<:s><:#220,8486>Replication Monitoring

<:s><:#400,8486>To report when replication hasn't occurred within a specific time period, you create a Replication Monitor document.

<:#600,8486>After you set up Replication monitoring of a database, Notes can also report infrequent replication in the Events view of the Stats & Events Report database if you create an Event Monitor document type Replication with severity level selected in the Replica
tion monitor document.

@Bhead title@<:s><:#220,8486>Setting up ACL monitoring

<:s><:#200,8486>To report to a designated person any changes to the ACL of a specific database:

@Numbered list@<:#200,8486>Open Stats & Events Config (EVTCONFI.NSF).

@Numbered list@<:s><:#200,8486>Choose Create - Monitors - ACL Monitor.

@Numbered list@<:s><:#400,8486>Next to Enabled/Disabled, leave Monitor Enabled selected, unless you want to temporarily disable ACL monitoring for this database.

@Numbered list@<:s><:#800,8486>Next to Server name, keep the default asterisk (*) to monitor ACL changes on all replicas of a database in a domain. Or type the complete name of a specific server that stores a database you want to monitor, using a hierarchical name if applicable. 
<+">You can only specify one individual server name per ACL Monitor document. 
<:f180,BArial,0,0,255><-"><+!><+">Last statement true? <-"><-!><:f>

@Numbered list@<:s><:#600,8486>Next to Database name, type the name of a database you want to monitor. You can specify only one database per document. 
<:f180,BArial,0,0,255><+!><+">Will you be able to specify more than one database as in replication monitoring??<-"><-!><:f>

@Numbered list@<:#600,8486>Next to Event severity, press ENTER to display severity levels and select one or more specific levels or All Severities. Your selection determines which ACL events, based on severity, are reported to the Stats & Events Report database. 

@Numbered list@<:s><:#400,8486>Next to "Person to notify via mail," optionally type the names of any people who should be notified of the ACL change. Typically you specify the managers of the database.

@Numbered list@<:s><:#200,8486>Press F9 to automatically fill in a brief summary of the information you've entered.

@Numbered list@<:s><:#200,8486>Click Save ACL Monitor.

<:s><:#200,8486>Repeat these steps for each additional database you want to monitor.

@Chead title@<:s><:#200,8486>Details: Setting up ACL monitoring

@Dhead@<:s><:#200,8486>Database name

<:#400,8486>If the database is in a subdirectory of the Notes directory, you must include the subdirectory name, for example, FORECAST\SALES.NSF.

@Dhead@<:s><:#200,8486>Person to notify via mail

<:s><:#400,8486>Include all the people who need to be notified in a single ACL Monitor document. If you create more than one document, Notes only notifies people listed in the last ACL Monitor document created.

<:s><:#400,8486>Names of people listed here must use Notes mail to receive a notification unless the notification is addressed to cc:Mail through the Lotus Mail Exchange Facility. 
<:f180,BArial,0,0,255><+!><+">STILL TRUE FOR R4? <-"><-!><:f>

@Bhead title@<:s><:#220,8486>Disabling ACL monitoring for a database

<:s><:#400,8486><-!><-">If you created an ACL Monitor document to temporarily monitor ACL changes, follow these steps to disable ACL monitoring when you are finished.

@Numbered list@<:#200,8486>Open Stats & Events Config (EVTCONFI.NSF).

@Numbered list@<:s><:#200,8486>Choose View - Database Monitors.

@Numbered list@<:#400,8486>Select the ACL Monitor document you want to disable and press CTRL+E (or COMMAND-E on the Macintosh).<-!><-">

@Numbered list@<:s><:#200,8486>Next to Enabled/Disabled, press ENTER, select Monitor Disabled, and click OK.

@Numbered list@<:s><:#200,8486>Click Save ACL Monitor.

@Bhead title@<:s><:#220,8486>Setting up replication monitoring

To monitor replication for a database to ensure that it's replicating regularly and to send a report to a designated person if replication isn't occurring as planned:

@Numbered list@<:#200,8486>Open Stats & Events Config (EVTCONFI.NSF).

@Numbered list@<:s><:#200,8486>Choose Create - Monitors - Replication

@Numbered list@<:s><:#200,8486>Next to Enabled/Disabled, leave Monitor Enabled selected.

@Numbered list@<:#200,8486>Next to "If the database(s)," type the name of the database or databases you want to monitor.

@Numbered list@<:#400,8486>Next to "On the server(s)," keep the default asterisk (*) or specify a specific server.  
<+">You can only specify one individual server name per ACL Monitor document. 
<:f180,BArial,0,0,255><-"><+!><+">Last statement true? <-"><-!><:f>

@Numbered list@<:#200,8486>Next to "Has not replicated with server(s)," keep the default asterisk (*) or specify a specific server.

@Numbered list@Next to "Within the last," type a time in hours after which the Event task should  generate a report if replication hasn't occurred.

@Numbered list@<:#600,8486>Next to "Generate an event of severity," press ENTER to display severity levels and select one or more specific levels or All Severities. If you select this option, you can create an event monitor document type replication to report this as an event.

@Numbered list@<:s><:#400,8486>Next to "And optionally mail a notification to," type the names of any people who should be notified,  typically database managers or the Notes administrator.

@Numbered list@<:s><:#200,8486>Press F9 to automatically fill in a brief summary of the information you've entered.

@Numbered list@<:s><:#200,8486>Click Save Replication Monitor.

<:s><:#200,8486>Repeat these steps for each additional database you want to monitor.

@Chead title@<:s><:#200,8486>Details: Setting up replication monitoring

@Dhead@<:s><:#200,8486>Database name

<:#400,8486>If the database is in a subdirectory of the Notes directory, you must include the subdirectory name, for example, FORECAST\SALES.NSF.

@Dhead@<:s><:#200,8486>Event severity<-!><-">

<:s><:#400,8486>If you enter a severity level, you can then create an Event Monitor document type Replication to report infrequent replication as an event. 

<:s><:#200,8486>If you don't enter an Event severity, you must select people to notify via mail.

@Dhead@<:s><:#200,8486>Person to notify via mail

<:s><:#600,8486>Include all the people who need to be notified in a single Replication Monitor document. If you create more than one document, Notes only notifies people listed in the last Replication Monitor document created.

<:s><:#400,8486>Names of people listed here must use Notes mail to receive a notification unless the notification is addressed to cc:Mail through the Lotus Mail Exchange Facility. 
<:f180,BArial,0,0,255><+!><+">STILL TRUE FOR R4? <-"><-!><:f>

<:s><:#200,8486>If you don't select people to notify via mail, you must select an Event severity. 

@Bhead title@<:s><:#220,8486>Disabling replication monitoring for a database<-!><-">

<:s><:#400,8486><-!><-">If you created a Replication Monitor document to temporarily monitor replication, follow these steps to disable replication monitoring when you are finished.

@Numbered list@<:#200,8486>Open Stats & Events Config (EVTCONFI.NSF).

@Numbered list@<:s><:#200,8486>Choose View - Database Monitors.

@Numbered list@<:#400,8486>Select the Replication Monitor document you want to disable and press CTRL+E (or COMMAND-E on the Macintosh).<-!><-">

@Numbered list@<:s><:#200,8486>Next to Enabled/Disabled, press ENTER, select Monitor Disabled, and click OK.

@Numbered list@<:s><:#200,8486>Click Save Replication Monitor.

@Ahead@<:s><:#240,8486>About reporting server statistics

<+@><:#400,8486>The server task Report collects server statistics and reports them to a database (STATREP.NSF) where you can view and analyze them. The Report task collects the following types of statistics:

@Bullet@<:s><:#200,8486>System statistics relating to disk space and memory and other server statistics

@Bullet@<:s><:#200,8486>Mail statistics

@Bullet@<:s><:#200,8486>Replication statistics

@Bullet@<:s><:#200,8486>Communication statistics

@Bullet@<:s><:#200,8486>Object store statistics

<:#600,8486>Although you can report statistics to any database designed for this purpose, typically you report them to Stats & Events Report (STATREP.NSF). The Report task automatically creates this database, if it does not already exist and if you haven't designated a
nother one for statistics collecting. 

<:s><:#400,8486>In addition to automatically reporting all statistics on a server, you can use the Report task to generate the following optional information: 

@Bullet@<:#800,8486>Alarms in the Stats & Events Report database when statistics exceed thresholds that you specify. For example, if you're concerned about disk space, you can generate an alarm when disk space on a server falls below 10MB. You set up an alarm by creating a Sta
tistics Monitor document in the Events and Config database; Notes automatically creates (EVTCONFI.NSF) for you.

@Bullet@<:#400,8486>Analysis reports in the Stats & Events Report database that report the averages and lows for reported statistics. 

@Bullet@<:s><:#600,8486>File statistic reports that shows the size, replica ID and percent of used space for each database and template on a server. These reports also warn you if the used space for a file drops below 70%<-!>, indicating the need for compacting.<-!>

<:s><:#400,8486>Statistics reporting consumes few server resources and therefore has negligible impact on server performance.

<:s><:#200,8486>All Notes servers except the Notes Server for Windows support statistics reporting. 

@Ahead@<:s><:#240,8486><-!>About databases used in statistics reporting

<:s><:#200,8486>Statistics reporting involves the following databases:

<:#200,8486><+!>Stats & Events Config<-!><+!> (EVTCONFI.NSF)<-!>

<:#400,8486>You use Stats & Events Config (EVTCONFI.NSF) to complete the following statistics reporting configuration tasks:

@Bullet@<:s><:#600,8486>Complete Server documents for each server that runs the Report task. A server document tells the Report task the name and location of the database that collects statistics, how frequently to generate statistic alarms, and if and when to generate statistics 
analysis reports.

@Bullet@<:s><:#200,8486>Set up statistic alarms.

<:s><:#400,8486><-!><-">Both the Event and Report tasks use this database, but the Event task creates it. Therefore, you must run the Event task at least once before running the Report task. 

<:#800,8486>The Event task creates a replica copy of Stats & Events Config on each server on which Event runs. This database replicates across servers in a domain, allowing you to configure Event or Statistics reporting from any location. 
<+!><+"><:f180,BArial,0,0,255>Stats & Events Config created on different domain servers has the same replica ID?<-"><-!><:f>

@See also prnt@<:s><:#200,8486>For more information on event reporting see "About reporting server events" earlier in this chapter.

<:#200,8486><+!>Stats & Events Report (STATREP.NSF)<-!>

<:#400,8486>Stats & Events Report is a mail-in database that collects server statistics reported by the Report task. You use this database to:

@Bullet@<:s><:#200,8486>View reported statistics

@Bullet@<:s><:#200,8486>Analyze reported statistics

@Bullet@<:s><:#200,8486>View reported statistic alarms

@Bullet@<:s><:#200,8486>Create trouble tickets to notify people of reported statistic alarms

<:s><:#400,8486>Using this database is recommended but not required; you can collect statistics in another database designed for this purpose.

<:s><:#600,8486>The Report task<:f180,BArial,0,0,255><+!><+"> (Or is it the Event task?)<-"><-!><:f> automatically creates this database in a server's data directory, if the database doesn't exist already or if you haven't designated another database for statistics collect
ion. To view the database, open it on a workspace.

@Note@<:#200,8486>Stats & Events Report can also contain events collected by the Event task.

@See also prnt@<:s><:#200,8486>For more information on event reporting see "About reporting server events" earlier in this chapter.

@Ahead@<:s><:#240,8486>About running the Report task

<:#400,8486>You must load the Report task manually as needed at the server console or run it automatically at server startup by adding Report to the ServerTasks NOTES.INI variable; Report does not run by default.

@Note@<:#400,8486>The Event task creates the Stats & Events Config database (EVTCONFI.NSF) which is shared by the Event and Report tasks. Therefore run the Event task before running Report for the first time.

@Bhead@<:s><:#220,8486>How the Report task prepares for statistics reporting

<:s><:#200,8486>The Report task automatically does the following to prepare for statistics reporting:

@Numbered list@<:#600,8486>If EVTCONFI.NSF (created by the Event task) does not contain a server monitor document for the local server, the Report task creates it and specifies Stats & Events Report (STATREP.NSF) as the mail-in database.

@Numbered list@<:s><:#600,8486>If the local public Name & Address Book does not include a Mail-In database document for the mail-in database specified in the server monitor document for the local server, the Report task creates it. 

@Numbered list@If the mail-in database specified in the server monitor document for the local server is a local database and does not exist, the Report task creates the Stats & Events Report database (STATREP.NSF). I<:f180,BArial,0,0,255><+!><+">s STATREP created on each 
server that runs Report, regardless of whether statistics collecting is occurring<-!><-"><:f><+!><+"><:f180,BArial,0,0,255> locally or on another server? If so, when is it created and by what process Event or Report)?<-"><-!><:f>

@Bhead@<:s><:#220,8486>How the Report task reports statistics 

<:#400,8486>Once you've configured statistics reporting on a server using Stats & Events Config (EVTCONFI.NSF) the Report task does the following to report statistics:

@Numbered list@<:#200,8486>Regularly reports statistics to Stats & Events Report (STATREP.NSF).

@Numbered list@<:#400,8486>(Optional) Reports any alarms you've set up to Stats & Events Report at an interval specified in the Server to Monitor document.

@Numbered list@<:#400,8486>(Optional) Generates statistic analysis reports in Stats & Events Report at an interval specified in the Server to Monitor document for the server.

@Ahead@<:#240,8486>About Server to Monitor documents in Stats & Events Config

<:#1000,8486>You configure a server document in Stats & Events Config (EVTCONFI.NSF) to control how the Report task reports statistics for a particular server. The Report task creates a server monitor document for the local server in Stats & Events Config if one doesn't
 already exist.<:f180,BArial,0,0,255><+!><+"> Correct?? Or does Event do this? 
<-"><-!><:f>The server document automatically includes the server name, domain, and administrators of the local server-- information derived from the server record in the public Name & Address Book. 

<:s><:#400,8486>You add the following information to the server document to control how the Report task collects statistics on the server:

@Bullet@<:#800,8486>The location of the Stats & Events Report database. The Report task on each server must report its statistics to a mail-in database, usually Stats & Events Report (STATREP.NSF). This database can be on the local server or on another server that also runs th
e Report task and collects statistics for multiple servers.

@Bullet@<:s><:#200,8486>(Optional) A collection interval that determines how frequently alarms are reported.

@Bullet@<:s><:#400,8486>(Optional) A statistics analysis interval that determines how frequently analysis reports are generated.

@Bhead title@<:s><:#220,8486>Configuring Server to Monitor documents<-!><-"><-!>

<:s><:#200,8486>To configure a Server to Monitor document:

@Numbered list@<:#200,8486>Select a server document and press CTRL-E (or COMMAND-E on a Macintosh).

@Numbered list@<:s><:#400,8486>Next to "Mail-in database address to receive reports," type the name of the database which will collect information from the Report task. 

@Numbered list@<:s><:#200,8486>Next to Collection interval, specify how frequently the Report task should report alarms.

@Numbered list@<:s><:#200,8486>Next to Analysis interval, specify how frequently you want to generate statistical analysis reports.

@Numbered list@<:s><:#200,8486>Save the document.

@Chead title@<:s><:#200,8486>Details: Configuring Server to Monitor documents

@Dhead@<:s><:#200,8486>Mail-in database address to receive reports

<:s><:#600,8486>Type the name as it appears in the Mail-in name field in the Mail-In Database document created for the database. 
<-!><-">Notes mails statistic reports generated by the Report task to the database specified in this field.

<:s><:#200,8486>The format for this field is:

<:s><:#200,8486><+">common server name<-"> Statistics/<+">organization<-">; for example, MARKETING Statistics/ACME.

<:s><:#400,8486>The database can be on the local server or on another server. Specify a database on another server if you want to collect statistics for multiple servers in one location.

@See also prnt@<:s><:#200,8486>See "About reporting statistics on multiple servers" for more information.

@Dhead@<:s><:#200,8486>Collection interval

@Dhead@<:s><:#400,8486><:f180,BArial,0,0,255><+">This refers only to when alarms are reported<-"><:f><+"><:f180,BArial,0,0,255>,<-"><:f><+"><:f180,BArial,0,0,255> n<-"><:f><+"><:f180,BArial,0,0,255>ot statistics in general? If true, what determines when<-"><:f><+"><:f180,BArial,0,0,255>
 new statistic reports are created?<-"><:f>

<:#800,8486>Notes creates a statistics report in the Stats & Events Report database for each collection. 
<-!><-">You can specify a collection interval as frequently as every 15 minutes. For everyday use, set this interval to every few hours (180) minutes or even just once a day (1440 minutes). To track specific conditions, collect statistics more frequently.

<:s><:#400,8486>If you specify an interval that's not divisible by 15 minutes, Notes rounds down to the nearest 15-minute interval. For example, if you specify 20 minutes, collecting actually occurs every 15 minutes. 

<:s><:#200,8486><-"><+!>Analysis interva<-!><+!>l<-!>

<:s><:#600,8486>If you select Daily, Weekly, Monthly as an analysis interval, the Report task generates an Analysis Report at the interval specified that summarizes statistical averages and lows for that interval. Use this feature to analyze statistical changes across mult
iple statistic reports. 

<:s><:#600,8486>Selecting this option also generates File Statistic reports on databases and templates at the specified interval; each File Statistic Report shows the size, replica ID and percentage of space in use for each database and template on the server.

<:s><:#200,8486>The default analysis interval is Weekly.

<:s><:#200,8486>If you select Never, Report does not generate Analysis Reports or File Statistic Reports.

@Ahead@<:s><:#240,8486>About reporting statistics on multiple servers

<:s><:#400,8486>If you run the Report task on more than one server, you can configure statistics reporting in one of two ways:

@Bullet@<:#200,8486>Report statistics to each server's own Stats & Events Report database (STATREP.NSF)

@Bullet@<:#200,8486>Report statistics on each server to a central Stats & Events Report database on a collecting server.

@Ahead@<:s><:#240,8486>About decentralized statistics reporting

You can configure statistics reporting so that each server reports statistics to its local replica of Stats & Events Report. Although all Stats & Events Report databases in a domain<:f180,BArial,0,0,255><+!><+"> (cross domain are replicas too?)<-"><-!><:f> 
share a replica ID, the default replication settings prevent most locally-reported statistics from replicating; the exception is file statistics which do replicate because they are most useful in the context of multiple servers.

<:#400,8486>To report statistics to each server's local replica of Stats & Events Report, specify the Mail-in database address of the local version of this database in each server's Server to Monitor document.

@Ahead@<:s><:#240,8486>About centralized statistics reporting

<:#800,8486>You can configure statistics reporting so that each server running the Report task reports statistics to Stats & Events Report (STATREP.NSF) on one collecting server. If you do this, all servers store a Stats & Events Report database but only the copy on th
e collecting server contains reported statistics. <:f180,BArial,0,0,255><+!><+">Correct?? Or would all copies eventually contain multiple-server statistics through replication? 
<-"><-!><:f>

<:#400,8486>To set up centralized statistics reporting, you specify the Mail-in database address for Stats & Events Report on the collecting server in each Server to Monitor document.

@Bhead title@<:s><:#220,8486>Reading a Statistics Report

<:#1200,8486>After you've set up a server document in Stats & Events Config (EVTCONFI.NSF) to configure statistics reporting on a server, you can view Statistics Reports generated by the Report task in Stats & Events Report (STATREP.NSF). The Report task generates a Sta
tistic Report each time it collects and reports statistics on a server. (The server document in Stats & Events Config determines the statistics collection interval).<:f180,BArial,0,0,255><+!><+">Or does the collection interval really refer only to alarms? I
f collection interval doesn't determine when statistics reports are generated, what does? 
<-"><-!><:f>

<:s><:#200,8486>To view a Statistics Report:

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:s><:#200,8486>Choose View - Statistics Report and one of the following sub-views:

@Indnt bullet@<:s><:#200,8486>System

@Indnt bullet@<:s><:#200,8486>Mail & Database

@Indnt bullet@<:s><:#200,8486>Communications

@Indnt bullet@<:#200,8486>NetBios

@Numbered list@<:s><:#200,8486>Open a specific Statistics Report.

@Chead title@<:s><:#200,8486><-!><-">Details: Reading a Statistic Report

<:s><:#200,8486>The following tables describe the information that appears in each Statistics Report.

@Note@<:s><:#200,8486>An asterisk (*) next to a statistic indicates an alarm is recommended for it.

@See also prnt@<:s><:#200,8486>See "About setting up alarms" later in this chapter for information on setting an alarm for a statistic.<-!><-">

@Dhead@<:s><:#200,8486>System statistics

<:s><:#400,8486>There are three categories of system statistic: disk statistics, memory statistics, and server statistics. The following tables list and describe each type of system statistic.

<:s><:#200,8486><+!>(Disk statistics)<-!>

@Bhead title@<:s><:t6>

<:s><:#200,8486><+!>(Memory s<-!><+!>tatistics<-!>)

@Dhead@<:s><:t5>

<:s><:#200,8486><+!>(Server s<-!><+!>tatistics)<-!>

<:s><:t4>

@Dhead@<:s><:#200,8486>Mail & database statistics

<:s><:#200,8486>The following tables list and describe Mail & Database statistics, respectively.

<:s><:#200,8486><+!>(Mail statistics)<-!>

@Ahead@<:s><:t7>

<:s><:#200,8486><+!>(Database Statistics <-">)<-!>

@Ahead@<:s><:t8>

@Chead title@<:s><:#200,8486>Communications statistics 

<:#600,8486>The following table describes X.PC or X.25 statistics that track modem communications. You can also see this information at the server console by typing SHOW PORTS or from the server workstation by choosing File - Tools - Notes Preferences, clicking the Por
ts icon, and clicking Show Status.

@See also prnt@<:s><:#200,8486>See the <+">Network Configuration Guide<-"> for information about configuring networks. 

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">S<-!><-"><:f><+!><+"><:f180,BArial,0,0,255>ome of these statistics will move to the next table<-!><-"><:f>.

@Dhead@<:t9>NetBios statistics<-!><-">

<:s><:#600,8486>The following table describes network port communication statistics. You can also see this information at the server console by typing SHOW PORTS or from the server workstation by choosing File - Tools - Notes Preferences, clicking the Ports icon, and click
ing Show Status.

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">Add table<-"><-!><:f>

@Bhead title@<:s><:#220,8486>Viewing Object Stores Statistics

<:s><:#200,8486>If single copy object store is enabled on a server, you can view object store statistics.

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:#200,8486>Choose View - Object Store Stats.

@Bhead title@<:s><:#220,8486>Ways to analyze reported statistics

<:s><:#200,8486>You can analyze reported statistics in the following ways:

@Bullet@<:s><:#200,8486>Read an Analysis Report<-!><-">

@Bullet@<:s><:#200,8486>View a graph of disk and memory statistics

@Bullet@<:s><:#200,8486>View a graph of system resource statistics

@Bullet@<:s><:#200,8486>View a graph of server load statistics

@Bullet@<:s><:#200,8486>View statistics for export to a spreadsheet

@Bhead title@<:s><:#220,8486>Reading a statistics Analysis Report

<:#800,8486>If you specify an analysis interval in a server document in Stats & Events Config (EVTCONFI.NSF), you can view Analysis Reports in Stats & Events Report (STATREP.NSF). An analysis report summarizes information in individual Statistic Reports by showing the 
averages and lows of reported statistics for a specified analysis interval.

<:s><:#200,8486>To view an Analysis Report:

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:s><:#200,8486>Choose View - Analysis Report

@Chead title@<:s><:#200,8486>Details: Reading a statistics Analysis Report

<:#400,8486>The Additive Statistics field analyzes additive statistics, showing their average and low values for the analysis interval. Additive statistics are statistics that are tallied, for example Server.Trans.Total. 

<:#600,8486>The Unique Statistics field analyzes non-cumulative statistics, showing their average and low values for the analysis interval. Unique statistics are statistics are non-tallied statistics, such as Disk.C.Free.Most statistics are Unique Statistics.

@Bhead title@<:s><:#220,8486>Viewing a graph of reported disk and memory statistics

<:s><:#200,8486>To view a graph summarizing reported disk and memory statistics: 

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:#200,8486>Choose View - Graphs - System Stats.

@Bhead title@<:s><:#220,8486>Viewing a graph of reported server load statistics

<:s><:#400,8486>To view a graph summarizing reported statistics relating to server load such as the numbers of users and transactions:

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:s><:#200,8486>Choose View - Graphs - System Loads.

<:s><:#200,8486>Use this view to quickly check server loads.

@Bhead title@<:s><:#220,8486>Viewing a graph of reported system resource statistics

<:s><:#400,8486>To view a graph summarizing reported statistics relating to server resources such as swap file size, disk space, and free memory:

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:s><:#200,8486>Choose View - Graphs - System Resources.

@Bhead title@<:s><:#220,8486>Viewing reported statistics in spreadsheet format

<:s><:#200,8486>To view statistics in a format that you can easily export to a spreadsheet:

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace.

@Numbered list@<:s><:#200,8486>Choose View - Spreadsheet Export.

<:s><:#400,8486>This view shows a variety of reported statistics. If you export this view to a spreadsheet, each entry is translated into a spreadsheet cell.

@Ahead@<:s><:#240,8486>About file statistics

<:s><:#600,8486>The Report task generates file statistic reports that shows the size, replica ID, amount of unused space, and percent of used space for each database and template on a server. These reports also warn you if the percent of used space for a file drops below 7
0%<-!>, indicating the need for compacting.<-!>

<:s><:#600,8486>The Report task generates a file statistics report when loaded and at subsequent analysis intervals, if you specify an analysis interval in the Server to Monitor document. You can also generate File Statistic Reports on demand by issuing the following serve
r console command:

@Mono@<:#200,8486>TELL REPORTER UPDATE FILE STATS

@Bhead title@<:s><:#220,8486>Viewing file statistics

<:s><:#200,8486>To view reported file statistics:

@Numbered list@<:#200,8486>Open Stats & Event Report (STATREP.NSF)

@Numbered list@<:#200,8486>Choose View - File Stats.

<:s><:#400,8486>An Investigate flag indicates that the percent of used space in a file is below 70%, and therefore requires compacting.

@Ahead@<:s><:#240,8486>About reporting statistic alarms

<:#600,8486>If you run the Report task on a server, you can set up Statistics Monitor documents in Stats & Events Config (EVTCONFI.NSF) that generate alarms in Stats & Events Report (STATREP.NSF) if statistics exceeds specified thresholds. 

<:#1200,8486>You may want to keep some Statistics Monitor documents in place permanently but use others only temporarily. For example, you may always want to know if disk space on a server falls below 10MB and therefore set up a permanent Statistics Monitor document in 
place to alert you when disk space on a server falls below this threshold.  On the other hand, if you suspect that server performance is slow, you can set up Statistics Monitor document to report if more than five server sessions are dropped, but disable it
 after monitoring dropped server sessions for a week.

<:#600,8486>The first time a threshold is exceeded, the Report task creates an Alarm document in Stats & Events Report. If the threshold remains exceeded during subsequent collections, the "Alarm Report Count" field in the Alarm document is incremented by one.

<:#400,8486>You can compose an Alarm Trouble ticket in Stats & Events Report to notify someone, for example another administrator, of a reported alarm.

<:#600,8486>Notes can also report alarms as events, if you create an Event Monitor document type Statistic and you also run the Event task. This is a convenient way to automatically notify someone by e-mail when an alarm occurs, in addition to reporting the alarm in St
ats & Events Report.

@See also prnt@<:s><:#200,8486>See "Creating an Event Monitor document" earlier in this chapter for information.

@Bhead title@<:s><:#220,8486>Setting up a Statistics Monitor document

@Numbered list@<:#400,8486>Open Stats & Events Config (EVTCONFI.NSF) on the workspace and choose Create - Monitors - Statistics Monitor.

@Numbered list@<:s><:#200,8486>Next to Enabled/Disabled, accept the default setting, "STATISTIC MONITOR ENABLED."

@Numbered list@<:s><:#400,8486>Next to Server name, select one or more servers from the list. <:f180,BArial,0,0,255><+!><+">Can you select more than one server from the list??<-"><-!><:f>

@Numbered list@<:s><:#400,8486>Next to Statistic Name, press ENTER to display a list of statistics, select a statistic for which to set an alarm or type an unlisted statistic in the New Keywords box. Click OK.

@Numbered list@<:s><:#400,8486>Click Fill In With Defaults to automatically enter default values for the remaining fields as specified in the Statistic Description document for the selected statistic. Then skip to step 10.

@Numbered list@<:s><:#400,8486>Next to Threshold operator, press ENTER, select one of the following threshold operators, then click OK:

@Indnt bullet@<:s><:#200,8486>Less than

@Indnt bullet@<:s><:#200,8486>Greater than

@Indnt bullet@<:s><:#200,8486>Multiple of

@Numbered list@<:s><:#400,8486>Next to Threshold value,  type a value that, along with the threshold operator, defines when to report the alarm.

@Numbered list@<:s><:#200,8486>Next to Event severity, press ENTER, select one of the following severity levels, then click OK:

@Indnt bullet@<:s><:#200,8486>Fatal

@Indnt bullet@<:s><:#200,8486>Failure

@Indnt bullet@<:s><:#200,8486>Warning (high)

@Indnt bullet@<:s><:#200,8486>Warning (low)

@Indnt bullet@<:s><:#200,8486>Normal (low)

@Numbered list@<:s><:#200,8486>Type a comment that suggests a course of action if an alarm is reported.<-!><-">

@Numbered list@<:s><:#400,8486>Click Save Statistics Monitor. The Description field summarizes how the alarm works based on the specified values.<-!><-">

@Numbered list@<:s><:#200,8486>Click Exit to close the Statistics Monitor document.

<:#400,8486>If a statistic exceeds the specified threshold, an alarm is reported to Stats & Events Report (STATREP.NSF) at the specified collection interval.

@Note@<:s><:#400,8486>If you create more than one Statistics Monitor document per statistic, Notes determines whether to generate an alarm based on the last Statistics Monitor document listed for the statistic.

@Chead title@<:s><:#200,8486>Details: Setting up a Statistics Monitor document

@Bullet@<:s><:#600,8486><+!>Statistic Name<-!> - The keyword list for Statistic Name lists statistics for which alarms are commonly set.  (If you purchased an add-on product designed to work with Notes server management tools, this list may include additional statistics.

@1st lev para@<:s><:#400,8486>The following table describes the statistics most commonly used with alarms, their suggested thresholds and severity levels, and the implications if thresholds are exceeded.<-!><-">

@1st lev para@<:s><:t3>

@Bullet@<:s><:#400,8486><+!>Fill in With Defaults<-!> This button only fills in default information for fields assigned default values in the Statistics Description document for the selected statistic.

@Bullet@<:#400,8486><+!>Event severity<-!> The severity level appears in the Alarms view of Stats & Events Report (STATREP.NSF) and within an Alarm document. 

@1st lev para@<:s><:#800,8486>You can also report alarms as events by creating an Event Monitor document and entering the Event type as Statistic. When you do this, you must indicate which alarms to generate as events by specifying an Event severity level--only Statistic Monitor documen
ts assigned the same severity level as one assigned in an Event Monitor document type Statistic are reported as events.<-!><-!><-">

@Chead title@<:s><:#200,8486>Examples: Setting up Statistics Monitor document<-!><-">

<:#400,8486>The following Statistics Monitor document generates an alarm when the amount of free memory on a server falls below 1MB:

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">Add example dialog here.<-"><-!><:f>

@Bhead title@<:s><:#220,8486>Viewing a reported alarm

<:#200,8486>Check daily in Stats & Events Report (STATREP.NSF) for any reported alarms.

@Numbered list@<:#200,8486>Open Stats & Events Report on the workspace.

@Numbered list@<:s><:#200,8486>Choose View - Alarms.<-!><-">

@Numbered list@<:s><:#200,8486>Double-click an Alarm document to open it.

@Chead title@<:s><:#200,8486>Details: Viewing a reported alarm

<:#400,8486>The Alarms view of Stats & Events Report (STATREP.NSF) provides the following information for each Alarm document:

@Bullet@<:s><:#200,8486>Server the alarm applies to

@Bullet@<:s><:#200,8486>Date and time the alarm was reported

@Bullet@<:s><:#200,8486>Severity level of the alarm

@Bullet@<:s><:#200,8486>Number of times the alarm has been reported

@Bullet@<:s><:#200,8486>Threshold setting

@Bullet@<:s><:#200,8486>Current value of the statistic associated with the alarm

<:s><:#400,8486>An alarm document provides additional details, including when the alarm was first and last reported and a suggested response.

@Ahead@<:s><:#240,8486>About alarm trouble tickets

<:#1000,8486>You can create a Trouble Ticket that notifies someone of an alarm reported in Stats & Events Report (STATREP.NSF). For example, you can send an alarm Trouble Ticket to somebody assigned to resolve the problem. Although you can also notify someone of an alar
m by creating an Event Monitor document type Statistic that mails a notification to someone, Trouble Tickets provide administrative features to help you resolve a problem.

@See also prnt@<:s><:#200,8486>See "About setting up event reporting" for information about creating Event Monitor documents.

<:#200,8486><+!><+"><:f180,BArial,0,0,255>Add that you can still send alarms to ALRMTRAK.NSF if you want.<:f><-"><-!>

@Bhead title@<:s><:#220,8486>Creating a trouble ticket to Notify someone of a reported alarm<-!><-"><-!><-">

@Numbered list@<:#200,8486>Open Stats & Events Report (STATREP.NSF) on the workspace and choose View - Alarms.

@Numbered list@<:s><:#200,8486>Select the Alarm document for which you want to create a Trouble Ticket.

@Numbered list@<:s><:#200,8486>Choose Create - Alarm Trouble Ticket.<-!><-">

@Numbered list@<:s><:#200,8486>Next to Ticket ID, type<:f180,BArial,0,0,255><+!><+"> <-!><-"><:f>an ID according to a ticket ID system you've set up.

@Numbered list@<:s><:#400,8486>Next to "Person assigned for corrective action," type the name of the person responsible for correcting the problem.

@Numbered list@<:s><:#200,8486>Next to Server Location:<:f180,BArial,0,0,255><+!><+">????<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Next to Problem Documentation, type any additional information related to the alarm.

@Numbered list@<:s><:#400,8486>Next to "Mail trouble ticket to" type the name of a person to receive the trouble ticket or click Address to select a name from a Name & Address Book.

@Numbered list@<:s><:#200,8486>Click "Mail Trouble Ticket" to send the trouble ticket to the designated person.

@Numbered list@<:#200,8486>Click "Save Trouble Ticket" to save the Trouble Ticket in Stats & Events Report.

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">Which fields are optional vs. required? 

<:s><:#400,8486><-">A description of the statistic and the time Notes queued it for delivery are filled in automatically.  
<:f180,BArial,0,0,255><+!><+">Correct? <-"><-!><:f>

@Chead title@<:s><:#200,8486>Details: Creating a trouble ticket to notify someone of a posted alarm

<:s><:#200,8486><-!><-"><+!>Mail Trouble Ticket<-!><-!>

@Chead title@<:s><:#200,8486>Examples: Creating a trouble ticket to notify someone of a posted alarm

<:s><:#200,8486><:f180,BArial,0,0,255><+!><+">To come<-"><-!><:f>

@Bhead title@<:#220,8486>Viewing an alarm trouble ticket in Stats & Events Report

<:#400,8486>If you save an alarm Trouble Ticket in Stats & Events Report (STATREP.NSF), follow these steps to view it:

@Numbered list@<:#400,8486>Double-click the Stats & Events Report database icon on the server. Or choose File - Tools - Notes administration, click the Databases icon, and choose Open Statistics.

@Numbered list@<:s><:#400,8486>Choose View - Trouble Tickets - Alarm. The view displays the existing alarm trouble tickets.  
<:f180,BArial,0,0,255><+!><+">How far back do they go? Do you have to occasionally delete them? 
<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Double-click a trouble ticket to open it.<-!><-">

@Bhead title@<:s><:#220,8486>Disabling a Statistics Monitor document<-!><-">

<:s><:#400,8486>Follow these steps to disable a Statistics Monitor document if you no longer want to monitor the statistic associated with it but want to keep a copy for future use.

@Numbered list@<:#200,8486>Open Stats & Events Config (EVTCONFI.NSF).

@Numbered list@<:#400,8486>Select the Statistic Monitor document you want to disable and press CTRL+E (or COMMAND-E on the Macintosh).<-!><-">

@Numbered list@<:s><:#200,8486>Next to Enabled/Disabled, press ENTER, select "Statistics Monitor Disabled," and click OK.

@Numbered list@<:s><:#200,8486>Click Save Statistic Monitor.

@Ahead@<:s><:#240,8486>About statistic documents

<:#800,8486>The Statistics Names view of Stats & Events Config (EVTCONFI.NSF) contains a document for each statistic the Report task can currently generate. You can edit these documents to customize the way in which statistics are reported. You can also create a new st
atistic for reporting, for example, a statistic specific to an operating system.

@Bhead title@<:s><:#220,8486>Viewing statistic names

<:#400,8486>To display a list of statistics (alphabetically by name) that are reported, open Stats & Events Config (EVTCONFI.NSF) on the workspace and choose View - Names & Messages - Statistic Names.

<:s><:#200,8486>The Statistics Names view provides the name and description of each statistic that can be reported.

@Bhead title@<:s><:#220,8486>Ways to customize statistics

<:s><:#200,8486>You can customize statistics by

@Bullet@<:s><:#200,8486>Modifying a statistic document

@Bullet@<:s><:#200,8486>Creating a new statistic document

@Bhead title@<:s><:#220,8486>Modifying a statistic document

<:#800,8486>You can modify a statistic document listed in Stats & Events Config (EVTCONFI.NSF). For example, you may want to change the wording of a suggested response created in an Alarm document. Generally, you don't need to change the default entries for statistics.
<:f180,BArial,0,0,255><+!><+"> (when would you want to do this; examples)<-"><-!><:f>. 
<:f180,BArial,0,0,255><+!><+">Mention only modifications typically made (which are?) and divide into separate tasks? 
<-"><-!><:f>

@Numbered list@<:#400,8486><-!><-">Open Stats & Events Config on the workspace and choose View - Names & Messages - Statistic Names.

@Numbered list@<:#200,8486>Select the statistic you want to edit and press CTRL+E (or COMMAND-E on the Macintosh).

@Numbered list@<:s><:#200,8486>Edit the fields you want to change.

@Numbered list@<:s><:#200,8486>Click Save Statistic and then click Exit.

@Bhead title@<:s><:#220,8486>Adding a new statistic<-!><-">

<:#600,8486>Add a new statistic if you want to monitor a non-Notes statistic, such as one specific to your operating system.<+"><+!><:f180,BArial,0,0,255> Correct? 
<:f180,BArial,0,0,255>Any other time you'd do this? Are there any Notes stats not in the list that someone might want to add?  Examples?<-!><-"><:f>

@Numbered list@<:#400,8486>Double-click the Stats & Events Config database icon.  Or choose File - Tools - Notes administration, click the Databases icon, and choose Configure Statistics Reporting.

@Numbered list@<:s><:#200,8486>Choose Create - Statistic.

@Numbered list@<:s><:#400,8486>Next to Statistic Name, type the name of the new statistic you want to monitor.  
<:f180,BArial,0,0,255><+!><+">How do you find out the name of the statistic ? What does a statistics name correspond to? 
<-"><-!><:f>

@Numbered list@<:s><:#200,8486>Next to Type, press ENTER, select Text, Number, or Time to indicate what type of statistic it is.

@Numbered list@<:s><:#400,8486>Next to Units, type the units in which the statistic is measured, for example, bytes. Type none if the statistic is a text statistic.

@Numbered list@<:s><:#200,8486>Next to Description, type a description of the statistic.

@Numbered list@<:s><:#200,8486>Next to Normal Value, type a normal value for this statistic if one exists; otherwise type Varies.

@Numbered list@<:s><:#400,8486>Next to "Is this statistic useful for setting thresholds?" press ENTER and select Yes if a statistic alarm would be useful for this statistic; otherwise select No. 
<-!><-">If you select No, skip to step 13. 

@Numbered list@<:s><:#400,8486>Next to Suggested Operator, press ENTER and select a threshold operator to be used as a default operator if you create an alarm for this statistic, and click OK.

@Numbered list@<:s><:#400,8486>Next to Suggested threshold, type a value to be used as a default threshold if you create an alarm for this statistic, and click OK.

@Numbered list@<:s><:#400,8486>Next to Suggest Severity, press ENTER, select a default severity level to be used if you create an alarm for this statistic, and click OK. 

@Numbered list@<:s><:#400,8486>Next to "Suggested response if this threshold is exceeded," type summary of the problem and a suggested solution to appear by default in the Comments field if you create an alarm for this statistic.

@Numbered list@<:s><:#200,8486>Click Save Statistic.

@Ahead@<:#240,8486>

>

[Embedded]
00127721
