Solution : https://service.sap.com/sap/support/notes/7140 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues with spooler functionality, particularly when managing large printed lists which may not print fully or at all due to a size limit of 2GB. The document delineates errors such as program termination, database overflow, and disk space limitations on spool requests. To mitigate these, SAP recommends adjusting profile parameters like 'rdisp/max_wp_runtime' and 'rspo/store_location', changing COMMIT WORK, enlarging database segments, and ensuring sufficient disk space. Additionally, unexpected spooler behaviors on remote systems and specific operating system configurations are highlighted, with troubleshooting steps provided for each scenario.
Key words :
=> profile parameter rspo/store_location = gthis means data, => enlarge tablespace=> profile parameter rspo/store_location = gdata, => examine profile parameter rspo/to_host/datafile, => examine profile parameter rsts/file/root/, => examine profile parameter rspo/host_spool/print, /usr/sap/c11/dbvmgs00/work/stderr2, /usr/sap/c11/dbvmgs00/work/dev_w8, => profile parameter rspo/store_location = dbdata, => profile parameter rdisp/max_wp_runtime=> install, stored indata base table tsp03
Related Notes :
| 19706 | Tuning the Spooler |
| 16513 | File system is full - what do I do? |