Job Attributes

Job attributes are used to control when and how the jobs get scheduled in the HVR run-time system. Job attributes can be configured using CLI command hvrjobconfig or UI options Job System Attributes or Job Attributes on the Jobs page.

Attribute	Arg1	Arg2	Description
quota_run	n		The maximum number of jobs which can be in RUNNING or HANGING state in a job group. So if attribute quota_run 2 is added to job groups CHN1, CHN2 and quota_run 3 is added to job group SYSTEM, then only two jobs can run for each channel (CHN1 and CHN2) and only three jobs can run in the whole system. The quota_run attribute can be used by for the sliced refresh to ensure that only x amount of refresh jobs are started at once. For example, if there are 100 tables to be refreshed, 100 refresh jobs (1 job per table) can be created. In this case, you can use quota_run to avoid running 100 jobs at the same time.
quota_speed	q	secs	Limit the speed with which the Scheduler starts jobs to no more than q job executions inside secs seconds. For example, quota_speed 20 1 means that if there are lots of jobs ready to be started, then the Scheduler will only start 20 jobs per second.
retry_delay	isecs	fsecs	Initially retry job after isecs and double this delay for each unsuccessful retry until the fsecs value is reached. The default value for isecs is 60 seconds and for fsecs is 3600 seconds.
retry_max	n		Allow n retries for an unsuccessful job. If n is zero, no retry is allowed. Jobs unaffected by this attribute are not retried: on error, they become FAILED directly. The retry_max attribute is used to prevent a job from being restarted if it fails. For example, it can be used when refresh is running and failing, and you do not want the refresh to retry unless you understand why the refresh failed.
timeo_hard	secs		Terminates the job in RUNNING or HANGING state after it has run secs seconds. If secs is zero then no time-out will occur.
timeo_soft	secs		After a job has been in the RUNNING state for secs seconds, write a time-out message and change its job state to HANGING. If secs is zero then no time-out will occur.
trig_at	time		Trigger job at specific (time) moment. Valid formats for time are: YYYY-MM-DD [HH:MM:SS] (in local time) YYYY-MM-DDTHH:MM:SS+TZD YYYY-MM-DDTHH:MM:SSZ today now[±SECS] an integer (seconds since 1970-01-01 00:00:00 UTC)
trig_crono	crono		Trigger job at crono moment. It can also be set by option CaptureStartTimes of action Scheduling. After applying attribute trig_crono, the job needs to be in a PENDING state for the Scheduler to trigger the job. The trig_crono attribute can be used to set when capture, integrate, refresh or compare jobs should run, rather than continuously or immediately. For the format of crono, see section Start Times on page Scheduling.
trig_delay	secs		Trigger cyclic job secs seconds after it last finished running (column job_last_run_end of HVR_JOB). If a cyclic job is not affected by any trig_delay attribute, it will remain PENDING indefinitely.