<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/da/nch/danch2520m000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">SyncChanges Server Runs (danch2520m000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to view the server runs. In other words, the runtime history of the synchronization object. When you start the session, an overview dialog is started. When you double-click a record a details dialog is started.</Paragraph>
		</AimSection>
		<GeneralSection><List><ListIntro>The following fields are displayed in the overview dialog:</ListIntro>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.serv" role="manual">Synchronization Object</GUIRef> (and description).</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.runn" role="manual">Server Run</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.stat" role="manual">Run Status</GUIRef> (Running, Stopped, or Interrupted)</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.rust" role="manual">Run Start Time</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.ruen" role="manual">Run End Time</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.cost" role="manual">Start Commit Time</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch220.coen" role="manual">End Commit Time</GUIRef>
				</ListItem>
			</List>
			<Paragraph class="Default">In the details dialog, all relevant server run attributes are displayed.</Paragraph>
			<List><ListIntro>You can run the following commands in the overview and in the details dialog:</ListIntro>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#exec.user.1" role="command">Check Run Status</GUIRef>: use this command to manually refresh the server runs: the server runs are displayed for the current synchronization object again, and a check is performed whether the status of a run is <GUIRef href="" role="manual">Running</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#danch2220m000" role="command">Purge Server Runs</GUIRef>: starts the <Link href="/baanerp/da/nch/danch2220m000" role="session">Purge Server Runs (danch2220m000)</Link> session.</ListItem>
				<ListItem><GUIRef href="/baanerp/da/nch/danch2520m000#display.log.file" role="command">Show Log File</GUIRef>: use this command to view the content of the log file.</ListItem>
			</List>
			<Paragraph class="Default">In addition, you can start the <Link href="/baanerp/da/nch/danch2420m000" role="session">Print SyncChanges Server Runs (danch2420m000)</Link> session through the <GUIRef href="" role="manual">Print</GUIRef> command.</Paragraph>
		</GeneralSection>
	</HelpTopic>
	<Fields><FieldHelp ID="danch220.serv"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Synchronization Object</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#58" role="glossary">synchronization object</Link> for which the run was executed.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.runn"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Server Run</Title>
			</Header>
			<FuncDesc>The sequence number of the server run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.stat"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Run Status</Title>
			</Header>
			<FuncDesc>The server run's current status.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.stpb"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Stopped Because</Title>
			</Header>
			<FuncDesc>This field indicates why the server was stopped. Possible values: Not Applicable, Completed, User Intervention, and Error.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.rust"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Run Start Time</Title>
			</Header>
			<FuncDesc>The time at which the server run process was started.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.ruen"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Run End Time</Title>
			</Header>
			<FuncDesc>The time at which the server run process was ended.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.usst"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Start User</Title>
			</Header>
			<FuncDesc>The user who started the server run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.usen"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">End User</Title>
			</Header>
			<FuncDesc>The user who stopped the server run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.busc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Bus Component</Title>
			</Header>
			<FuncDesc>The bus component (communication channel) that was used to transfer the data.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.sttr"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Start After Transaction ID</Title>
			</Header>
			<FuncDesc>This indicates the transaction after which the current run started. If the previous run was stopped or interrupted, the end commit time of the previous run is not accurate enough to continue the next run. In that case the last transaction ID of the previous run is used as the 'transaction to start after' for the current run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.cont"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Continue Previous Run</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the server run continued where the previous run ended. That is: the run started at the first database transaction after the last transaction that was processed by the previous run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.cost"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Start Commit Time</Title>
			</Header>
			<FuncDesc>The start of the commit time interval specified for the server run. This means that all transactions processed will have a commit time greater than or equal to this start commit time.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.coen"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">End Commit Time</Title>
			</Header>
			<FuncDesc>The end of the commit time interval specified for the server run.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.fitr"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">First Transaction Processed</Title>
			</Header>
			<FuncDesc>The ID of the first transaction that is processed by the server.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.latr"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Last Transaction Processed</Title>
			</Header>
			<FuncDesc>The ID of the last transaction that is processed by the server.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.logf"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Log File</Title>
			</Header>
			<FuncDesc>The path of the log file that is used to log the server's output.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.libr"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Configuration Library</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#55" role="glossary">configuration library</Link> that is used during the server process.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.poll"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Polling Frequency</Title>
			</Header>
			<FuncDesc>The number of times per second the audit trail is checked to detect whether a transaction has occurred.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.bufs"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Buffer Size</Title>
			</Header>
			<FuncDesc>The size, in Mb, of the memory that is used to buffer transactions. When this limit is exceeded, the buffering process will swap data to file.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.rdel"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Read Delay</Title>
			</Header>
			<FuncDesc>The delay, in seconds, between logging a <Link href="/baanerp/tt/glossary/glossary#100235" role="glossary">transaction</Link> in the audit files and the reading of the transaction by the <Link href="/baanerp/da/glossary/glossary#59" role="glossary">synchronization server</Link>. A delete delay is only necessary for databases that use 'dirty reads':</FuncDesc>
			<SimpleSection><Paragraph class="Default">For more information refer to <Link href="/baanerp/da/nch/danch2510m000#danch210.rdel" role="formfield">Read Delay</Link>.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="trace.yesno"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Tracing</Title>
			</Header>
			<FuncDesc>This check box indicates whether tracing was done. Detailed technical information is stored in <GUIRef href="/baanerp/da/nch/danch2520m000#danch220.tfil" role="manual">Trace File</GUIRef> in the synchronization object's Log Folder.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="danch220.tlev"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Trace Level</Title>
			</Header>
			<FuncDesc>The level of detail for the trace:</FuncDesc>
			<SimpleSection><List><ListItem>Low: only events are logged to show the server activity and the processing steps being executed. For each transaction being processed only the transaction ID and commit time is written.</ListItem>
					<ListItem>Medium: in addition to the events, some transaction data are logged. For the transaction data, only the status at the beginning of the process (just after reading the transaction from the audit trail), the status at the end of the process (just before sending the result to the store), and the status in case of errors are included.</ListItem>
					<ListItem>High: events and transaction data details are logged. The status of the transaction data after each process step is logged. This can result in a very large trace file.</ListItem>
				</List>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="danch220.tfil"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Trace File</Title>
			</Header>
			<FuncDesc>The path of the trace file. This file can be used for trouble-shooting and gives more detailed information than the server log file. It shows the server activity, for example, what transactions were read and how they are processed. It does not only log exceptions, but also transactions that were processed successfully.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The amount of data that is stored depends on the <GUIRef href="/baanerp/da/nch/danch2520m000#danch220.tlev" role="manual">Trace Level</GUIRef>.</Paragraph>
			</SimpleSection>
		</FieldHelp>
	</Fields>
</Session>
