ExecutionTask - addOneTimeScheduleWithTimeZone
ExecutionTask - addOneTimeScheduleWithTimeZone
Description :
This command adds a one-time schedule to an execution task with a specified time zone. The execution task waits until the approval is received and then runs. If the approval does not come on time, the schedule is marked as expired and the approval system closes the change ticket.
The argument etKey is a handle to the execution task being modified. To find the etKey, use the ExecutionTask getDBKeyByGroupAndName command.
The dateString argument defines a one-time schedule to be added to the execution task definition. It must be in the format YYYY-MM-DD HH:MM:SS.
This command does not send execution task notification.
For a list of valid Time Zone ids, use the Schedule listValidTimeZones command.
Return type : java.lang.Object
Command Input :
Variable Name | Variable Type | Description |
---|---|---|
etKey | com.bladelogic.om.infra.model.base.keys.SExecutionTaskKey | Handle to the execution task. |
dateString | String | One-time schedule to be added. The date string must be in the format YYYY-MM-DD HH:MM:SS. |
timeZoneId | String | Time zone to be used for the one-time schedule to be added. |
Example
The following example shows how to add a schedule to an execution task for a single run on the 1st of January 2005 at 11:35 PM in the UTC time zone.
Script
DATE_STRING="2005-01-01 23:35:00"
ET_KEY=`blcli ExecutionTask getDBKeyByGroupAndName /tasks tstEt`
ET_KEY=`blcli ExecutionTask addOneTimeScheduleWithTimeZone $ET_KEY "$DATE_STRING" UTC`
Comments
Log in or register to comment.