[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[master]
	C:\AMIPRO\NOTES4\MIGRATE\toc.SAM
	
	0
	210
	6
	c:\amipro\notes4\migrate\about.sam
	c:\amipro\notes4\migrate\chap1.sam
	c:\amipro\notes4\migrate\chap2.sam
	c:\amipro\notes4\migrate\chap3.sam
	c:\amipro\notes4\migrate\chap4.sam
	c:\amipro\notes4\migrate\chap5.sam
[sequence]
	9
	0
	0
	0
	23
	4
	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
	0
	_COND_IF
	0
	_COND_ELSE
	0
	_COND_ENDIF
[prn]
	Apple LaserWriter II NT
[port]
	LPT3:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	
	
	
	
	
	801446871
	44
	798505259
	1858
	8
	1122
	6655
	7
	28
	
	
	
	
	
	
	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]
		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
		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
		240
		255
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		100
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		IF
		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]
	_COND_ELSE
	0
	[fnt]
		Arial
		240
		255
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		100
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		ELSE
		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]
	_COND_ENDIF
	0
	[fnt]
		Arial
		240
		255
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		100
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		ENDIF
		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
[lay]
	Standard
	2055
	[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
		960
		1200
		3
		960
		720
		0
		1
		0
		1
		0
		2
		1
		960
		9446
		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
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		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
		360
		480
		3
		11940
		715
		0
		1
		0
		1
		1
		0
		1
		360
		9450
		1
		3
		9900
	[txt]
<:I0,630,0,0><:R1,1,1,6868,><:P19999,0,4->  Migration 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
		360
		480
		3
		11940
		715
		0
		1
		0
		1
		1
		0
		1
		360
		9450
		1
		3
		9900
	[txt]
<:I540,0,90,0><:R1,1,1,4080,>Lotus Confidential	Making Additional Changes to Servers and Workstations  
<:P19999,0,4->

>
[elay]
[l1]
	0
[pg]
	8
	29 192 20 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
	52 109 50 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
	81 105 57 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
	102 200 17 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
	126 0 78 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
	151 99 5 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
	178 0 91 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
	179 0 0 1025 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><:#600,8486>Chapter 4 Making Additional Changes to Servers and Workstations

<:s><:#200,8486>This chapter describes optional procedures that you can use to optimize the system at your organization.

@Ahead@<:s><:#240,8486>About using new features to optimize the system

<:#600,8486>Release 4 comes with new features that make your system easier to expand and maintain.  Depending on your schedule, you may want to start implementing these new features anywhere from a few days to a few months after you have migrated your entire organizati
on. 

<:#400,8486>To maintain server stability and reliability, implement one new feature, test for any problems, and then repeat this process for each new feature your organization requires.

<:#400,8486>The following is a list of new features you may want to implement and where to find additional information on these features:

@Bullet@<:s><:#200,8486>Modify the replication strategy to utilize new replication features and enhancements.

@1st lev para@<:s><:#200,8486>For more information, see "About modifying the replication strategy" below.

@Bullet@<:s><:#200,8486>Reduce the size of mail databases by storing one copy of messages shared by several users.

@1st lev para@<:s><:#200,8486>For more information, see "Reducing the size of mail databases" below.

@Bullet@<:s><:#200,8486>Set up multiple servers on one computer to save on hardware and administration costs.  

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Bullet@<:s><:#200,8486>Plan your system topology for subsequent releases.

@1st lev para@<:s><:#200,8486>For more information, see "Planning for subsequent releases" below.

@Bullet@<:s><:#200,8486>Upgrade user IDs to use the hierarchical naming scheme.

@1st lev para@<:s><:#200,8486>For more information, see "Upgrading user IDs to hierarchical naming" below.

@Bullet@<:s><:#200,8486>Set up servers for pass through so users can access one server and use another server.

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Bullet@<:s><:#400,8486>Distribute responsibility for the Name & Address Book and secure the Name & Address Book against any errors by assigning roles to people in your organization.

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Bullet@<:s><:#400,8486>Create a Server Configuration Document so you can make changes to NOTES.INI when you are not at the server machine.

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Bullet@<:s><:#200,8486>Specify a maximum size for databases.

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Database Manager's Guide<-">.

@Bhead title@<:s><:#220,8486>About modifying the replication strategy

<:#400,8486>The new replication features and enhancements enable you to redesign your replication strategy to be faster, simpler, and easier to maintain.

<:s><:#200,8486>These features and enhancements apply only to servers using Release 4. 

<:s><:#200,8486>The following are enhancements to replication that Notes implements for you automatically:

@Bullet@<:s><:#600,8486>Instead of dynamically building a list of matching databases between two servers, each server automatically maintains in memory a list of databases on that server. This way Notes can scan for replica IDs quickly.

@Bullet@<:#600,8486>When Notes replicates between two Release 4 databases, it scans each document for fields that are modified and replicates only those fields instead of the entire document. This field-level replication saves time on the server.

@1st lev para@<:#200,8486>This feature is not available on Release 3.x format databases.

@Bullet@<:s><:#600,8486>Instead of scanning the destination database (the database that will receive the replication information) for matching information every time a replication occurs, Notes automatically uses an index of the database stored in memory to search quickly for matc
hing information.

<:s><:#200,8486>The following are new features that you can implement to improve replication speed and efficiency:

@Bullet@<:#600,8486>You can run multiple replicators so replication among multiple servers will be faster. Each replicator can replicate with a different server; you cannot use multiple replicators to replicate with multiple databases on the same server.

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Bullet@<:#600,8486>You can specify exactly which databases you want to replicate instead of automatically replicating all databases in common. Use a Server Connection document in the Public Name & Address Book to specify the databases to replicate so Notes saves time scanning
 for replica IDs on servers.

@Bullet@<:#400,8486>You can specify a time limit for replication using a Server Connection document. Use this feature to save money on connection costs to remote sites.

@Bullet@<:#800,8486>You can use the Pull-Push replication method to reduce the load on a server and reduce the time it takes to determine what information to replicate. Notes no longer restricts replication to only one server pushing at a time; you can now have two or more rep
licators replicating changes to a database simultaneously. Specify the replication method in the Server Connection document.

@Bhead title@<:#220,8486>About reducing the size of mail databases

<:#400,8486>The single copy object store feature lets you create a central database stored on a single server that contains messages shared by users who have their mail databases on that server. 

<:#1200,8486>After you enable the central database, the server's mail router checks an incoming mail message to see if it has multiple recipients. If it has multiple recipients, the mail router then checks to see if the recipients' mail databases reside on the same serv
er and if so, stores a portion of the message in each user's mail database and delivers the body of the message to the central database. The portion of the message that resides in the user's mail database contains a link to the central database where the bo
dy of the message resides.

<:#600,8486>You can add existing messages to the central database on the server instead of just the new messages that the mail router sends to the mail databases on the server. This conversion takes xxx minutes for an xxx size database.

<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Bhead title@<:s><:#220,8486>Reducing the size of mail databases

<:#400,8486>You can reduce the size of users' existing mail databases by storing shared messages in a central database.

@Numbered list@<:s><:#200,8486>Shut down the server and workstation.

@Numbered list@<:#200,8486>Using a text editor, open the NOTES.INI file.

@Numbered list@<:#200,8486>Find the line RouterUsesObjectStore= and change this to Yes.

@Numbered list@<:#200,8486>Restart the server program.

@Numbered list@<:s><:#200,8486>At the server console, type the following:

@Indnt mono@<:#200,8486>load object link <+">databasename <-"><+">databasestore<-">

@1st lev para@where <+">databasename<-"> is the name of the mail database and <+">databasestore<-"><+"> 
<-">is the name of the central database that will store the shared mail messages.

@Ahead@<+@><:s><:#240,8486>Changing the Notes server platform

<+@><:#400,8486>As the Notes system grows and as system requirements change at your organization, you may decide to use a different platform.

@Note@<+@><:#400,8486>You must know which platform you want to use before you continue with this section.  For more information, see xxx in xxx in the<+"> Deployment Guide.<-">

@Numbered list@<+@><:#400,8486>Create backup copies of the following files: NOTES.INI, DESKTOP.DSK, NAMES.NSF, the server ID, certifier IDs, LOG.NSF, and any databases, database templates, and database links on the server.

@Numbered list@<:#200,8486>Route mail to an available server to clear the messages waiting in MAIL.BOX.

@1st lev para@<:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Numbered list@<+@><:s><:#200,8486>Shut down the Notes server.

@Numbered list@<+@><:s><:#200,8486>Install the platform software as described in the documentation that came with it.

@Numbered list@<+@><:s><:#200,8486>Install protocols that are compatible with the platform software and Notes.

@1st lev para@<+@><:#200,8486>For more information, see xxx in xxx in the <+">Network Configuration Guide<-">.

@Numbered list@<+@><:#400,8486>Install Notes Release 4 and run the Setup program.  Make a note of the Notes data directory you specify during Install. Specify the following during the Setup program:

@Indnt bullet@<+@><:#200,8486>Enter the same server name, domain name, and network name of the original server.

@Indnt bullet@<+@><:#400,8486>Deselect the create IDs check boxes in Advanced Options so you can supply the original server ID,  user ID for the administrator, and certifier ID.

@1st lev para@<+@><:s><:#200,8486>For more information, see the <+">Install Guide<-"> for the server platform.

@Numbered list@<+@><:s><:#200,8486>Copy the files that you saved in step 1, except for NOTES.INI, to the Notes data directory.

@Numbered list@<+@><:s><:#400,8486>If you edited NOTES.INI and customized it by adding variables manually, copy the information you added from the backup copy of NOTES.INI to the new version of NOTES.INI.

@Numbered list@<+@><:#400,8486>If you installed new protocols, add these to the Server Document in the Public Name & Address Book and use File - Tools - Notes Preferences to enable the ports. 

@Ahead@<+@><:s><:#240,8486>Changing a Notes user's license type

<+@><:#400,8486>You can change a Notes Express user to a Notes Desktop user or a Notes Express or Desktop user to a Notes user. The license type determines the type of access the user has to certain features.

<+@><:#200,8486>For a list of features that each license allows, see xxx in xxx in the 
<+">Administrator's Guide<-">.

@Numbered list@<+@><:s><:#200,8486>Make sure you purchased the correct license type for the user.

@Numbered list@<+@><:#200,8486>Open the person's User document in the Public Name & Address Book.

@Numbered list@<+@><:s><:#200,8486>In the Client License Type field, enter the type of license.

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

@Numbered list@<+@><:#400,8486>After the Public Name & Address Book replicates with the Public Name & Address Book on the user's home server, tell the user to choose File - Tools - User ID - Trade-up and start Notes again.

@Ahead@<+@><:s><:#240,8486>About changing a cc:Mail mailbox to a Notes mail database

<+@><:#400,8486>You can convert a cc:Mail mailbox to a Notes mail database by using the Lotus Mail Exchange Facility (LMEF), a program that you purchase separately from Notes Release 4.

<+@><:#600,8486>LMEF converts existing cc:Mail messages to Notes messages and adds them to the Notes mail database.  It also creates a personal Name & Address Book for the user and converts private mailing lists to Group documents.

<+@><:#400,8486>After you convert the cc:Mail mailbox, you must register the user and install the workstation version of Notes if the user does not already have a copy installed.

<+@><:#200,8486>For more information on LMEF, see the <+">LMEF Administrator's Guide<-">.

@Ahead@<+@><:#240,8486>About planning for subsequent releases

<+@><:#200,8486>tbd

@Ahead@<+@><:s><:#240,8486>About upgrading IDs to hierarchical naming

<+@><:#800,8486>Notes includes a new NotesFlow feature to make upgrading server and user IDs from flat to hierarchical easier. You must install Notes Release 4 on all workstations and servers that will be involved in the upgrade process. You need to install Notes Release 4
 only on those servers that contain databases that will have their access control lists automatically updated.

@Note@<+@><:#400,8486>You can also use this feature to recertify an ID, rename a user ID, and change the hierarchical name of a user. For more information, see xxx in xx in the 
<+">Administrator's Guide<-">.

<+@><:#800,8486>The feature uses the administration agent, which runs on every Release 4 server, to automate the process of renaming the server or user with a hierarchical name and updating documents and access control lists for databases that contain the server or user na
me. Notes no longer requires administrators or end users to mail a safe copy of their user IDs to you to recertify.

<+@><:#600,8486>The administration agent uses an administration requests database, called ADMINP.NSF, which you create when you set up Notes. The administration requests database replicates to all servers in a domain and creates documents that convert a server or user name
 to a hierarchical name.

<+@><:#400,8486>When you specify the servers to convert to hierarchical names in the Public Name & Address Book (PNAB), the following occurs:

@Bullet@<+@><:s><:#400,8486>Notes automatically creates requests to update the server IDs and stores any information regarding these updates in the requests. Notes stores these requests in the administration requests database.

@Bullet@<+@><:#400,8486>Each server periodically checks its server document in the PNAB to make sure the certificate stored in the Server document matches the certificate of the server ID. 

@Bullet@<+@><:#600,8486>If the certificates do not match, Notes updates the server ID with the new certificate and issues a request in the administration requests database to update the Server document and all occurrences of the flat server name in the PNAB.

@1st lev para@<+@><:#600,8486>In order to change the documents in the PNAB, each PNAB must have an administration agent server set in the access control list.  The administration agent server determines which server's administration agent will make the change to the PNAB.

@Bullet@<+@><:#200,8486>Notes updates each Server document and all occurrences of the flat server name in the PNAB.

@Bullet@<+@><:s><:#400,8486>Notes issues requests to update the access control lists for databases.  Notes stores these requests in the administration requests database, which replicates to all administration requests databases.

@1st lev para@<+@><:s><:#600,8486>In order to change the access control list for a database, the database must have an administration agent server set in the access control list. The administration agent server determines which server's administration agent will make the change to the datab
ase.

@Bullet@<+@><:s><:#400,8486>The administration agents for each of the servers update the access control lists by changing any occurrences of the flat server names to the hierarchical server names. 

<+@><:#200,8486>When you specify the users to convert to hierarchical names in the PNAB, Notes does the following:

@Bullet@<+@><:s><:#400,8486>Notes automatically creates requests to update the user IDs and stores any information regarding these updates in the requests. Notes stores these requests in the administration requests database.

@Bullet@<+@><:#400,8486>When each user accesses a server, the server looks in the PNAB to make sure the certificate stored in the User document matches the certificate for the user ID.

@Bullet@<+@><:#600,8486>If the certificates do not match, Notes updates the user ID automatically and issues a request in the administration requests database to update the User document and all occurrences of the flat user name in the PNAB.

@1st lev para@<+@><:#600,8486>In order to change the documents in the PNAB, each PNAB must have an administration agent server set in the access control list.  The administration agent server determines which server's administration agent will make the change to the PNAB.

@Bullet@<+@><:#200,8486>Notes updates each User document and all occurrences of the flat user name in the PNAB.

@Bullet@<+@><:s><:#400,8486>Notes issues requests to update the access control lists for databases. Notes stores these requests in the administration requests database, which replicates to all administration requests databases.

@1st lev para@<+@><:s><:#600,8486>In order to change the access control list for a database, the database must have an administration agent server set in the access control list. The administration agent server determines which server's administration agent will make the change to the datab
ase.

@Bullet@<+@><:s><:#400,8486>The administration agents for each of the servers update the access control lists by changing any occurrences of the flat user names to the hierarchical user names.

@Bhead title@<+@><:#220,8486>About developing a hierarchical naming scheme

<+@><:#800,8486>Proper planning is required before you upgrade server and user IDs to hierarchical naming. You can structure hierarchical names based on geographical location, departments in the organization, or workgroups, or you can use a combination of these naming sche
mes. The scheme you use depends on the structure of your organization.

<+@><:s><:#200,8486>Keep these things in mind when deciding how to name servers and users in your organization:

@Bullet@<+@><:#600,8486>Choose a naming scheme that requires minimal  maintenance. For example, if your users change departments more frequently than they change office location, use a geographical location scheme to ensure that the hierarchical name will be correct even if a user
 changes jobs.

@Bullet@<+@><:#200,8486>Choose a scheme that requires 4 or fewer levels of organizational units. 

@Bullet@<+@><:#600,8486>Choose a simple naming scheme. This makes names easier for users and administrators to remember and eliminates unnecessary confusion. Although Notes supports up to 4 levels of organizational units, it is best to use only 2 or 3 organizational units.

@Bullet@<+@><:#800,8486>Choose a naming scheme that applies to all servers and users in your organization. For example, if you name the organization Acme, and Acme Corp. owns another company called Premier Corp., the servers and users in Premier Corp. will have a naming scheme tha
t does not make sense for their organization.

<+@><:#400,8486>After you develop a hierarchical naming scheme, create a chart of servers and users in your organization, with the hierarchical name assigned to each group.

<+@><:#200,8486>For more information on hierarchical naming, see xxx in xxx in the 
<+">Deployment Guide<-">.

@Ahead@<+@><:s><:#240,8486>Upgrading IDs to hierarchical naming

<+@><:s><:#200,8486>In order to change server and user IDs from flat to hierarchical, you must do the following:

@Numbered list@<+@><:#200,8486>Upgrade workstations and all servers that you will use as administration agent servers.

@Numbered list@<+@><:#400,8486>Create hierarchical certificates using the naming scheme you decided on in "About developing a hierarchical naming scheme" above.

@1st lev para@<+@><:s><:#200,8486><+!>?? Do I need something here about converting existing certificates to hierarchical naming??<-!>

@1st lev para@<+@><:#200,8486>For more information on creating certificates, see xxx in xxx in the 
<+">Administrator's Guide<-">.

@Numbered list@<+@><:#200,8486>Create the administration requests database and replicate it to all servers in the domain.

@1st lev para@<+@><:s><:#200,8486>For more information, see "Creating the administration requests database" below.

@Numbered list@<+@><:s><:#400,8486>Upgrade the server IDs from flat to hierarchical.  You must create hierarchical names for server IDs that are used as administration agent servers.

@1st lev para@<+@><:s><:#200,8486>For more information, see "Upgrading server IDs to hierarchical naming" below.

@Numbered list@<+@><:#600,8486>Upgrade the user IDs from flat to hierarchical. This will cause Notes to update the Public Name & Address Books on all servers and update the access control list of all databases for which an administration agent server is specified.

@1st lev para@<+@><:s><:#200,8486>For more information, see "Upgrading user IDs to hierarchical naming" below.

@Bhead title@<+@><:s><:#220,8486>Creating the administration requests database

<+@><:#400,8486>Before you can use the administration agent, you must create the administration requests database and replicate it to all servers in the domain.

@Numbered list@<+@><:#200,8486>Choose Database - New and enter ADMINP.NSF as the database name.

@Numbered list@<+@><:s><:#200,8486>Click Show all templates.

@Numbered list@<+@><:s><:#200,8486>Select Administration Requests Database.

@Numbered list@<+@><:s><:#200,8486>Choose OK.

@Numbered list@<+@><:s><:#200,8486>Create a replication schedule to replicate this database to all servers in the domain.

@Bhead title@<+@><:#220,8486>About upgrading server IDs to hierarchical naming

<+@><:#600,8486>The Name & Address Book contains a new field that stores the public key for a server ID.  Notes needs to certify this public key and compare the certificate to the server ID's certificate to see if the name of the server changed.

<+@><:#400,8486>You must upgrade the first server ID to a hierarchical name manually because the administration agent can run only on a server with a hierarchical name.

<+@><:#600,8486>Notes combines the server's flat name and the certifier name to create the hierarchical name.  For example, if a server's flat name is Server1 and the hierarchical certifier name is Marketing/Acme, the server's hierarchical name is Server1/Marketing/Acme. 

<+@><:#400,8486>The flat name must be the same as the common name component in the hierarchical name; you cannot change the name of the server when creating the hierarchical name.

<+@><:#600,8486>If your organization uses a hub and spoke topology, you should upgrade server IDs on the hub servers first, followed by the spoke servers. Servers and users using flat names will still be able to access servers using hierarchical names without any problems.

<+@><:#600,8486>Notes modifies the access control list and the documents in the Public Name & Address Book in the background and replicates the changes to all servers in the domain. The amount of time this takes to occur depends on the replication schedule for your organiz
ation.

@Bhead title@<+@><:s><:#220,8486>Upgrading server IDs to hierarchical naming

<+@><:#400,8486>Before you can upgrade user IDs, you must upgrade the IDs of the servers that run the administration agent servers.

@Numbered list@<+@><:#600,8486>Choose File - Database - Access Control, select Advanced, and add an administration agent server to each Public Name & Address Book (PNAB) and each database whose access control list you want to modify automatically.

@1st lev para@<+@><:#200,8486>For more information, see xxx in xxx in the <+">Database Manager's Guide<-">.

@Numbered list@<+@><:#400,8486>To upgrade the first server ID in the domain, choose File - Tools - Notes Administration, select Certifiers, and choose Register Organization or Register Organizational Unit.

@1st lev para@<+@><:#200,8486>For more information, see xxx in xxx in the <+">Administrator's Guide<-">.

@Numbered list@<+@><:#400,8486>Shut down the server and start it again to add the server's certified public key to its Server document in the PNAB.

@Numbered list@<+@><:#200,8486>After the PNAB replicates with all servers in the domain, open the PNAB located on any server.

@Numbered list@<+@><:s><:#400,8486>In the Server view, select one or more servers that you want to certify with the same hierarchical name.

@Numbered list@<+@><:s><:#200,8486>Choose Action - Convert Selected Entries to Hierarchical Names.

@Numbered list@<+@><:s><:#200,8486>Click Upgrade to Hierarchical.

@Numbered list@<+@><:#200,8486>Choose the hierarchical certifier to use and enter the password.

@Numbered list@<+@><:#200,8486>Enter the name and location of the certifier ID and enter the password.

@Numbered list@<+@><:s><:#200,8486>Enter the date when this certificate will expire for the server.

@Numbered list@<+@><:s><:#200,8486>Click Upgrade.

@Numbered list@<+@><:s><:#400,8486>After the administration requests database replicates to all servers, shut down and restart all servers that have new server IDs.

@Numbered list@<+@><:s><:#400,8486>Repeat steps 5 through 12 for every group of servers that you want to certify with the same hierarchical name.

@Bhead title@<+@><:#220,8486>About upgrading user IDs to hierarchical naming

<+@><:#600,8486>The Public Name & Address Book (PNAB) contains a new field that stores a certified public key for a user ID. Notes compares the certificate in the User document to the certificate in the user ID to see if you made any changes. 

<+@><:#600,8486>Notes combines the user's flat name and the certifier name to create the hierarchical name.  For example, if a user's flat name is Mark Hunt and the certifier name is Marketing/Acme, the user's hierarchical name is Mark Hunt/Marketing/Acme.

<+@><:#600,8486>When the user accesses a server that contains the changed name in the PNAB, the user ID automatically accepts the new certificate and displays a message in the status bar to indicate that the upgrade is complete.

<+@><:#600,8486>Notes modifies the access control list and the documents in the PNAB in the background and replicates the changes to all servers in the domain. The amount of time this takes to occur depends on the replication schedule for your organization.

@Bhead title@<+@><:s><:#220,8486>Upgrading user IDs to hierarchical naming

@Numbered list@<+@><:s><:#400,8486>Make sure you completed the steps in "Creating the administration requests database" and "Upgrading server IDs to hierarchical naming" above.

@Numbered list@<+@><:#200,8486>Open the Public Name & Address Book.

@Numbered list@<+@><:s><:#400,8486>In the Users view, select one or more users with user IDs that you want to certify with the same hierarchical name.

@Numbered list@<+@><:s><:#200,8486>Choose Action - Rename selected entries.

@Numbered list@<+@><:s><:#200,8486>Click Upgrade to Hierarchical.

@Numbered list@<+@><:#200,8486>Choose the hierarchical certifier to use and enter the password.

@Numbered list@<+@><:s><:#200,8486>Enter the date when this certificate will expire for the user.

@Numbered list@<+@><:s><:#200,8486>Click Upgrade.

@Numbered list@<+@><:s><:#400,8486>Repeat steps 3 through 8 for every group of users that you want to certify with the same hierarchical name.

@Bhead title@<+@><:s><:#220,8486>About checking for errors

<+@><:#600,8486>After Notes has a chance to change database access control lists and documents in the Public Name & Address Book, check the Certifier Log for any errors. Notes stores errors when recertifying servers and users with hierarchical names in a separate view call
ed <+!>??.<-!>

<+@><:#200,8486><+!>I need some info on errors that could occur.

<+@><:#200,8486>For more information on the Certifier Log, see xxx in xxx in the <+">Administrator's Guide<-">.

<+@><:#200,8486>

>

[Embedded]
00049526
