[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[sequence]
	4
	0
	0
	0
	20
	8
	Numbered list
	0
	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]
	
	
	
	
	
	801505501
	13
	797876920
	1148
	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,5 - >  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,5 - >

>
[elay]
[l1]
	0
[pg]
	1
	16 85 41 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
[edoc]
@Chapter title@<:s><:#300,8486>Chapter 5: Planning a Replication Strategy

<:s><:#1000,8486>As you deploy Notes applications, you will need to plan carefully how applications get distributed on servers. Replication is the process that allows two copies of a database to exchange updates and synchronize data. This means that instead of maintaining o
ne "master copy" of a database that users must be constantly connected to, you can distribute replicas of a database and use temporary LAN and dial-up connections to synchronize the data.

<:s><:#600,8486>Developing a replication strategy will ensure that users get the most up-to-date information in a timely way. Because replication may involve exchanging large amounts of information, it is important to plan carefully to get the best performance out of your 
system.

<:#200,8486>Replication is a server task. Using the replication task is described <[>XREF to Replication in AG.]

@Ahead@<:s><:#240,8486>About database replicas

<:s><:#1000,8486>A database replica is an exact copy of a database. When you create a  database replica, the replica and the original database share the same Replica ID. This is a unique number that Notes assigns to each database. For two databases to replicate, they must e
ach have this unique Replica ID, which Notes stores in the Database Properties. The file names of the databases can be completely different, but if their Replica IDs are identical, the databases will replicate. 

<:s><:#800,8486>When replication occurs, a database on one server transfers any new, edited, or deleted documents and design elements to a replica copy on another server. Data can be transferred one way or two ways between servers. Because replication is incremental, trans
ferring only changes to a database, the amount of network traffic and server time involved in synchronizing databases is kept to a minimum.

@Bhead@<:#220,8486>Database replicas on servers

<:s><:#1000,8486>Creating a database replica on a server allows additional users in different sites or on different networks to access information without having to access one centrally located database. Only users who are specifically granted the privilege to create replic
a copies of a database on a server can do so. This is an essential security and administrative precaution to prevent the proliferation of database replicas in your Notes system.

<:s><:#600,8486>One way of monitoring which users have replica creation privileges is to create a group document in the Public Name & Address Book (PNAB) that lists the users who can create database replicas. That way, you can add and delete user names from that list to co
ntrol who has this privilege. 

<:s><:#1200,8486>Create database replicas only as necessary. Unnecessary proliferation of replicas wastes server and network resources, as well as results in increased replication, access control list, and database management problems. To determine if a database replica is 
necessary, put the database on only one server and monitor the database statistics to see how heavily used the database is. If you find that it is heavily used by a particular group of people--for example, people at a regional office that is connected over 
a wide area network--create a database replica on a local server for that group.

<:#200,8486>

@Bhead title@<:s><:#220,8486>About connecting servers for replication

<:#800,8486>In order for replication to occur between two servers, the servers must be connected with connection documents that create a two-way path for the information to travel.  Connection documents are stored in the Public Name & Address Book of a server. (XREF to
 Connection Docs) The connection document specifies a schedule for replication to occur between two servers. 

<:s><:#600,8486>For servers on the same Notes network, connections are defined using a Network Connection document. For servers on different networks, or in different domains, connections are defined using Remote Connection documents.

@Note@<:s><:#400,8486>Connection documents are also used for scheduling mail routing.  Mail routing occurs automatically with scheduled replication.

The way you set up replication is tied closely to your Notes server topology. In a hub and spoke arrangement of servers, replication generally begins at the hub server and proceeds to the spokes. There must be at least one connection document from each hub 
server to each immediately adjacent server in its hub and spoke.<:f200,BHelv,0,0,0> (XREF to Topology<:f><:f200,BHelv,0,0,0>)<:f>

@Bhead@<:s>Database replicas on workstations

<:s>Even though most users are restricted from making replica copies of a database on a server, they can make a local replica copy of a database their own workstation, as long as they have at least Author access in the Access Control List of the database. Creat
ing a database replica on a workstation allows an individual user to make changes to a database and decide what changes, if any, to post to a server copy of the database. This is also the way a remote user can work with a database without maintaining a dial
-up connection. At any given point, the user can force replication to either pass the local changes to a server replica, to get changes from the server replica, or to exchange data in both directions.

See also <+!><[>Ways to create database replicas, ]<-!>

@Ahead@<:s>About types of replication

<:s>There are two types of replication. Both types have similar results.

@Bullet@<:s>Server-to-server replication replicates all databases that the two servers have in common. For more information, see  
<+!><[>jump to About server-to-server replication]<-!>.

@Bullet@<:s>Workstation-to-server replication allows you to replicate all databases that your workstation has in common with the server or to replicate only databases that you specify. For more information, see 
<+!><[>jump to About workstation-to-server replication]<-!>.

<:s>Replication can be either scheduled, where a server task initiates replication based on a schedule in a connection document, or forced, where a user initiates replication by selecting a database and using the menu command Tools - Replicate.

@See also btn@<:s>See also <+!><[>About <-!><+!>replication, About types of server-to-server replication, About setting up replication]<-!>

@See also btn@
@Ahead@<:s>About how replication works

<:s>The following steps describe how replication works for server-to-server replication. The process for workstation-to-server replication is somewhat different, because only one database at a time is involved, but the end result is the same.

@Numbered list@<:s>Replication is initiated by Server A to Server B, either by a scheduled replication event (recorded in a connection document in the server Name & Address book), or by a replication request typed at the server console.

@Numbered list@<:s>The two servers authenticate their identities by checking for mutually acceptable certificates. <[>xref to certificates]

@Numbered list@<:s>Server A sends a request to the Server B to begin replication. Replication is a parallel process, although the servers do not exchange data from the same database at the same time.

@Numbered list@<:s>The two servers compare lists of databases to identify databases with common replica IDs.  Then each server builds a list of document, design, and Access Control List modifications since the last replication with the other server.

@Numbered list@<:s>The transfer of updates takes place.

@Numbered list@<:s>When a database replication completes successfully, Server A uses the time stamp from Server B to record the time at which replication completed in the replication history of each database. Server B uses the time stamp from Server A to do the same.

<:s><:p<* >>

@Ahead@<:s>About when to replicate

<:s>The factors you might consider before approving a replica on a server include:

@Bullet@<:s>Has the database being replicated been approved for use in your organization? There should be a chain of command established to approve the use of organization resources for databases and database replicas.

@Bullet@<:s>Can all of the users of a database it access it in the most cost-effective way? If all of the users of a database can access an existing version across a LAN, you may not need to create any replica copies. If, however, a group of users is accessing a databa
se across a WAN, it is probably more cost-effective and a better performance decision to replicate a copy of the database to a server local to that group.

@Bullet@<:s>Is a heavily-used database overloading a server? To improve performance you might replicate the database to another server.

@Bullet@Does information need to be real-time? Keeping in mind that replicas of a database are almost always out of sync with the latest information, users needing access to real-time data should not access replica copies of a database.

@Ahead@<:s>About who controls replication

<:s>Replication can be controlled in two places: at the database level and at the server level. A database manager can make a database available for all users to replicate, turn off replication entirely, or limit replication through a variety of settings. Datab
ase managers should understand what your organizations policies are concerning database replication.

The key to controlling replication, however, is controlling server access. Only those users who specifically have 
<+!><+">(which?)<-"><-!> privileges in a server's Access Control List can place a replica copy of a database on that server. All server administrators, therefore should understand the organization policies for server access and replication and follow them a
ccordingly. 

@Ahead@<:s>About determining policies for replicating databases

<:s>The following are some general guidelines for managing replication. Your policies might differ.

@Bullet@<:s>Determine how a domain's Public Name & Address book will replicate.

@1st lev para@In a smaller, centrally administered organization, a single administrator or group of administrators might control the Name & Address book. The N&A book might replicate changes to other servers, but be set up to refuse changes made by anyone other than the 
designated administrator or administrators.

@Bullet@<:s>Decide who has the authority to place a database replica on a server

@1st lev para@<:s>Databases and replicas should be approved before they are granted server space. Replicas should be justified for reasons of access, cost, or performance to avoid unnecessary proliferation and increased administrative overhead.

@Bullet@<:s>Decide on a division of responsibility.

@1st lev para@<:s>Generally, a database manager is responsible for determining what users can access a database. A server administrator is responsible for ensuring that replications happen when they should. The administrator sets up the server-to-server connection documents 
and monitors the replication activities.

@Ahead@About keeping track of replication activities

Although the information that replicates from a database should be controlled by the database manager, making sure that replication takes place as scheduled is the job of an administrator. Notes provides you with a database, Log.nsf, that logs replication e
vents for a server. Using the Notes log, you can track:

@Bullet@<:s>Disconnection between servers -- network or remote

@Bullet@<:s>Certification problems

@Bullet@<:s>Documents damaged in replication

@Bullet@<:s>Problems resulting from insufficient ACL access

<:s>For information on setting up Log.nsf see (XREF to AG)

<:s>Each database also maintains a replication history that is useful for tracking down problems with replication. The manager of a database is generally responsible for monitoring the replication history.

@Ahead@About scheduling replication

<:s>The way that you schedule replication between servers is important because you need to find a balance between updating information in a timely way and not putting too much strain on system resources. To create a replication schedule, you need to establish a
 logical sequence that moves data to all of the servers in your Notes system.  Planning the relationships between servers is related to the server topology you establish. <[>XREF to Topology].

<:s>The common kinds of replication sequences are:

@Bullet@<:s>End to end, which applies have only two servers exchanging information.

@Bullet@<:s>Ring, which has Server A call Server B, Server B call Server C, and so on.

@Bullet@<:s>Mesh, where each server replicates with every other server in a domain.

@Bullet@<:s>Hub and spoke, where one hub server schedules and initiates replication requests to all other servers, or spokes. This is usually the best choice when you are scheduling more than a few servers for replication.

@Bhead title@About end-to-end and ring replication scheduling

<:s>End to end is the simplest replication sequence. It is simply replication scheduled between two servers.

<:s><[><+!><+">Need diagram here<-"><-!>]

<:s>Ring sequencing is direct replication involving more than two servers. Information travels in a ring, as Server A calls Server B, Server B calls Server C, Server C calls Server D, and Server D calls Server A.

<:s><[><+!><+">Need diagram here]<-"><-!>

<:s>The advantages of ring sequencing is that it is easy to administer in a site with few servers.

<:s>The disadvantages include:

@Bullet@<:s>A failure in one server calls all of the servers to fall behind

@Bullet@<:s>All servers must have a copy of all databases, which uses a lot of hard disk space.

@Bullet@<:s>Security might be compromised because all servers need Manager level access for every database.


@Bhead title@<:s>About mesh replication scheduling

<:s>A mesh, or cluster sequence allows each server to replicate with every other server in a domain. For example, Server A can call Server B or Server C directly, without going through another connection.

<:s><[>Need diagram here]

<:s>The advantages of mesh scheduling  include:

@Bullet@<:s>Direct database-to-database replication means timely updates

@Bullet@<:s>Fault tolerance increases because fewer servers are involved. Information passes directly from one server to another without passing through a hub or an intermediary server.

@Bullet@<:s>Direct replication works on a small scale

<:s>The disadvantages of mesh scheduling include:

@Bullet@<:s>Requires many connection documents, as determined by the equation n*(n-1)/2.

@Bullet@<:s>Can be more difficult to administer because you must plan to connections carefully to avoid overlapping replication schedules

@Bullet@<:s>Does not allow for standardized Access Control List requirements.

@Bullet@<:s>Gets very complicated when the number of servers exceeds four.

@Bhead title@About hub and spoke replication scheduling

<:s>In a hub and spoke sequence, one server is designated a hub for scheduling and initiating all replication requests for the other servers, which are spokes. This is the recommended sequence for sites who have a large number of servers or who need to replicat
e between different network topologies and with servers connected remotely.

<:s>The hub server initiates, in sequence, replication with the spoke servers. Four connection documents are required for the following arrangement.

<:s><[>Need a diagram here]

<:s>If a server acts as a hub for numerous servers, you might want to dedicate the server as a hub. In this case, users cannot access the hub directly but must access a spoke server.

If you use multiple networks at your site, a hub server can also be a multi-protocol machine with multiple interface cards using different media or network types.

<:s>The advantages of a hub and spoke sequence include:

@Bullet@<:s>The Access Control List for databases can be standardized so that the hub server has Manager access

@Bullet@<:s>You can increase security by limiting access to the hub and reducing the level of ACL privileges available for spoke servers.

@Bullet@<:s>Replication is more efficient and network traffic minimized because the number of "hops" between any two servers is minimized.

@Bullet@<:s>Maintenance of replication activities and server backups can be done centrally at the hub.

@Bullet@<:s>Administration is simplified because all replication is initiated from the hub so connection documents are minimized and the overlapping of requests is eliminated.

@Bullet@<:s>Server load is better balanced.

<:s>The disadvantage of a hub and spoke sequence include:

@Bullet@<:s>Network traffic increases on the LAN segment to which the hub is attached.

@Bullet@<:s>If you have too many servers (more than eight or nine servers per hub), you might need to establish tiers of hubs, which could require several dedicated servers.

@Bullet@<:s>In the event of a hub failure, all replication is disabled until the hub is replaced or repaired. 
<+!><+"><[>Reviewers: is this corrected by the new fault-tolerant feature??]<-"><-!><:p<* >>

@Ahead@<:s>About advanced tips for scheduling replication

<:s>Because replication can involve the movement of large amounts of data, the way that you set up and schedule replication can have significant performance consequences. After you have developed a basic replication strategy, consider some of these advanced tip
s to help you tune your system

@Bullet@<:s>The number of "hops" in a replication route should be kept to a minimum. The number of hops results directly from the way you connect servers in a Notes system via connection documents. Generally, when you get beyond a few servers in a Notes system, the mos
t effective arrangement for servers is hub and spoke, where the hub initiates replication by calling the spokes and passing the replication data along. 

@Bullet@<:s>Because replication can affect response time on a server, you should limit replication on servers where users are attached. Heavy replication schedules should be restricted to dedicated replication servers, or "hubs".

@Bullet@<:f180,BArial,0,0,0>Server tasks such as CHRONOS, UPDALL and UPDATE should not be run on a hub<:f180,BArial,0,0,0> server and no Full Text indexes should be calculated or stored on a hub server.  

@Bullet@<:s><:f180,BArial,0,0,0>Hub servers should not be on the same "network" as any other servers because they do not participate in mail routing and they should not appear in a user's Open Database dialog box.  The Access Control List of a hub server should enforce
 these restrictions.

@Bullet@<:s><:f180,BArial,0,0,0>When a replica is placed on a hub, it should be a complete replica.  This allows spoke 
<:f180,BArial,0,0,0>servers to selectively replicate from any hub server.  There may be specific conditions which warrant a departure from this rule, but exceptions should be carefully managed.

@Bullet@<:s><:f180,BArial,0,0,0>It is tempting to try to schedule replications at the different levels of the hub and spoke arrangement to bring some kind of predictability to the movement of data up<:f><:f180,BArial,0,0,0> to the central hub and then back down to the 
spokes, but this does not bring any benefit.  Each hub serves its spokes best by conducting a simple round robin schedule among them, repeating as often as practical.  This spreads all data within a hub's sphere of influence as quickly as possible. 

@Bullet@<:f180,BArial,0,0,0>An exception to hub and spoke replication is if you have a very large database (greater than 500 MB of data), that is supported on only 2 or 3 servers, these servers should replicate directly with each other so that all the hubs do not n
eed to have 500 MB of space to support the database.  This should be considered for any database over 100 MB.

@Bullet@<:f180,BArial,0,0,0>The biggest problem with a tree structure is that any problem with a hub server partitions the network into two pieces which don't communicate.  This risk should be alleviated by having a backup server available which is configured in su
ch a way that it  can be quickly (fewer than 10 minutes) substituted for any hub server.<:f>

>

[Embedded]
00041366
