3.3 Task Maintenance Detail

This topic provides information on task maintenance detail.

User has to maintain TASKID parameter to specify the Report Parameters. UTDTASK is the screen to maintain Report Parameters.

Figure 3-2 Task Maintenance Detail

Description of "Figure 3-2 Task Maintenance Detail"

A Java job can be stateful or stateless.

• Stateful Job

  If the job is configured to be STATEFUL, then missed instances will be queued up so that scheduler would start executing once the long running job ends. It means, there will be no parallel execution of the java class.

  To make a class as Stateful, please add two annotations to the job class.

  • @PersistJobDataAfterExecution
  • @DisallowConcurrentExecution
• Stateless Job

  If the job is configured as STATELESS, threads can be run in parallel and can execute the same java class.

  If the job is configured as stateless, the value of field Max Number Instances will denote the number of threads that can be executed in parallel. If the job is configured as stateful, then the above value will denote the number of missed instances that will be queued up so that Quartz Scheduler would start executing them once a long running job ends. This field specifies the number of such job instances that needs to be queued up.

  The class defined in the class field has to be provided a fully qualified name.

  Note:

  Job params can be added to a particular java job in Task Maintenance Detail screen.