The job identification code.
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. To use an identical job in another company, you must define the basic job data again for that company. Job Types In LN, you can create these two job types:
Storage of job data Typically, each company stores its own basic job data. Therefore, a job runs for a particular company. 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 UI to change the current company number. 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 these job tables as logical tables to one physical table:
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 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:
Note To change the job status to In Queue, click Queue Job on the appropriate menu in the Job Data (ttaad5500m000) session. For more information about job statuses, see Job Status. Advanced scheduling options If the scheduling options using a calendar or running the job at fixed intervals is not sufficient, the job scheduling lines can be used. Alerts On the Alerts tab you can specify per check box when to publish a Job alert.
Job The job identification code. Status The Job Status. Linked to Job Group If this check box is selected, the job is linked to a job group, see the Job Groups (ttaad5140m000) session. User The LN user ID of the person who created the job. Creation Date The time at which the job was created. Use External Schedule 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 Schedule 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 continued 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. Leave this field blank or 0 (zero) when using Job Scheduling Lines only. 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. Leave this field blank or 0 (zero) when using Job Scheduling Lines only. 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. Time Zone Select the time zone you require. 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 and time on which the job was last executed. Last Date Session Added The last date and time a session was added to the job. When a session is added, the existing history records become useless for the calculation of the expected duration of the job. After the job is executed again, the expected duration is recalculated. Only history records that include the new session are used in the calculation. Older records are ignored. Expected Duration [sec] The expected duration, in seconds, of the job. For repeating jobs, this value is calculated based on the job history. You can overwrite this value, but after running the job, the value is recalculated based on the new job history. During a Tools update in a tenant environment, all tenant processes, including scheduled jobs, must stop. If the landlord has scheduled an upgrade, LN uses the expected duration of the scheduled jobs to determine whether to start these jobs. For example: The landlord has scheduled and upgrade at 2.00 AM. A job is scheduled to run at 1.00 AM. The expected duration of the job is 7200 seconds, that is, 2 hours. The job is postponed. After a restart of the LN server, postponed jobs are started automatically.
| |||