[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[sequence]
	6
	0
	0
	0
	20
	6
	Numbered list
	8
	Bullet
	0
	Indnt bullet
	0
	Indnt caution
	0
	Indnt tip
	0
	Indnt note
	0
	Caution
	0
	Tip
	0
	Note
	0
	Browse
	0
	Keyword
	0
	Context
	0
	Title
	0
	Macros
	0
	Alink
	0
	Butnbar
	0
	Window
	0
	Win95 macros
	0
	Win31 macros
	0
	Build tag
[prn]
	HP LaserJet III PostScript
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	
	
	
	
	
	801442280
	13
	798835333
	1052
	6
	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]
	1st lev para
	9
	[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]
	Bullet
	11
	[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]
	Indnt bullet
	12
	[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]
	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]
	See also prnt
	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
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	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]
	See also hlp
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		40
		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
		.
		,
		$
	See also btn
	0
	120
[tag]
	See also btn
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		240
	[spc]
		24
		200
		4
		0
		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 btn
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	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]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt tip
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	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]
		48
	[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
		100
		0
		3
		100
	[brk]
		68
	[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
		.
		,
		$
	Body Text
	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]
		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
		.
		,
		$
	Parameter
	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
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[tag]
	Alink
	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
		A
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Alink
	0
	0
[tag]
	Butnbar
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		0
		0
		3
		100
	[brk]
		48
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		\li-140 
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Butnbar
	0
	0
[tag]
	Window
	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
		.
		,
		$
	Window
	0
	0
[tag]
	Win95 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
		W
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win95 macros
	0
	0
[tag]
	Win31 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
		X
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win31 macros
	0
	0
[tag]
	Build tag
	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
		.
		,
		$
	Build tag
	0
	0
[tag]
	_COND_IF
	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
		.
		,
		$
	_COND_IF
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ELSE
	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
		.
		,
		$
	_COND_ELSE
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ENDIF
	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
		.
		,
		$
	_COND_ENDIF
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[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]
@Left pg foot@<:R1,1,3,8460,><:P19999,0,6 - >  Deployment Guide	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
		900
		480
		3
		11940
		780
		0
		1
		0
		1
		1
		0
		1
		900
		9386
		1
		3
		9900
	[txt]
@Right pg foot@<:R1,1,3,8486,>Lotus Confidential	Deployment Guide <:P19999,0,6 - >

>
[elay]
[l1]
	0
[pg]
	6
	15 91 48 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
	32 0 5 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
	52 0 5 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
	65 417 69 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
	89 0 51 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
	100 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@<:s><:#300,8486>Chapter 6: Developing a Plan for NotesMail

<:s><:#1200,8486>NotesMail is a key component of the Notes communication picture. NotesMail enables the flow of Notes and non-Notes documents throughout your organization as well as with outside organizations. Your plan for using NotesMail at your site could be to have all 
users use NotesMail as their electronic mail package. Or you could support a system that has some users using NotesMail and some using another mail program such as cc:Mail from within Notes. Notes allows you a high degree of flexibility for supporting mail 
services to your users.

<:s><:#400,8486>Other parts of your NotesMail plan involve managing network traffic and server load as well as planning for managing and maintaining mail databases.

<:#200,8486>For information on integrating other mail packages with Notes, see <[>XREF to AG topic]

@Bhead title@<:s><:#220,8486>About NotesMail

<:s><:#1400,8486>NotesMail lets you move documents and file attachments throughout your Notes system. On the server side, NotesMail provides mail routing for both constantly connected and remote (dial-in) users. Users can take advantage of Notes high-level security capabili
ties, for example encryption and authentication, and use the Notes directory service, which provides customizable domain and personal Name & Address books as well as support for hierarchical naming based on the X.500 model. NotesMail has all of the attribut
es of other Notes databases and has access to server capabilities such as full-text indexing and server-based agents.

<:s><:#1200,8486>The Notes client supports remote access via replication or direct dial-in connection, allowing the remote user full access to mail functionality. Notes supports the use of rich text as well as graphics, images, audio, and video directly within a document. N
otes also supports the inclusion of live data from non-notes applications via Object Linking and Embedding (OLE). Users can also insert links to other documents in Notes databases into a NotesMail message. These links are maintained during the routing proce
ss.

<:s><:#600,8486>NotesMail services are available to other applications via VIM (Vendor Independent Messaging), or direct calls to the Notes API. You can connect NotesMail to other mail systems via a large number of gateways, including X.400, SMTP, MHS, PROFS, ALL-IN-1, Mic
rosoft Mail, and Soft*Switch.

<:s><:#200,8486><[><+!><+">Note to Reviewers: Will MAPI be supported in V4??<-"><-!>]

@Ahead@<:#240,8486>About mail routing basics

<:s><:#600,8486>An important part of implementing Notes is making sure mail gets delivered reliably and efficiently. To plan your mail strategy, you need to understand how Notes routes mail between users, servers, networks, and domains. 

<:s><:#1000,8486>Mail routing is the process of moving a document along a path of servers until the Mail Router finds the server that contains a mail file for the recipient. The mail route starts at the Notes editor. When a sender mails a document, it goes to the MAIL.BOX f
ile on the sender's server. The Mail Router program, which runs on all Notes servers, searches for the recipient's address in all available Name & Address books, and works out a routing path to the recipient's home server.

<:s><:#400,8486>To establish mail routing between servers in your system, you need to understand the definition of the following terms:

@Bullet@<:s><:#800,8486> A Notes network names a collection of servers that communicate directly on a LAN or bridged/routed WAN. A server's named network is listed in the server document in the PNAB. Servers on the same Notes network communicate directly, without using connection 
documents. Thus mail routing happens automatically for servers in the same Notes network.

@Bullet@<:s><:#400,8486> A Notes domain is a collection of Notes servers and users that share the same PNAB. Notes considers outside organizations foreign domains.

@Bullet@<:s><:#600,8486>Connection documents are required to establish communication between servers that are not on the same Notes network. Connection documents can link servers within the same domain, or can link servers in different domains.

@Bullet@<:s><:#200,8486> A home server is the where a user's mail file is stored. This is the final destination of mail messages. 

<:#200,8486><[>XREFS to topics on Notes networks, PNAB, Domain, Connection docs and mail routing how-to.]

@Bhead@<:s><:#220,8486>A simple example of mail routing

<:s><:#1200,8486>To understand the basics of mail routing, consider what happens in the simplest case of mail routing between two users in the same domain. When a user mails a document, the Notes workstation looks for the recipient's mail address in the PNAB. The workstatio
n program appends the address to the document. Then the  Mail Router examines the document to find the location of the recipient's mail file, which is located on the recipient's home server. Based on the location of the recipient's home address, the Mail Ro
uter does one of three things:

@Bullet@<:s><:#400,8486>If the recipient's mail file is on the same server as the sender's mail file, the Mail Router moves the document into the recipient's mail file.

@Bullet@<:s><:#800,8486>If the recipient's mail file is on another server that is connected via a network connection document in the PNAB to the sender's server, the Mail Router establishes a connection with the destination server based on connection schedules, and transfers the d
ocument to the Mail Router mailbox on that server. 

@Bullet@<:s><:#400,8486>If the Mail Router cannot find an address for the recipient or cannot determine a path to the destination, it returns the mail to the sender as undeliverable.

<:s><:#400,8486>If there is more than one possible route to the destination server, the Mail Router computes the least-cost route from the source server to the destination server. 

<:#200,8486><[>ART: Use the diagram from page 3-A-2 of the Sys Admin I course book.]

@Bhead@<:s><:#220,8486>How mail routing occurs automatically

<:s><:#1800,8486>Mail routing occurs automatically during scheduled replication. If you establish pairs of connection documents for all of the pairs of servers in your Notes system, you do not need to schedule mail routing separately. All you need to do is identify mail rou
ting as a task on each connection document, and let the replication schedule handle the rest of the work. For example, if you want to route mail between servers A and B, make sure that you have a connection document that has server A call server B for repli
cation and another connection document that has server B call server A for replication. This is a smart way to minimize the number of connection documents and prevent unnecessary traffic between servers. The same topology that establishes efficient replicat
ion between servers should also provide efficient mail routing. In most cases, the most efficient arrangement of servers is the hub and spoke.

<:s><:#200,8486><[>XREF to topology section and to replication]

@Ahead@<:#240,8486>Scheduling mail delivery

<:s><:#1000,8486>Because you can specify both replication and mail routing tasks in the same connection documents, you can make one dependent on the other, for example having mail routed when scheduled replication occurs, or initiating replication when a threshold count for
 mail to deliver is exceeded. Remember that if you are relying on a replication schedule, replication between servers requires only one connection document, but mail routing requires two (one in each direction.)

<:s><:#600,8486>In either case, you must always explicitly schedule routing for low-priority mail to servers outside of a named network. On the server's connection document, you can specify that mail should be routed at times that you indicate, or at specified intervals. <[>
XREF to AG procedure.]

<:s><:p<* >>

@Ahead@<:s><:#240,8486>About mail priority levels and routing

<:s><:#400,8486>When users compose mail messages, they can specify the priority level of the messages. The priority level--high, normal, or low--determines how quickly the mail will be delivered to its recipient. 

@Bullet@<:s><:#200,8486>High-priority mail is routed immediately, regardless of the routing schedule. 

@Bullet@<:s><:#600,8486>Normal-priority mail is routed at the next scheduled time or as soon as the number of pending messages reaches the route-at-once limit, as specified in the connection document. Normal is the default value for delivery priority.

@Bullet@<:#600,8486>Low-priority mail is, by default, routed only between midnight and 6:00 AM, even if is pending when normal or high-priority mail is routed.  Outside of a Notes network, a connection document is required in order to route low-priority mail.

@Bhead@<:s><:#220,8486>About mail routing and Notes system topology

<:s><:#800,8486>How Notes routes mail from one server to another depends entirely on the Notes system topology. In some cases, routing is fairly simple and quick. In other cases, routing requires that a document make multiple hops from server-to-server as it finds its way 
to the destination. How many hops a message makes depends on the locations of the sender's and the recipient's home server.

<:s><:#200,8486>The following are possible Notes topologies for mail routing:

@Bullet@<:s><:#400,8486>The sender and recipient are in the same Notes network and in the same domain.  For more information, see 
<+!><[>jump to About mail routing within the same Notes network and domain]<-!>

@Bullet@<:s><:#400,8486>The sender and recipient are in different Notes networks . For more information, see 
<+!><[>jump to About mail routing between<-!><+!> different Notes networks]<-!><+!>  
<-!>

@Bullet@<:s><:#400,8486>The sender and recipient are in different domains. For more information, see 
<+!><[>jump to About mail routing between different domains<-!><+!>]<-!>

@Bullet@<:#400,8486>The sender and recipient are different domains that are connected by a common domain. For more information, see 
<+!><[>About mail routing to a non-adjacent domain]<-!>

@Bhead@<:s><:#220,8486>About mail routing within the same Notes network and domain

<:#1000,8486>Mail routing between servers who are in the same Notes network and domain is the fastest, since it's virtually automatic. When a user mails a document, the Notes workstation examines the Public Name & Address Book (PNAB) for the recipient's address. If the 
document is addressed to a named group, Notes examines the PNAB for the group document and then translates the group into a list of individual users. Then, the workstation program appends the correct address(es)) to the document.

<:s><:#400,8486>Next the Mail Router examines the address for the location of the recipient's mail file, which is located on the recipient's home server. Then the Mail Router does one of two things:

@Bullet@<:s><:#400,8486>If the recipient's mail file is on the same server as the sender's mail file, the Mail Router moves the document into the recipient's mail file. 

@Bullet@<:s><:#800,8486>If the recipient's mail file is on a different server and the PNAB contains a connection document that allows the two servers to communicate, the Mail Router establishes a connection with the destination server, based on the connection document schedule, an
d transfers the document to the destination server's mailbox (MAIL.BOX). 

@1st lev para@<:s><:#600,8486>If there are a number of servers between the sender's server and the recipient's server, the Mail  Router temporarily stores the document in each server's mailbox until a connection, scheduled via a connection document, routes the document to the next stop 
on its way.

<:s><:#600,8486>If there is more than one possible route to the destination server, the Mail Router computes a least-cost route from the source server to the destination server. The Mail Router uses the server, connection, and domain documents in the PNAB to compute the ro
ute.

<:s><:p<* >>

@Bhead@<:s><:#220,8486>About mail routing between different Notes networks

<:s><:#1200,8486>Networks in the same Notes domain are connected to each other by network connection documents and remote connection documents that you create in the Public Name & Address Book (PNAB). When a user mails a document to a user in another connected Notes network
, the Mail Router looks at connection documents in the PNAB to determine how to route the mail. Each server's Mail Router along the route computes the least-cost route to the destination server and sends the document to the next hop along the route.

<:#800,8486>For mail routing between Notes networks to work properly, it is critical that all network connection documents between networks in a domain be replicated in the domain's PNAB, so that they will be visible to all servers.<+!> 
<-!>If network connection documents do not define a complete route from the sender's network to the recipient's network, the Mail Router returns the mail to the sender.

@Ahead@<:s><:#240,8486>About mail routing to different domains

<:s><:#1800,8486>Domains are connected to each other by remote connection documents that you create in the Public Name & Address Book (PNAB) and that connect a server in one domain with a server in the other domain. When a user in one domain mails a document to a user in an
other domain, the Mail Router looks at connection documents in the PNAB to determine how to route the mail. The Mail Router on the sender's mail server looks in the PNAB for a server in the local domain that has a connection to a server in the remote domain
. The Mail Router than transfers the mail document to the server that has a connection. The next time this server connects to the server in the other domain, it transfers the mail. When the mail reaches the server in the other domain, the Mail Router there 
determines where the recipient's mail server is, and then transfers the mail to it.

<:#600,8486>If the sender's mail server doesn't have a replica copy of the other domain's PNAB and the correct Names = variable in NOTES.INI, Notes won't be able to translate the group names or check the spelling of recipient's names in the other domain. 
<+!><[>KAREN: What is this Names= thing?]<-!> 

@Ahead@<:s><:#240,8486>About mail routing between non-adjacent Notes domains

<:s><:#1000,8486>In a large organization, there may be two Notes domains that are not directly connected via  a connection document, bridge, or router. These domains are not connected because they do not contain networks that run compatible protocols. To route mail between 
these domains, you identify a third, "middle" domain that  runs multiple protocols and can communicate directly with the two non-adjacent domains.  Then you route mail through the "middle" domain to the non-adjacent domain.

<:s><:#800,8486>To set up mail routing between non-adjacent domains, you create a non-adjacent domain document in the Public Name & Address Book (PNAB). This document specifies a domain that is connected to the source domain and that can route mail to the non-adjacent, des
tination domain. The adjacent domain is then a hop on the route to the non-adjacent destination domain.

@Bhead@<:#220,8486>Mail routing without a schedule

<:s><:#1000,8486>Mail routing occurs automatically during scheduled replication. If you establish replication schedules for all of the pairs of servers in your Notes system, you do not need to schedule mail routing separately. All you need to do is identify mail routing as 
a task on each connection document, and let the replication schedule handle the rest of the work. This is a smart way to minimize the number of connection documents and prevent unnecessary traffic between servers.

@Bhead@<:s><:#220,8486>The "route at once" limit

<:s><:#1000,8486>The connection document contains a field that allows you to automatically force a connection when a specified number of mail messages to a single destination server are pending delivery in the MAIL.BOX. To do this, you enter a value in the Route at once fie
ld of the connection document. For example, if you enter 5 in the field, the fifth mail message to the same server forces a mail connection. If fewer than five messages are waiting, mail is transferred according to the schedule. 

<:#400,8486>This setting applies only to normal-priority mail because high-priority mail forces an immediate call and low-priority mail is handled according to different criteria.

@Ahead@<:s><:#240,8486>About connecting servers that run different protocols

<:#1000,8486>There may be times when you want to connect two servers that are on networks that are running different protocols. When that's the case, you cannot use network or remote connection documents to connect them directly. Instead, you identify an intermediate se
rver on a network that is running both  protocols. This intermediate server, known as a passthrough server,  becomes a "stepping stone" to route information between the two servers. 

<:#400,8486>To set up a passthrough server, you create a passthrough connection document in the Public Name & Address Book (PNAB).   

<:#400,8486>Using a passthrough server, a mobile user can access multiple servers by making a single phone connection to the passthrough server.

<:#200,8486><[>XREF to how-to in AG]

@Ahead@<:s><:#240,8486>About tuning your mail operation

<:s><:#600,8486>After you get NotesMail working so that mail is being reliably routed and delivered, you can start to consider ways to make your mail system perform better for your organization. Notes includes some features for helping you tune NotesMail.

<:#1200,8486>The single copy object store makes use of a special-purpose database, MAILOBJ.NSF,  that holds copies of documents that are available to other databases. For example, if a mail document is sent to 20 users, a single copy of that mail message can reside in t
he object store database, and pointers will link the users' mail files to the database. Each recipient will have the experience of having an individual copy of the mail document without having the system burdened by having to deliver and store copies of the
 data in the document. This translates into significant savings of resources.

<:#200,8486>Setting up and using the single copy object store is described in <[>XREF to AG]

@Ahead@<:s><:#240,8486>Guidelines for routing mail

<:s><:#200,8486>You must use a connection document for mail routing to:

@Bullet@<:s><:#400,8486>route mail to a server in a different Notes named network (even if it is the same domain). A pair of connection documents is required to route mail in both directions.

@Bullet@<:s><:#200,8486>route mail to a server in a different domain

@Bullet@<:s><:#200,8486>schedule mail routing for low-priority mail at least once between midnight and 6:00 AM

<:s><:#200,8486>You do not need connection documents to:

@Bullet@<:s><:#200,8486>route mail between servers in the same Notes named network (mail routing occurs automatically)

@Bullet@<:s><:#400,8486>connect a server in your organization with a server in another organization. For this, you need a Remote Connection document.

<:s><:#200,8486>To minimize the number of connection documents:

@Bullet@<:s><:#400,8486>designate one server in each Notes named network to route mail to other Notes named networks or to outside organizations. This simplifies administration and provides you with more security.

@Bullet@<:s><:#400,8486>use one connection document for replicating and routing from Server A to Server B, then create a connection document from Server B to Server A that enables mail routing in the other direction.

<:s><:#200,8486>Synchronize the Name and Address books across a domain:

@Bullet@<:s><:#400,8486>replicate the public Name & Address book between all servers in your domain to successfully route mail

<:s><:#200,8486>To avoid Router confusion, eliminate the following:

@Bullet@<:s><:#400,8486>overlapping connection documents for the same task in the same direction so that the Router does not receive conflicting instructions

@Bullet@<:s><:#200,8486>connection documents for the same task that call the same server

<:s><:#200,8486>To improve the performance of your mail system:

@Bullet@<:s><:#400,8486>use the single copy object store feature to store single copies of mail messages that are distributed to many users

@Bullet@<:s><:#200,8486>use the mail trace feature to locate and debug mail routing problems

@Bullet@<:#200,8486>use mail trace to identify the fastest way to route mail between servers

@Ahead@<:s><:#240,8486>Planning for administering mail users

<:s><:#1000,8486>Every NotesMail user has a mail database on a server. If you are administering a large site, you may want to consider dedicating servers to be mail servers; that is they only hold mail databases. No matter where a user's mail database resides, you will need
 to monitor the size of the database. Mail databases can grow to large sizes, consuming considerable server resources, if not carefully monitored and maintained.

<:#1200,8486>Develop a policy that deals with user mail databases. One part of this policy could be the establishment of a maximum size for a mail database. Notes allows you to set a maximum database size, so this is easily enforced. <[>XREF to this in Database Manager'
s Guide or AG?] Setting a maximum size also allows you to more easily plan for server space. For example, if you allot a maximum mail database size of 10 MB per user for mail databases, and you dedicate a server that has 1 GB of hard disk space, you know yo
u can have 100 users on that server.

<:#600,8486>Another aspect of a mail policy is whether you allow mail users to perform a full-text index on their mail databases.  Indexing can provide users with the powerful capability of searching their database for the existence of a particular word or phrase, but 
full-text indexing can strain CPU and hard disk resources.

@Ahead@<:#240,8486>

>

[Embedded]
00043742
