| # Job management You can use ERP Enterprise ’s job management, for example, to schedule jobs at non-peak hours to improve the overall system performance in a heavily loaded environment. A job consists of one or more sessions and/or shell commands that run without user interaction. The sessions and/or shell commands in a job can be started while you are not logged on to ERP Enterprise. You can schedule jobs to start processes periodically, at a defined interval, or immediately. Typically, you use ERP Enterprise job management for print and processing sessions. Job data To create a job, you must specify basic job data and link sessions and/or shell commands to the job. In the basic job data you specify whether the job is periodical. For periodical jobs, you specify how the job will be scheduled. Shared job data tables Typically, each company stores its own basic job data. As a result, a job runs for a particular company. However, in a job, you can also run sessions in more than one company. You can only run sessions in multiple companies if the job data tables of the involved companies are physically mapped on one main company. Job execution Jobs can be started in multiple ways. The job’s status defines how you can start the job. You can start the job if the job’s status is In Queue or Free. Job history When the execution of a job stops, for example because the job is completed successfully, or because of a runtime error, information is written to a history log. The job history contains information such as the date and time of execution, the reason why the job has ended, and why the session in the job has ended. |