Let’s look at the properties of the job from the code

In the module code

  • The vertical XML tags are job or group node types

  • Horizontal XML tags are job attributes

Job attribute classification

Currently, there are 23 job attributes and they are divided into four categories: What, Where, How, and Other

What

It is also the basic information of a job, including various information when running a job:

(1) The most core information of a job: the complete information required for running a job: Progname, para, exppara

  • Progname: indicates the program name of the job

  • Para: entry parameter required for running a job

  • Exppara: environment information required to run a job

(2) name(job name), and (jobdesc) description. These two properties are not information needed to run the job, but information that TASKCTL itself can use to manage the job.

Where

The Where class, which describes the problem of Where jobs are run.

In TASKCTL, the scheduling logic is handled primarily by the scheduling server, which dispatches jobs that meet the running conditions to specific machines. The specific machine to be distributed to (Where) is mainly determined by the two attributes of the job, agentid and HostUser.

  • Agentid: proxy mode

  • Hostuser: no proxy mode

  • If the two properties are not set, the job is in the scheduling service installation user environment.

How

The How class mainly describes the problem of scheduling and running jobs under what conditions. Its attributes mainly include:

  • Relationship class: lean \ ostr

  • Execution plan class: Period \ dateType

  • Error tolerance policy class: maxnum \ ignoreeer \ errdelay

  • Return value Policy class: SuccessV \ ErrorV \ Failed \ WarnningV

  • More: Condition cycle timingPlan virresource etc

Other

Monititle (Monitor TAB) : Overview has no control and is designed for a more user-friendly presentation of TASKCTL.

Not only do you need to understand the meaning and usage of each attribute, but you also need to understand the module code and the basic characteristics of the job attribute in TASKCTL.

1. Default, inherit, overload of attributes

Default, inheritance, and overloading of attributes are important paranguage features of TASKCTL code that make your design cleaner, more flexible, more manageable, and achieve special controls.

2. Variable and functional characteristics of attributes

The quantization and functionalization of attributes make your TASKCTL code more quasi-linguistic, further making your design more flexible.

3. Versatility and difference

23 attributes of the job, for each job type, usage has both universality and difference, specific can be experienced in the application of each job type; Also, the 23 attributes are not valid for every job type. Which jobs have which attributes can be clearly designed by Designer. The system will automatically filter the valid attributes of each job when the attribute box is displayed.

Here is a list of all job attributes: