schedtime

Represents the time when the job stream is positioned in the plan. The value assigned to schedtime does not represent a dependency for the job stream. While the production plan is in process, the job or job stream instance might start processing before the time set in the schedtime keyword if all its dependencies are resolved and if its priority allows it to start.

Syntax

schedtime time [timezone|tz tzname][+n day[s]] [,...]

Arguments

time: Specifies a time of day in the format: HHHHmm. Possible values are from 0000 to 240000, or 0000 + <number of days>.
Where <number of days> can be from 1 to 100 days.
tzname: Specifies the time zone to be used when calculating 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.
n: Specifies an offset in days from the scheduled start date and time.

Comments

Differently from the at key, the schedtime key does not represent a time dependency, that is it does not state a time before which a job or job stream cannot start. Instead, the value specified in the schedtime keyword is used only to position the specific job or job stream instance in the preproduction plan. While the production plan is in process, the job or job stream instance might start processing before the time set in the schedtime keyword if all its dependencies are resolved and if its priority allows it to start.

For an explanation on how the schedtime keyword is used to identify predecessors in the preproduction plan, refer to Managing external follows dependencies for jobs and job streams.

The at and schedtime keywords are mutually exclusive. If schedtime is not specified and the at keyword is specified in the job or job stream, then its value is used to position the instance in the preproduction plan.

If neither the at nor the schedtime keywords are specified in the job or job stream definition, it is assumed by default to be the value assigned to the startOfDay global option set on the master domain manager.

For job streams with a schedtime definition, the value of the Start time field displayed on the Dynamic Workload Console depends on the setting of the enPreventStart global option (which determines if job streams without an at dependency can start immediately, without waiting for the run cycle specified in the job stream):

If enPreventStart is set to yes, the start time is 12:00 AM converted to the time zone specified on the graphical user interface.
If enPreventStart is set to no, the start time field is blank.

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 scheduled to start at 3:00 a.m. on Wednesday morning. Its two jobs are launched as soon as possible after the job stream starts processing.
```
schedule sked7 on tu schedtime 0300:
job1
job2
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. Job stream sked8 is selected to run on Friday. It is scheduled to start on workstation sfran at 10:00 a.m. America/Los_Angeles Saturday (as specified by the + 1 day offset). Job job1 is launched on sfran as soon as possible after the job stream starts processing. Job 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 schedtime 1000 + 1 day:
job1
job2 at 1400 tz America/New_York 
nycity#job3 at 1600
end
```