<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/aad/ttaad5100s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Job Data (ttaad5100s000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to define the basic data for a <Link href="/baanerp/tt/glossary/glossary#000025" role="glossary">job</Link>. The basic job data is only valid for the current company. If you want to use an identical job in another company, you must define the basic job data again for that company.</Paragraph>
		</AimSection>
		<GeneralSection><SectionTitle>Job Types</SectionTitle>
			<List><ListIntro>In ERP LN, you can create the following two job types:</ListIntro>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100036" role="glossary" Update="No">Periodical</Link> jobs that are carried out multiple times. For a periodical job, you must specify a time interval or a calendar. If desired, you can restart the job automatically.</ListItem>
				<ListItem>Non-periodical jobs that are carried out only once. When the job is carried out, the job data is removed automatically.</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>Storage of job data</SectionTitle>
			<Paragraph class="Default">Typically, each company stores its own basic job data. As a result, a job runs for a particular company. Therefore, before you define the job’s basic data, you must first check whether the current company is the appropriate one to define the job data for. Otherwise, use the <GUIRef href="" role="manual">Change Company</GUIRef> command in the WorkTop/WebTop to change the current company number.</Paragraph>
			<Paragraph class="Default">However, in a job, you can also run sessions in more than one company. You can only run sessions in multiple companies if the job data tables of the involved companies are physically mapped on one main company.</Paragraph>
			<List><ListIntro>You can use the <GUIRef href="/baanerp/tt/aad/ttaad4120m000" role="session">Logical Tables (ttaad4120m000)</GUIRef> session to link the following job tables as logical tables to one physical table:</ListIntro>
				<ListItem>Job Data (ttaad500)</ListItem>
				<ListItem>Sessions by Job (ttaad501)</ListItem>
				<ListItem>Job Input Variables (ttaad503)</ListItem>
				<ListItem>Job Daemon Indicator (ttaad505)</ListItem>
				<ListItem>Calendars (ttaad506)</ListItem>
				<ListItem>Dates by Calendar (ttaad507)</ListItem>
				<ListItem>Job History (ttaad510)</ListItem>
				<ListItem>Job Session History (ttaad511)</ListItem>
				<ListItem>Job Session History (ttaad512)</ListItem>
			</List>
			<Paragraph class="Default">Before you add a session to a job, you must check the company number. If a job applies to more than one company, you must switch to the other companies with the <GUIRef href="" role="manual">Change Company</GUIRef> command in the WorkTop/WebTop to define the job for each company. You can then define the job data for the other companies.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>To start a job</SectionTitle>
			<List><ListIntro>How you start the job depends on the job’s status:</ListIntro>
				<ListItem>If the job’s status is Free, you can start the job in the following ways: <List><ListItem>Use the <GUIRef href="/baanerp/tt/aad/ttaad5203m000" role="session">Activate Job (ttaad5203m000)</GUIRef> session. You can start this session from the <GUIRef href="" role="menu">Specific</GUIRef> menu in the <GUIRef href="/baanerp/tt/aad/ttaad5500m000" role="session">Job Data (ttaad5500m000)</GUIRef> session.</ListItem>
						<ListItem>Use the rc.startjob shell command (UNIX platform)</ListItem>
						<ListItem>Use the startjob.bat batch file (Windows platform)</ListItem>
					</List>
				</ListItem>
				<ListItem>If you want the ERP LN Job Daemon to start the job, you must change the job’s status to In Queue. Before you set the status to In Queue, make sure that all sessions have been added to the job (at least one session must be in the job). If the Job Daemon is already running, the job will be active as soon as the job status changes to In Queue and the record is saved.</ListItem>
			</List>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">To change the job status to In Queue, click <GUIRef href="/baanerp/tt/aad/ttaad5500m000#exec.user.2" role="command">Queue Job</GUIRef> on the <GUIRef href="" role="menu">Specific</GUIRef> menu in the <GUIRef href="/baanerp/tt/aad/ttaad5500m000" role="session">Job Data (ttaad5500m000)</GUIRef> session.</Paragraph>
			</Note>
			<Paragraph class="Default">For more information about job statuses, refer to <Link href="/baanerp/tt/domains/aad.jsta" role="domain">Possible values</Link>.</Paragraph>
		</GeneralSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/basictasks/000038" role="manual">To define a job</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/100010" role="manual">To define a calendar</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/basictasks/000041" role="manual">To run a job</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/basictasks/000042" role="manual">To cancel a job</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="ttaad500.cjob"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Job</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/glossary/glossary#000025" role="glossary">job</Link> identification code.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.user"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">User</Title>
			</Header>
			<FuncDesc>The ERP LN user ID of the person who created the job.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.indt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Creation Date</Title>
			</Header>
			<FuncDesc>The time at which the job was created.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.iedt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Use External Sched</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, an external job scheduler, such as Maestro from UNISON, or an external program, for example, a UNIX crontab starts the job. Therefore, in that case, the calendar/time schedule in the job data is ignored.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.perd"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Periodical</Title>
			</Header>
			<FuncDesc>Select this check box if the <Link href="/baanerp/tt/glossary/glossary#000025" role="glossary">job</Link> must be started or restarted periodically at a predefined date and time. You can use the <GUIRef href="/baanerp/tt/aad/ttaad5106m000" role="session">Calendars (ttaad5106m000)</GUIRef> session and the <GUIRef href="/baanerp/tt/aad/ttaad5107m000" role="session">Dates by Calendar (ttaad5107m000)</GUIRef> session to create an irregular job activation schedule. To create a regular schedule, you can use the <GUIRef href="/baanerp/tt/aad/ttaad5100s000#ttaad500.peri" role="manual">Period</GUIRef> fields. For example, you can specify that the job must be started twice a month.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the <GUIRef href="/baanerp/tt/aad/ttaad5100s000#ttaad500.iedt" role="manual">Use External Sched</GUIRef> check box is selected, the <GUIRef href="/baanerp/tt/aad/ttaad5100s000#ttaad500.perd" role="manual">Periodical</GUIRef> check box is only used as a reminder to indicate that an external program periodically starts the job.</Paragraph>
				<Paragraph class="Default"></Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttaad500.rept"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Suspend Job Until Next Execution</Title>
			</Header>
			<FuncDesc>Indicates whether the <Link href="/baanerp/tt/glossary/glossary#100036" role="glossary">periodical job</Link> must be executed automatically after last execution. After execution of a periodical job, the next execution date is automatically updated according to the given period and/or calendar date.</FuncDesc>
			<SimpleSection><Paragraph class="Default">
                                    If this check box is selected,, the job is suspended until the next execution date. For jobs started by the <GUIRef href="/baanerp/tt/aad/ttaad5203m000" role="session">Activate Job (ttaad5203m000)</GUIRef> session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat, the job’s status is set to Waiting. The job is automatically restarted at every next execution date that is defined in the calendar or by the interval.</Paragraph>
				<Paragraph class="Default">
                                    If this check box is cleared, the job runs once and is then stopped. For jobs started by the <GUIRef href="/baanerp/tt/aad/ttaad5203m000" role="session">Activate Job (ttaad5203m000)</GUIRef> session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat, the job’s status is set to Free. To restart the job, you must manually start the <GUIRef href="/baanerp/tt/aad/ttaad5203m000" role="session">Activate Job (ttaad5203m000)</GUIRef> session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttaad500.calc"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Calendar</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/glossary/glossary#100041" role="glossary">job calendar</Link>.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If you do not use a calendar you can specify the period interval between two executions using the <GUIRef href="/baanerp/tt/aad/ttaad5100s000#ttaad500.peri" role="manual">Period</GUIRef> fields.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ttaad500.peri"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Period</Title>
			</Header>
			<FuncDesc>The number of period units.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.peru"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Period</Title>
			</Header>
			<FuncDesc>The period unit, e.g. Days or Weeks.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.fidt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">End of Period</Title>
			</Header>
			<FuncDesc>If the job is only valid during a specific period, you can enter the last date the job can be started.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can use this option, for example, if a job that is started twice a month is only valid for six months.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttaad500.edte"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Next Execution Date</Title>
			</Header>
			<FuncDesc>The date of the next execution of the <Link href="/baanerp/tt/glossary/glossary#000025" role="glossary">job</Link>. If the job is <Link href="/baanerp/tt/glossary/glossary#100036" role="glossary">periodical</Link>, this field shows the next date of the calendar or the date corresponding to the given period, after executing the job.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.maxd"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Maximum Duration</Title>
			</Header>
			<FuncDesc>If a job exceeds its maximum duration, it is stopped. The running session is completed, but the next session will not be executed. The history record explains the cause of the termination.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If you enter 0 [zero] in this field, the job duration is unlimited. Values under 60 represent minutes. To specify a duration longer than 59 minutes, you must enter the hours followed by the minutes, without a separator. For example, enter 30 to specify 30 minutes. Enter 100 to specify one hour. Enter 130 to specify 1 hour and 30 minutes.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttaad500.ldat"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Last Execution Date</Title>
			</Header>
			<FuncDesc>The date on which the job was last executed.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ttaad500.jsta"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Status</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/tt/domains/aad.jsta" role="domain">Possible values</Link>.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
