6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 16: OperationsBackground (Batch) Jobs Daylight savings time endsThis period creates a problem where a one-hour period of time repeats itself. Forexample, at 3:00 a.m., the clock resets back to 2:00 a.m. This time period will occur twice.One way to avoid problems when daylight savings time is switched on and off is to useUTC (formerly known as GMT) as your master clock. If you are in a U.S. state that does notuse daylight savings time, such as Hawaii, it is not a concern.See the following SAP notes: 7417 - Changing to daylight savings time and back 102088 - End of daylight savings time: the “double” hourBackground jobs are used for the following reasons: Users have the flexibility of scheduling jobs when they are not in the office. The program can be run without locking a user session. Jobs that run for a long time would time out if run online. The job class determines the start priority of the job.For example, a “class A” job would start before a “class B” job, and a “class B” job wouldstart before a “class C” job. Once started, all job classes have equal priority.A “class A” job will not take processing resources away from a “class B” job to finishfaster. Jobs in the start queue do not affect running jobs.A “class A” job in the start queue will not replace a currently running “class C” job.Avoid “playing priority games” with the job class. If you make every job a “class A” job,there is no priority, because every job will be at the same priority level.The recommended method is to assign all jobs to job “class C”. The exceptions to thisrecommendation are those jobs that need the priority. This priority increase should beproperly justified.A batch job may require that a variant be created to execute the job.16–8Release 4.6A/B