User Guide > Objects > Alphabetical Listing > Attributes Tab

Attributes Tab

The Attributes tab is object typeAn individual object is provided for the individual activities: There are User, UserGroup, Notification, Cockpit, CodeTable, Documentation, Event, Agent, FileTransfer, Group, Include, Job, Workflow, Calendar, Login, Client, RemoteTaskManager, Schedule, Script, Server, Sync, Variable and TimeZone objects-specific and is only available in Job objects. The target system and all settings that are required in order to execute a jobAn Automation Engine object type for a process that runs on a target system. are defined here.

Object: Job
Object class:
Executable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task
Object type (short name):
JOBS

Description

Field/Control

Description

Attributes  

Host

You can define the name of the target system (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) on which the job should run here. You can also specify an agent group.

Code

Name of the CodeTable that this job should use.

If no CodeTable has  been selected, the default CodeTable of the agent that uses this job is used.
See:
CodeTable - Usage

Group

If the job should be started by a group, you can select this groupAn Automation Engine object type that integrates tasks so that they can be processed together. here. If there is no entry, the job is activated immediately.

Note that the entry specified here is not considered if the job was started through a Workflow or Schedule object, or as a recurring task.

Queue Selection of a Queue object in which the job should be processed. The job automatically starts in the Client Queue (object name: CLIENT_QUEUE) if nothing has been specified in this field.

Login

Selection of a Login object.

The Login object contains the data that is used by jobs in order to log on to operating systems or applications.

The userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. profile that is specified in the Login object must be activated on the OS/400 platform as well because you cannot start jobs otherwise.

Runtime Parameters  

Consumption ... (Resources)

Resources consumed during execution.

Allowed values: 0 to 99999
Default value: 0

Selecting value 0 has the effect that the resource value that the administrator has specified in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_SYSTEM_SETTINGS with the key WORKLOAD_DEFAULT_JOB is used.

Automation Engine priorityAffects the order of task execution within an Automation Engine system. ... (0-255)

Priority that should be used to execute this job in AE.

Allowed values: 0 to 255
Default: 0

Selecting value 0 has the effect that the priority that the administrator has specified in the variable UC_CLIENT_SETTINGS with the key TASK_PRIORITY is used.

TimeZone

TimeZone that should be used.

Attribute Dialog

If this checkbox is selected, a dialog is displayed at activation. Attributes for the current execution of the job can be modified here.

Generate at runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start).

Select this checkbox if the job should not be generated at activation time but at its runtime.

Tasks running parallel

 

Max ...

Setting that defines the maximum number of parallel executions for this job.

Allowed values: 0 to 99999
Default: 0 (no limit on tasks running parallel)

Examples: 

Max. 1 - At any time, not more than one job execution must be available
Max. 2 - At any time, not more then two active job executions must be available.
.etc.

Else: Wait Abort

Instruction that defines how this job should be handled if the execution exceeds the specified maximum number of tasks that can run at the same time.

Wait = The job waits until execution is possible.
Abort = The job is interrupted.

Extended reports

Extended reports can be written for all executable objects. They log the complete scriptA particular Automation Engine object type. with all Includes, the generated JCL of jobs, and accesses to objects.

Default (UC_CLIENT_SETTINGS)

When you select this option, the reports that the administrator has defined in the variable UC_CLIENT_SETTINGS with the key EXT_REPORTS will be generated.

All

All extended reports are written for this object.
This option overwrites possible presets of the clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type..

None

No extended reports are written for this object.
This option overwrites possible presets of the client.

Int. Account

Specification of an internal account.

Contents do not affect the AE system's internal processing. You can access the attribute "Int. Account" with script elements and integrate it in your processes.

Automatically deactivate when finished

The workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."]'s settings for automatic deactivation apply for file transfers that are processed as part of this workflow. These settings overrule the settings of subordinate tasks.

When the Activity Window contains many tasks that are not deactivated automatically or manually when they are finished, this can negatively affect performance and the Activity refresh cycle.

Note that jobs that use the option Generate at runtime which end on the statusThis represents the condition of a task (such as active, blocked, generating). "FAULT_OTHER - Start impossible" are not automatically removed from the Activity Window. The settings that are defined for an automatic deactivation process are ignored in this case.

Never

The job is not automatically deactivated and remains visible in the Activity Window after it has been executed.

After error-free execution

The job is automatically deactivated after successful execution. Interrupted jobs remain visible in the Activity Window and must be deactivated manually.

You can also set a status for the error-free execution and a time delay for de-activation. Do so by specifying the fields Error-free status and/or Time delay ... Minutes .

Activating this option will deactivate the taskAn executable object that is running. Tasks are also referred to as activities.'s original execution after a successful restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. even when it has got the status 'aborted'.

If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:

  • Task delay time = 0: The setting in UC_CLIENT_SETTINGS applies.
  • Task delay time > 0: The setting in UC_CLIENT_SETTINGS is ignored.

After an error-free restart

The job is automatically deactivated when a restart has been successfully executed. Previously interrupted jobs are also deactivated.

You can also set a status for the error-free execution and a time delay for de-activation. Do so by specifying the fields Error-free status and/or Time delay ... Minutes .

If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:

  • Task delay time = 0: The setting in UC_CLIENT_SETTINGS applies.
  • Task delay time > 0: The setting in UC_CLIENT_SETTINGS is ignored.

Error-free status

Status that confirms a successful job execution. If no status is selected, the system-return codes 1900 - 1999 (ANY_OK) represent error-free execution.

Always

The job is always automatically deactivated after it has been executed.

Additionally you can specify a time delay for deactivation in the Time-Delay field.

If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:

  • Task delay time = 0, The setting in UC_CLIENT_SETTINGS applies.
  • Task delay time > 0: The setting in UC_CLIENT_SETTINGS is ignored.

Time delay ... Minutes

The job is automatically deactivated after a specified number of minutes. You can also manually deactivate it before this time is over. The time difference only affects jobs whose execution also results in automatic deactivation.

 


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

Copyright © 2016 Automic Software GmbH