| Job Data (ttaad5100s000) |  |
| Use this session to define the basic data for a job. 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. Job Types In ERP LN, you can create the following two job types: Periodical 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. Non-periodical jobs that are carried out only once. When the job is carried out, the job data is removed automatically. Storage of job data 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 Change Company command in the WorkTop/ Web UI to change the current company number. 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. You can use the Logical Tables (ttaad4120m000) session to link the following job tables as logical tables to one physical table: Job Data (ttaad500) Sessions by Job (ttaad501) Job Input Variables (ttaad503) Job Daemon Indicator (ttaad505) Calendars (ttaad506) Dates by Calendar (ttaad507) Job History (ttaad510) Job Session History (ttaad511) Job Session History (ttaad512) 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 Change Company command in the WorkTop/ Web UI to define the job for each company. You can then define the job data for the other companies. To start a job How you start the job depends on the job’s status: If the job’s status is Free, you can start the job in the following ways: Use the Activate Job (ttaad5203m000) session. You can start this session from the Specific menu in the Job Data (ttaad5500m000) session. Use the rc.startjob shell command (UNIX platform) Use the startjob.bat batch file (Windows platform) 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. Note To change the job status to In Queue, click Queue Job on the Specific menu in the Job Data (ttaad5500m000) session. For more information about job statuses, refer to Possible values. Related topics To define a job To define a calendar To run a job To cancel a job
Fields | Description
Job | The job identification code.
User | The ERP LN user ID of the person who created the job.
Creation Date | The time at which the job was created.
Use External Sched | 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.
Periodical | Select this check box if the job must be started or restarted periodically at a predefined date and time. You can use the Calendars (ttaad5106m000) session and the Dates by Calendar (ttaad5107m000) session to create an irregular job activation schedule. To create a regular schedule, you can use the Period fields. For example, you can specify that the job must be started twice a month. If the Use External Sched check box is selected, the Periodical check box is only used as a reminder to indicate that an external program periodically starts the job.
Suspend Job Until Next Execution | Indicates whether the periodical job 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. If this check box is selected,, the job is suspended until the next execution date. For jobs started by the Activate Job (ttaad5203m000) 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. If this check box is cleared, the job runs once and is then stopped. For jobs started by the Activate Job (ttaad5203m000) 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 Activate Job (ttaad5203m000) session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat.
Calendar | The job calendar. Note If you do not use a calendar you can specify the period interval between two executions using the Period fields.
Period | The number of period units.
Period | The period unit, e.g. Days or Weeks.
End of Period | If the job is only valid during a specific period, you can enter the last date the job can be started. You can use this option, for example, if a job that is started twice a month is only valid for six months.
Next Execution Date | The date of the next execution of the job. If the job is periodical, this field shows the next date of the calendar or the date corresponding to the given period, after executing the job.
Maximum Duration | 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. 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.
Last Execution Date | The date on which the job was last executed.
Status | The Possible values.