Job Scheduling Principle

Univ of Hawaii - ITS Technical Architecture - Principle   

Job Scheduling

Principle

ITS will establish a central job scheduling system for its critical enterprise batch program execution and monitoring.

Generally, production batch jobs that meet one or more of the following conditions should be scheduled in the central system:

• If others jobs are dependent on the successful execution of the job.

• If the job has some level of audit requirements associated with it.

• If staff in the IT Operations Center are expected to monitor the result of the job or take action based on the successful or unsuccessful completion of the job.

• If the job updates data or system contents in a meaningful way.
  

If jobs are scheduled outside of the central environment, teams should be highly sensitive to the sustainability and reliability of the configuration.  For example, it is probably not appropriate to have a regularly scheduled systems job run off an individual’s account.

Exceptions

This principle is not intended to apply to ITS’ High Performance Computing environment.

This principle is not intended to apply to productivity jobs run by an individual to assist with his/her daily work.

In some cases, technical limitations may make it impossible to schedule a job using the central tool.

Change History

• Approved: February 26, 2016