【正文】 used by the capacity manager to generate operational reports that are used to assess system performance and processing errors or any other information the capacity manager deems useful. Batch Processing This section provides an introduction to batch processing. It describes how a scheduled batch run is executed and what resulting information is recorded. Figure 3. Batch process hierarchy Before discussing scheduled batch runs, it is useful to first understand the hierarchy of the batch process and the contents of a batch script. Figure 3 shows the batch process hierarchy. A batch run consists of multiple independent batch jobs that are scheduled for execution on a recurring basis. A large anization may execute multiple batch runs throughout the day depending on the resources required to process them. Each batch job consists of multiple batch job steps that control specific activities of job execution. An anization typically processes numerous batch jobs. To ensure a consistent approach to the execution of each job, a batch job skeleton should be devised that Batch Job Batch Run Batch Job 1 Batch Job 2 Batch Job 3 Batch Step 1 Batch Step 2 Batch Step 3 Service Management Function 13 contains the standardized code required for each job。 jobspecific information should be coded into a designated area within the skeleton. The skeleton also serves to facilitate development and maintenance requirements by standardizing the content and structure of each job script. For example, any type of standardized actions, such as the notification of a successful or nonsuccessful batch job execution and transaction data archiving and deletion, should be included in the code of every script that is executed. Scheduled batch runs are initiated by a scheduling tool during a predefined batch window, typically when user activity of the system is at a minimum. After the scheduling tool has been programmed, capacity manager interaction should not be necessary during batch runs unless an error, from which the tool cannot recover, occurs. Figure 4 is a flow chart of a typical scheduled batch process. This highlevel overview is meant to give the reader a general understanding of how scheduled batch jobs are processed. Keep in mind that the capabilities of the scheduling tool determine exactly what functionality can be automated. Figure 4. Batch processing flow chart Run Success No Yes Run Halts Batch Scheduler Log File Recorded in Error Batch Job A Execute Job Halts Batch Scheduler Fatal Warning Fatal or Yes Error Warning No (etc.) Batch Job B Execute Scheduler Initiates Batch 14 Job Scheduling The scheduling tool initiates all batch runs. If the run does not begin as scheduled, the tool halts the run and records an error in the error log。 Operations Framework (MOF). The guide assumes that the reader is familiar with the intent, background, and fundamental concepts of MOF as well as the Microsoft technologies discussed. An overview of MOF and its panion, Microsoft Solutions Framework (MSF), is available in the MOF Service Management Function Overview guide. This overview guide also provides abstracts of each of the service management functions defined within MOF. Detailed information about the concepts and principles of each of the frameworks is also available in technical papers available at 3 Job Scheduling Overview Job scheduling involves the continuous anization of jobs and processes into the most efficient sequence, maximizing system throughput and utilization to meet service level agreement (SLA) requirements. Job scheduling is closely tied to service monitoring and control and to capacity management. Job scheduling entails defining: ? Job schedules. The workloads are broken down into time periods (daily, weekly, monthly, annually) and jobs are scheduled for execution according to business needs, length of job, storage requirements, and associated dependencies. ? Scheduling procedures. Schedules are set up and maintained, conflicts and problems pertaining to scheduling are managed, and special needs (such as asneeded jobs) are acmodated. ? Batch processing. Jobs are executed according to the work schedule, run priority, and job dependencies. Batchprocessing procedures include: ? Job documentation ? Hardware instructions (for example, tape units, data cartridge units, and printers) ? Console operations ? Control checks ? Problem management Goal and Objectives The goal of job scheduling is to ensure the successful execution of batch processes at a time that minimizes the impact on interactive users of system resources. The main objectives of job scheduling include monitoring, analysis, tuning, and implementation of batch runs. 6 Job Scheduling Scope Job scheduling ensures the successful execution of batch runs while minimizing the impact on users of system resources: ? Job scheduling establishes batch schedules and maintains batch job standards, ensuring that operational level agreements (OLAs), service level agreements (SLAs), and resource thresholds are not breached. ? Job scheduling manages, tests, and implements changes to the schedule via change management, taking account of changes to the scheduling calendar (holidays, for example) and the targets detailed in the OLAs in place. ? Job scheduling monitors and controls the batch schedule, ensuring that batch runs do not affect the live service. It monitors the oute of successful or unsuccessful batch jobs and establishes alert, error, and event management processes. It also identifies baselines for job scheduling performance. ? Job scheduling implements asneeded requests, ensuring that the existing schedule is not adversely affected. It is responsible for the analysis and correction of batch process errors, implementing