Previous Topic: listItem—Show Information about Jobs Assigned to Software PolicyNext Topic: showAttrItem—Show Information about Job Assigned to Software Policy


modifyItem—Modify Job of Unsealed Local Software Policy

This command modifies a job of an unsealed local software policy. You can optionally seal the policy with this command.

This command has the following format:

swPolicy	action=modifyItem
name=software_policy_name
jobname=name_of_job
[newjobname=new_job_name]
[after={exacttime | boottime}]
[reinstall[={y|n}]]
[preaction={none | reboot | logoff}]
[postaction={none | reboot | logoff | rebootAtEnd | logoffAtEnd | shutdownAtEnd}]
[promptUser[={y|n}]]
[allowCancel[={y|n}]]
[execTimedOut[={y|n}]]
[offline[={y|n}]]
[runAtShutdown[={y|n}]]
[preventLogon[={y|n}]]
[triggeredByScalSrv[={y|n}]]
[globaltime[={y|n}]]
[calendarname=delivery_calendar_name]
[noCalendar[={y|n}]]
[resolveQuery[={y|n}]]
[stagingServer[={y|n}]]
[parameters=user_parameters]
[prompt=d.h]
[jobTimeout=d.h]
[repeat[={y|n}]]
[seal[={y|n}]]
[userJobMessage]
name

The name of the software policy that contains the job to be modified.

jobname

The name of the job that is modified.

newjobname

The new name of the job. If not coded the old name remains.

after

This option times when the job will start executing at the target systems. The following values are valid:

exacttime

The job starts processing as soon as the order has fallen due.

boottime

After falling due the processing of the job is deferred until the next (re-)boot time.

If not coded this option is not changed.

reinstall

If “reinstall” or “reinstall=y” is coded then the item will be reinstalled at the targets each time the software policy evaluates. If “reinstall=n” is coded then the item will only be installed if it is missing at the targets. The option is valid for install procedures only; for any other type of procedure this option is ignored.

If not coded this option is not changed.

preaction={none | reboot | logoff}]

Specifies any actions that must take place before the related job is processed at the target computers. The valid pre-actions are:

none

Performs no pre-actions.

reboot

Restarts the system before executing the job.

logoff

Logs off the users before executing the job.

If not coded, this option is not changed.

postaction={none | reboot | logoff | rebootAtEnd | logoffAtEnd | shutdownAtEnd}]

Specifies any actions that must take place after the related job has been processed at the target computers. The following post-actions are valid:

none

Performs no post-actions.

reboot

Restarts the system after executing the job.

logoff

Logs off the users after executing the job.

rebootAtEnd

Specifies that the job requires a reboot after it has been processed. But the reboot can be deferred until all other jobs resulting from the same evaluation of the software policy have been processed or a subsequent job requires an immediate reboot before or after being processed.

logoffAtEnd

Specifies that the job requires a user logoff after it has been processed. But the logoff can be deferred until all other jobs resulting from the same evaluation of the software policy have been processed or a subsequent job requires an immediate reboot or logoff before or after being processed.

shutdownAtEnd

Shuts down the target computer after completion of the jobs.

If not coded, this option is not changed.

promptUser

If “promptUser” or “promptUser=y” has been specified then the user at the targets is prompted before the job is executed. If “promptUser=n” is specified then the job is executed without any user prompting.

If not coded this option is not changed.

allowCancel

If “allowCancel” or “allowCancel=y” is specified then the user at the targets can cancel the execution of the job when being prompted for execution. If “allowCancel=n” is specified then the user cannot cancel the job.

For enabling the cancel the prompting must be required otherwise an error is reported.

If not coded this option is not changed.

execTimedOut

If “execTimedOut” or “execTimedOut=y” is coded then the processing of the job is automatically started when the user prompting times out. If “execTimedOut=n” is coded then the procedure does not start at time out.

For enabling the start at time out the prompting must be allowed, otherwise an error is reported.

If not coded this option is not changed.

offline

If “offline” or “offline=y” is coded then connection between the target and the associated server will be released for the job’s execution; if “offline=n” is coded the connection is not released.

If not coded this option is not changed.

runAtShutdown

If “runAtShutdown” or “runAtShutdown=y” is coded then the job is only executed at system shutdown; if “runAtShutdown=n” is coded then the job is also executed at any other time it falls due.

If not coded this option is not changed.

This option applies to UNIX only.

preventLogon

If “preventLogon” or “preventLogon=y” is coded then a user logon attempt at the targets is rejected while the job is running. If a user is already logged on when the job starts then execution is deferred until the user logs off.

If “preventLogon=n” is coded then the processing of the job does not care whether a user is logged in or tries to login during run time.

If not coded this option is not changed.

This option applies to Windows targets only.

triggeredByScalSrv

If “triggeredByScalSrv” or “triggeredByScalSrv=y” is coded then the scalability servers associated with the targets initiate the job’s execution. If “triggeredByScalSrv=n” is coded the target initiates the execution at time of reboot or jobCheck.

If not coded this option is not changed.

globaltime

If “globalTime” or “globalTime=y” is coded then all dates associated with the job are based on enterprise manager time, if “globaltime=n” is coded it is based on domain manager time.

If not coded this option is not changed.

calendarname

Specifies the name of the calendar that is responsible for driving the delivery of the job to the scalability servers and targets. If the empty string (“”) is coded then delivery calendar entry is emptied.

If not coded this option is not changed.

noCalendar

If “noCalendar” or “noCalendar=y” is coded a possible execution calendar attached to the target computers will be ignored for the job processing. If “noCalendar=n” is coded then the calendar is taken into account.

If not coded this option is not changed.

resolveQuery

If “resolveQuery” or “resolveQuery=y” is coded and the group associated with the software template is a query group then this group is re-evaluated before the job is created for the related procedure. If “resolveQuery=n” is coded then no re-evaluation takes place.

If not coded this option is not changed.

stagingserver

If “stagingserver” or “stagingserver=y” is coded the related item is staged at the scalability servers that are associated with the targets otherwise it is not staged. The option is ignored if the job is not an installation job. If “stagingserver=n” is coded then the staging step is skipped

If not coded this option is not changed.

parameters

Specifies the parameters that are passed to the job procedure. If an empty string (“”) is coded then it is assumed that no parameters have to be passed.

If not coded this option is not changed.

prompt

Specifies the time period in which the user will be re-prompted for the job procedure’s start at the target when the user defers the execution. The period’s format is “d.h” where "d" means days and "h" means hours and the range is 0.3 <= d.h <=7.0.

If the specified value is fallen below the allowed minimum then the minimum is set and if it exceeds the maximum then the maximum is set. No warning is given in these cases.

If not coded this option is not changed.

jobTimeout

Specifies the expiration date of the procedure in form of a time period. The period’s format is “d.h” where d means days and h means hours. The range of the parameter is configurable at the manager’s site.

If the specified value is fallen below the allowed minimum then the minimum is set and if it exceeds the maximum then the maximum is set. No warning is given in these cases.

If not coded this option is not changed.

repeat

If “repeat” or “repeat=y” is coded then the related job is repeated every time an evaluation takes place. If “repeat=n” is coded the related job is not repeated.

If not coded this option is not changed.

seal

If “seal” or “seal=y” is coded then the policy is sealed after the modification has been completed otherwise it remains unsealed for further modifications. The seal is only performed when the modifications have been successful and no error has been reported. Warnings do not suppress the seal.

If not coded, this option is not changed.

userJobMessage

Modifies the custom administrator message for a job in a software policy.