Job executionJobs 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. In Queue status If the job’s status is In Queue, you can use the Job Scheduler BSE Service to start the job. You must ensure the Job Scheduler BSE Service is running before it can activate any job. Jobs with status In Queue can be monitored using the Scheduled Jobs (ttaad5120m000) session. This session shows an overview of all scheduled jobs across all companies and displays the this information:
Jobs started by the Job Scheduler BSE Service are carried out by a separate bshell. This bshell runs in the company of the job, using the settings of the LN user who created the job. For more information about BSE Services, see chapter XXX. Job Daemon In case BSE Services are not used, you can use the Job Daemon to start the job. Ensure the Job Daemon is running before it can activate any job. The implementation of the Job Daemon depends on the operating system of the LN server:
When the Job Daemon runs, you can stop your bshell without any problem. The Job Daemon, and not your bshell, carries out the job. To run a job for multiple companies, you must start a Job Daemon for each company. Free status If the job’s status is Free, you can start the job in the following ways:
Activate Job (ttaad5203m000) If you start the job before the time and date of execution, the job’s status changes to Waiting. While the job is being carried out, the job’s status changes to Running. Because the bshell of the user who starts the job carries out the job, the user cannot quit the bshell until the job is finished. If a job that belongs to more than one company must be started, you must use the Change Company command on the Menu browser’s Option menu to switch to the required company. The rc.startjob shell command (UNIX) You can also start the job with the UNIX ${BSE}/etc/rc.startjob shell script. For this purpose, you must enter this syntax at the UNIX prompt: ${BSE}/etc/rc.startjob [job name]. You can include the rc.startjob script in a UNIX user job scheduler (crontab), which can automatically start jobs. For this purpose, some UNIX variables must be defined in the shell script. For more information, see the shell script. To run a job for multiple companies, you must create a unique version of rc.startjob for each company. The startjob.bat batch file (Windows) If LN runs on a Windows server, you can also start the job with the startjob.bat batch file. To start a job, specify this syntax at the Windows command prompt: startjob.bat [job name] Before you can specify this command, you must run the fillenv.bat batch file to set the LN environment variables. To automate the execution of jobs, you can run startjob.bat with a scheduler. To run a job for multiple companies, you must create a unique version of startjob.bat for each company. Job status This table shows the statuses a job can have during its life span:
If required, you can cancel a job that the Job Daemon starts, for example, to change the job’s basic job data. To cancel the job, use the Job Data (ttaad5500m000) session. On the Zusatzoptionen menu, click Cancel Job. If you cancel a job, the current session of the running job is carried out, but the following sessions in the job will not be started. The job’s status changes from In Queue to Canceled. To restart a canceled job, you must release the job to change the job’s status to In Queue or Free. To temporarily stop a job, start the Job Data (ttaad5500m000) session. On the Zusatzoptionen menu, click Block Job.
| |||||||||||||||||||