HCL Workload Automation, Version 9.4

General rules

When the time zone is enabled in the HCL Workload Automation environment, regardless of which value is set for the enLegacyStartOfDayEvaluation option, some general rules are applied. These rules are now described divided by topic:
Identifying default time zone settings for jobs and job streams:
Within a job stream definition you can set a time zone for the entire job stream and for the jobs contained in the job stream. These time zones can differ from each other. To manage all possible time zone settings the time zone conversion is made respecting the following criteria:
  • If a time zone is not set for a job within a job stream, then that job inherits the time zone set on the workstation where the job is planned to run.
  • If a time zone is not set for a job stream, then the time zone set is the one set on the workstation where the job stream is planned to run.
  • If none of the mentioned time zones is set, then the time zone used is the one set on the master domain manager.
Choosing the correct time zone for the workstations:
To avoid inconsistencies, before enabling the time zone management feature across the HCL Workload Automation network, make sure that, if a time zone is set in the workstation definition, it is the same as the time zone set on the system where the workstation is installed.
Default time zone setting for the master domain manager:
If a time zone is not set in the master domain manager definition, it inherits the time zone set on the system where the master domain manager is installed. To see which time zone is set on the master domain manager you can run the following command:
conman showcpu;info
Using the time zone on extended agents:

Extended agents inherit the time zone of the master domain manager.

Displaying time zone setting in production for an AT time dependency:
If you use conman commands sj or ss to display a job or a job stream having an at time dependency with a time zone set, the time specified for the at dependency is displayed applying the time zone defined on the workstation where the job or job stream is defined to run.
Applying an offset to a time zone when scheduling a job stream:
If you submit in production a job stream specifying an at dependency with an offset of +n days, then HCL Workload Automation first adds the offset to the date and then converts the time zone set in the at dependency. This is important especially when referring to the time when daylight saving time moving occurs.

As a best practice, if you enable time zone management, set a time zone on each workstation of your HCL Workload Automation network.