<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ec/onlinemanual/000066" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Terminating communication</Title>
		<Keyword><Level1>Terminating communication</Level1>
		</Keyword>
		<Keyword><Level1>Communication</Level1>
			<Level2>terminating</Level2>
		</Keyword>
		<Keyword><Level1>Network communication</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>You can run the <GUIRef href="/baanerp/ec/edi/ecedi0249m000" role="session">Terminate Front-End EDI Processor (ecedi0249m000)</GUIRef> session to terminate communication to your translation/communication software. This session creates a file called Command.end in the command directory. The existence of this file can be used to terminate the translation/communication software.</Paragraph>
		<Paragraph>To use this semaphore mechanism provided by ERP EDI, your translation/communication software must create, delete, and check these semaphore files as indicated.</Paragraph>
		<Paragraph>You will want to avoid the unnecessary allocation of CPU resources during the create, delete, and check process that occurs before semaphores have been removed. To do so, activate (at sequenced and staggered intervals) the interchange controller within ERP EDI and the scheduling mechanism within the translation/communication software.</Paragraph>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/ec/onlinemanual/000028" role="manual">Communication</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
