The Jobs tab displays the following information:
Lists the jobs in the job container.
You may change the order using the arrow buttons at the right of the window.
Each job in the job container is represented by the tabs Job, Procedure Options, and Job Options. The Job tab displays general information about the job, whereas the other tabs provide more specific information.
The Job tab displays the following information:
By default, a concatenation of 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.
The state of the job, for example, Waiting, Active, OK or Error.
Type of the job, for example, Original or Cascade.
The name of the software item selected for setting up the job. This field is empty, if more than one software item has been selected in the Job Order list.
Here you can set the date and time 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.
The time is changed by clicking on the hour, minute or second values and increasing the value by using the upward-pointing little arrow at the right-hand side of this field.
The downward-pointing little arrow decreases the selected value.
Note: If you change the delivery time later to a time that is earlier than the delivery time, then the delivery time is set to the same as the activation time.
Check this box, if you want the evaluation of the current assigned job's potential targets to be repeated for every evaluation of this group.
Note: The software policy job property Repeat for every evaluation has no effect on ad-hoc software policy evaluation. Ad-hoc evaluation never performs repetition of non installation jobs. This property only has an effect during scheduled evaluation of software policies.
Here you can set the date and time when you want the job to be activated.
By default, the current date and time are provided here as well.
The date and time are changed as for Deliver at above.
On the correlation of these time settings, see further Time Setting Rules.
The procedure to be used for the job. In a scroll box, you can select among the procedures, of the appropriate task type, defined for the current software item.
The install procedure to be referred to for the job, when the task type is not install. In a scroll box, you can select among the install procedures that are defined for the current software item. The box can also contain an asterisk (*), which refers to any of the installations made on the computer.
Check this box, if you want existing installation records to be deleted, thus preventing the job from failing with a status of Already Installed, before the install process is activated.
The box is useful in, for instance, the following situation: a user has manually deleted an installation but the install record still exists on its manager.
This check-box only applies to install jobs. By default the box is not checked.
The box should not be checked, if an installation of the software already exists on the intended target and you are not sure if a re-install (a rerun of the install process) will succeed.
Displays status messages after evaluation. Initially, this field is empty and thus not displayed.
Displays numerical values for each of the status fields, OK, Error, Active, and Waiting. Initially, these fields are empty and thus not displayed.
Displays the procedure inherited options:
Defines whether the target computer is to be rebooted prior to the job activation, and at what level this should be done. All the options available in this list are supported on the Windows, Linux, and MAC agents.
Levels: None, Restart machine, Logoff user
This option is set to None by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab. Select one of the options from the drop-down list.
Note: The option Logoff user does not prevent the user to re-login before the job is executed.
Defines whether to restart the target computer after the job activation, and at what level this must be done. It also defines whether to shut down the target computer after completion of the last SD job. All the options available in this list are supported on the Windows, Linux, and MAC agents.
Levels: None, Restart machine, Logoff user, Restart machine after last job, Logoff user after last job, Shutdown machine after last job
This option is set to None by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab. Select one of the options from the drop-down list.
Note: The Shutdown machine after last job option always takes precedence over the Restart machine after last job option. For example, consider a scenario where one job in a job container uses the Shutdown machine after last job option and another job uses the Restart machine after last job option. In this case, the Shutdown machine after last job option takes precedence over the Restart machine after last job option, and the target computer shuts down after completion of the last job.
Note regarding Boot level: The level selected here (booting job driven) should not be confused with the boot level concept used in the Software Management Installer: booting installer driven (if any active dll's, or other active system components, must be changed or deleted during the installation, the Installer introduces a restart, so that the appropriate components can be updated by the operating system during the restart).
Regarding the latter case, just note here that after the Software Management Installer has processed its jobs (installs, uninstalls, and updates), a system start (boot or logoff/logon) will be initiated once a respective boot level (0, 1, 2, 3 or 4) has been set, or when a system start is necessary because of locked files.
This check box defines whether questions should be asked of the users at the target computer(s) before and after the activation.
This option is not checked by default for all job linkage settings (batch job, synchronized or no linkage) on the Job container tab.
Before the job activation is started, the user is asked to confirm that it is to be started, to be run later, or not at all. If "Prompt user" is not checked, the job activation will always start.
After activation: At the conclusion of an item procedure activation, of a 16-bit Windows program in Windows NT/2000/XP environment only, users will be prompted to indicate if the item procedure completed successfully. If it did not complete successfully, the user can specify the reason for the interrupt. Then the installation register will list this installation as an error.
Check this box, if you want to use this feature. "Prompt user" must also be checked.
If Prompt user is selected, the check box for Execute if prompt times out is eligible.
If Execute is checked, the execution of the job, when the timeout elapses, could depend on the settings of the parameters “UserPrompt: Timeout Action” and “UserPrompt: Timeout action when user is logged off” in the common configuration. For example, if “UserPrompt: Timeout Action” is set to 0 on the target, the job will be cancelled at the target if the prompt times out.
If “UserPrompt: Timeout action when user is logged off” is not set on the target, the checking of this box determines the action. If the box is checked, the job will execute and if it not checked, the job will be postponed.
If Prompt user is not selected, the Execute check box is grayed out.
This check box defines whether the Job check program of the target computer should release communication with the server during execution of the job. When the job has finished, the agent reconnects to the server to report job status.
The reason for this check box is that when updating, for example, kernel drivers on a UNIX manager, a reboot is required. Since these kind of managers will be rebooted only occasionally, a mechanism is needed to schedule jobs for execution, while the system is going to shutdown.
This option is not checked by default for all job linkage settings (batch job, synchronized, or no linkage) on the Job container tab.
If this box is checked, the box Job will be triggered by server will automatically be grayed out, since these two options are mutually exclusive.
The box will be set by default, if the box Run at shutdown (UNIX only) is checked on the Options tab of Procedures.
If the UNIX agent lacks the shutdown functionality, the job will never run and hence time out.
The box should not be checked for jobs targeted at non-UNIX systems. In such a case, the job will never run but time out.
Jobs for execution on shutdown must not be combined with standard jobs within the same container, since this will postpone all jobs of the container.
This option (only supported for Windows NT/2000/XP agents) is to be selected, if a user is to be prevented from logging on, while the agent processes a job. When the user is already logged on, the Software Delivery agent will proceed with the scheduled job when the user has been logged off.
This option is not checked by default for all job linkage settings (batch job, synchronized, or no linkage) on the Job container tab.
In order for this function to be activated, it is necessary to execute the Enable per job procedure first, a Logon Shield function. It will prevent the user from disturbing applications that are currently updated or not completely installed. A message is presented during attempts to log in.
When the Logon Shield has been activated, a dialog will inform the user about the current state of the job. If the user hits CTRL+ALT+DEL, the dialogue will appear and continuously display the progress. It will disappear automatically after the job has ended. All progress messages can be configured.
Note: This option PREVENTS the user to re-login before the job is executed.
Displays job specific options:
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).
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.
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.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|