FAQ: Background Jobs
1. Q: Can I reserve background work processes for individual applications or users?
A: No. Reservation is only possible for job class A
2. Q: Can I assign priorities (job classes) in the function modules 'JOB_OPEN', 'JOB_SUBMIT' and 'JOB_CLOSE'?
A: No. If jobs of the class A or B must be scheduled automatically, you can do this as follows: You schedule a job of the required class and set it to start periodically.
3. Q: Can I influence the priority of the jobs, regardless of the job class?
A: In distributed systems via a well-designed distribution on the servers - see Note 24092.
4. Q: Can I save job logs in the database (analogously to the spool)?
A: There is no such option in the standard.
5. Q: What happens if the background work process needs to be switched and a job is running in that workprocess?
A: The instance kernel waits for the job to finish before the background workprocess is switched to an alternate type. Jobs are never terminated by the R/3 system to make way for an op-mode switch.
6. Q: Can job definitions be transported into other clients or systems?
A: No. Job definitions contain system specific parameters (target host, user, program, operation mode, ...). Therefore it wouldn't make sense to develop a transport tool. .
For similar reasons, copying a job across clients is not foreseen. The following trick, however, is possible: Login to the target client (the one, where the job is to be copied to). The user must have job administrator authorizations. Then using transaction SM37 all jobs in all clients can be displayed. With the "Job > Copy" option a job can now be copied from the source client (only steps, no start time).
7. Q: Does the user receive a message if their job is cancelled?
A: No, but as of Release 4.x, cancelled jobs can trigger an alert in RZ20 which allows you to react correspondingly.
8. Q: How can I set that a periodic job is to be deleted after a maximum waiting time?
Example: A job is to run every 15 minutes after 08:00 hours. Automatic deletion is to apply for each of these jobs if it has to wait more than 20 minutes for execution.
A: Schedule the job with the following parameters: Start time 08:00 hours, No start after 08:20 hours, period 15 minutes. For each job, move the earliest and latest start time by 15 minutes in each case.
9. Q: How can I set that a periodic job no longer runs as of a certain date?
A: This is not provided in the standard system. It can, however, be implemented with the function modules 'JOB_OPEN', 'JOB_SUBMIT' and 'JOB_CLOSE' (see Note 4751).
10. Q: Can I restrict the number of jobs that a user can schedule in order to avoid that a single user uses all work processes?
A: No, a user can either schedule/releases job or he cannot.
11. Q: What do I do if an error occurs?
A: See Note 37104