13.07.2015 Views

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 16: OperationsBackground (Batch) JobsRegularly scheduled jobs are background jobs that will run on a schedule (for example,daily at 11:00 a.m., Sundays at 5:00 a.m., etc.)Regularly schedule jobs are run to: Collect performance statistics Populate an information system, such as the Special Ledger. Generate a report Generate output for an outbound interface Process an inbound interface Perform housekeeping tasks, such as deleting old spool requestsThe job is scheduled like any other background job, but with a few additionalconsiderations: Create a special user ID to be used only for scheduling batch jobs, such as BATCH1.The reason for special user IDs is to keep scheduled jobs independent of any user. Thisway, when a user leaves the company, the jobs will not fail when the user ID is locked,shut down, or deleted. Consider multiple-batch user IDs when batch jobs are scheduled by or for differentorganizations or groups. This method has the disadvantage of having to managemultiple accounts. For example: BATCH1 System Jobs BATCH2 FinanceBATCH3 Accounts PayableBATCH4 WarehouseBATCH5 Material Planning/InventoryFor more information on performance, see 16–5.These background jobs must be run regularly to perform administrative tasks, such as: Deleting old spools Deleting old batch jobs Collecting statistics16–4Release 4.6A/B

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!