Name

Indicates the name of the software item and the procedure selected for setting up the job. This field is empty, if more than one software item has been selected in the Job Order list.

Software

Indicates the name of the software item and the procedure.

Deliver At (Date)

Specify the date when you want the job to be delivered. By default, the current date and time are provided. Selecting the date drop-down opens a calendar, where you can choose another day in the current month or move to another month. Delivery date and time must be less than or equal to

Activate at

date and time.

Deliver At (Time)

Specify the time when you want the job to be delivered.

Activate At (Date)

Specify the date when you want the job to be activated. By default, the current date and time are provided.

Activate At (Time)

Specify the time when you want the job to be activated.

Procedure

Indicates the procedure to be used for the job. Select among the procedures that are defined for the current software item.

User Message

Defines the custom administrator message text to display to the end users.

Jobs will be triggered by Scalability Server

If you check this box, the scalability server will initiate job execution and the job will be performed at the Scheduled at date and time, or as soon as possible after that. This option is checked by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab. If the box is not checked, jobs to target computers will be executed, when the target computer contacts the scalability server (at reboot or execution of Job check).

Delivery / Activation times are relative to the Enterprise Manager time

If you do not check this box, then the job will be executed by each domain manager at the Scheduled at date and time, or as soon as possible after that. Each domain manager considers this point of time as being given in its own local time system. If you check this box - selecting universal time - the activation time specified is interpreted as universal time and the time deviation configured on each domain manager will be taken into consideration for converting the point of time received into the own local time system. This option is not checked by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab.

Use delivery calendar

Delivery calendars are useful when setting up bulk deliveries to scalability servers and NOS-less target systems using DTS to occur out-of-office hours. Hence, this setting is only applicable for agents that use the download option DTS push. If the job uses an external procedure, this setting is not applicable. If you already use Job Execution calendars, it is recommended that you name another calendar here, a Job Delivery Calendar, to control deliveries. Regardless of whether the option is used or not, manual halt or resume is possible from the DSM Explorer, for the job container and for each individual job, in order to control the delivery to scalability servers and NOS-less target systems. The selection for use of a CCS calendar is an option for each individual job in a job container. The calendar works as ordinary CCS calendars, to control the days, dates and times when delivery is permitted. The time cells not set on in the CCS calendar thus define the exclusion intervals. If you try to define a calendar, the name of which is unknown, you see one of the following job status :

If you are defining the job as part of a job container, the job container is created, whereas this job is not created.
If you are redefining the job by using the Properties choice in the context menu, the job will remain in its previous state.

This option is not checked by default for any job linkage setting (batch job, synchronized or no linkage) on the Job container tab.

Ignore job calendars on target computer

If the target computer has a Job Execution Calendar attached, this calendar controls the days, dates, and times when jobs can be performed. By checking this box, the job is executed regardless of the calendar settings.

Resolve query groups

By checking this Job specific flag, you may get true dynamic evaluation of the condition for a computer group. That evaluation takes place when the Domain Manager sets up the job for execution. This option is not checked by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab.

Store packages in the Scalability Server's staging library

By checking this Job specific flag, you ensure that not only is the job setup. A delivery job to a scalability server staging library is also automatically set up, unless the delivery has already executed. Checking this option is relevant for jobs to all computers (that are not NOS-less) that are downstream of a scalability server, and the scalability server itself. The option is without effect, if the procedure is external. That is, the job is executed but the package is not registered in the staging library. The option is not checked by default for any job linkage setting (batch job, synchronized or no linkage) on the Job Container tab.

User parameters

In this field, you can enter parameters for the execution of the job. Entries are used, if the macro $up has been set for the procedure that is used when setting up this job. In this way, the macro up expands on an individual job basis. The parameters can also be references, in the form $(Parameter Reference), to parameters stored in the database. For example, you can pass the package-specific MSI properties as user parameters. For more information about package-specific MSI properties, see the Implementation Guide. Note: If a user parameter in the Job Options dialog contains spaces it must be surrounded by quotation marks

Prompt during

This field can only be used, if the Prompt user check box was selected. It then details for how many days and/or hours the prompt is displayed, if the user selects Later every time the prompt appears. When the timeout has expired, the job is performed (unless the user selects Never, which is only enabled, if Allow user to cancel the job was selected when setting up the job). The default value is 1 day for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab. This parameter should be set to a value that does not exceed the timeout value for the job.

Job timeout

Here you specify, how many days and/or hours the job activation order is valid after the date and time it is set to be performed (in the Scheduled at date and time calendar, in the Job - General tab). When the timeout has expired, the job activation order is not performed, but it is still visible till removal. The range for this parameter is by default 3-168 hours (given by configuration parameters "Software job options: Minimum Activation Time" and "Software job options:Maximum Activation Time"). If, for example, the value 1 hour is selected, it is replaced by 3 hours by the system. The default value is 7 days (that is 168 hours) for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab.