Transaction SM50 (process overview) shows that the spooler
work process is working for a user "SAPSYS".
- 1. There is an internal "user", "SAPSYS". It is used in several places in the system when no real user is the trigger:
- a) batch scheduler
- b) modules called via RFC
- c) Self-management of the spool work process
- d) Wait states in the spooler work process when waiting for confirmation messages from the host spooler. If nothing else is going on, but requests are still open at the host spooler, the system waits for five seconds at a time up to twelve times (because the spooler work process does not report back to the task handler during this time, it cannot differentiate this from a real job, and displays it in the process overview).
- 2. You will see "SAPSYS" in the process overview in cases (1a), (1d) and
and, if spool requests have been generated, in state (1b).
----
Key word: Spooler
No comments:
Post a Comment