2. Generation

This is the second stage. The specifications made in the object are now generated, and Sync objects or the maximum number of parallel running tasks are checked. Scripts are also processed now.

The structure and start time of the generation stage depend on the option that has been activated when defining the object:

Depending on this, the script is processed either directly aftertask activation or just before its processing stage starts:

Although there is no remarkable difference between the above generation types when a task activation stage is immediately followed by its start stage, a gap can exist between them. This is because the start time of the activated object is usually subject to superordinate objects, such as a workflow or a group.

Example:

A workflow contains several tasks. Activating this workflow means that its tasks are also activated. If Generate Job at Runtime is NOT activated, object scripts are processed now. The individual workflow tasks start according to their position within the workflow order.

Advantage of object generation in the activation stage:

Advantage of object generation directly before the processing stage:

 

 

Status: Waiting for Predecessor

Status: Waiting for Start Time

Status: Registered

Generation

Steps

Description

Script
(Generate Job at Runtime is NOT activated)

The script is processed directly after the activation stage.

 

Manual release

In manual executions you can select the Wait for manual release option. Tasks must be released in the Tasks Window before their start can be initiated.

See also Executing Options.

 

Sync verification

The system checks if the specified Sync objects are available.

 

Parallel running tasks

On the Attributes page you specify the maximum number of object executions that can run simultaneously.

 

Script
(Generate Job at Runtime is activated)

The script is processed just before the processing stage begins.

Script Processing in Detail

Not every script type is processed in the generation stage. Event Processes (Event objects) and Child Post Processes are executed in the processing state. Post Processes are processed in the completion stage.

Steps

Description

Agent group resolution

The relevant agent is selected for tasks that are processed in Agent Groups (HOSTG). Subsequent changes are possible in the Process page.

 

Object variables

The object variables of the task and its superordinate task are provided.

 

Pre-Process

For Jobs: The contents of the Pre-Process page are processed.

 

Attribute dialog

This dialog is displayed only if the task is activated manually and NOT generated at runtime.

For details see Modifying Object Attributes for a Particular Execution

 

Header

For Jobs: The header include and related user includes are processed.

For detail see Include Object (JOBI).

 

Process

The contents of the Process page are processed.

 

Trailer

For Jobs: The trailer include and related user includes are processed.

 

JCL generation

For Jobs: JCL generation is possible after AE Script processing. JCL modifications are possible before the job starts on the destination computer.

See also: