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 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 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 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 appropriate 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 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 appropriate menu in the Job Data (ttaad5500m000) session. For more information about job statuses, see the online help of the Status field.
  • The user who created the job is the owner of the job. Other users, except super users, cannot modify the job.

Field Information

Job

The job identification code.

Status

The job status.

Allowed values

Free

The job’s basic data is defined and the job is ready to be started.

You can start the job in the following ways:

  • Use the Activate Job (ttaad5203m000) session.
  • Use the rc.startjob shell command (UNIX platform)
  • Use the startjob.bat batch file (Windows platform)
Running

The job is started and is running.

Waiting

The job is started and is waiting to be carried out at the next execution date and time.

Note: A job with the Waiting status will not be started by the job daemon: the Job Daemon only starts jobs with the In queue status.
In queue

The job is queued and will be started automatically when the job daemon runs.

To queue a job, use the Queue Job command in the Job Data (ttaad5500m000) session.

Blocked

The job is blocked and cannot be started.

Before you can restart the job, you must release the job, to change the job's status to Free. To release a job, use the Release Job command in the Job Data (ttaad5500m000) session.

Canceled

The job has been stopped with the Cancel Jobs (ttaad5204m000) session. A job is also canceled when the Maximum Duration is exceeded.

Before you can restart the job, you must release the job, to change the job's status to Free. To release a job, use the Release Job command in the Job Data (ttaad5500m000) session.

Runtime error

This status signals an error during the execution of the job. You can use the Print Job History (ttaad5411m000) session to print the corresponding error messages.

Before you can restart the job, you must release the job, to change the job's status to Free. To release a job, use the Release Job command in the Job Data (ttaad5500m000) session.

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.

Note: The user who created the job is also the owner of the job. Only this user, and super users, can modify the job.
Creation Date

The time at which the job was created.

Show Dates and Times in Job Time Zone

If the Time Zone field is set and the Show Dates and Times in Job Time Zone check box is selected or cleared, adjustments to the date and times are shown in the display of this session.

If this check box is selected, the Time Zone field in this session is used for adjusting how the date and time in the Planned Execution Date field and other Execution details fields are shown in this session.

If this check box is cleared, the time zone is used of the user who is running the job.

In a Cloud environment this means this user is the Job Owner.

In an On-premises environment it depends on the resource setting if the BSE Services framework user is used.

The resource setting is: exec_job_as_job_owner:0 or exec_job_as_job_owner:1

exec_job_as_job_owner:0 means that the job is run with the current user, the BSE Service Framework user.

exec_job_as_job_owner:1 means that the job is run with the job user.

You can specify this setting in: $BSE/lib/defaults/all

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 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.

Non-periodical jobs that are carried out only once. When the job is carried out, the job data is removed automatically.

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.

This field becomes functional when the Show Dates and Times in Job Time Zone check box is selected. It adjusts the display of the date and time to show in the Time Zone field in this session. It affects the display of the time and dates in the Creation Date, Planned Execution Date, Last Execution Date, Last Date Session Added, and also the dates on the Job Sessions History tab. If the Time Zone field is set and the Show Dates and Times in Job Time Zone check box is selected or cleared, adjustments to the date and times are shown in the display of this session. The Planned Execution Date time does not change unless the time is changed and then saved. Selecting only the Show Dates and Times in Job Time Zone check box does not have impact on when the job runs. Changing the Time Zone field on its own does not have impact on when the job runs either. By default, the time zone defined in the User Data Template in the User Data (ttaad2500m000) session is the Time Zone that is used in the Job Data (ttaad5100s000) session.

Planned Execution Date

The date of the planned 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 time in which the job can be finished with a 99% certainty, expressed in seconds.

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.

For repeating jobs, the calculation of the expected duration is based on the number of records in the job history, starting from the last time a session was added to the job.

This changes the time needed, so previous records are not valid. You can overwrite the value in this field, but after running the job, the value is recalculated based on the new job history.

If no history has been built yet, the value is set to a long time based on the Default Job Safety Time [min] or Maximum Job Duration Time [sec] parameters in the Tools Parameters (ttaad0100m000) session.

If the job history contains at least 30 records, the calculation of the statistic normal distribution is used.

If the job history contains less than 30 records, the expected duration is set to 2 * the longest run. This multiplier cannot be changed.

The reason is that the expected duration is set to a relatively long time to prevent that a job is still running when the planned downtime starts. Jobs that are still running when the Tools update starts are terminated. Planned downtimes, for example, for Tools updates, are specified in the Planned Downtime (ttaad5530m000) session.

Related topics