Solution : https://service.sap.com/sap/support/notes/108799 (SAP Service marketplace login required)
Summary :
As of SAP R/3 Release 4.0A, it's possible to configure multiple spool work processes per instance, optimizing the server landscape for processing print requests and managing spool tasks. Key activities include handling print requests, managing host spool system interactions, monitoring spool database for overflow issues, and managing output requests during spool server shutdowns. From Release 4.6A, spool work processes also manage the deletion of obsolete spool requests, configurable via Transaction SPAD. Practical guidelines suggest configuring an additional spool work process to handle peak loads efficiently while ensuring smooth output request processing. Management tasks are distributed, with specific work processes dedicated to global, local, or particular functions like link checks or host spool demands, thereby preventing blockages and ensuring reliable operation across different server tasks.
Key words :
host spool link check global management actions scanning, lost requests reassigning requests deleting obsolete requests, output requests local management actions requesting, reserved spool work process exists, -reserved spool work process accepts, additional spool service load arises, profile parameter rdisp/wp_no_spo_fro_max, lengthy host spool demands, additional key words reservation, spool work process receives
Related Notes :
| 923610 | Memory parameter recommendations for banking systems |
| 351492 | Setting up frontend printing as of Release 4.6B |
| 65109 | Long delays when printing during overload |
| 39412 | How many work processes should be configured? |