Jobs typically send notice of their results via the event mechanism, and system error events are automatically triggered if a problem occurs.
Job control is similar to the same mechanism used so successfully on mainframes for many years.
It can be used for any function which takes more time than is practical for an interactive session, such as a complex calculation, a data load from a legacy system, or the running of a group of long reports or analyses. A job can also have parameters associated with it to control it's functions, much like arguments to a method. Session EJB's, allowing business logic to be developed with all of the advantages of Enterprise JavaBeans. Job Order Jobs are handled in priority order, and a job can be suspended and it's priority changed even once it has begun running. Jobs frequently trigger event notifications when they are complete or when problems occur.