Attributes Page

Agent

Target system (agent or agent group), that is, the system where the job is going to run.

Generic Jobs are a special case. When defining them, it is not necessary to assign them an Agent. If you do so and if you want to use the &$PLATFORM# predefined variable in a script statement, you must also define the &AGENT# variable. The &AGENT# variable can be set to an Agent, but not to an Agent Group.

In the Agent and Queue fields, it is not possible to use { } expressions combined with script-variables like {VARIABLE.STATIC,&SCRIPTVAR#,1}. It is possible to use either { } expressions or script-variables, but only the combination is not valid. A possible workaround is to use GET_ATT and :PUT_ATT in statements in pre-process scripts.

Login

Login object that contains the necessary information for the job to be able to log on to the target system.

For OS/400 platforms the user profile specified in the selected Login object must also be activated in the OS/400 platform. Otherwise, starting jobs is not possible.

Code Table

Code table that is applied to transform character sets. See Code Table Object (CODE)

Queue in which the object is going to be executed.

If you do not select a queue here, the object starts in the CLIENT_QUEUE. See CLIENT Queue.

In the Agent and Queue fields, it is not possible to use { } expressions combined with script-variables like {VARIABLE.STATIC,&SCRIPTVAR#,1}. It is possible to use either { } expressions or script-variables, but only the combination is not valid. A possible workaround is to use GET_ATT and :PUT_ATT in statements in pre-process scripts.

If you want to include this object in a group (JOBG), select the group from this drop-down list. If nothing is specified here, the object is activated immediately.

This option is ignored if the object is started by a workflow (JOBP), a schedule (JSCH) or a recurring task.

The number of resources that are consumed during the execution.

The default value applies the value set by your administrator in the WORDKLOAD_DEFAULT_FT key of the UC_SYSTEM_SETTINGS variable.

• Default value: 0
• Allowed values: 0 to 100000

Objects are processed in queues based on their priority. Here you specify the priority you assign to this object. For details see Automation Engine Priority.

The default value applies the value set by your administrator in the TASK_PRIORITY key of the UC_SYSTEM_SETTINGS variable.

• Default value: 0, which corresponds to a priority of 200
• Allowed values: 1 (lowest) to 255 (highest)

You can select a time zone here. This will be applied to runtime calculations.

Select this option to display a dialog box allowing you to change the attributes for the current execution of the object.

The activation and the start time of an object can be different, for example when an object is executed by a workflow.

With this setting you define when the script is processed.

This setting also affects the way the system decides which agent in an agent group will process the task.

• Activation time: The script is processed when the object is activated (before processing).

  The start time of the task is used for agent selection. The status of the task switches to Waiting for resource in case no sufficient resources are available on the agent at that moment. It waits until processing is possible again. It does NOT change the agent even if a different one had enough resources.

• Runtime: The script is processed directly after activation.

  The start time of the task is used for agent selection and resource allocation at the same time. The status of the task switches to Waiting for host in case no sufficient resources are available on any agent at that moment. It waits until one of the agents in the group has the necessary amount of free resources.

See 2. Generation for details of what happens when selecting the one or the other option.

You can define how many tasks are processed in parallel. You will have to consider this when you assign single objects to a group and decide whether they should be executed simultaneously or not.

• Default value: 0 (no limit)
• Allowed values: 0 to 99999

Note: Changes to these settings are active only after the first generation and do not apply to Jobs that are already running.

Remaining Task: When you define a limit for parallel file transfers, you can also define what happens with the tasks exceeding this limit:

• Wait: The object waits until processing is possible.
• Abort: The object ends.

The task is always deactivated after its execution. It is available on the Tasks window as long as it is active; once finished, it is removed from it.

You can still access it from the Process Monitoring perspective if you filter the list of tasks to be displayed activating the Include deactivate tasks checkbox.

The task is only deactivated if it has been executed without errors and its successful status is confirmed.

If no status is selected, the system return codes 1900 to 1999 (ANY_OK) indicate a successful file transfer.

Workflows: An interrupted workflow including its tasks remain the Tasks window. To deactivate and remove them from the list.

You can define a time span in minutes after which the task is automatically deactivated. You can still deactivate the object manually within the given time span.

The default value is 0. This means that the value that the system administrator has defined in the UC_CLIENT_SETTINGS variable will be applied.