When defining a job, you need to consider whether you can group jobs according to one of the following:
Scheduling criteria: If jobs run on similar schedules or need to run at the same time, you should group them in the same folder. All jobs in a folder are ordered for scheduling at the same time. You may want to define a SMART folder, which uses more capabilities such conditions, post processing, and so on. For example, Folders contain end of year jobs, daily jobs, jobs that must produce reports for an audit, and jobs that must run as a group to handle emergency situations, such as backup procedures in the event of a natural disaster.
Applications: Provides a logical name for sorting groups of jobs, which is used to supply a common descriptive name to a set of related job groups, but do not necessarily have to run at the same time. For example, Applications such as Inventory, Accounting Payroll, etc.
Sub Applications: Indicates the name of the Sub Application where the job belongs logically. It is a sub-category of the Application that you can use to organize your jobs.
EXAMPLE:
Jobs in an Accounting application might be divided into sub applications such as Budgets, Finance, Receivables, and Expenditures.
Jobs in an Employees application might be divided into sub applications such as Pilots, Flight Attendants, Ground Crew, and Reservations.
Jobs in any application might be divided into sub applications such as Managers, since processing of managers remains the same regardless of the department (application) in which they work. Jobs that calculate the bonuses of managers of the ground crew
staff and managers of the reservations staff might be similar enough to include in the same sub application.
You should also consider the type of job you are automating (job script, or operating system command) and when (daily/specific days/cyclically) and where the job should run, on which computer and whether workload balancing on several computers is required. Does the job need resources and what specific action should be taken if the job finishes as expected or the the job does not finish as expected.
For Batch Impact Manager, decide whether any jobs represent batch tasks that will seriously impact critical business services if delayed. If so, define these jobs as a batch service, so BMC Batch Impact Manager can provide early warning.
Examples of critical batch business services are:
A set of jobs that, if delayed, will cause a shipping company to miss the express mail delivery truck.
A set of jobs that, if they finish way ahead of schedule, indicate that proper processing did not occur. A payroll application that finishes too soon might indicate that the proper calculations did not occur to process employees’ salaries.
You can define and run a new job by defining the job, ordering the job and ignore scheduling criteria. When the job starts running, you can monitor the job. The following examples describe how to define, order, and monitor a running job.
