Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

This field holds the external code used to identify a job.

Description of job

This field describes the pattern of recurrence for this job (e.g. daily, weekly, monthly). See embedded codetable for details.

Earliest time of the day when this job can be executed.

Latest time of the day when this job can be executed. Where jobs are executed more than once per day (i.e. hourly or every x minutes), this time signals the end of processing for the day: the next execution is scheduled for the following day.

For 'weekly' jobs only, the field identifies the day of the week when the job is to be executed.

For jobs executed 'monthly' or in longer periods, the field defines the day of the month when the job is to be executed.

Date and time when the job was last started.

Date and time when the job was last finished.

Date and time when job next scheduled.

Specifies whether a TradeDesign transaction/script/executable is to be executed by job.

Name of transaction/script/executable to be executed. The name of the transaction should not contain a path or extension.

Arguments passed to the transaction/script for execution.

Session in which this job was last executed (only for transaction type jobs).

Status of last job. See embedded codetable for details.

Frequency of execution (in minutes). Used only for jobs that can repeat 'every x minutes'.

Optional field. If not zero the field defines the maximum gap between scheduled and actual execution. After this time, the job is moved to its next scheduled run.

Defines an optional maximum runtime for a job. If this time is set and exceeded the JOBTSK manager marks the job as faulty and continues with the next job. A global maximum runtime can be defined in JOBTSK settings which will take effect if no job limit has been defined.

If set to a non blank value the job will be executed using this user id. A sample usage is to get a fitting user id for Remote Client Printing.

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.

Calendar to be used for calculation of next job execution.

The time zone may be set in tdpara.ini “system”, under TZUser.

This field holds the external key of the owning entity to identify the logical owner of this entry.

This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.

When the checkbox is set, a multiple execution of this job will take place for all entities visible to the user.

When the ETYFLG is set this field controls the entity the job is currently executing for. When this field is empty, the job should process the full list of entities. During the execution of a job the entity the currently running execution is using is updated in this field. When a job is restarted after an interruption the first entity the job is executed for is taken from this field.