HCL Workload Automation, Version 9.4

at

Specifies a time dependency. If the at keyword is used, then the job or job stream cannot start before the time set with this keyword.

Syntax

at time [timezone|tz tzname][+n day[s]] [absolute|abs]

Arguments

time: Specifies a time of day. Possible values can range from 0000 to 2359.
tzname: Specifies the time zone to be used when computing the start time. See Managing time zones for time zone names. The default is the time zone of the workstation on which the job or job stream is launched.
Note: If an at time and an until or deadline time are specified, the time zones must be the same.
n: Specifies an offset in days from the scheduled start date and time.
absolute: Specifies that the start date is based on the calendar day rather than on the production day.

Comments

If an at time is not specified for a job or job stream, its launch time is determined by its dependencies and priority and its position in the preproduction plan is determined by the value assigned to the schedtime keyword. For more information about the schedtime keyword refer to schedtime.

If the run cycle and job stream start times are both defined, the run cycle start time takes precedence when the job stream is scheduled with JNextPlan. When the job stream is launched with the submit command, the run cycle start time is not used.

The time value in the at option is considered as follows:

If the time value is less than the value set in the startOfDay global option, it is taken to be for the following day.
If the time value is greater than the value set in the startOfDay global option, it is taken to be for the current day.

If the master domain manager of your network runs with the enLegacyStartOfDayEvaluation and enTimeZone options set to yes to convert the startOfDay time set on the master domain manager to the local time zone set on each workstation across the network, you must add the absolute keyword to make it work when you submit a job or a job stream.

If neither the at nor the schedtime keywords are specified in the job stream definition then, by default, the job or job stream instance is positioned in the plan at the time specified in the startOfDay global option.

Examples

The following examples assume that the HCL Workload Automation processing day starts at 6:00 a.m.

The following job stream, selected on Tuesdays, is launched no sooner than 3:00 a.m. Wednesday morning. Its two jobs are launched as soon as possible after that time.
```
schedule sked7 on tu at 0300:
job1
job2
end
```
The following example launches job stream mysked on Sundays at 8:00 a.m.. Jobs job1, job2, and job3 are all launched on Sundays.
```
schedule mysked on fr at 0800 + 2 days
:
job1
job2 at 0900
job3 follows job2 at 1200
end
```
The time zone of workstation sfran is defined as America/Los_Angeles, and the time zone of workstation nycity is defined as America/New_York. The following job stream is selected to run on Friday. It is launched on workstation sfran at 10:00 a.m. America/Los_Angeles Saturday. job1 is launched on sfran as soon as possible after that time. job2 is launched on sfran at 2:00 p.m. America/New_York (11:00 a.m. America/Los_Angeles) Saturday. job3 is launched on workstation nycity at 4:00 p.m. America/New_York (1:00 p.m. America/Los_Angeles) Saturday.
```
sfran#schedule sked8 on fr at 1000 + 1 day:
job1
job2 at 1400 tz America/New_York 
nycity#job3 at 1600
end
```