Step 1: Creating a new job

The primary component of the EnterpriseSCHEDULE system is the job. Jobs contain vital information about what is being scheduled, when the job will run, how it will behave when it is run and whether or not it will with other jobs. When a job is created, some or all of these factors should be considered:

• What will the job do? If it runs a batch file or executable.
• When will it run? Do I want the job to be rescheduled?
• What other jobs should run when it completes? Do I want to have any initiates or prerequisites?
• Do I want to view the job in a layout? The job can be viewed in a layout for easy monitoring and job procedures.
• Are there any users that should be notified of events? Event notifications can be set using e-mail addresses.
• Where do I want to save the log file? A log file is a record of the job's completion. You can designate where it's stored and what it's name is.

There are many other attributes that affect the way a job behaves. These are all contained in the Job Properties Page. For now we will just deal with a few of these properties.

When a new job is created it inherits the attributes of the job named "DEFAULT" in the current directory or, if that does not exist, the "DEFAULT" job in the SCHEDULE directory \default. This default job should have the properties most commonly desired for subsequently created jobs. For instance, if you want your jobs to use Named Day scheduling, set the "DEFAULT" job with that attribute. Once the job is created, attributes may be changed in the Job Properties Page.

In this step we will create two new jobs Job1 and Job2.