Displays job specific options:
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 to Unicenter, the following will happen:
* If you are defining the job as part of a job container, the job container will be created, whereas this job will not be 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.
If the target computer has a Job Execution Calendar attached, this calendar will control the days, dates and times when jobs can be performed. By checking this box, the job will be executed regardless of the calendar settings.
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.
By checking this Job specific flag, you ensure that not only is the job set up. A delivery job to a scalability server's 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, as well as the scalability server itself.
The option is without effect, if the procedure is external. That is, the job will be executed but the package will not be 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.
In this field you can enter parameters for the execution of the job. Entries in this field will only be 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
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 will be displayed, if the user selects Later every time the prompt appears. When the timeout has expired, the job will be 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.
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 will not be performed, but it is still visible until removed.
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 will immediately be 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.
By clicking the Set as default button, you save the settings in the Registry of the computer you are currently using.
If there are more people connecting to the same manager, each using Set as Default, each user will have the own settings saved, in a personal user registry.
The default settings only work for the job specific options. The procedure specific options use the default value from the procedure options.
Job 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 (in the Job - General tab), 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 (in the Job - General tab), 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 will be 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.
|
Copyright © 2013 CA.
All rights reserved.
|
|