Executing Objects Once

With the Execute Once option you can start processing the task immediately or at a predetermined point in time. It helps you test and adjust the object settings and adapt its execution time to meet your needs.

What you can find here:

Use Scenarios

There are many scenarios in which you can execute an object once and take advantage of the ad-hoc editing possibilities. Here we mention but a few.

The Execute Once command is also available in client 0; this allows administrators to check when tasks are scheduled.

ClosedTesting and Editing Parameters before Executing

This option is particularly useful if you are designing objects because it allows you to specify the execution parameters and test the results immediately; the activation report provides the necessary information for you to decide if the outcome complies with your expectations or not. If not, you can modify the settings, execute and test again.

  1. Select this option and, on the Execute Once dialog, activate the test options you need.

  2. Click Execute.

  3. Switch to the Process Monitoring perspective, where the task is now available on the Tasks list.

    There are two possible scenarios here:

    • If PromtSets or READs have been defined for this object, the task will not be executed until you enter the required data. The application will display a message prompting you to enter it.
    • No PromptSets or READs have been defined and, therefore, the object is executed.

    After the object has been executed, you can right-click the task and press the Details button. The details pane opens on the right hand side displaying information on the execution.

  4. Right-click the task and select Open Report.

    Select Activation (ACT) from the dropdown list at the top of the dialog to open the page where the execution details are recorded:

ClosedChecking Execution when Switching Agents at Runtime

When executing certain objects, you may want to switch at runtime the agent that will process it. In this case, you execute it once and activate the test options that will provide information on the results. If something went wrong, you can recognize it and react immediately.

ClosedAvoiding Conflicts during Maintenance Activities

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

To Execute Objects Once

  1. In the Process Assembly perspective do one of the following:

    • Right-click the task and select Execute Once.
    • Select the task, click the arrow on the Execute toolbar button and select Execute Once.

      Execute manually

  2. The Execute Once dialog is displayed, where you can define the execution settings:

    Setting

    Description

    Execute: Immediately

    Select this option if you want the task to be executed right away using the activation time for any calendar considerations.

    Execute: Wait for manual release

    This option is available for immediate executions only.

    Before being actually executed, tasks go through the following phases: Activation, Generation and Transfer. Activate this checkbox if you want the task to go through them but stop after transferring because you want to control when to execute it.

    For details see Executing Once with the Manual Release Option below.

    At Date/Time

    You can schedule the task to be executed at a particular time that you define here. Click this checkbox to open the date/time picker and select the desired date and time.

    The task is then available in the Tasks list of the Process Monitoring perspective with the "Waiting for start time" status. You can edit it as long as it is in this status

    You can also decide to execute the task at a predetermined time in the future considering the calendar conditions defined in your company. The task has the "Waiting for start time" status
    Use logical date

    In some situations you may need to start a task knowing that it should be processed at a time in the future. For example, a task that should run on the weekend due to calendar conditions but you must start on Friday.

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

    On the screenshot below the Execute Once option was selected on the 20th of June 2016 at 08:24 AM, so this is also its activation time. However, the logical date time has been set to the 21st of June, when the task is actually executed.

    The details of the process display the start and activation times. The logical date of tasks is displayed in the activation report.
    Time Zone If you have defined a Time Zone Object (TZ) that you want this execution to consider, select it here.
    Alias

    If you specify an alias here, this is displayed on the Tasks window in the Process Monitoring perspective. This makes it easier for you to identify this execution later on, in case you want to edit its parameters.

    You can use the same characters as for names, that is, it can contain up to 200 characters.

    It is not possible to use variables here.
    Queue

    You can assign a particular queue for this execution, which can be different to the one in the object's definition.

    If you leave this field empty, the object queue is used.
    Test Options
    Activate attributes dialog

    When you define an object type, you specify the general attributes that will always apply to objects with this type. In some cases, however, it might be necessary to change specific settings for a particular run of an object without modifying its general definitions.

    If you activate this checkbox, before the task is executed a dialog pops up displaying the attributes that can be changed for this particular run. These values apply only to this execution.

    Display in activation report

    Activating option in this section causes the script to be processed and overrules the Generate at Runtime settings defined for the object in the General - Runtime page.

    The activation report includes both the script statements and the content of all involved Include objects. In the case of jobs, also the job includes such as Header and Trailer.
    Generated JCL Activate it to display the JCL in the report.

    After clicking the Execute button, the task is activated and the report opens. This allows you to check and, if necessary, modify it.

    You can use this in combination with the Wait for manual release option. When you are happy with the results you can release the task for execution.
    Original script

    Activate it to display the script in the report.

    After clicking the Execute button, the task is activated and the report opens. This allows you to check and, if necessary, modify it.

    You can use this in combination with the Wait for manual release option. When you are happy with the results you can release the task for execution.
    Modifications of variables

    When testing your object definitions, you may want to modify your variables and check the results before actually executing them. Activate this option if you want those changes to be displayed in the activation report.
    Modifications of attributes When testing your object definitions, you may want to modify their attributes and check the results before actually executing them. Activate this option 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 run.

      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 PromtSets or READs have been defined for this object, the task will not be executed until you enter the required data. The application will display a message prompting you to enter it.

Executing Once with the Manual Release Option

Before being actually executed, tasks go through the following phases: Activation, Generation and Transfer. Use this option with jobs, to test them and have the possibility to modify the generated JCL before executing them (see Stages of Job Processing). 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

There are several ways of releasing the task: