Actions

Job definitions have the following actions:

Compulsory Fields

Some fields need to be filled, like the Job Definition Name field, which is the only field that does not have a default and that needs to be filled for every job definition type. Other job definition types additionally require other fields be filled. For example, RedwoodScript job definitions need to have the Source field filled with at least the following: {}. Furthermore, the source is not editable with job definitions of certain types, like the SAPR3 job definition type. The keep clause, which by default is set to keep all jobs of the job definition, is also compulsory and needs to be changed if you want the system to automatically delete old jobs.

Finding Job Definitions

You can search for job definitions using filters and the Search Job Definitions box on the Job Definitions tab. This box is known as the intelliSearch box and located under your username on the top right-hand side of the user interface. Filters allow you to specify a list of objects with static criteria. IntelliSearch allows you to specify complex queries in a simple way using prefixes. Prefixes are used to specify which property you are searching in and have short and long syntaxes. For example, if you want to display all job definitions with the term import in the comment, you would use the search criteria as follows:

c:import

You can search more than one property, as follows:

c:import n:System

See the Advanced Object Search for more information.

The following table illustrates the available prefixes for job definitions:

Deleting Job Definitions

You can only delete job definitions when no other objects relate to them. For example, if the job definition is called in a job chain job, the job definition cannot be deleted until all job chain jobs using it have been deleted. You can see all job chain jobs that relate to the job definition in Related Objects in the lower detail pane and on the show page. Furthermore, jobs of a job definition will prevent you from deleting the job definition. Theseare found by selecting Show Related Jobs from the context menu. It is also possible to cancel and delete related jobs from the context menu.

The table in related objects contains three columns:

Job definitions that are called in job chains will have the call-reference in Related Objects. The type will be Job, and the Related Object will be the name of the job. For example, if it is the first job in a step, it will be Job 1.

Security

The following privileges are available for job definitions:

You can grant privileges on two levels, Access and Admin; a privilege granted on Admin level allows the grantee to grant the privilege to other users. These privileges can be granted system-wide, per partition or isolation group. Note that to be able to schedule a job, the user also needs privileges on the queue and other objects referenced by the job definition.

If you have the security module, which requires the Module.Security license key, you have an additional Security tab on the job definition. It allows you to specify which users can access, edit and delete the job definition.

Editing XML Source

You can also edit the XML source directly or copy it into your editor of choice. This is especially handy when you want to perform repetitive tasks such as a Search and Replace. You enable the the XML source tab in the user options by enabling the Allow edit as XML option; see Setting User Parameters. Special care needs to be taken when you edit in XML, as you will have to use entities for special signs, such as the less-than (<) sign, which needs to be replaced with &amp;lt;. Please see XML resources on-line for a list of common XML entities.