Inside Automation Engine > Job > Stages of Job Processing

Stages of Job Processing

The following illustration shows the different stages of jobAn Automation Engine object type for a process that runs on a target system. processing in detail.


Activation

 

 

 

 

 

RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component . is created

Generation

       
Job appears in the Activity Window AE Script is executed in the Pre-Process and Process tab

Transfer

     
  Final JCL is generated JCL is transferred to the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host

Execution

   
      Job is executed

Transfer

 
      Runtime commences Report is transferred to the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes.

Post Process

 

 

        Post Process is executed (if available)

Some checks are made before the job is executed in the order shown below :

  1. Was the job canceled in the meantime?
  2. Should the job be started manually?
  3. Does job execution depend on Sync objects?
  4. Was the maximum number of jobs reached that may run parallel on the agent?
  5. Is the agent active?

Finding Jobs After Agent Downtime

When an agent ends and is then restarted, it obtains the whole restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. information from the Server - i.e. about all jobs that were being executed at the time the agent ended. Of course, jobs might have ended during the agent's downtime. The agent starts searching for jobs in the process lists of the particular operating system. If it does not find a job anymore, it searches for its reportA report provides more detailed information about a task's execution or a component. file in the temporary directory and retrieves the point in time when the particular job has ended and its return codeThe value that represents the result of tasks and script functions.. If the agent is not able to find any information, the job statusThis represents the condition of a task (such as active, blocked, generating). changes to "V - status vanished".

 

See also:

Sample Collection - Setting End Status depending on Report Content

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH