Time Zone

Indicates the time zone according to which the job should be scheduled.

Consider the following:

• Newly defined jobs with specified time zones must be saved at least 48 hours before their intended execution dates (in order to ensure that they are ordered automatically by the appropriate New Day Procedure or User Daily).

  If they must run "today" they should be ordered manually (for example, using the ctmorder utility).

• Specified Odates are calculated according to the working date (not the actual date). This means that if a job is defined as working on the 5th of the month at 3:00 A.M., and the working day begins at 5:00 A.M., then the job is actually run at 3:00 A.M. on the morning of the 6th (which is still part of the working day of the 5th).
• In addition to time zones, you can also order a job that is intended for execution on a future date. For more information, see the odate and odate_option parameters in any of the following Control‑M/Server utilities:
  • ctmudly
  • ctmudchk
  • ctmorder
  • ctmcreate

For more information about these utilities, see Control‑M Utilities.

BMC Software recommends that you do not combine jobs that have time zone specifications with jobs that do not specify a time zone in the same folder.

When a job is considered for ordering by the New Day procedure, it is ordered if its scheduling date occurs within the next 48 hours. When a job is ordered by a User Daily job, it is ordered only if its scheduling criteria are satisfied for the current working date. For this reason, BMC Software recommends that you arrange the jobs for each time zone in a separate folder.

A job with Time Zone that was forward order becomes eligible to run at the same hour as specified in the configuration of the New Day time but this hour is reflected by the job’s timezone. For example if the Control-M/Server is running New Day in California on PST at 7am and the jobs timezone is in New York (EST), the job will be eligible to run for specific date from 7:00 EST to next 7:00 EST. From Control-M/Server perspective that is 4:00am PST until the next day 4:00am PST. The job is ordered one day prior to the ODATE of the job and remain in the Active jobs for 48 hours. However it's eligible to run only 24 hour period from 7:00am to 7:00am EST. The time prior to the 7:00 am EST the job is Pre-ODATE state and the hours after the next day 7:00 EST the job state is in Post-ODATE state. When the job is in Pre/Post ODATE state it cannot be managed nor any actions can be performed on it. At the next New Day time it will be removed from AJF. If a job has a Maxwait value then additional modification apply because of timezone considerations.

Non cyclic:

Job will stay in AJF if it has maxwait, when it gets a chance to run on the next day and ends ok, it will then change to POST ODAT during the next run of the timezone cleanup, which occurs every 30 minutes on the hour.

Cyclic:

Job will stay in AJF if it has maxwait, it will be allowed to rerun during the whole next day. When changed to POST ODAT it will not be allowed to rerun. New day will remove jobs that are in POST ODAT state.