Executing Objects Once

Use the Execute Once option in the following situations:

  • You want to test the results of the execution and, if necessary, change the object properties, test its execution again, and so forth. These changes affect only this execution of the object and not its definition.

  • Specify a later point in time for its execution

  • Check the execution of an object when switching Agents at runtime

    When executing an object, you may want to switch the Agent at runtime. Execute it once and activate the test options that provide information about the results. If something goes wrong, you can react immediately.

  • Avoid conflicts during maintenance activities

    Some maintenance activities such as database backups or reorganizations are performed during non-office hours. For these purposes, select this execution option and set a time outside the working hours at your company.

In Client 0, this option lets system administrators check when tasks are scheduled and adapt maintenance activities accordingly.

To Execute Objects Once

  1. In the Process Assembly perspective, right-click the object and select Execution Options > Execute Once.
  2. On the Execute Once dialog define the following:

    Parameters section

    • Execute: Immediately

      The task is executed using the activation time for any calendar calculation.

    • Execute: Wait for manual release (immediate executions only)

    • At Date / Time

      Lets you select the date and time on which this object is executed. At the selected time the task is visible on the Tasks list of the Process Monitoring perspective. Its status is Waiting for start time. You can edit it as long as it is in this status.

    • Use logical date

      In some situations, you may need to start a task at a specific time that should be executed at a time in the future.

      Select this option and pick the date/time you need as logical date. The task is activated immediately, that is, its activation time corresponds to the current OS time. However, for Automation Engine internal purposes, the logical date is used.


      On June 20 at 08:24 AM you select this option and set June 21 at 08:00 as logical time. The task is executed on June 21. The activation report displays both the start and activation times, indicating its logical date:

      Report dialog diaplying the activation details of a task explicitly indicating the logical date.

    • Time Zone

      Relevant if your company has teams across different time zones and common processes that affect them. If your company has defined a Time Zone object that this execution should consider, select it here.

    • Alias

      The alias applies to this particular execution of the object. Use it to be able to identify it easily when testing execution options. The alias replaces the object name everywhere, also in the Name column in all Executions lists, in the Tasks list in the Process Monitoring perspective and in the search result list in the advanced search.

      Length: 200 characters

      Allowed characters: A–Z, 0–9 , $ @ _ - . #

      Restrictions: Variables are not allowed

    • Queue

      You can assign a particular Queue for this execution, which can be different to the one in the object definition. If you leave this field empty, the Queue assigned to the object is used.

    Test Options section

    • Activate attributes dialog

      This option lets you change specific settings for a particular execution without modifying its general object definition. If you activate this checkbox, a dialog pops up before the task is executed. It displays the attributes that can be changed for this particular execution. These values apply only to this execution.

    • Display in activation report

      Select this option to include the script statements and the content of all involved Include objects in the activation report, regardless of the Generate at: Activation/Runtime setting. In the case of Jobs, the header and trailer are also included in the report.

      • Generated JCL, Original script

        The JCL and the script are displayed in the report.

        Use these options in combination with the Wait for manual release option. If you are happy with the results, you can release the task for execution.

      • Modifications of variables, Modifications of attributes

        When testing your object definitions, you may want to modify your variables and attributes and check the results before actually executing them. Activate these options if you want those changes to be displayed in the activation report.

  3. Click Execute.

    • If the Activate attributes dialog checkbox is activated, a dialog pops up where you can enter specific attribute settings for this execution.

      If any of the other test options is activated, a message opens prompting you to confirm that you want to execute the task after the script has been generated.

    • If PromptSets or READs have been defined for this object, the task is not be executed until you enter the required data. A message prompts you to enter it.

Executing Once with the Manual Release Option

Use this option with Job objects to test them and modify the generated JCL before executing them. The task is activated, the script is generated and, if applicable, transfers are carried out. The task, however, is not executed. It is available in the Process Monitoring perspective displaying the Waiting for manual release status.

To Release the Task Manually

Workflows in the Process Assembly perspective:

  1. Right-click the object and select Monitoring > Last Monitor.
  2. The Process Monitoring perspective is displayed showing the task monitor.
  3. Expand the Workflow button and select Release manually. Before releasing the task, you can modify its parameters. These changes apply to the current execution only.

All executable objects:

  1. Open the Process Monitoring perspective and search for the task. You can filter the list using the Waiting for manual release status criterion.
  2. Right-click it and select Release manually.

See also: